similar to: incomplete features for external snapshot

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

Recently I had a system with an incomplete snapshot. The destination system hung in the middle of a zfs recv. It ended up taking about 75 GB of kernel memory to destroy that incomplete snapshot. Yet destroying another copy of that same snapshot took less than 6 GB of memory. Does a destroy of a snapshot take a different path through the code than destroying an incomplete snapshot (as part of

On 04/30/2015 12:28 AM, NoxDaFox wrote: > Sorry for the lack of information, my bad. > Also, we tend to avoid top-posting on technical lists. > > The snapshot is an internal one and the machine is running. > > The whole thing was set-up by another person and left to me to cope with. > The typo is mine, as the machine is isolated I cannot actually copy-paste > it so

If I want to go back to a snapshot, what is the difference between snapshot-current and snapshot-revert? What happens to disk sectors of the current state when reverting to another snapshot? I'm using qemu qcow2.

On 04/29/2015 01:08 AM, NoxDaFox wrote: > Greetings, > > due to hardware failure I had to replace my workstation which has a > different CPU. I have a VM with several snapshots and I need to revert to a > specific one. > > While reverting to it, I get an error due to unsupported CPU features. > Therefore, I try to edit the snapshot XML through the command: > >

Sorry for the lack of information, my bad. The snapshot is an internal one and the machine is running. The whole thing was set-up by another person and left to me to cope with. The typo is mine, as the machine is isolated I cannot actually copy-paste it so have to do it in the traditional way. I am aware of the issue which come when changing HW but I couldn't do otherwise. I am only

Greetings, due to hardware failure I had to replace my workstation which has a different CPU. I have a VM with several snapshots and I need to revert to a specific one. While reverting to it, I get an error due to unsupported CPU features. Therefore, I try to edit the snapshot XML through the command: virsh snapshot-edit <domain_name> <snapshot_name> When I save the changes I get

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

Versions: $ rpm -q libvirt-daemon-kvm qemu-system-x86 libvirt-daemon-kvm-1.2.9-3.fc21.x86_64 qemu-system-x86-2.1.2-4.fc21.x86_64 When I attempt to revert to an internal snapshot: $ virsh snapshot-list node1 Name Creation Time State ------------------------------------------------------------ snap1 2014-06-03 14:07:28 -0400 running $

Hi Team, I have created a "External system checkpoint snapshot" using the following link. http://kashyapc.fedorapeople.org/virt/external-system-checkpoint-snapshot.txt The disk and ram snapshot has been created successfully. The disk snapshot have the QCOW2 file format,I tried to boot the disk snapshot (qcow2)file using the KVM but it throws the error *" No bootable disk

<div dir='auto'>How can I automatically revert to a snapshot after the guest is stopped?<div dir="auto"><br></div><div dir="auto">/etc/libvirt/hooks/qemu </div><div dir="auto">#!/bin/sh </div><div dir="auto">name="<span class="money">$1</span>" </div><div

On 09/11/2015 10:18 AM, Jérôme wrote: >> Yep, that about covers it. Note that the --quiesce step in snapshot >> creation requires qemu-guest-agent running in the guest, and that you >> trust interaction with your guest. > > Yes, I think I get this. I don't really figure out what these cases > could be. We're using Debian Jessie and I installed

On 08/06/2014 10:06 AM, Yuanzhen Gu wrote: > yes, I got your point, thanks very much Eric. not entirely, because you still top-posted. > > If I want to take a distributed snapshot, which need pause all the VMs and > then take snapshot, how can I control the pause for all the VMs? You mean, you have multiple VMs, and want to take a snapshot of all their storage at the same point in

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

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.

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 there, I''m running several VMs within Xen, and now I''m trying to create/revert snapshots of my VMs. Along with Xen and blktap2, another utility, vhd-util is also delivered, and according to its description, i guess I can use it to create/revert VM snapshots. To create a snapshot is actually easy, I just call |vhd-util snapshot -n aSnapShot.vhd -p theVMtoBackup.vhd | But

Hi, If I make an external snapshot using the method of active block commit, I get these messages after the block commit: $virsh snapshot-create-as CmsrvAPP2 --name onderhoudscript --disk-only --atomic --quiesce --no-metadata Domein snapshot onderhoudscript is aangemaakt $virsh blockcommit CmsrvAPP2 vda --verbose --pivot 2016-01-03 18:14:52.784+0000: 15861: info : libvirt version: 1.2.16,

On standard Fedora 18 I was attempting blockcommit on a *live* VM, libvirt said it was not supported, so I tried fedora-virt-preview as recommended. We found a problem with qemu 1.4, there seems to be an acknowledged bug, a missing library. On a different system we loaded Fedora 18, and then pulled qemu (1.3) and libvirt (1.0.2) from rawhide. I tried blockcommit with domain shut down, it said