Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
running the same VMs between different hypervisors is more than just taking the image, same as moving the physical hard drive between different physical machines will mean the installed OS will have problems with drivers.
Interesting article, the following paragraph suggests that maybe the hyper-v VM can actually be opened directly:
So obviously the next thing I thought of is that if kvm-img supports vpc as a file format, perhaps KVM can boot it. Well it can. So if you are so inclined you could simply copy the file from the Hyper-V server to the KVM server and start it (and uninstall the Integration Components if applicable) I plan on investigating the perfomance implications of this choice though that is not part of this article.
According to this article the file format on Hyper-V is actually vpc (.vhd file).
I tried to create a new VM in VMM and pointed it towards an existing .vhd file but encountered the problem that vpc is not listed as a file format in VMM, that only includes raw/qcow2/vdi/vmdk not vpc.