On Wed, Jan 09, 2013 at 02:23:50PM +0200, Vangelis Koukis wrote: > Hello, > > I'd like to ask a few questions about the way migrations work in KVM > among different emulated machine types and different versions of the > qemu-kvm package. I am sending to both the kvm@ and qemu-devel@ lists, > please redirect me if I was wrong in doing so. > > In a nutshell: while trying to live-migrate a VM on ~okeanos [1], we > see VM migrations fail silently if going from kvm 1.0 to kvm 1.1. > The source VM is frozen, "info migrate" on the source monitor reports > success, but the VM is dead upon arrival on the destination process. > Please see [3] for the exact package versions for qemu-kvm we have > tested with. > > Migration works if the destination kvm has been started with the same > machine type as the source VM, e.g., using "-M pc-1.0" specifically on > the destination, when migrating a pc-1.0 machine from kvm 1.0 to > kvm 1.1. > > How does the machine type specified with -M work in the case of > migrations? Are migrations expected to fail if the machine type is > different between source and destination process? If yes, shouldn't KVM be > able to detect this and abort the migration instead of failing silently? When doing migration, the fundamental requirement is that the guest OS visible machine ABI must not change. Thus there are three key things to take care of when launching QEMU on the migration target host. - The device PCI/USB addresses must be identical to the source - The machine type must be identical to the source - The CPU model must be identical to the source If you don't follow those requirements, either QEMU or the guest OS or both will crash & burn during migration & you get to keep both pieces :-) > Regarding different package versions of qemu-kvm, it seems migrations do > not work from source 0.12.5 to any other version *even* if -M pc-0.12 is > specified at the incoming KVM process. For versions >= 1.0 everything > works provided the machine type on the destination is the same as on the > source. Some older versions of QEMU were buggy causing the machine type to not correctly preserve ABI. > Our goal is to patch Ganeti [2] so that it sets the destination machine > type to that of the source specifically, ensuring migrations work > seamlessly after a KVM upgrade. Is there a way to retrieve the machine > type of a running KVM process through a monitor command? IIRC there is not a monitor command for this. The general approach to dealing with migration stability should be to launch QEMU with a canonical hardware configuration. This means explicitly setting a machine type, CPU model and PCI/USB devices addresses upfront. NB you should not use 'pc' as a machine type - if you query the list of machine types from QEMU, it will tell you what 'pc' corresponds to (pc-1.2) and then use the versioned type so you have a known machine type. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
