similar to: Ignoring invalid update watch -1

I'm seeing this problem with both the virtio and e1000 driver with both linux and windows guests. About 5 - 10% of the VMs I launch have network problems. They seem to always get an IP from the DHCP server (dnsmasq), but afterwards either they can not make an outside network connection or they lose connectivity at a later time. Sometimes the connectivity comes back, sometimes it doesn't.

Hello, I'm receiving a lot of these since a couple of days ago: libvirtd: 16:30:10.960: error : qemudDispatchServer:1282 : Too many active clients (20), dropping connection I'm trying to figure out where all these active clients are coming from. I have a daemon running the interacts with libvirtd, but it only creates two long-lived connections (I'm very sure). What constitutes an

hello everybody and happy new year! I am a newbie in libvirt use, and I use it mostrly throught OpenNebula. Anyway, I noticed that one of the nodes can be a destination of a livemigrate but not the source. This is the environment: 4 blades nicknamed(*) red3, red9, red10, red11, each with 8 Intel E5506 cores (@ 2.13GHz) running CentOS 5 and KVM as hyoervisor. (*) these are names I

Me again! Think we've found it. By diving into the LXC logs for the specific container, we found this: 2014-04-17 21:07:06.066+0000: 2861: debug : virCgroupSetValueStr:678 : Set value '/sys/fs/cgroup/devices/machine/oshi32134.libvirt-lxc/devices.allow' to 'c 189:130 rw' Looks like libvirt the permission to 'rw', not 'rmw' [1], so no surprise that when it

Ah, nevermind, think my last post may not have been entirely correct. We've spent some more time correlating the log output from our failed LXC startup via libvirt [1] with libvirt code from the 1.2.2 tag. Interestingly, the error we get back is different, and digging through the multitudes of logs, nothing comes up about 'operating not permitted' regarding the USB bus that I saw

Further followups! We are correlating DEBUG-level output from libvirt with the libvirt 1.2.2 code to try to figure out what libvirt is doing under the hood. Even though we have the log level set to 1 (info) in our libvirtd.conf, we are not seeing the VIR_DEBUG() [1] statements being printed out. There are tons of other presumably-debug lines of output showing up in our log. We are sort of

I have two hosts, vm1 and vm2, which are both running libvirt 0.7.0. They share a common ocfs2 file system that resides on a san, and have identical network configurations. I am running qemu-kvm 0.11.0 on ubuntu 9.10 servers. I start base32 on vm1 and it comes up (it also runs fine if started on vm2). Then from vm2 I do: vm2#: virsh -c qemu://vm1/system migrate --live base32 qemu://vm2/system

Hello everybody, i oberserve a strange behavior of libvirtd. I have an xen vm (HVM, windows xp) that i restore from an statefile. If i do so, it works. But if i do that in an loop, where i restore the vm, let it run 60 seconds, destroy it, wait 30 second, and then i restore again, it runs 91 times and then libvirt crashed and the give me in the syslog logs the messages after "from

Hi, Anybody know how to build libvirt on Mac OSX 10.6 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20100215/ee529872/attachment.htm>

Yeah, AppArmor is enabled, but I put everything (that I could find) into complain mode: $ sudo apparmor_status apparmor module is loaded. 12 profiles are loaded. 3 profiles are in enforce mode. lxc-container-default lxc-container-default-with-mounting lxc-container-default-with-nesting 9 profiles are in complain mode. /sbin/dhclient /usr/bin/lxc-start

Hi all, I have a problem with libvirt, it works slow. For example, "virsh list" takes 6..7 seconds. I found this in libvirt log: ... 11:38:12.765: debug : virEventDispatchHandles:477 : Dispatch n=8 f=56 w=9 e=1 0x25ce830 11:38:12.765: debug : virEventUpdateHandleImpl:147 : Update handle w=8 e=3 11:38:12.765: debug : virEventInterruptLocked:668 : Interrupting 11:38:12.766: debug :

To follow up on this a little bit, tail'ing kern.log while trying to get our little container up doesn't yield anything with apparmor complaining, so, unless I'm looking in the wrong spots for apparmor logs (which I don't think so, as I see other apparmor-related log entries in kern.log), I am not entirely sure this is an apparmor issue at this point. On Wed, Apr 16, 2014 at 3:25

All, I just downloaded and installed libvirt-bin and this is my first email to the group, so I apologize in advance if my questions are too naive! So, I am trying to access VMs running on xen3.2 hypervisor (host with kernel 2.6.24-24-xen) using virt-manager installed on a machine running Ubuntu 9.04 (client machine). I got to the point where I can connect to my virtual machine and my domain-0

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 systemd: Starting Virtualization daemon... >>> May  2 11:02:06 hl308-3

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 <http://bugs.centos.org>, 2019-04-24-14:04:12, x86-01.bsys.centos.org) > May  2 11:02:06

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

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

I have over 20 guests running on a particular host and the three longest running ones are missing the network device information in their XML description: <interface type='network'> <mac address='54:52:10::f2:c5'/> <source network='local'/> </interface> Compared to the others which have: <interface

Hi guys. In hope that an expert read this - what is, can be, the below a result of? 12284 still running (86040) Invalid value '-1' for 'cpu.max': Invalid argument 12284 still running (86035) 12284 still running (86030) this is a snippet from libvirtd logs which is a consequence of what ovirt's engine setup is doing. To troubleshoot ansible playbooks which is what engine

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