On 09/30/2012 12:20 PM, Shawn Starr wrote: > Hello, > > I noticed some issues migrating a VM > > 1) I had to have ssh key authentication exchanged or it would refuse to > connect tunneled to the remote libvirtd server Correct - per http://libvirt.org/migration.html, under tunnelled migration, there is this warning: The destination URI must be reachable using the source libvirtd credentials (which are not necessarily the same as the credentials of the client in connecting to the source). There has also been a recent addition of a new qemu+libssh2://host/system URI, with better credential handling through libvirt APIs, although I'm not sure if the new URI is capable of handling the authentication exchange as part of the libvirt migrate command. > > 2) When it attempts to finish live migrating the VM it fails saying it can't > find the domain on the remote libvirtd server host Can you print the exact error message it gave? [Oh, I see you did that below] > > However, if I run the command again to migrate, it DOES migrate the VM over, however the Windows guest is not usable, cant type/use mouse, but i can see the VM display fine. I can gracefully shut the VM down from virt-manager and > I see the VM shut down gracefully from display attached via spice. As for the mouse not being usable after migration, that sounds more like an issue in qemu; you might get better results asking on a qemu list, and/or upgrading to newer qemu on both source and destination machines before attempting another migration. > LIBVIRT_DEBUG=1 virsh --debug=4 migrate --verbose --live --tunnelled --p2p Windows_7 qemu+ssh://root@172.18.2.3/system > > Output: > > 2012-09-30 17:59:15.751+0000: 24710: debug : virObjectUnref:135 : OBJECT_UNREF: obj=0x26693b0 > 2012-09-30 17:59:15.751+0000: 24708: debug : virDomainFree:2281 : dom=0x2669e70, (VM: name=Windows, uuid=41562d70-d0a8-25bc-10ec-a3dc46b3d258) > 2012-09-30 17:59:15.751+0000: 24708: debug : virObjectUnref:135 : OBJECT_UNREF: obj=0x2669e70 > 2012-09-30 17:59:15.751+0000: 24708: debug : virObjectUnref:137 : OBJECT_DISPOSE: obj=0x2669e70 > 2012-09-30 17:59:15.751+0000: 24708: debug : virDomainDispose:225 : release domain 0x2669e70 Windows 41562d70-d0a8-25bc-10ec-a3dc46b3d258 > 2012-09-30 17:59:15.752+0000: 24708: debug : virObjectUnref:135 : OBJECT_UNREF: obj=0x26693b0 > 2012-09-30 17:59:15.752+0000: 24708: debug : virFileClose:72 : Closed fd 9 > 2012-09-30 17:59:15.752+0000: 24708: debug : virFileClose:72 : Closed fd 10 > error: Domain not found: no domain with matching name 'Windows' It sounds like this particular migration attempt hit a case where qemu failed to migrate, so libvirt aborted the migration (perhaps with a confusing message, though). -- Eric Blake eblake@xxxxxxxxxx +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list