similar to: Live Snapshot and Rebasing using blockpull

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

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

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,

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

----- Original Message ----- > From: "Eric Blake" <eblake@redhat.com> > To: "Andrew Martin" <amartin@xes-inc.com> > Cc: "Gergely Horváth" <gergely.horvath@inepex.com>, libvirt-users@redhat.com > Sent: Thursday, February 6, 2014 9:31:29 AM > Subject: Re: [libvirt-users] Can I move the disk image of the guest while it is running? >

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

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

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

Hello, I am running qemu-kvm 1.4.0 and libvirt 1.0.2 on Ubuntu 12.04. I have two NFS mountpoints configured as two separate pools in virsh: <pool type='dir'> <name>nfs1</name> <uuid>419d799c-2493-6ebc-6848-53b0919e7bad</uuid> <capacity unit='bytes'>6836057014272</capacity> <allocation unit='bytes'>0</allocation>

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

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, I''m running XEN 3.0.3 on RHEL5 2.6.18-53.1.4.el5xen. I used to start the vm with "xm create myvm -c". I see the boot during a couple of second, then, it freeze. The console is freezed, not the vm, a couple of second later, I can ssh the vm without any problem. "xm console myvm" also display a freezed state. This is an extrat of the console : # xm

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

I'm using ubuntu 12.04LTS I setup a bridged network: # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp auto br0 iface br0 inet dhcp bridge_ports eth0 bridge_stp off bridge_fd 0 bridge_maxwait 0 Seems to work. Then I created a virtual machine using Ubuntu's vmbuilder tool like so: vmbuilder

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 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 Libvirt, Does libvirt-python currently support adding a base path to virDomain.blockPull()? In particular, I would like to have the behavior of the following virsh command (from https://kashyapc.wordpress.com/2013/01/22/live-backup-with-external-disk-snapshots-and-libvirts-blockpull/) in libvirt-python: [image: image.png] Thanks! Sincerely, Roger Jin -------------- next part --------------

Hello, I am writing an LLVM backend that generates byte code for a custom virtual machine. Standard function calls are lowered to a simple CALL $offsetInByteCode This works fine so far using the standard machinery of LLVM. But some functions are not implemented in byte code, but delegated to native implementations within the VM. Calls to these functions use a non-standard calling convention