similar to: Re: Libvirtd Fails to Launch First Time

1. It takes minutes to start the virtual machine when I add "filterref" to libvirt.xml and run command "virsh start vm1". It also takes minutes to destroy the virtual machine. <interface type="bridge"> <mac address="fa:16:3e:fa:f7:94"/> <target dev="tap69e948b0-bf"/> <source bridge="br02"/> <model

Hi all: It takes more than 10 seconds to create a vm on a Dell R830 machine, but it takes less than 2 seconds on other machines. This is not normal, so I turned on the debug log for libvirtd. I analyzed the log and found that the time was spent on libvirtd calling qemu. Thread 95225 calls the qemuProcessLaunch interface at 14:22:30.129 and then builds the emulator command line, but the

I am trying to connect a KVM-QEMU VM to OVS-DPDK vhostuser port. But, I am encountering a few errors. Since I am very new to libvrt and Linux I am not able to sort them out. Any guidance in this regard would be a great help. These are my System Logs: Mar 28 18:03:04 dpdk-OptiPlex-5040 libvirtd.service: 1529: debug : virCommandRunAsync:2429 : About to run LIBVIRT_LOG_OUTPUTS=3:stderr

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 up. >> >> $ sudo systemctl status libvirtd.service >> ● libvirtd.service -

On 06/04/2017 05:46 AM, Martin Kletzander wrote: > 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,

I just built libvirt 0.9.3 from scratch on my Ubuntu 10.10 system. It appeared to build and install correctly. When running a command like 'virsh -c qemu:///session list --all', I get the following: error: Failed to connect socket to '@/home/heath/.libvirt/libvirt-sock': Connection refused error: failed to connect to the hypervisor When looking into it, I realized libvirtd

I just built libvirt 0.9.3 on my Ubuntu 10.10 box. It appears to have built correctly. When I try "virsh -c qemu:///session list --all" I get the following: error: Failed to connect socket to '@/home/heath/.libvirt/libvirt-sock': Connection refused error: failed to connect to the hypervisor After that, libvirtd isn't running as user heath as it did when I was using

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

Hi there I’ve just moved to libvirt-1.2.3 from 1.2.1; we use it for dealing with lxc containers I just wanted to report that everything went well for us with this new release, except for one little glitch At some point the lxc drivers seems to check that the kernel indeed has the netns feature built in Well in our environment this checks miserably fails; I haven’t been able to tell exactly why,

On Tue, Apr 08, 2014 at 04:53:44PM +0200, Thierry Parmentelat wrote: > Hi there > > I’ve just moved to libvirt-1.2.3 from 1.2.1; we use it for dealing with lxc containers > I just wanted to report that everything went well for us with this new release, except for one little glitch > At some point the lxc drivers seems to check that the kernel indeed has the netns feature built in

On Thu, Mar 26, 2015 at 02:55:04PM +0800, 梅磊 wrote: >Thanks for your reply, Martin, I have read the coredump, but I am not familiar with libvirt, so could you help me to figure it out why it crash? >Attachment is the coredump gdb output and all the generate files when libvirtd stop. > I forgot to ask you to install debuginfo packages to further investigate. But looking at the log only

Hi, I have encountered problem running virsh as non-root user. I am using eucalyptus software on top of KVM, eucalyptus requires to run virsh as non-root user. I've found that people had similiar issue posted in the list, but I didn't find the solution. I've tried few things. 1) put user eucalyptus in the libvirt group. 2) even changed owner /var/run/libvirt/libvirt-sock to

Hi, I have installed libvirt 4.9. libvirtd 4.9 takes a long time to come up. I enabled debug prints and also put my own prints Logs are below 2019-02-06 05:55:49.082+0000: 377: info : libvirt version: 4.9.0 2019-02-06 05:55:49.082+0000: 377: info : hostname: draco 2019-02-06 05:55:49.082+0000: 377: info : virObjectNew:248 : OBJECT_NEW: obj=0x558e782d8bb0 classname=virAccessManager

Hello All, Since 4.5.0-23.el7 version (Red Hat 7.7), when I launch pinned VM, libvirtd reset CPU affinity to all enabled in host CPUs, if it runs in custom cpuset. I can't reproduce this behavior with 4.5.0-10.el7_6.12 with the same kernel version (Red Hat 7.7). Libvirt runs in a custom cpuset 'libvirt', where the number of available cpus is restricted to 0,2,4,6,8. And this

Hi, I have installed libvirt 4.9. libvirtd 4.9 takes a long time to come up. I enabled debug prints and also put my own prints Logs are below 2019-02-06 05:55:49.082+0000: 377: info : libvirt version: 4.9.0 2019-02-06 05:55:49.082+0000: 377: info : hostname: draco 2019-02-06 05:55:49.082+0000: 377: info : virObjectNew:248 : OBJECT_NEW: obj=0x558e782d8bb0 classname=virAccessManager

Hi experts, The libvirtd can’t start on my server after the server interruption of power supply, the status is below: [root@openstack3 libvirt]# service libvirtd status Redirecting to /bin/systemctl status libvirtd.service libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: failed (Result: signal) since Tue 2015-03-24

Hi Martin: Actually, I have installed all the debuginfo for this coredump file. But the netcf debuginfo report "mismatch" as below: warning: the debug information found in "/usr/lib/debug/usr/lib64/libnetcf.so.1.4.0.debug" does not match "/lib64/libnetcf.so.1" (CRC mismatch). So I ignore this warning before. You can check what I did on the attachment

[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 nothing was logged when connections were attempted via >virsh. > >I also tried

I added libvirt-users@redhat.com back to the Cc for this response. Please don't remove the list address when responding to postings on a mailing list. A message to the list is *much* more likely to reach someone who knows the answer than is a private message to a single person. On 3/26/19 10:03 AM, Harsh Gondaliya wrote: > Mar 26 19:25:01 dpdk-OptiPlex-5040 libvirtd.service: 20423:

2017-10-24 12:58 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: > On Fri, Oct 20, 2017 at 10:12:19PM +0300, Matwey V. Kornilov wrote: >> >> 2017-10-20 17:14 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: >>> >>> 2017-10-20 15:16 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: >>>> >>>> On Fri, Oct 20, 2017