similar to: Re: 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

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

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

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

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

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

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:

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

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

Hello! I am trying to create snapshots for sheepdog disks using libvirt API or virsh. The disk is defined in domain as follows: <disk type='network' device='disk'>       <driver name='qemu' cache='none'/>       <source protocol='sheepdog' name='sheepvol1'/>       <target dev='vdb' bus='virtio'/> </disk>

Hello! I am trying to create snapshots for sheepdog disks using libvirt API or virsh. The disk is defined in domain as follows: <disk type='network' device='disk'>       <driver name='qemu' cache='none'/>       <source protocol='sheepdog' name='sheepvol1'/>       <target dev='vdb' bus='virtio'/> </disk>

(switched to libvirt-users as it seems to be more appropriate) On 2019-05-16 23:02, Eric Blake wrote: > On 5/16/19 10:20 AM, Thomas Stein wrote: >> Hello all. >> >> My currently used versions: libvirt-5.2.0 and qemu-4.0.0. >> >> Here is my problem. I'm struggeling since a few weeks with a strange >> behaviour by either qemu or libvirt. After a reboot

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

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

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