[libvirt] [PATCH 0/3] Enable automatic kill of running guests

Eric Blake eblake at redhat.com
Thu Jun 23 12:52:47 UTC 2011


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)?

-- 
Eric Blake   eblake at redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 619 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20110623/a6e554e0/attachment-0001.sig>


More information about the libvir-list mailing list