similar to: Libvirtd freezes

On 04/27/2017 03:11 PM, Michal Privoznik wrote: > On 04/27/2017 02:02 PM, Stefano Ricci wrote: >> Hello everyone >> I come back to ask for a hand to solve a problem that has affected me >> since October 2016 and I have not yet solved using libvirt. >> I thought I would solve it by going to a 4.9.x kernel with qemu >> 2.8.1.1 and with libvirt 3.2.0. >> Compile

On 12.10.2016 19:16, Stefano Ricci wrote: > I checked with qmp and your consideration was correct, the status of > qemu process is in prelaunch and running equals false. > But I do not understand why [Please don't top post on technical lists] Well, I don't have any idea either. I mean, the daemon logs you provided are from the second run of libvirtd. Maybe this is qemu or

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 /usr/bin/qemu-system-x86_64 but it takes ages to init. In the debug logs you might see the actual command line that

On Sat, Jun 03, 2017 at 09:22:58AM -0400, Michael C Cambria wrote: > > >On 06/02/2017 09:53 AM, Michael C. Cambria wrote: >> >> >> On 06/02/2017 09:43 AM, Martin Kletzander wrote: >>> [adding back the ML, you probably hit reply instead of reply-all, this >>> way other people might help if they know more] >>> >>> On Fri, Jun 02, 2017 at

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.] >> >>> >>>

On Sat, Jun 03, 2017 at 05:20:47PM -0400, Michael C Cambria wrote: >I also tried stopping libvirtd, renaming both qemu-system-i386 and >qemu-system-x86_64, start libvirtd. Things get further along; dnsmasq >log messages show up. > >$ sudo systemctl status libvirtd.service >● libvirtd.service - Virtualization daemon > Loaded: loaded

On 04/27/2017 02:02 PM, Stefano Ricci wrote: > Hello everyone > I come back to ask for a hand to solve a problem that has affected me > since October 2016 and I have not yet solved using libvirt. > I thought I would solve it by going to a 4.9.x kernel with qemu > 2.8.1.1 and with libvirt 3.2.0. > Compile it all in a stable LFS environment version 7.9 and that all > checks pass

Here is the backtrace of the libvirt process just started https://pastebin.com/R66myzFp Stefano 2017-04-27 15:12 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: > On 04/27/2017 03:11 PM, Michal Privoznik wrote: >> On 04/27/2017 02:02 PM, Stefano Ricci wrote: >>> Hello everyone >>> I come back to ask for a hand to solve a problem that has affected me

On Sat, Jun 03, 2017 at 08:27:08PM -0400, Michael C Cambria wrote: > > >On 06/03/2017 05:47 PM, Martin Kletzander wrote: >> On Sat, Jun 03, 2017 at 05:20:47PM -0400, Michael C Cambria wrote: >>> I also tried stopping libvirtd, renaming both qemu-system-i386 and >>> qemu-system-x86_64, start libvirtd. Things get further along; dnsmasq >>> log messages show

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 packages is) could help as well. >Is there a "how to" similar to [1]

On 06/02/2017 09:43 AM, Martin Kletzander wrote: > [adding back the ML, you probably hit reply instead of reply-all, this > way other people might help if they know more] > > On Fri, Jun 02, 2017 at 08:10:01AM -0400, Michael C. Cambria wrote: >> >> Hi, >> >> libvirtd never seems to get notified that there is work to do. journalct >> -f indicated that

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; permission problem, some other mistake along the way to >>> Fedora 25.

On 12.10.2016 16:06, Stefano Ricci wrote: >>> ---------- Forwarded message ---------- >>> From: Stefano Ricci <sfn.rcc@gmail.com> >>> Date: 2016-10-11 12:35 GMT+02:00 >>> Subject: Re: [libvirt-users] Problems connecting to the libvirtd server >>> To: Michal Privoznik <mprivozn@redhat.com> >>> >> >> [Please don't top

On 05/01/2017 09:57 AM, Stefano Ricci wrote: > 2017-05-01 7:32 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: >> On 04/30/2017 07:12 PM, Stefano Ricci wrote: >> >>> >>> The version used for backtrace is 3.2.0, now I have also tried the >>> current downloaded with git but the problem is always present. >>> This is the current version log

On 04/30/2017 07:12 PM, Stefano Ricci wrote: > > The version used for backtrace is 3.2.0, now I have also tried the > current downloaded with git but the problem is always present. > This is the current version log file, set as shown on the DebugLogs page: > > https://drive.google.com/open?id=0By9lwQyveHENdEt4aEtZcUV3ZEU Couple of my findings: 2017-04-30 16:19:34.894+0000:

Hello everyone I do not know if it is correct address this mailing lists but I can not use libvirt. I run compile libvirt version 2.2.0 into environment lfs stable with qemu 2.7.0 and have not had any problems. The program when it starts not report any errors in the log, with activated debug level file. Only when you try to connect with the following command virsh -c qemu:///system remains hung

On 11.10.2016 18:39, Stefano Ricci wrote: > ---------- Forwarded message ---------- > From: Stefano Ricci <sfn.rcc@gmail.com> > Date: 2016-10-11 12:35 GMT+02:00 > Subject: Re: [libvirt-users] Problems connecting to the libvirtd server > To: Michal Privoznik <mprivozn@redhat.com> > [Please don't top post on technical lists] > > There is not AppArmor and

There are a couple of problems with passthrough qemu: 1. virsh version/capabilities command executes "qemu -help" but this gives an error in my case because my customized qemu has to receive mandatory non-standard parameters "qemu -c -n -- -help". 2. Similarly when passing arguments as passthrough in a VMs XML. How can I make sure that these non-standard arguments are passed

On 06/03/2017 04:22 PM, Martin Kletzander wrote: > On Sat, Jun 03, 2017 at 09:22:58AM -0400, Michael C Cambria wrote: >> >> >> On 06/02/2017 09:53 AM, Michael C. Cambria wrote: >>> >>> >>> On 06/02/2017 09:43 AM, Martin Kletzander wrote: >>>> [adding back the ML, you probably hit reply instead of reply-all, this >>>> way other

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