>
> This would work for current versions of qemu, but may not work in the
> future (as HMP does not guarantee stable output) - parsing QMP output
> would be more reliable. Furthermore, the 'qemu-monitor-command' is
> intentionally unsupported, although this particular use is safe because
> it does
On 01/14/2014 08:13 PM, Gao Yongwei wrote:
>>
>>
>>>
>>> So, if I'm not mistaken, looks like the only way to test for the support
>> in QEMU is to actually
>>> request a snapshot and see what happens.
>>> Is this right?
>>
>> Unfortunately true for the moment.
>>
> Hi, does this command can help wi
>
>
> >
> > So, if I'm not mistaken, looks like the only way to test for the support
> in QEMU is to actually
> > request a snapshot and see what happens.
> > Is this right?
>
> Unfortunately true for the moment.
>
Hi, does this command can help with you?
virsh qemu-monitor-command vmname --hmp
On 01/13/2014 04:57 AM, Francesco Romani wrote:
>
> After reading from the docs, it seems that libvirt doesn't reports yet this
> information about
> the hypervisor in the capabilities XML: http://libvirt.org/formatcaps.html
>
> a quick test against libvirt 1.1.3 (qemu 1.6.1) on Fedora 20 seems
Hi everyone,
Using the QEMU hypervisor, when a live disk snapshot is requested through
libvirt,
the request can fail if the underyling qemu binary lacks the snapshotting
support.
In python, we have something like
libvirtError: Operation not supported: live disk snapshot not supported with
this
