similar to: disabling disk cache

Hello, one of my VM's blockcommit job always fails. How can I find the reason? Error message is not clear. virsh snapshot-create-as --domain my-vm backup-snapshot \ --diskspec vda,file=/foo/my-vm-snapshot.img \ --disk-only --atomic --no-metadata virsh blockcommit my-vm vda --active --verbose --wait --async virsh blockjob my-vm vda --pivot internal error: unable to execute QEMU

I also have problems with a live migration. I’ve experienced that migrating over tcp instead of ssh is more stable. But with big disks ( > 30Gb) and –copy-storage-all, I keep getting problems… for now I don’t use it. Van: libvirt-users-bounces@redhat.com [mailto:libvirt-users-bounces@redhat.com] Namens Firat KÜÇÜK Verzonden: woensdag 4 november 2015 12:01 Aan: libvirt-users@redhat.com

Please provide more information like Virsh version Virsh dumpxml my-vm qemu-info /foo/my-vm-snapshot.img According to http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit your active block commit command should look like: virsh blockcommit vm1 vda --active --verbose –pivot thus one command… Does your error comes after your third command? Van:

Hi, I use this procedure to backup my VM's: http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit It works on my current host: Compiled against library: libvirt 1.2.16 Using library: libvirt 1.2.16 Gebruikte API: QEMU 1.2.16 Draaiende hypervisor: QEMU 2.1.0 Now I'm doing a test on a testing host: Compiled against library: libvirt 1.2.21 Using library: libvirt 1.2.21

On 11/21/2017 09:14 PM, Jens Axboe wrote: > On 11/21/2017 01:12 PM, Christian Borntraeger wrote: >> >> >> On 11/21/2017 08:30 PM, Jens Axboe wrote: >>> On 11/21/2017 12:15 PM, Christian Borntraeger wrote: >>>> >>>> >>>> On 11/21/2017 07:39 PM, Jens Axboe wrote: >>>>> On 11/21/2017 11:27 AM, Jens Axboe wrote:

On 11/21/2017 09:14 PM, Jens Axboe wrote: > On 11/21/2017 01:12 PM, Christian Borntraeger wrote: >> >> >> On 11/21/2017 08:30 PM, Jens Axboe wrote: >>> On 11/21/2017 12:15 PM, Christian Borntraeger wrote: >>>> >>>> >>>> On 11/21/2017 07:39 PM, Jens Axboe wrote: >>>>> On 11/21/2017 11:27 AM, Jens Axboe wrote:

On 11/21/2017 09:21 PM, Jens Axboe wrote: > On 11/21/2017 01:19 PM, Christian Borntraeger wrote: >> >> On 11/21/2017 09:14 PM, Jens Axboe wrote: >>> On 11/21/2017 01:12 PM, Christian Borntraeger wrote: >>>> >>>> >>>> On 11/21/2017 08:30 PM, Jens Axboe wrote: >>>>> On 11/21/2017 12:15 PM, Christian Borntraeger wrote:

On 11/21/2017 09:21 PM, Jens Axboe wrote: > On 11/21/2017 01:19 PM, Christian Borntraeger wrote: >> >> On 11/21/2017 09:14 PM, Jens Axboe wrote: >>> On 11/21/2017 01:12 PM, Christian Borntraeger wrote: >>>> >>>> >>>> On 11/21/2017 08:30 PM, Jens Axboe wrote: >>>>> On 11/21/2017 12:15 PM, Christian Borntraeger wrote:

On 11/21/2017 08:30 PM, Jens Axboe wrote: > On 11/21/2017 12:15 PM, Christian Borntraeger wrote: >> >> >> On 11/21/2017 07:39 PM, Jens Axboe wrote: >>> On 11/21/2017 11:27 AM, Jens Axboe wrote: >>>> On 11/21/2017 11:12 AM, Christian Borntraeger wrote: >>>>> >>>>> >>>>> On 11/21/2017 07:09 PM, Jens Axboe wrote:

On 11/21/2017 08:30 PM, Jens Axboe wrote: > On 11/21/2017 12:15 PM, Christian Borntraeger wrote: >> >> >> On 11/21/2017 07:39 PM, Jens Axboe wrote: >>> On 11/21/2017 11:27 AM, Jens Axboe wrote: >>>> On 11/21/2017 11:12 AM, Christian Borntraeger wrote: >>>>> >>>>> >>>>> On 11/21/2017 07:09 PM, Jens Axboe wrote:

On 11/21/2017 07:39 PM, Jens Axboe wrote: > On 11/21/2017 11:27 AM, Jens Axboe wrote: >> On 11/21/2017 11:12 AM, Christian Borntraeger wrote: >>> >>> >>> On 11/21/2017 07:09 PM, Jens Axboe wrote: >>>> On 11/21/2017 10:27 AM, Jens Axboe wrote: >>>>> On 11/21/2017 03:14 AM, Christian Borntraeger wrote: >>>>>> Bisect

On 11/21/2017 07:39 PM, Jens Axboe wrote: > On 11/21/2017 11:27 AM, Jens Axboe wrote: >> On 11/21/2017 11:12 AM, Christian Borntraeger wrote: >>> >>> >>> On 11/21/2017 07:09 PM, Jens Axboe wrote: >>>> On 11/21/2017 10:27 AM, Jens Axboe wrote: >>>>> On 11/21/2017 03:14 AM, Christian Borntraeger wrote: >>>>>> Bisect

Hi Kashyap Chamarthy: thank you very much for answer my question: 一： lead to VM filesystem becoming read-only 1： test case it lead to VM filesystem becoming read-only test case as follows: we want to snapshot for VM , to obtain VM incremental data，and use virsh blockcommit，qemu-img commit，qemu-img rebase to shorten snapshot chain. Details are as follows（when VM running state， we perform the

Hello, it happened with another VM: # virsh snapshot-create-as --domain rasa sn1 --diskspec vda,file=/var/lib/libvirt/images/rasa-sn1.qcow2 --disk-only --atomic --no-metadata # virsh blockcommit rasa vda --active --verbose --pivot Block commit: [100 %]error: failed to pivot job for disk vda error: block copy still active: disk 'vda' not ready for pivot yet # virsh domblklist rasa

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

Hello, I want to live migrate a vm from one host to another host. Bu I got this error: error: internal error: process exited while connecting to monitor: 2015-11-06T07:53:59.006762Z qemu-system-x86_64: Failed to start VNC server on `0.0.0.0:3': Failed to bind socket: Address already in use The same VNC port is in use at the destination host. Is it possible to change port address without