On Thu, Jun 23, 2011 at 06:52:47AM -0600, Eric Blake wrote: > On 06/23/2011 04:58 AM, Daniel P. Berrange wrote: > > I am building an application which uses KVM to run specific tasks, rather > > than as a general purpose guest OS. I want to ensure that when the app > > exits, the guest goes away too. To enable this, this series introduces > > the concept of 'autokill', whereby a guest is forcably destroyed when > > the virConnectPtr that launched it closes. This also lets us fix a long > > standing problem with migration leaving an unkillable guest > > Cool! > > How does this interact with migration? If a domain is currently marked > autokill on the source, should that mean that attempts to migrate it are > forbidden (since the connection to the source would end up being useless > after the migration, at which point the connection is gone and autokill > should kick in)? That's a good point. I reckon we should forbid migration and save/restore for such guests. 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 :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list