Yeah, something like that would be handy. From: matt <[email protected]<mailto:[email protected]>> Date: Wednesday, May 13, 2015 10:29 AM To: "Daniel P. Berrange" <[email protected]<mailto:[email protected]>> Cc: Matt Van Winkle <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [Openstack-operators] Venom vulnerability
honestly that seems like a very useful feature to ask for... specifically for upgrading qemu. -matt On Wed, May 13, 2015 at 11:19 AM, Daniel P. Berrange <[email protected]<mailto:[email protected]>> wrote: On Wed, May 13, 2015 at 03:08:47PM +0000, Matt Van Winkle wrote: > So far, your assessment is spot on from what we've seen. A migration > (if you have live migrate that's even better) should net the same result > for QEMU. Some have floated the idea of live migrate within the same > host. I don't know if nova out of the box would support such a thing. Localhost migration (aka migration within the same host) is not something that is supported by libvirt/KVM. Various files QEMU has on disk are based on the VM name/uuid and you can't have 2 QEMU processes on the host having the files at the same time, which precludes localhost migration working. 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 :| _______________________________________________ OpenStack-operators mailing list [email protected]<mailto:[email protected]> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
