similar to: some problem with snapshot by libvirt

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

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

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

Hi Kashyap Chamarthy: thank you very much for answer my question: 一： lead to VM filesystem becoming read-only 1： test case it lead to VM filesystem becoming read-only test case as follows: we want 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

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

Hi,all,i build qemu-kvm1.0.93 from source code on centos6.2 , # qemu-system-x86_64 --version QEMU emulator version 1.0.93 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice Bellard and the guestfish's version: # guestfish --version guestfish 1.7.17 but when i use the guestfish command to upload a file to a vm,it does not work , # guestfish --rw -i -d centosvm upload /test/ifcfg-eth0_centos

Hi, dear friend. My guest has two 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

On Wed, Mar 20, 2019 at 15:48:43 -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

Hi, 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

Hi all, I was trying to take live snapshot of VMs, but I got the following error: [root@localhost ~]# virsh snapshot-create-as 1 test desc --live --memspec file=mem.bak,snapshot=external --diskspec vda,snapshot=external,file=/root/root.bak.qcow2 error: Operation not supported: live disk snapshot not supported with this QEMU binary I upgraded my qemu-kvm 0.12.1 to qemu 1.2, the error still

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

Dear all, Please let me start 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

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.

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

Hello, I am working on a script to automatically create live snapshots of running VMs using qemu-kvm 1.4.0 and libvirt 1.0.2. If a VM has multiple disks, I'd like to back them up individually with 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

Hi, Recently We've upgraded some KVM hosts from Fedora 29 to Fedora 30 and now experience broken VM configurations on filesystem after virsh blockcommit. Commands "virsh dumpxml ..." and "virsh dumpxml --inactive ..." is showing diffrent configuration than the one on filesystem. In case of restart libvirtd or system reboot, there are broken VM xml configurations on

Thank you! But snapshot-create-as will traverse all disks of the virtual machine and create snapshots for all of them. In my case, I want to create snapshot for root disk. What's more. I understand "--diskspec" is a description of the disk. Do you mean it's used to specify a single disk to snapshot. 在 2013-06-26 09:10:31，"Gao Yongwei" <itxx00@gmail.com> 写道：

Hi, I'm trying to create an external snapshot for backup purposes. Only I get an error after the command: virsh snapshot-create-as --domain PCVIRT1 PCVIRT1-SN1 --diskspec vda,file=/var/lib/libvirt/images/VIRT1-SN1.qcow2 --disk-only --atomic --quiesce fout: internal error: kan AppArmor profiel 'libvirt-2c9c04d7-f86d-df12-da9f-9847ac8b994f' niet vernieuwen (Sorry about the

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