search for: diskspec

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 (...

...to snapshot for VM , to obtain VM incremental data，and use virsh blockcommit，qemu-img commit，qemu-img rebase to shorten snapshot chain. Details are as follows（when VM running state， we perform the following operations）: (1) the host machine control VM test virsh snapshot-create-as mix snap1 --diskspec vda,file=/tmp/mul/loop-mix-commit-rebase/snap1-mix.img --disk-only --atomic --quiesce virsh snapshot-create-as mix snap2 --diskspec vda,file=/tmp/mul/loop-mix-commit-rebase/snap2-mix.img --disk-only --atomic --quiesce virsh snapshot-create-as mix snap3 --diskspec vda,file=/tmp/mul/loop-mix-commit-r...

Hi everyone! I use the libvirt(version: 1.2.2) and QEMU(version: 2.2.1) to test qemu snapshot features: I tried virsh blockcommit when VM offline, the virsh blockcommit failed: the error messase as below: error: Requested operation is not valid: domain is not running when I start the VM, the virsh blockcommit work fine! my question is：we need

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 regardless of diskspec. Is this a known issue? > &gt...

...tart by indicating that I am not from a technical background, so please be gentle and patient with me. I am trying to get a snapshot from my virtual machines (vm) and the following command works for all of them bar one: # virsh snapshot-create-as --quiesce --no-metadata --domain myvm myvm-state --diskspec vda,file=overlay.qcow2 --disk-only --atomic The only exception is this one vm, which has two disks as two separete qcow2 files: vda and vdb. Vdb contains my nexcloud data, resides on a btrfs subvolume, and a daily snapshot of this subvolume is taken by a cronjob by the host machine. Therefore, I d...

On Fri, Feb 16, 2018 at 04:37:38PM +0100, Lentes, Bernd wrote: [...] > Hi, > > again thanks for your quick answer. I had a look on > https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit > and i liked it. I'm thinking of upgrading my systems to SLES 12 SP3. > With that i have qemu 2.9.1 and libvirt 3.3.0, so it should work. Yep. > Does this procedure

I scripted the creation of snapshots and it works fine. Now I'd like to run the script as non-root. virsh snapshot-create-as --domain hq-live-v01 \      --name snappy \      --diskspec vda,file=/var/lib/libvirt/images/hq-live-v01.snappy,snapshot=external \      --diskspec vdb,file=/var/lib/libvirt/images/hq-live-storage.snappy,snapshot=external \      --disk-only --quiesce --atomic This fragment creates the snapshots, but get created with mode 0600: -rw-------  1 qemu qemu     3...

...disks, vda and vdb. both are qcow2 local file. When guest running state. I want to take the vda snapshot of guest(just vda, no include vdb). but I met libvirt do snapshot for all disks of guest. About methods for follow: 1、 ``` bash virsh snapshot-create-as 8x0lbzvS --name sys_disk3 --disk-only --diskspec "vda,snapshot=external" ``` ``` result [root@10k03 ~]# ls -lh /opt/Images/*sys_disk3 -rw-------. 1 qemu qemu 194K 3月 20 23:27 /opt/Images/00d76a58-9637-4402-9739-21afd1246e06.sys_disk3 -rw-------. 1 qemu qemu 704K 3月 20 23:52 /opt/Images/8d582c1c-355a-4297-9434-2f2f562c77df.sys_disk3 `...

...separate calls to snapshot-create-as, so I can more easily manage the disk images. The code I have now is essentially as follows: virsh snapshot-create-as --domain "vmname" --name "snapshotname" --description "snapshot description" --disk-only --atomic --no-metadata --diskspec "vda" I run this command for each block device (e.g vda, vdb, etc). However, after running the above command (to only backup vda), I see that a snapshot has also been created for vdb. I tried running it with --print-xml, which gives this output: <domainsnapshot> <name>05-22...

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 guest --diskspec vda,file=/path/to/snapshot/snapshot1.qcow2 --diskspec v...

Thank you so much for your informative response. The man page of virsh did not include "snapshot=no" sub-option under the --diskspec option, but it is very intuitive. Thanks developers for their excellent work! Hakan Peter Krempa <pkrempa@redhat.com>, 6 Oca 2020 Pzt, 02:57 tarihinde şunu yazdı: > On Sun, Jan 05, 2020 at 17:21:52 -0600, Eyüp Hakan Duran wrote: > > Dear all, > > Please let me start by indic...

...#39;sheepdog' name='sheepvol1'/>       <target dev='vdb' bus='virtio'/> </disk> I have tried both options "external" and "internal". If I try to create external snapshot with virsh command: snapshot-create-as vps vpssnap --disk-only --diskspec vda,snapshot=no --diskspec vdb,snapshot=external I get an error: source for disk 'vdb' is not a regular file; refusing to generate external snapshot name. If I try the same command but with "internal" mode: snapshot-create-as vps vpssnap --disk-only --diskspec vda,snapshot=no -...

...#39;sheepdog' name='sheepvol1'/>       <target dev='vdb' bus='virtio'/> </disk> I have tried both options "external" and "internal". If I try to create external snapshot with virsh command: snapshot-create-as vps vpssnap --disk-only --diskspec vda,snapshot=no --diskspec vdb,snapshot=external I get an error: source for disk 'vdb' is not a regular file; refusing to generate external snapshot name. If I try the same command but with "internal" mode: snapshot-create-as vps vpssnap --disk-only --diskspec vda,snapshot=no -...

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 1338041515 --force error: unsupported configuration: revert to external disk snapshot not supported yet version: v...

...en 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 to you. > > When create snapshot, just add ’no’ value to the ’snapshot’ option with —diskspec. > > As below: > > > > ``` bash > > snapshot-create-as 8x0lbzvS --name sys_disk --disk-only --quiesce --atomic --diskspec "vda,snapshot=external" --diskspec "vdb,snapshot=no" > > ``` > > > > > > -- > > James Iter > &...

...-0500, Eric Blake wrote: > On 3/20/19 1:50 PM, Mircea Husz wrote: > > I scripted the creation of snapshots and it works fine. Now I'd like to run the script as non-root. > > > > virsh snapshot-create-as --domain hq-live-v01 \ > >      --name snappy \ > >      --diskspec vda,file=/var/lib/libvirt/images/hq-live-v01.snappy,snapshot=external \ > >      --diskspec vdb,file=/var/lib/libvirt/images/hq-live-storage.snappy,snapshot=external \ > >      --disk-only --quiesce --atomic > > > > This fragment creates the snapshots, but get created with...

...W dniu 29.05.2019, śro o godzinie 09∶55 +0200, użytkownik Peter Krempa napisał: > I understand, that it is not possible to make a snapshot of > > physical > > device, but it is enough for me to take snapshot of vda. How to > > force > > virsh to ignore sda ? > > --diskspec sda,snapshot=no now it works, thanks a lot! best regards Jarek

...alls to snapshot-create-as, so I can more easily manage the disk > images. The code I have now is essentially as follows: > virsh snapshot-create-as --domain "vmname" --name "snapshotname" --description "snapshot description" --disk-only --atomic --no-metadata --diskspec "vda" > > I run this command for each block device (e.g vda, vdb, etc). However, after running the above command (to only backup vda), I see that a snapshot has also been created for vdb. I tried running it with --print-xml, which gives this output: > <domainsnapshot> >...

Hi! I need to convert a KVM virtual machine from LVM to a qcow2 image, and wonder if this is the best way to do it (*1): [$] qemu-img convert -O qcow2 /dev/vg_name/lv_name/ /var/lib/libvirt/images/image_name.qcow2 If this is the best way to do this, will this keep the information on: /dev/vg_name/lv_name/ untouched? Thanks, and please point me towards another mailing list if this it not right

try snapshot-create-as like below: virsh snapshot-create-as vm --disk-only --diskspec "vda,snapshot=external" 2013/6/25 cmcc.dylan <dx10years@126.com> > > Hi, everyone, > I have found the API snapshotCreateXML() can create a snapshot for a > virtual machine, and the xml configuration file - snapshot.xml as folllows: > <domainsnapshot> >...