Hi, I've got a small problem using libvirt-1.0.5.1 (with the latest patch in the v1.0.5-maint branch on git added). I'm using slackware64-14.0 but the situation is exactly the same described on a debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707201 When trying to start a domain I got error: Failed to start domain debian-wheezy-xfce error: Unable to initialize /machine cgroup: Invalid argument with this in libvirtd.log virCgroupDetect:373 : Failed to detect mounts for /machine qemuInitCgroup:425 : Unable to initialize /machine cgroup: Invalid argument and the error goes away if I unmount /sys/fs/cgroup. Reverting to 1.0.4 fixes this, but this exposes another thing that I report even if I'm not sure it's an error: if I create a domain with 1.0.5.1 (I use the latest virt-manager to do this), in the xml of the domain there's a line that doesn't seem to have the close tag <controller type='pci' index='0' model='pci-root'/> If I revert to 1.0.4 the domain with this line in the xml doesn't even get listed between the available domains and I got this in libvirtd.log virDomainControllerDefParseXML:4838 : internal error Unknown controller type 'pci' deleting the interested line make it available again. Please let me know if you need further informations on the matters. Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20130522/1c58d897/attachment.htm>
On 05/22/2013 11:01 AM, Matteo Bernardini wrote:> Hi, > > I've got a small problem using libvirt-1.0.5.1 (with the latest patch in > the v1.0.5-maint branch on git added). > I'm using slackware64-14.0 but the situation is exactly the same described > on a debian bug > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707201 > > When trying to start a domain I got > > error: Failed to start domain debian-wheezy-xfce > error: Unable to initialize /machine cgroup: Invalid argument > > with this in libvirtd.log > > virCgroupDetect:373 : Failed to detect mounts for /machine > qemuInitCgroup:425 : Unable to initialize /machine cgroup: Invalid argument > > and the error goes away if I unmount /sys/fs/cgroup. > > Reverting to 1.0.4 fixes this,sorry, just to report the same effect with 1.0.6: this is my /sys/fs/cgroup layout http://pastebin.com/Gxsgb8KG and this is the corresponding stuff in /var/lib/libvirt/libvirtd.log (with log level 1) when I issue a # virsh start s64cont http://pastebin.com/Rhg3tSzt as I've had a look at http://libvirt.org/cgroups.html I'm just wondering if systemd is necessary (we don't have it in Slackware) or I'm simply missing something... Matteo
Daniel P. Berrange
2013-Jun-07 10:24 UTC
Re: [libvirt-users] cgroup error starting domains
On Thu, Jun 06, 2013 at 06:26:23PM +0200, Matteo Bernardini wrote:> On 05/22/2013 11:01 AM, Matteo Bernardini wrote: > > Hi, > > > > I've got a small problem using libvirt-1.0.5.1 (with the latest patch in > > the v1.0.5-maint branch on git added). > > I'm using slackware64-14.0 but the situation is exactly the same described > > on a debian bug > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707201 > > > > When trying to start a domain I got > > > > error: Failed to start domain debian-wheezy-xfce > > error: Unable to initialize /machine cgroup: Invalid argument > > > > with this in libvirtd.log > > > > virCgroupDetect:373 : Failed to detect mounts for /machine > > qemuInitCgroup:425 : Unable to initialize /machine cgroup: Invalid argument > > > > and the error goes away if I unmount /sys/fs/cgroup. > > > > Reverting to 1.0.4 fixes this, > > sorry, just to report the same effect with 1.0.6: this is my > /sys/fs/cgroup layout > > http://pastebin.com/Gxsgb8KG > > and this is the corresponding stuff in /var/lib/libvirt/libvirtd.log > (with log level 1) when I issue a > > # virsh start s64cont > > http://pastebin.com/Rhg3tSzt > > > as I've had a look at > > http://libvirt.org/cgroups.html > > I'm just wondering if systemd is necessary (we don't have it in > Slackware) or I'm simply missing something...No, systemd is definitely /not/ mandatory. Can you provide your /proc/mounts file contents Libvirt seems to be failing to detect the mount points 2013-06-06 15:49:37.688+0000: 29305: debug : virCgroupNewPartition:1248 : path=/machine create=1 controllers=5f 2013-06-06 15:49:37.688+0000: 29305: debug : virCgroupNew:808 : parent=(nil) path=/machine controllers=95 2013-06-06 15:49:37.688+0000: 29305: debug : virCgroupDetect:359 : group=0x7f601007f6e0 controllers=95 path=/machine parent=(nil) 2013-06-06 15:49:37.688+0000: 29305: error : virCgroupDetect:366 : Failed to detect mounts for /machine 2013-06-06 15:49:37.688+0000: 29305: error : qemuInitCgroup:733 : Unable to initialize /machine cgroup: Invalid argument also do you have anything in /etc/libvirt/qemu.conf set for the cgroups controllers setting ? Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|