Re: [PATCH 5/5] [OPTIONAL] qemu: allow save and managedsave on guests marked as autodestroyable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx <mailto:pkrempa@xxxxxxxxxx>>
>>
> 
> [...]
> 
>>
>> 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

Attachment: signature.asc
Description: OpenPGP digital signature

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]