-
Hi, iam testing the vmware-kvm-feature in our testing-environment right now. We now have a Cloudstack 4.19.2.0-Installation with zwo Zones: 1x VMware (2 Hosts) + 1x KVM (1 Host) Everything generally seems to work and we have all functionalities we are used to. But migration of a vmware-vm to kvm unfortunately does not finish successfully atm. I can monitor the export in vcenter and after it i can follow virt-v2v-conversion via cloudstack-agent-log. But in this process the failure happens. I suspect an virt-v2v-error 'nbdcopy command failed' to be responsible for the failing migration. See logs and Screenshots attached. Any suggestions on this? Versions Cloudstack-Agent-Log: |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
Hello, Do you have the package "libnbd-bin" installed? |
Beta Was this translation helpful? Give feedback.
-
You need to export your NFS volumes with option no_root_squash, it's in the docs. |
Beta Was this translation helpful? Give feedback.
-
After you modified the superuser set on NetApp are your mounts still with nobody nogroup? We are using NetApp as well and have superuser set to any. Files as observed from the hypervisors are mounted as nobody nobody. We recently had some issues when deploying a new zone with the permissions on the SVM disk file that was copied to the new zone. Just trying to figure out if the issue was storage related as other templates were copied with no errors. |
Beta Was this translation helpful? Give feedback.
Ok, this is a more complicated one (although it seems so easy to achieve):
Its Netapp Storage and since the no_root_squash option isnt supported directly, according to docs you can reach it with special export settings...
My export ist setup like that.
An additional Problem here is client and server defaults to NFSv4 and this adds a check for matching domain-strings, see here:
https://www.reddit.com/r/netapp/comments/175ppl1/why_nfs_is_owned_by_nobodynobody/
and here
https://www.youtube.com/watch?app=desktop&v=UfaJTYWSVAY
I can see the nss-error in my kvm-host-log.