[libvirt] [PATCH 5/5] [OPTIONAL] qemu: allow save and managedsave on guests marked as autodestroyable
Eric Blake
eblake at redhat.com
Tue Dec 11 16:13:47 UTC 2012
On 12/07/2012 06:27 AM, Peter Krempa wrote:
> On 12/07/12 14:19, Gao Yongwei wrote:
>>
>>
>> 2012/12/7 Peter Krempa <pkrempa at redhat.com <mailto:pkrempa at redhat.com>>
>>
>
> [...]
>
>>
>> I think, if a vm is marked has autodestroyed,then this means that we do
>> not need this vm again on next reboot.? if so,what's the reason for us
>> to save this vm?
>> if we want to save it,why we marked it has autodestroyed? ^ ^
>
> Well, autodestroy means that the guest is destroyed when the current
> libvirt connection (the connection that started the guest) is
> terminated. I don't see any reason why the user shouldn't be allowed to
> save the guest if he explicitly wishes to do so.
The decision to forbid saving autodestroy guests was an intentional
design decision. If you don't want the guest to survive a libvirtd
restart, then you should not need to save the guest for any other
reason, either. NACK to this patch.
--
Eric Blake eblake redhat com +1-919-301-3266
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/20121211/38566b9b/attachment-0001.sig>
More information about the libvir-list
mailing list