Displaying 4 results from an estimated 4 matches for "virdomainsnaphostcreatexml".
2014 Oct 14
3
drive-backup command permission denied.. and need some clarification
Hi
* Trying to get drive-backup command, getting permission denied. :(
sudo virsh qemu-monitor-command --hmp my-instance --cmd
drive_backup drive-virtio-disk0 /tmp/foo.vda.img
Looks like apparmor issue. What can I modify to make this work ?
* Couple of other questions
drive-backup :
* The doc seems to claim that it gives a point in time copy
of
2014 Oct 15
2
Re: drive-backup command permission denied.. and need some clarification
...t;
> I have not yet had time to look into wiring up libvirt to drive the
> command; the libvirt solution will probably have the optional ability to
> quiesce the file system around the snapshot event, similar to the
> existing --quiesce flag of virDomainSnapshotCreateXML (in fact,
> virDomainSnaphostCreateXML might even BE the interface we use to wire up
> the qemu drive-backup command)
>
> > * Suppose I have base <-- sn1 --<-- sn2 (QEMU active) . does
> > it take data from sn2 only ? or base+sn1+sn2 .. full drive and creates
> > a new qcow2 sparse file.
>...
2014 Oct 14
0
Re: drive-backup command permission denied.. and need some clarification
...o not see any options here.
I have not yet had time to look into wiring up libvirt to drive the
command; the libvirt solution will probably have the optional ability to
quiesce the file system around the snapshot event, similar to the
existing --quiesce flag of virDomainSnapshotCreateXML (in fact,
virDomainSnaphostCreateXML might even BE the interface we use to wire up
the qemu drive-backup command)
> * Suppose I have base <-- sn1 --<-- sn2 (QEMU active) . does
> it take data from sn2 only ? or base+sn1+sn2 .. full drive and creates
> a new qcow2 sparse file.
If I understand the qemu comma...
2014 Oct 15
0
Re: drive-backup command permission denied.. and need some clarification
...not yet had time to look into wiring up libvirt to drive the
>> command; the libvirt solution will probably have the optional ability to
>> quiesce the file system around the snapshot event, similar to the
>> existing --quiesce flag of virDomainSnapshotCreateXML (in fact,
>> virDomainSnaphostCreateXML might even BE the interface we use to wire up
>> the qemu drive-backup command)
>>
>>> * Suppose I have base <-- sn1 --<-- sn2 (QEMU active) . does
>>> it take data from sn2 only ? or base+sn1+sn2 .. full drive and creates
>>> a new qcow2 sp...