similar to: Pivot without copy

Hi Eric, Thanks for the info. I see the value in this, but it isn't quite what I was looking for. Basically what I want to do is to switch between snapshots quickly. For instance, I am currently working on designing a HA SQL implementation with failover. So right now I have 5 VM's running postgresql as a replication group. I am trying a lot of different things and often have to take a

On 05/19/2015 12:52 PM, Mathew Moon wrote: > Hi, > > Is it possible to "pivot" to a new image without doing blockcopy or > blockpull? No. Qemu does not support arbitrary reopening of a backing chain yet (even with the 'change-backing-file' QMP command, that is just rewriting contents of the qcow2 metadata, and not actually reopening the chain). The only way to pivot

It seems that my version of libvirt does not support the flags that yours does either. I have the latest version from the Ubuntu repos and am running 14.04. What version are you running and do you know if these features depend on libvirt, or qemu-img to be upgraded? =============================================================================================

Thank you Eric, On 2014-02-05 17:23, Eric Blake wrote: > Yes, live storage migration is possible; although at the moment, qemu is > lacking a way to restart the operation if it fails midstream, so libvirt > only allows the operation if you are willing to temporarily make your > guest transient. What does this mean? Will I loose anything if - for example - there is not enough space on

I am searching for directions for using live block migration to copy running vm's to a different storage pool. Example: VM1 running on Host1, the image(s) for VM1 are stored in /var/lib/libvirt/images. I'd like to copy the disk image(s) that VM1 is using to /nfs/images. Without stopping/pausing/powering down the VM. Do you have any examples or documentation of how to accomplish this

All, I have a service that takes new live KVM snapshots Si regularly, keeps a fixed number N (Si ,..,Si-N+1), and therefore needs to delete Si-N in this cycle. Until libvirt includes support for this capability that is said to be available in qemu, what is a safe workflow to delete old live KVM snapshots w/o losing data. Do I need to pause/shut down the VM? The development environment is

----- Original Message ----- > From: "Eric Blake" <eblake@redhat.com> > To: "Gergely Horváth" <gergely.horvath@inepex.com>, libvirt-users@redhat.com > Sent: Wednesday, February 5, 2014 4:47:47 PM > Subject: Re: [libvirt-users] Can I move the disk image of the guest while it is running? > > On 02/05/2014 02:54 PM, Gergely Horváth wrote: > >

Am 13.10.14 16:25, schrieb Eric Blake: > On 10/13/2014 03:56 AM, Thomas Stein wrote: >> Hello. >> >>> blockcommit vm1 vda --active --verbose --pivot >> >> That's where libvirt stops working at the moment, right? >> >> virsh # blockcommit puppet-test vda --active --verbose --pivot >> error: unsupported flags (0x4) in function

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

Hello If I'm not terribly mistaken, looks like libvirt 1.2.1 does not provide ability of merging only a subset of the entire chain of backing files. So, if I have a chain like this: root <- a <-b <- c <- d <- active ... and I'd like to obtain a chain like this: root <- c <- d <- active ... looks like it's not supported,

Hello, it happened with another VM: # virsh snapshot-create-as --domain rasa sn1 --diskspec vda,file=/var/lib/libvirt/images/rasa-sn1.qcow2 --disk-only --atomic --no-metadata # virsh blockcommit rasa vda --active --verbose --pivot Block commit: [100 %]error: failed to pivot job for disk vda error: block copy still active: disk 'vda' not ready for pivot yet # virsh domblklist rasa

I have lvm based (thin pool) storage on local disks. I need to move vps from one vg on one disk to another. Does it possible to migrate to localhost with blockcopy migration to another vg? I'm understand that i can move lv from one vg to another, but i don't need that. -- Vasiliy Tolstov, e-mail: v.tolstov@selfip.ru jabber: vase@selfip.ru

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

Hello, I did a virsh snapshot-create-as --domain meta sn1 --diskspec vda,file=/var/lib/libvirt/images/meta-sn1.qcow2 --disk-only --atomic --no-metadata Then I successfully blockcommitted 2 disks: virsh blockcommit meta vda --active --verbose --pivot virsh blockcommit meta vdb --active --verbose --pivot But when doing virsh blockcommit meta vdc --active --verbose --pivot I got: Block commit:

On Wednesday 07 January 2015 09:46:09 Eric Blake wrote: > On 01/07/2015 07:19 AM, Thomas Stein wrote: > > Hello. > > > > I'm seeing this error while doing a backup of a VM. > > > > + virsh blockcommit kaltura vda --active --verbose --pivot > > Block Commit: [100 %]error: failed to pivot job for disk vda > > error: internal error: unable to execute

Hello All, I think I have seen this in previous bugs. Trying to live backup qcow2 images. I am able to virsh snapshot-create-as and virsh domblklist shows correct new source, but I am unable to commit back changes to qcow base. I get the above error. Libvirt at 1.2.2-0ubuntu13.1.17 Qemu is (2.0.0+dfsg-2ubuntu1.22) I tried compiling latest libvirt, but cannot get it to connect to socket on

Hi guys, When performing live merge, in few cases, we see the following exception: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 736, in wrapper return f(*a, **kw) File "/usr/share/vdsm/virt/vm.py", line 5278, in run self.tryPivot() File "/usr/share/vdsm/virt/vm.py", line 5247, in tryPivot ret =

Hello one and all. Got a problem with libvirt 6.2.0 and qemu 5.0.0. virsh blockcommit mymachine vda --active --verbose --pivot works until it shows [100%] but it never actually pivots. It just sits there. Is this a known issue with 6.2.0 and i should try 6.3.0? For now i switched back to qemu 4.2.0 and this seems to solve the issue too. Any hints? Ahoi! t.

On Fri, Oct 10, 2014 at 07:32:06PM -0600, Eric Blake wrote: > On 10/10/2014 11:37 AM, Jd wrote: > > Hi > > Looking in to implementing (CBT like) delta backup for KVM. > > Not quite sure what you mean by CBT. > > > > > The following looks promising..(last paragraph) > > http://wiki.qemu.org/Features/Snapshots2 > > > > Libvirt

Hello. I'm seeing this error while doing a backup of a VM. + virsh blockcommit kaltura vda --active --verbose --pivot Block Commit: [100 %]error: failed to pivot job for disk vda error: internal error: unable to execute QEMU command 'block-job-complete': The active block job for device 'drive-virtio-disk0' cannot be completed I'm on qemu 2.2.0 and libvirt-1.2.11. Does