similar to: Problem about Disk Dize of Destination and Source File after Do Blockcopy

Hi Eric, On 07/22/2014 08:52 PM, Eric Blake wrote: > On 07/21/2014 10:01 PM, shyu wrote: > >> # rpm -q libvirt qemu-kvm-rhev >> libvirt-1.1.1-29.el7.x86_64 >> qemu-kvm-rhev-1.5.3-60.el7ev_0.2.x86_64 > These are downstream builds. Can you reproduce your situation with > upstream libvirt 1.2.6 and qemu 2.1-rc2? It may be that you are hitting > behavior that was

On 07/21/2014 10:01 PM, shyu wrote: > > # rpm -q libvirt qemu-kvm-rhev > libvirt-1.1.1-29.el7.x86_64 > qemu-kvm-rhev-1.5.3-60.el7ev_0.2.x86_64 These are downstream builds. Can you reproduce your situation with upstream libvirt 1.2.6 and qemu 2.1-rc2? It may be that you are hitting behavior that was introduced by downstream backports. > 1. Check source file > # qemu-img

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 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 >>> virsh snapshot-create gentoo-template >>> virsh undefine

On 07/03/2014 03:12 AM, Kashyap Chamarthy wrote: > 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

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

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

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 "snapshot-create" ? Because: You cannot undefine a guest with a snapshot without

On 01/16/2015 10:21 AM, Scott Sullivan wrote: > 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? Sadly, this is not yet possible. There is work being done in upstream qemu to add persistent bitmap support, and the libvirt would have to be

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 the VM will not be necessary after two things happen: 1. qemu supports persistent

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

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 storage migration. Let's say you are running on a cluster, where your VM is running locally but

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

Right now, on a virsh blockcopy, I know you can do something like this: # Connect DEST target iscsiadm -m node -p ${DESTINATION}:3260 -T ${VOLNAME} -o new iscsiadm -m node -p ${DESTINATION}:3260 -T ${VOLNAME} --login # Copy to connected iSCSI target virsh blockcopy ${DOMAIN} vda /dev/sdc --raw --bandwidth 300 However I have libiscsi compiled into my QEMU. So I can do this with the monitor

On Thu, Jul 03, 2014 at 12:42:20AM +0530, Kashyap Chamarthy wrote: [. . .] Forgot to note: Before blockcopy, the current block device is snap1.qcow2 (after too, it's the same, since we didn't `--pivot` to the copy. > Now, let's do a live blockcopy (with a '--finish' to graecully finish > the mirroring): > > $ virsh blockcopy --domain testvm2 vda \ >

On 12/23/14 6:17 AM, Kashyap Chamarthy wrote: > 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: >>>

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

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

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/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 to boot, no? > > I see you're playing with NBD disks. I'll admit, I haven't