similar to: libvirtd via unix socket using system uri

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 4/29/19 5:42 PM, lameventanas@gmail.com wrote: > > > 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

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 group, added my normal user to the > libvirt group, and made sure the

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

Dell Customer Communication Hi All, I am using Compiled against library: libvirt 1.2.9 Using library: libvirt 1.2.9 Using API: QEMU 1.2.9 Running hypervisor: QEMU 2.1.2 I want user to provide username and password authentication to virConnectPtr virConnectOpenAuth(const char *name, virConnectAuthPtr auth, unsigned int flags) to login remotely for the qemu

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 work! I have to do far more > thorough threat analysis than I would do if I knew which capabilities it > had. So

On 4/30/19 3:15 PM, Peter Crowther wrote: > 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?

We accidentally moved /var/lib/libvirt/qemu to another directory which is on a different disk partition, then we moved it back; however, that caused changing the inode ids of the files inside /var/lib/libvirt/qemu including the socket files ( <instance>.monitor ) of the running VMs. The problem we are facing is that when libvirtd is restarted it terminates the running VMs with "error :

https://bugs.freedesktop.org/show_bug.cgi?id=47846 Bug #: 47846 Summary: Nouveau -> overscan using HDMI Classification: Unclassified Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Hi all, When I try to start libvirtd, using "libvirtd -d", error notification shown below:error : virPidFileAcquirePath:345 : Failed to acquire pid file '/$HOME/.libvirt/libvirtd.pid': Resource temporarily unavailable Using "libvirtd -v", show: "libvirtd: error: Unable to obtain pidfile. Check /var/log/messages or run without --daemon for more

Hi All, I have a question regarding the uses of libvirtd. We have the following situation to manage. We have several hosts with libvirtd running. We have one management application to manage different VMs launched in those different hosts. We want to configure the system such a way so that one libvirtd can collect information about the VMs launched by other libvirtd running in different

Hi, There is a strange issue in the CentOS 7.2 libvirtd 1.2.17 service. If there is a symlink in the "/etc/libvirt/qemu/autostart/" which is created before the libvirtd service is started, libvirtd wont start. Deleting the symlink from the autostart folder, then starting the libvirtd service works. Is this a know issue ? We have found this on 4-5 servers. Regards,

Hi All, Am new to this list, and have asked in #ovirt / ovirt-users list and they pointed me to here ... I've seen libvirtd using ~11 GB of resident memory after the host has been running for about 60+ days with about 40 VMs running on it. The versions I'm currently running are : libvirt.x86_64 0.9.10-21.el6_3.7 libvirt-client.x86_64 0.9.10-21.el6_3.7

Hi everybody, I've set up an new CentOS 7.6.1810 server. Then, via yum I installed qemu-kvm libvirt libvirt-python libguestfs-tools virt-install. There were no problems. But when I try to systemctl start libvirtd I get the following message: "libvirtd: process 472: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)"

Hi, I'm having a problem with libvirtd (backend being kvm) losing its if I restart it with /etc/init.d/libvirtd restart. What I did was: Start libvirtd Connect to it using virsh Create a new storage pool with pool-create-as Create some volumes with vol-create-as Create some virtual machines with create Restart libvirtd using /etc/init.d/libvirtd restart Reconnect with virsh After

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

Hello List like described in the topic I have a problem with starting the libvirtd. I'm a complete newbie with libvirtd, today I heard the first time that such a daemon exists after I get the message that our webserver isn't running (a former colleague has installed this system). We have the following configuration: A Ubuntu based host on which our webserver runs within a qemu virtual

libvirtd is starting dnsmasq! This is on RHEL5.5 I don't see it mentioned in /etc/init.d/libvirtd or /etc/libvirt/* or /etc/sysconfig/libvirtd 4337 ? S 0:00 /usr/sbin/dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --listen-address 192.168.122.1 --except-interface lo --dhcp-range 192.168.122.2,192.168.122.254

Hello, I've done some research prior to this and the answer is clear that libvirtd doesn't compile on BSD or OSX, but I'd like to know more details about this, if I can have a bit of your time: * Are there any current efforts to get libvirtd running on BSD? * What are the blockers to getting it running? * My main goal is really to, at first only control VirtualBox, so KVM/Xen/etc is