similar to: Re: libvirt segfaults with "internal,error: Missing monitor reply object", during block live-migration

On 7/30/20 4:13 PM, Alex Walender wrote: > Dear libvirt community, > libvirt-daemon 5.0.0-1ubuntu2.6~cloud0 Also, this is oldish libvirt. Is there a way you could check something more recent (if not the current HEAD). It's likely that the bug is fixed. Michal

On Tue, Oct 03, 2017 at 08:44:10 +0200, Michal Privoznik wrote: > On 10/02/2017 11:42 PM, Nick Gilmour wrote: [...] > > 2) storage backends are static. While we have libvirt drivers in > separate modules (.so files) and load them at start up, it's not the > same story with storage driver backends. These are hardcoded into the > storage driver. Might be worth it to have

Hi Peter, thanks for your help. ----- On Jun 5, 2019, at 9:27 AM, Peter Krempa pkrempa@redhat.com wrote: >> ============================================================= >> ... >> 2019-05-31 20:31:34.481+0000: 4170: error : qemuMonitorIO:719 : internal error: >> End of file from qemu monitor >> 2019-06-01 01:05:32.233+0000: 4170: error : qemuMonitorIO:719 :

I have finally found the solution here: https://www.mail-archive.com/search?l=ubuntu-bugs@lists.ubuntu.com&q=subject:%22%5C%5BBug+405388%5C%5D+Re%5C%3A+virt%5C-manager+cannot+create+image+file%22&o=newest&f=1 By default is qemu:///system activated but I had to change to qemu:///session because I was getting errors. I created a VM with qemu:///session and it was running without any

----- On Jun 5, 2019, at 4:49 PM, Peter Krempa pkrempa@redhat.com wrote: > On Wed, Jun 05, 2019 at 13:33:49 +0200, Lentes, Bernd wrote: >> Hi Peter, >> >> thanks for your help. >> >> ----- On Jun 5, 2019, at 9:27 AM, Peter Krempa pkrempa@redhat.com wrote: > > [...] > >> >> > >> > So that's interresting. Usually assertion

On Fri, Jan 17, 2020 at 01:45:00 +0100, Oliver Dzombic wrote: > Hi, > > i try to test live-migration using this command: > > #virsh migrate --copy-storage-all --verbose --live kvm1776 > qemu+ssh://nodeb/system > > > Instant error message: > > error: internal error: unable to execute QEMU command 'blockdev-mirror': > Cannot find

On Tuesday 24 February 2015 16:58:22 you wrote: > On 24.02.2015 16:10, Thomas Stein wrote: > > On Tuesday 24 February 2015 14:56:10 Michal Privoznik wrote: > >> On 24.02.2015 14:29, Thomas Stein wrote: > >>> Hola. > >>> > >>> Just tried a live migration after fixing the pc-q35-2.1 error. Now i > >>> have new problem. It seems

On Fri, Apr 03, 2015 at 10:13:38AM +0200, Kashyap Chamarthy wrote: > On Fri, Apr 03, 2015 at 10:08:21AM +0200, Kashyap Chamarthy wrote: > > Migration without --p2p works just fine, ie. the below works: > > > > > > $ virsh migrate --verbose --copy-storage-all \ > > --live cvm1 qemu+ssh://kashyapc@devstack3/system > > Migration: [100 %] >

Hi all, For some reason when I run "libvirtd -d" as root it seems to not start. I investigate by running "libvirtd -v" as root and I get a segfault. Here is the output: 2012-08-23 19:01:23.237+0000: 27464: info : libvirt version: 0.10.0 > 2012-08-23 19:01:23.237+0000: 27464: error : virDriverLoadModule:78 : > failed to load module >

Trying again. Is there another mailer list for libvirt-python related discussions? Regards, Harish On Thu, Mar 19, 2015 at 9:02 PM, Harish Vishwanath <harish.shastry@gmail.com > wrote: > Hello > > I am trying to get libvirt-python working in Ubuntu 14.04 64 bit system. I > tried installing the binaries from the repo itself: > > 1. > > root@test-vm8-109:/home/test#

Hello I am trying to get libvirt-python working in Ubuntu 14.04 64 bit system. I tried installing the binaries from the repo itself: 1. root@test-vm8-109:/home/test# libvirtd --version libvirtd (libvirt) 1.2.2 root@test-vm8-109:/home/test# python Python 2.7.6 (default, Mar 22 2014, 22:59:56) [GCC 4.8.2] on linux2 Type "help", "copyright", "credits" or

On Fri, Jun 30, 2017 at 09:23:29 -0400, Doug Hughes wrote: > On Jun 30, 2017 6:22 AM, "Peter Krempa" <pkrempa@redhat.com> wrote: > > On Fri, Jun 30, 2017 at 12:05:47 +0200, Peter Krempa wrote: > > > On Thu, Jun 22, 2017 at 11:02:41 -0400, Doug Hughes wrote: [...] > file or directory > > $ virsh blockcommit --active --pivot fedora23 vda > > >

Hi Harish, I believe the proper establishment of a connection should be done by libvirt.open() or libvirt.openAuth() or libvirt.openReadOnly(). All of them will return a functional virConnect instance. I'm not sure this segfault is worth to fix since instantiate a virConnect directly is not an expected usage. Hope this information will help you. Best Regards, Hao Liu +86-010-62608262

----- On Jun 5, 2019, at 4:49 PM, Peter Krempa pkrempa@redhat.com wrote: > On Wed, Jun 05, 2019 at 13:33:49 +0200, Lentes, Bernd wrote: >> Hi Peter, >> >> thanks for your help. >> >> ----- On Jun 5, 2019, at 9:27 AM, Peter Krempa pkrempa@redhat.com wrote: > > [...] > >> >> > >> > So that's interresting. Usually assertion

On 24.02.2015 16:10, Thomas Stein wrote: > On Tuesday 24 February 2015 14:56:10 Michal Privoznik wrote: >> On 24.02.2015 14:29, Thomas Stein wrote: >>> Hola. >>> >>> Just tried a live migration after fixing the pc-q35-2.1 error. Now i >>> have new problem. It seems during live migration only the ram gets >>> migrated. I use the following

sorry about top post, tablet mail client... brilliant! that did it! Any idea what happened to cause it to partially fail and get into this state? oot@vm1 ~]# virsh blockjob serv1r2 vda Active Block Commit: [100 %] [root@vm1 ~]# virsh blockjob --pivot serv1r2 vda [root@vm1 ~]# [root@vm1 ~]# ls -l /var/lib/libvirt/images/serv1r2.qcow2 -rw-r--r--. 1 qemu qemu 54200696832 Jun 30 10:39

Am 13.10.14 16:25, schrieb Eric Blake: > On 10/13/2014 03:56 AM, Thomas Stein wrote: >> Hello. >> >>> blockcommit vm1 vda --active --verbose --pivot >> >> That's where libvirt stops working at the moment, right? >> >> virsh # blockcommit puppet-test vda --active --verbose --pivot >> error: unsupported flags (0x4) in function

Migration without --p2p works just fine, ie. the below works: $ virsh migrate --verbose --copy-storage-all \ --live cvm1 qemu+ssh://kashyapc@devstack3/system Migration: [100 %] Result: - On the source host, the guest is shut off - On the destination host, the guest is live migratied successfully Migration with "--p2p" fails, a simple test below:

On Tue, Aug 28, 2018 at 05:07:18PM -0400, David Vossel wrote: > 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

On Tuesday 24 February 2015 14:56:10 Michal Privoznik wrote: > On 24.02.2015 14:29, Thomas Stein wrote: > > Hola. > > > > Just tried a live migration after fixing the pc-q35-2.1 error. Now i > > have new problem. It seems during live migration only the ram gets > > migrated. I use the following command. > > > > # virsh migrate --live domain