similar to: virsh blockcopy without undefine

On 10/13/2015 09:46 PM, Nathan Shearer wrote: > I have a script that performs a backup with the following steps: > > virsh dumpxml --inactive "$DOMAIN" > "$TMP/${DOMAIN}.xml" && \ > virsh dumpxml --inactive "$DOMAIN" > "$DESTINATION_XML" && \ > virsh undefine "$DOMAIN" && \

> virsh dumpxml --security-info dom > dom.xml > virsh undefine dom Hello. Someone was talking about this (undefining the VM) would not be neccessary anymore when qemu-1.5 has been released. Is that true? > virsh blockcopy dom vda /path/to/backup-vda > polling loop - check periodically until 'virsh blockjob dom vda' > shows 100% completion > virsh suspend

Hello. I just tried the following: virsh dumpxml --security-info gentoo-template > gentoo-template.xml virsh snapshot-create gentoo-template virsh undefine gentoo-template virsh blockcopy gentoo-template vda /opt/virt-backup-blockcopy/gentoo-template/gentoo-template.qcow2 --wait --verbose --finish virsh define gentoo-template.xml virsh snapshot-delete gentoo-template --current But if i

Am 10.06.13 09:07, schrieb Kashyap Chamarthy: > On 06/09/2013 02:46 PM, Thomas Stein wrote: >> Hello. >> >> I just tried the following: >> >> virsh dumpxml --security-info gentoo-template > gentoo-template.xml >> virsh snapshot-create gentoo-template >> virsh undefine gentoo-template > > Wait - is that really the command you used after

Am 02.07.13 15:42, schrieb Eric Blake: > On 07/02/2013 06:55 AM, Thomas Stein wrote: >> >>> virsh dumpxml --security-info dom > dom.xml >>> virsh undefine dom >> >> Hello. >> >> Someone was talking about this (undefining the VM) would not be >> neccessary anymore when qemu-1.5 has been released. Is that true? > > Undefining

I am experimenting with the blockcopy command, and after figuring out how to integrate qemu-nbd, nbd-client and dumpxml/undefine/blockcopy/define/et. al. I have one remaining question: What's the point? The "replication" disk file is not, from what I can ascertain, bootable. I expect this operation to create a pristine copy of my source qcow2 file (at a given point in time)

On Thu, Jan 08, 2015 at 01:44:58PM -0600, Gary R Hook wrote: > On 12/24/14 4:42 AM, Kashyap Chamarthy wrote: > >On Tue, Dec 23, 2014 at 12:38:57PM -0600, Gary R Hook wrote: > > > >[. . .] > > > >In my case, the block device is a QCOW2 disk image file. If I boot > >without using the disk image file which has the operating system, the > >domain will fail

On Mon, Dec 22, 2014 at 03:50:58PM -0700, Eric Blake wrote: > On 12/22/2014 03:27 PM, Gary R Hook wrote: > > I am experimenting with the blockcopy command, and after figuring out > > how to integrate qemu-nbd, nbd-client and > > dumpxml/undefine/blockcopy/define/et. al. I have one remaining question: > > > > What's the point? > > Among other uses, live

Am 10.06.13 10:40, schrieb Kashyap Chamarthy: > On 06/10/2013 01:20 PM, Thomas Stein wrote: >> Am 10.06.13 09:07, schrieb Kashyap Chamarthy: >>> On 06/09/2013 02:46 PM, Thomas Stein wrote: >>>> Hello. >>>> >>>> I just tried the following: >>>> >>>> virsh dumpxml --security-info gentoo-template > gentoo-template.xml

Hello, I'm seeking the solution to live storage migration using blockcopy. Previously, the "virsh undefine" is required before blockcopy. https://www.redhat.com/archives/libvirt-users/2015-October/msg00027.html QEMU has "block-dirty-bitmap-*" operations now, are there steps for the live storage migration using blockcopy without undefine? By the way, why's the purpose

Hello, I have two servers where I can push VMs from one to the other by issuing the command virsh migrate --live --persistent --copy-storage-all --verbose \ test6 qemu+ssh://kvmhost2/system on kvmhost1. I can get the VM back by issuing the equivalent command on kvmhost2: virsh migrate --live --persistent --copy-storage-all --verbose \ test6 qemu+ssh://kvmhost1/system virsh

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

Hi, Is it possible to "pivot" to a new image without doing blockcopy or blockpull? I know how to use snapshots and blockpull to create a new image and pivot to using it live, but what I would like to do is to have a VM switch from using imageA.qcow2 to image2.qcow2 while running. I don't see why this wouldn't be possible since some of the existing libvirt tools can do this when

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

Versions -------- (Libvirt locally built from a recent git commit -ec7b922): $ rpm -q libvirt-daemon-kvm qemu-system-x86 libvirt-daemon-kvm-1.2.6-1.fc20.x86_64 qemu-system-x86-2.0.0-1.fc21.x86_64 Test ---- [All images are qcow2 files.] We have this simple chain: base <- snap1 Let's quickly examine the contents of 'base' and 'snap1' images:

On 01/08/2015 12:44 PM, Gary R Hook wrote: > I've learned how to use the blockcopy command to create a local copy in > a simple disk file: > > virsh dumpxml my_domain > my_domain.xml > virsh undefine my_domain > virsh blockcopy --domain my_domain vda $PWD/dsk.copy.qcow2 --wait > --verbose --finish > virsh define my_domain.xml > > and the resulting copy in

On 12/23/2014 05:24 PM, Gary R Hook wrote: > I read that article. > > Now shut down the domain (post-pivot) which is using the new disk file, > and start it up, without using a block device. This is the part that no > one seems to write about, nor do I see that in your example. But thank > you very much for your help and your articles; very much appreciated. What do you mean by

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

My question is this: If you have an ongoing blockcopy (drive-mirror) of a running transient VM, and the VM kernel panics, can you restart the VM without interrupting the ongoing blockcopy? A virsh reboot won't work since if the VM is kernel panicked, its not going to respond to ACPI requests.