similar to: Re: libvirt 1.2.10 and latest EL6 qemu-kvm

Hi, since we're running more than 20 hosts per KVM server, we needed to update libvirt to at least 1.1.2 for virtlockd to be able to cope with this (due to an old hardcoded limit that was in there before). But where 1.1.0 compiles and runs just fine on a fully-patched CentOS 6.4 server, newer version have all kinds of issues: Every version of libvirt >= 1.1.2 crashes with a segfault on

Hi , I Sent this to the wrong list (libvirt-devel) on friday ... so i am trying to send it to the correct one this time. Apologize for double posting. I also created a ticket on bugzilla.redhat.com for this https://bugzilla.redhat.com/show_bug.cgi?id=927336 still i am posting it here because is absolutely possible i am doing something wrong and someone here will see it . Description of the

Hello Everyone, My pc run in CentOS 7.4 and install libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10 ALL-in-One. I use python-sdk with libvirt and run [self.domain.updateDeviceFlags(xml, libvirt.VIR_DOMAIN_AFFECT_LIVE)] on CDROM (I want to change media path). However, I enable libvirt debug log , the log as below: "2018-02-26 13:09:13.638+0000: 50524: debug :

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

[Dropping libvir list and adding libvir-users list.] On Mon, Jan 19, 2015 at 04:12:46PM +0100, liedekef@telenet.be wrote: > Hi all, > > I had libvirt 1.2.10 running without issues together with the qemu package > qemu-kvm-0.12.1.2-2.415.el6_5.14.x86_64.rpm That's a really old QEMU and the libvirt you're using is relatively newer. > Now, after updating my server,

Kashyap Chamarthy <kchamart@redhat.com> schreef op 19 januari 2015 19:00:23 CET: >[Dropping libvir list and adding libvir-users list.] > >On Mon, Jan 19, 2015 at 04:12:46PM +0100, liedekef@telenet.be wrote: >> Hi all, >> >> I had libvirt 1.2.10 running without issues together with the qemu >package >> qemu-kvm-0.12.1.2-2.415.el6_5.14.x86_64.rpm >

On Tue, Jun 23, 2015 at 03:41:45PM +0200, Michal Privoznik wrote: > On 23.06.2015 14:16, Ivo Hora wrote: > > Dear Sir, > > > > I am facing the same problem you were discussing here: > > https://www.redhat.com/archives/libvirt-users/2015-January/msg00070.html > > > > I am getting this error: > > Starting install... > > ERROR internal error:

2017-04-28 14:33 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: > On 04/27/2017 04:31 PM, Stefano Ricci wrote: >> Here is the backtrace of the libvirt process just started > > [Just a side note, you shouldn't top post on technical lists. Gmail > sucks at this.] > >> >> https://pastebin.com/R66myzFp > > Looks like libvirtd is trying to spawn

2017-04-29 7:24 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: > On 04/29/2017 04:38 AM, Stefano Ricci wrote: >> 2017-04-28 14:33 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: >>> On 04/27/2017 04:31 PM, Stefano Ricci wrote: >>>> Here is the backtrace of the libvirt process just started >>> >>> [Just a side note, you shouldn't

On 04/29/2017 04:38 AM, Stefano Ricci wrote: > 2017-04-28 14:33 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: >> On 04/27/2017 04:31 PM, Stefano Ricci wrote: >>> Here is the backtrace of the libvirt process just started >> >> [Just a side note, you shouldn't top post on technical lists. Gmail >> sucks at this.] >> >>> >>>

Dear Sir, I am facing the same problem you were discussing here: https://www.redhat.com/archives/libvirt-users/2015-January/msg00070.html I am getting this error: Starting install... ERROR internal error: unable to execute QEMU command 'qom-list': The command qom-list has not been found Domain installation does not appear to have been successful. If it was, you can restart your domain

On 07/03/2014 08:39 AM, Claudio Bley wrote: > At Thu, 03 Jul 2014 17:32:20 +0300, > Gleb Voronich wrote: >> >> >>> Actually, you should get more stats when using the virtio balloon >>> driver in your guests. >> I use the balloon but I can't get more stats. >> I use python binding for libvirt and as far as I can see it calls >>

I just recompiled libvirt and qemu myself and got rid of all errors :-) Yes, I know this might be risky, but I needed the new libvirt for virtlockd and more than 8 attached disks, and the newer redhat qemu just stopped working lately, so I recompiled the stable qemu myself and got more features for it in place :-) Franky On Tue, Jun 23, 2015 at 2:16 PM, Ivo Hora <ivo.hora@gmail.com>

On 23.06.2015 14:16, Ivo Hora wrote: > Dear Sir, > > I am facing the same problem you were discussing here: > https://www.redhat.com/archives/libvirt-users/2015-January/msg00070.html > > I am getting this error: > Starting install... > ERROR internal error: unable to execute QEMU command 'qom-list': The > command qom-list has not been found > Domain

On 06/01/2013 03:16 PM, Dennis Chen wrote: > On 05/29/2013 04:28 AM, Eric Blake wrote: >> On 05/28/2013 02:24 PM, Eric Blake wrote: >> >>>> So the question is: is there any method I can't find yet to change the >>>> vcpu count of a running vm dynamically? >>> Wait for newer qemu and libvirt, or else pitch in and help write >>> patches.

Hi, Since a few weeks I'm getting lot of messages in syslog in FC20 sent by libvirt. I've tried to find the reason using our best friend, but all I can find is some kind of bug related to CPU feature reporting. I'm not really interested what is the reason of the message (I'm sure it will be fixed in an upcoming release), but I would like to get rid of these annoying messages

On Fri, 29 Mar 2019 16:46:13 -0500 Matthew Delfino <mdelfino.list.samba at knockinc.com> wrote: > Hey Rowland, thank you for getting back to me so quickly. Answers in > line below... > > From: Rowland Penny via samba <samba at lists.samba.org>  > > To: <samba at lists.samba.org> > Sent: 3/29/2019 4:33 PM > Subject: Re: [Samba] Attempts to

On 06/05/2017 10:46 AM, Martin Kletzander wrote: > On Sun, Jun 04, 2017 at 06:42:39PM -0400, Michael C Cambria wrote: >> I've upgraded from Fedora 20; probably missed a merge of rpmnew with >> existing .conf; permission problem, some other mistake along the way to >> Fedora 25. >> > > Yeah, probably some 'rpm -qV' (or whatever the command to verify all

Description of problem: libvirt 3.9 on CentOS Linux release 7.4.1708 (kernel 3.10.0-693.21.1.el7.x86_64) on Qemu version 2.10.0 I’m currently facing a strange situation. Sometimes my vm is shown by ‘virsh list’ as in state “in shutdown” but there is no qemu-kvm process linked to it. Libvirt log when “in shutdown” state occur is as follows: “d470c3b284425b9bacb34d3b5f3845fe” is vm’s name,

On 06/06/2017 04:43 AM, Martin Kletzander wrote: > On Mon, Jun 05, 2017 at 07:52:58PM -0400, Michael C Cambria wrote: >> >> >> On 06/05/2017 10:46 AM, Martin Kletzander wrote: >>> On Sun, Jun 04, 2017 at 06:42:39PM -0400, Michael C Cambria wrote: >>>> I've upgraded from Fedora 20; probably missed a merge of rpmnew with >>>> existing .conf;