similar to: About live migration with snapshots

Hi All, Sorry, I do not know to reply the previous message directly, so I have to manually copy them here. I have two questions about the following issue? 1. I follow the instructions blew to migrate a vm with snapshots. When I perform 'virsh snapshot-create --redefine $dom file' on the destination.' I got an error saying that "no domain with matching name $dom". I'm

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

Hello, I want to do a snapshot which the VM has volumes. But I want to skip the volume check when I do the snapshot. (Which means I want to do a snapshot without detaching the volume) So I try to write a snapshot XML refer by http://libvirt.org/formatsnapshot.html as following: vda is my VM basic disk (qcow2) vdb is a volume (raw) ================ t1.xml =============== <domainsnapshot>

[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

Hey all, With libvirt 6.5.0 and qemu 5.1.0 migration of non shared disks in tunneled mode does not work for me: virsh # migrate alpinelinux3.8 qemu+tls://ratchet.lan/system --live --persistent --undefinesource --copy-storage-all --tunneled --p2p error: internal error: qemu unexpectedly closed the monitor: Receiving block device images Error unknown block device 2020-08-15T21:21:48.995016Z

On Mon, Aug 17, 2020 at 3:24 AM Peter Krempa <pkrempa@redhat.com> wrote: > > On Sat, Aug 15, 2020 at 15:38:19 -0700, Vjaceslavs Klimovs wrote: > > Hey all, > > With libvirt 6.5.0 and qemu 5.1.0 migration of non shared disks in > > tunneled mode does not work for me: > > > > virsh # migrate alpinelinux3.8 qemu+tls://ratchet.lan/system --live > >

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: Failed to reserve port 49153 virsh # On target host with debug logs, nothing

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

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

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

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

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

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

# virsh snapshot-create-as small snap1 --disk-only --atomic error: Operation not supported: live disk snapshot not supported with this QEMU binary OS used: CentOS 7 #virsh version Compiled against library: libvirt 1.1.1 Using library: libvirt 1.1.1 Using API: QEMU 1.1.1 Running hypervisor: QEMU 1.5.3 Any help would be greatly appreciated. Best Regards, Payes

Hi, thanks for previous help. I have some question about Lustre RPC and the sequence of events that occur during large concurrent write() involving many processes and large data size per process. I understand there is a mechanism of flow control by credits, but I''m a little unclear on how it works in general after reading the "networking & io protocol" white paper. Is

All, Using Centos 6.4 with provided libvirt: [root@node1 ~]# rpm -q libvirt libvirt-1.0.1-2.el6.x86_64 Assume a VM with one or more live snapshots. In virsh the VM snapshots can be listed. With virsh: - Stop and undefine this VM. - Then define (and start) this VM. The new VM does not have the list of snapshots. Is there a way with virsh to rebuild the metadata such that

Hi all, I was trying to take live snapshot of VMs, but I got the following error: [root@localhost ~]# virsh snapshot-create-as 1 test desc --live --memspec file=mem.bak,snapshot=external --diskspec vda,snapshot=external,file=/root/root.bak.qcow2 error: Operation not supported: live disk snapshot not supported with this QEMU binary I upgraded my qemu-kvm 0.12.1 to qemu 1.2, the error still

Hello, I am working on my PhD thesis and it would be really helpfull if someone could advise me, whether can Virsh create snapshots of VMs using copy-on-write. Thanks for reply. Juraj