similar to: libvirtd using 11GB

Hi, I'm having this odd problem with being unable to install gcc, this is what I tried and what I'm getting as an error: $ sudo yum install gcc.x86_64 Loaded plugins: security Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package gcc.x86_64 0:4.4.6-4.el6 will be installed --> Processing Dependency: cpp = 4.4.6-4.el6 for package:

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

On Tue, 30 Apr 2019 at 10:40, Michal Privoznik <mprivozn@redhat.com> wrote: > Is there any problem running libvirtd as root? > > Yes, in the regulated environment in which I work! I have to do far more thorough threat analysis than I would do if I knew which capabilities it had. So far, we've accepted the extra work; but it would be wonderful to be able to run a locked-down

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

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

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 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 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 Tue, 30 Apr 2019 at 10:48, Daniel P. Berrangé <berrange@redhat.com> wrote: > On Tue, Apr 30, 2019 at 10:45:03AM +0100, Peter Crowther wrote: > > On Tue, 30 Apr 2019 at 10:40, Michal Privoznik <mprivozn@redhat.com> > wrote: > > > > > Is there any problem running libvirtd as root? > > > > > > Yes, in the regulated environment in which I

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:

Thanks, I discovered I had wrong permissions for /var/lib/libvirt/qemu/, after setting them to drwxr-x--x. qemu qemu and executing daemon-reload libvirtd.service exists now on my vms :) However - I'm not able to get it to run. In the journal I see the message libvirtd[6800]: Unable to import CA certificate list /etc/pki/vdsm/certs/cacert.pem I have verified its permissions and that it's

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

Thanks, Michal, On my laptop I do have libguestfs and libvirt-daemon-qemu. both libvirtd.service and libvirtd.socket are running ok on my laptop I just realized I haven't mentioned - my vms intend to serve as hosts themselves, and that's why they, too, need to have libvirtd.service running on them. up to recently I didn't have such a problem when I installed a vm on my laptop -

On 29/04/2019 22.01, Michal Privoznik wrote: > On 4/29/19 1:06 PM, lameventanas@gmail.com wrote: >> I want to run libvirtd as a special user, and allowing users that belong >> to a special group to connect via qemu+unix:///system (eg: unix socket). >> >> I did everything necessary to do so: created a libvirt user and group, >> added the libvirt user to the kvm

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

1. I run a user domain like this: [root@kvm1 ~]# qemu-system-x86_64 -enable-kvm -m 1G -smp 4 /images/test1.img WARNING: Image format was not specified for '/images/test1.img' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to

hi,all requested operation is not valid: domain is not running but exactly vm is running when call getCPUStats,interfaceStats... system: centos6.3 libvirt-0.9.10-21.el6_3.7.x86_64 libvirt-python-0.9.10-21.el6_3.7.x86_64 thanks -------------- next part -------------- An HTML attachment was scrubbed... URL:

if I understand correctly then I shouldn't have installed libvirt-daemon on the guests VMs? On Tue, May 12, 2020 at 2:34 PM Daniel P. Berrangé <berrange@redhat.com> wrote: > On Tue, May 12, 2020 at 02:25:29PM +0300, Dana Elfassy wrote: > > Thanks, Daniel > > I verified I had libvirt-daemon rpm on my laptop and reloaded its units, > > but that didn't solve the

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When