similar to: libvirt-python blockPull

On 01/29/2014 08:21 PM, Richard Gomes wrote: > 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

Hi Libvirt, Is there a command that performs the same operation as blockpull while a domain is shutoff? I have a backing chain base <-- A <-- B that I would like to shorten to base <-- B It seems like blockpull B, setting --base <path-to-base> does this, but only when the domain is running. Thanks! Sincerely, Roger Jin -------------- next part -------------- An HTML

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,

On 07/21/2016 03:05 PM, Andrew Martin wrote: > Hello, > > I use snapshot-create-as followed by blockpull when creating external snapshots > of VMs. This works well, however I am curious about the behavior of blockpull > after an unexpected shutdown (or SIGKILL). If a blockpull is in progress and an > unexpected power loss occurs, will the VM continue to reference the backing

----- Original Message ----- > From: "Eric Blake" <eblake@redhat.com> > To: "Andrew Martin" <amartin@xes-inc.com>, libvirt-users@redhat.com > Sent: Thursday, July 21, 2016 5:40:07 PM > Subject: Re: [libvirt-users] Blockpull behavior when interrupted > > On 07/21/2016 03:05 PM, Andrew Martin wrote: > > Hello, > > > > I use

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

Hello, I use snapshot-create-as followed by blockpull when creating external snapshots of VMs. This works well, however I am curious about the behavior of blockpull after an unexpected shutdown (or SIGKILL). If a blockpull is in progress and an unexpected power loss occurs, will the VM continue to reference the backing file for the parts of it that have not yet been copied? Or, will will the disk

Coming off of xen environment; still testing with kvm, just a few questions: 1. What is the roadmap for release of qemu-kvm 1.1 and libvirt 0.10.2 for el6, cause I had to compile from upstream to get the latest stuff. 2. Should not virt-manager show the sparsed disk size instead of actual reserved size of a vm? 3. Where is the virsh bash_completion conf.d file from upstream; since el6 rpm

Hi all, I have a kvm virtual machine running (qemu version 2.0), and I had took several external snapshots of the disk( using "virsh snapshot-create-as"). Now, the existed disk files relationship look like: base <- snap1 <-snap2 <- current using disk file. Now I want to remove snap1 and snap2, and let current disk using the base image file as back file directly. Unfortunately,

On 08/06/2014 06:04 AM, chenyanqiu@keytonecloud.com wrote: > Hi all, [please configure your mailer to wrap long lines] > ...Now I want to remove snap1 and snap2, and let current disk using the base image file as back file directly. Unfortunately, for some reason, I can not shutdown the vm, and exectue the "virsh blockpull" command. Can I execute the "virsh blockpull"

Hi Libvirt, Does libvirt-python currently support the creation of external snapshots? I ran domain.snapshotCreateXML(xml) where xml is <domainsnapshot> <name>snap1</name> <description>Snapshot of OS install and updates</description> <disks> <disk name='vda'> <source

Hello, I am looking for a solution for live backups of running KVM hosts. I recently read this article which highlights the following method: http://www.linux-kvm.com/content/first-look-virtual-machine-online-disk-snapshots-coming-fedora-18 1. virsh snapshot-create-as to create the snapshot 2. cp myvm.qcow2 myvm-backup.qcow2 to copy off the now read-only backing image file 3. virsh

This is a libvirt question, so asking it on the qemu-block might not get you an answer that quick, ... or ever if I didn't notice your other question also addressed incorrectly. [adding libvirt-users@redhat.com to cc] On Tue, Sep 01, 2020 at 10:57:34 -0400, Yoonho Park wrote: > I am trying to perform a blockpull on an attached disk, but I cannot do > this using "virsh

On 01/29/2014 07:51 AM, Richard Gomes wrote: > 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. Correct - qemu doesn't provide full functionality for merging in all directions. And even though upstream qemu has been adding more pieces (for example, they recently added

Hello Eric, Absolutely enlightening! Thanks a lot :) Richard Gomes http://rgomes.info http://www.linkedin.com/in/rgomes mobile: +44(77)9955-6813 inum <http://www.inum.net/>: +883(5100)0800-9804 sip:rgomes@ippi.fr On 29/01/14 16:46, Eric Blake wrote: > On 01/29/2014 07:51 AM, Richard Gomes wrote: >> Hello >> >> If I'm not terribly mistaken, looks like libvirt

Migration without --p2p works just fine, ie. the below works: $ virsh migrate --verbose --copy-storage-all \ --live cvm1 qemu+ssh://kashyapc@devstack3/system Migration: [100 %] Result: - On the source host, the guest is shut off - On the destination host, the guest is live migratied successfully Migration with "--p2p" fails, a simple test below:

On Fri, Apr 03, 2015 at 10:08:21AM +0200, Kashyap Chamarthy wrote: > Migration without --p2p works just fine, ie. the below works: > > > $ virsh migrate --verbose --copy-storage-all \ > --live cvm1 qemu+ssh://kashyapc@devstack3/system > Migration: [100 %] > [. . .] > > (2) Perform peer to peer live migration (as root): > > $ virsh migrate

On 07/22/2016 11:30 AM, Andrew Martin wrote: > > Thanks, that was a helpful overview. To clarify, block commit is changing > the backing files,but even though it is doing that, the data is consistent > even if it is interrupted? Yes, the guest's view of the data is consistent. Intermediate backing files may have contents that don't correspond to any historical state seen by

On Fri, Apr 03, 2015 at 10:13:38AM +0200, Kashyap Chamarthy wrote: > On Fri, Apr 03, 2015 at 10:08:21AM +0200, Kashyap Chamarthy wrote: > > Migration without --p2p works just fine, ie. the below works: > > > > > > $ virsh migrate --verbose --copy-storage-all \ > > --live cvm1 qemu+ssh://kashyapc@devstack3/system > > Migration: [100 %] >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone, Is this being worked on? I rather need this thing... Although my system is Debian Lenny, not RH: kulfon 10.0.0.228 /etc/default % dpkg -l | grep libvirt ii libvirt-bin 0.4.6-10+lenny1 the programs for the libvirt library ii libvirt0 0.4.6-10+lenny1 library for