On 29/03/11 21:13, Kenni Lund wrote:
Den 29/03/2011 15.41 skrev "David Sommerseth" dazo@users.sourceforge.net:
[...snip...]
Thanks a lot for good information!
The main problem is Windows guests, which easily chokes on hardware changes (forced reactivation of Windows or unbootable with BSOD). Each qemu-kvm version will behave differently, so moving from one major qemu-kvm version to another (0.1x -> 0.1y), will most likely change the virtual hardware seen by the guest, unless you have libvirt etc. configured to keep track of the guest hardware.
Do you know how to set up this? Or where to look for more details about this? I do have one Windows guest, and I can't break this one.
If it's only Linux guests, it should work fine when moving the guests between any recent Linux distribution with KVM. Of course, if you don't use libvirt or a similar management solution, the hardware in the guest will likely change, for example causing your MAC-addresses of your NICs to change, etc, when moving to a new KVM host.
It's all using libvirt already, so this should be pretty much the same.
kind regards,
David Sommerseth