similar to: What can cause "libvirtd dead but pid file exists."

Dear All, Please find few minutes from your time and guide us with some pointers if possible. We are facing a libvirtd crash when we are trying to connect to qemu by default TLS transport. # virsh -c qemu+tls://localhost/system version error: authentication failed: TLS handshake failed A TLS packet with unexpected length was received. error: failed to connect to the hypervisor I used my own CA

Hi, Eric: I compiled libvirt-0.9.8 source code with the msys environment on windows xp. the compiltion was successed. but when I connect the remote host using virsh.exe, it occured error like: error: Failed to connect to the hypervisor error: Unable to set close-on-exec flag: No such file or directory Is there something wrong? give me some help, thanks! xuanmao_001 -------------- next part

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 want to know when I press run button. start a domain. What is the procedure of libvirt internal. I know it will call virDomainCreate(),then qemuDomainStart() -> qemuDomainStartWithFlags(). what is the next? xuanmao_001 -------------- next part -------------- An HTML attachment was scrubbed... URL:

I want to know if libvirt supporting qemu domain Autostart? my libvirt version is 0.9.8. xuanmao_001 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20120716/5fd5dedb/attachment.htm>

Hi, Eric: I want to reboot vm using libvirt reboot api virDomainReboot(). but it occured error like following: "error: Failed to reboot domain abc" "error: Requested operation is not valid: Reboot is not supported without the JSON monitor". I updated qemu version,such as "qemu-kvm-1.2.0", it still like that. can you give me any ideas? my libvirt version: 0.9.8.

Libvirt Version: 0.9.8 Hi: I added a new api for qemu_driver. and both added libvirt.c and remote. I tested it and it worked well. the function of this new api was add a new field in xml config of domain. (I added it like qemudDomainSetMemoryFlags)at the same time, I added a new member to struct virDomainDef. then I tested xml config converted to virDomaindef and virDomainDef converted to xml

2017-10-20 14:59 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: > On Thu, Oct 19, 2017 at 09:11:00PM +0300, Matwey V. Kornilov wrote: >> >> Hello, >> >> I use libvirt 3.3.0 and qemu 2.9.0 >> >> My domain XML spec is the following: >> >> <domain type='qemu'> >> <name>s390_generic</name> >>

Hi all. I run into trouble, while try to start libvirtd inside docker container (actually it is LXC container). During startup libvirtd can't load shared library libvirt-qemu.so.0 (and strace results looks very odd). * I run libvirtd as root. * libvirt-bin - 0.9.8-2ubuntu17 * selinux/apparmor both disabled. * No other security extension are used. * No sticky bits are set. * Required library

Hello, I use libvirt 3.3.0 and qemu 2.9.0 My domain XML spec is the following: <domain type='qemu'> <name>s390_generic</name> <uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu

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

Am 02.05.2019 um 11:43 schrieb Martin Kletzander: > On Thu, May 02, 2019 at 11:22:39AM +0200, Lothar Schilling wrote: >> 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

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

Am 03.05.2019 um 16:43 schrieb Martin Kletzander: > On Thu, May 02, 2019 at 02:25:28PM +0200, Martin Kletzander wrote: >> On Thu, May 02, 2019 at 01:07:32PM +0200, Michal Privoznik wrote: >>> On 5/2/19 12:08 PM, Lothar Schilling wrote: >>> >>>> I turned logging up to maximum. That's all I get: >>>> >>>> May  2 11:02:06 hl308-3

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,

On Thu, May 02, 2019 at 01:07:32PM +0200, Michal Privoznik wrote: >On 5/2/19 12:08 PM, Lothar Schilling wrote: > >> I turned logging up to maximum. That's all I get: >> >> May  2 11:02:06 hl308-3 systemd: Starting Virtualization daemon... >> May  2 11:02:06 hl308-3 libvirtd: 472: info : libvirt version: 4.5.0, package: 10.el7_6.7 (CentOS BuildSystem

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

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 -

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