similar to: Re: About live migration with snapshots

Hello, I'd like to live migration with snapshots. But it doesn't work. It comes out a message "cannot migrate domain with 1 snapshots" Then I try to trace the code(Libvirt 0.9.8 to 1.0.3), I find out the code in src/qemu/qemu_migration.c @ Line 1395 - 1440 (Libvirt 1.0.3) It will check the VM which has snapshots or not. I just curious about this limitation, why the VM

[dropping multiple lists; let's just use libvirt-users] On 02/11/2015 02:45 PM, Edward Young wrote: > I perform a simple test, but failed. > > In the source, I create: base <- mid <- active (2 snapshots, the active > one is the current one) > In order to migrate this vm to the destination, I manually copy both base > and mid to the destination, and put them in the

Hi Eric, Please see the blew: On Wed, Feb 11, 2015 at 3:12 PM, Eric Blake <eblake@redhat.com> wrote: > On 02/11/2015 02:07 PM, Edward Young wrote: > >>> What if this vm has a number of disk-only external snapshots? In the > >>> current version, how can live migrate this vm? > >> > >> Are the snapshots based on shared storage, or local-only

On 10/12/20 4:46 AM, Vjaceslavs Klimovs wrote: > On libvirt 6.8.0 and qemu 5.1.0, when trying to live migrate "error: > internal error: Failed to reserve port" error is received and > migration does not succeed: > > virsh # migrate cartridge qemu+tls://ratchet.lan/system --live > --persistent --undefinesource --copy-storage-all --verbose > error: internal error:

On 02/11/2015 10:08 AM, Edward Young wrote: > Hi all, [probably didn't need to cross-post to quite that wide of an audience, oh well] > > I'm investigating the ways to improve the live migration performance in > libvirt. I have a question about the vm live storage migration. the > platform is libvirt + qemu + kvm > > If we want to migrate a running vm with its

On 02/11/2015 02:07 PM, Edward Young wrote: >>> What if this vm has a number of disk-only external snapshots? In the >>> current version, how can live migrate this vm? >> >> Are the snapshots based on shared storage, or local-only storage? >> > > Yes, I'm talking about the local-only storage. Okay, glad I guessed as much, then. > > Yes, I

On 05/23/2014 08:41 AM, Andrew Martin wrote: >> >> Any reason you aren't upgrading to newer versions? Although these seem >> sufficient for what you are trying. > The VM hosts I'm using all run Ubuntu 12.04 and I haven't had time to backport > and test newer versions yet. I've published the latest versions I built in this > PPA:

On 05/22/2014 04:31 PM, Andrew Martin wrote: > Hello, > [Can you convince your mailer to wrap long lines?] > 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 Any reason you aren't upgrading to newer versions? Although these seem sufficient for what you are trying. > multiple disks, I'd

> >> --live only makes sense when mixed with memory snapshots (with --memspec); > >> but > >> as you are doing a --disk-only snapshot, it doesn't help (I'm not sure if > >> it > >> will error out as mutually exclusive or just be silently ignored, > >> without reading the code). > > I'm using this code in a script for creating

Hi all, I'm investigating the ways to improve the live migration performance in libvirt. I have a question about the vm live storage migration. the platform is libvirt + qemu + kvm If we want to migrate a running vm with its virtual disk images to another node. we can use 'virsh migrate ....' commands. What if this vm has a number of disk-only external snapshots? In the current

Hi Eric, Thanks for your reply! I have the follow up questions blew. On Wed, Feb 11, 2015 at 11:52 AM, Eric Blake <eblake@redhat.com> wrote: > On 02/11/2015 10:08 AM, Edward Young wrote: > > Hi all, > > [probably didn't need to cross-post to quite that wide of an audience, > oh well] > > > > > I'm investigating the ways to improve the live

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

Hello, I recently compiled libvirt 1.0.1 and qemu 1.3.0 on Ubuntu 12.04. I have performed live snapshots on VMs using "virsh snapshot-create-as" and then later re-merge the images together using "virsh blockpull". I am wondering how I can do a couple of other operations on the images while the VM is running. For example, VM1 is running from the snap3 image, with the following

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

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

----- Original Message ----- > From: "Eric Blake" <eblake@redhat.com> To: "Andrew Martin" > <amartin@xes-inc.com>, libvirt-users@redhat.com Sent: Thursday, May 22, 2014 > 5:44:54 PM Subject: Re: [libvirt-users] Live snapshots of a single block > device > > On 05/22/2014 04:31 PM, Andrew Martin wrote: > > Hello, > > > > [Can you

Hey, Over in KubeVirt we're investigating a use case where we'd like to perform a live migration within a network namespace that does not provide libvirtd with network access. In this scenario we would like to perform a live migration by proxying the migration through a unix socket to a process in another network namespace that does have network access. That external process would live

The gluster side looks like this: root at B741:~# gluster volume get glvol_samba features.show-snapshot-directory features.show-snapshot-directory???????? on root at B741:~# gluster volume get glvol_samba features.uss features.uss???????????????????????????? enable I found an error when the samba client is mounting the gluster volume in the gluster logs

On 12/04/2013 08:29 AM, Juraj Melo wrote: > Thanks for your answer, [please don't top-post on technical lists, and use proper in-reply-to headers to keep things properly threaded] > > I am trying to make a snapshot of whole virtual machine (disk, CPU > state, memory). But I need to make this snapshot in matter of seconds. This is possible using external snapshots with memory,

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