Virtv2v with libnsl required by ovftool from VMware for migration causes cloudstack agent to crash

[chunkyen]

Hi I am trying out a migration from VMware to KVM cluster managed by cloudstack. The requirements is to install virt-v2v and ovftool. For ovftool specifically, I need to install libnsl as a dependency on Alma Linux 8 . However after doing this, a restart of the agent will cause the agent to crash. It will try to restart but crash again in an endless loop.
After removing the libnsl, the agent can start normally again.
Is there a way to workaround this issue?
Thank you

[weizhouapache]

I guess the issue is same as #11604 (comment)

[chunkyen]

Hi, can you point to me to the actual fix as the thread is pretty long and I cannot find the fix. So virt-v2v is actually causing the agent restart loop and not the libnsl?

[weizhouapache]

@chunkyen
the fix is a db change:

insert into host_details (host_id,name,value) values (xxx, 'host.uefi.enable', 'false');

[macdchsmba]

I also have experienced similar problem where host that was working fine the agent crashed after installing virt-v2v. Having read this post I applied the patch "insert into host_details (host_id,name,value) values (2, 'host.uefi.enable', 'false'); where 2 was my host ID. The agent still fails until virt-v2v is uninstalled. I tried to restart the management sever and the host, problem persists.

[weizhouapache]

I also have experienced similar problem where host that was working fine the agent crashed after installing virt-v2v. Having read this post I applied the patch "insert into host_details (host_id,name,value) values (2, 'host.uefi.enable', 'false'); where 2 was my host ID. The agent still fails until virt-v2v is uninstalled. I tried to restart the management sever and the host, problem persists.

@macdchsmba
Can you share some agent logs ?

[weizhouapache]

@chunkyen
which ACS version do you use ?

I tested with 4.20.2.0 and 4.22.0.0, I did not have issues when virt-v2v is installed and uefi.properties is/isn't present.
I believe #11610 has fixed it

[chunkyen]

Yes, I encountered this agent loop issue with virtv2v only on 4.21, upgrading to 4.22 solve this