similar to: External snapshot issue addendum

I have used virsh snapshot-create-as <VM name> <snapshot name> "<snapshot description>" --diskspec "vda,snapshot=external,file=/path/to/external-snapshot" --disk-only --atomic to create an external snapshot of a running VM. I followed it with virsh blockpull <VM name> --path /path/to/external-snapshot and monitored it until done.

Hi,all,i am using libvirt to manage my vm,in these days i am testing the libvirt snapshot ,but meet some problem: the snapshot was created from this command: snapshot-create-as win7 --disk-only --diskspec vda,snapshot=external --diskspec hda,snapshot=no but when i tried to revert from the snapshot which created from the above command ,i got error below: virsh # snapshot-revert win7

Eric Blake <eblake@...> writes: > > On 05/27/2012 06:39 PM, xingxing gao wrote: > > Hi,all,i am using libvirt to manage my vm,in these days i am testing > > the libvirt snapshot ,but meet some problem: > > > > the snapshot was created from this command: > > snapshot-create-as win7 --disk-only --diskspec > > vda,snapshot=external --diskspec

On Sun, Mar 15, 2015 at 10:28:30PM +0800, Yitao Jiang wrote: > Hi,guys > I wanna to get the disk snapshot size, but found nothing libvirt commands > related,except qemu-img. > I create two disk snapshots, but nothing return its' size The below does not seem like snapshots. They're *internal* qcow2 snapshots (original and delta are on the same file). A quick example of disk

Hi, I am wondering if the --print-xml option is working correctly. The output for two snapshot-create commands are the same, even though the first one includes additional options (no-metadata and atomic). I want to use the generated XML to create a snapshot via a perl script, and Sys::Virt only seems to support snapshots using a XML description of the arguments. timos@cerberus:~$ sudo virsh

Eric Blake <eblake@...> writes: > > On 05/27/2012 06:39 PM, xingxing gao wrote: > > Hi,all,i am using libvirt to manage my vm,in these days i am testing > > the libvirt snapshot ,but meet some problem: > > > > the snapshot was created from this command: > > snapshot-create-as win7 --disk-only --diskspec > > vda,snapshot=external --diskspec

On 09/11/2015 06:45 AM, Jérôme wrote: > AFAIU, live backups using libvirt may be done thanks to blockcommit as > explained here on the wiki [2]. > > -> Considering our use case, is this the recommended way? Yes, using active block-commit is the ideal way to perform a live backup. > > Assuming yes, here is the plan. > > I wrote a script that does > > #

Hello, I have virtual machines running with a ceph storage backend. When creating an external qcow2 snapshot with a libvirt version without support for the new object secret passing, the backing file info would list the ceph secret in plain,e.g. # virsh snapshot-create-as vm-123 --no-metadata --disk-only --diskspec sda,file=/var/lib/libvirt/qemu/snapshot/vm-123-wrapper.qcow2 # qemu-img info

Hi (Eric?), A couple of questions while using the 'virsh blockpull' Summary: 1] Created snapshots this way: base<-snap1<-snap2<-snap3 (online, external snapshot --disk-only) 2] I did a 'virsh blockpull' from snap2 into snap3 3] Next, did another 'virsh blockpull' from snap1 into snap3 - Here, 'qemu-img info /path/to/snap3' shows its backing file

Hi, Can you try this command: virsh snapshot-delete serv1r2 snap --metadata On Wed, Aug 23, 2017 at 4:41 PM, Doug Hughes <doug.hughes@keystonenap.com> wrote: > I'm not sure how this snapshot got created, but, I cannot delete it, and > its presence prevents me from creating other snapshots. I don't know if it > was created by a command gone amok or something else. >

I had the same problem yesterday. I found the solution from this article https://kashyapc.fedorapeople.org/virt/lc-2012/snapshots-handout.html. According to the article it deletes the tracking metadata by libvirt. You can physically remove the snapshot now that there is no tracking stream data by libvirt On Wed, Aug 23, 2017 at 4:56 PM, Doug Hughes <doug.hughes@keystonenap.com> wrote:

On 04/10/2014 04:38 PM, rolf wrote: >> [Can you convince your mailer to wrap long lines? It makes it easier >> for other readers] > > I’ll try and keep the lines short. I don’t see any obvious setting to change the wrap. Thanks for being accommodating; this was indeed easier to read (alas, many web mailers these days lack settings for automatic wrap, so I end up whacking the

Hi, a small update on this. We have migrated the virtualized host to use the virtio drivers and now the drive performance is improved so that we can see a constant transfer rate. Before it used to be the same rate but regularly dropped to a few bytes/sec for a few seconds and then was fast again. However we still observe that the following fails regularily: $ virsh snapshot-create-as --domain

Hi. I'm following here a conversation that was initiated on Kashyap's website [1]. We have a server we use as a host for virtual machines using KVM (virt-manager used for VM creation) and we would like to setup VM backups. Basically, we're thinking of a backup schedule like "keep 7 daily and 4 weekly backups". We'd rather not shutdown the VM every day so live backups

On 08/07/2015 09:53 AM, Silver Sky Soft Services, Inc. wrote: > Hi, > I'm trying to create a snapshot on a specific disk by using diskspec > option. However, libvirt/virsh seems to ignore it and takes a snapshot of > all disks. Am I using this option incorrectly? > > In below examples, I'm trying to snapshot only vdb. However even vda is > getting snapshotted

Hi, different day, same issue.. cronjob runs and fails: $ virsh snapshot-create-as --domain domain --name backup --no-metadata --atomic --disk-only --diskspec hda,snapshot=external error: failed to pivot job for disk hda error: block copy still active: disk 'hda' not ready for pivot yet Could not merge changes for disk hda of domain. VM may be in invalid state. Then running the

Hi, I'm trying to create a snapshot on a specific disk by using diskspec option. However, libvirt/virsh seems to ignore it and takes a snapshot of all disks. Am I using this option incorrectly? In below examples, I'm trying to snapshot only vdb. However even vda is getting snapshotted regardless of diskspec. Is this a known issue? I'm on CentOS 7.1, libvirtd (libvirt) 1.2.8, virsh

On Mon, Aug 14, 2017 at 08:42:24 +0200, Dominik Psenner wrote: > Hi, Hi, > > a small update on this. We have migrated the virtualized host to use the > virtio drivers and now the drive performance is improved so that we can see > a constant transfer rate. Before it used to be the same rate but regularly > dropped to a few bytes/sec for a few seconds and then was fast again.

Hi, i just realized that i have a guest with two disks. What would be the appropiate way to snapshot both of them ? virsh snapshot-create-as --domain guest --diskspec vda,file=/path/to/snapshot/snapshot1.qcow2 -disk-only --atomic && virsh snapshot-create-as --domain guest --diskspec vdb,file=/path/to/snapshot/snapshot2.qcow2 -disk-only --atomic or virsh snapshot-create-as --domain

My negligence。 -- James Iter 在 2018年3月22日 星期四，下午11:02，Dominik Psenner 写道： > I believe that Your mail went to the wrong recipient. As far as I'm > concerned it should have been sent to the libvirt-users mailing list, > shouldn't it? > > > On 2018-03-22 15:55, James Iter wrote: > > Thank your reply. > > I found the method. > > Now, I sharing