Re: [libvirt] Unable to create cgroup for driver
Jun
To avoid just configure --without-lxc
Daniel here is the back-trace
(Didn't have time to explore)
[root@rain8 libvirt-0.7.0]# ./qemud/libvirtd
16:11:02.700: warning : qemudStartup:521 : Unable to create cgroup for driver: No such
device or address
Segmentation fault (core dumped)
gdb ./qemud/.libs/libvirtd ../core.19690
(gdb) where
#0 virDomainEventCallbackListFree (list=0x0) at domain_event.c:41
#1 0x000000000043ecee in lxcShutdown () at lxc_driver.c:1582
#2 0x000000000043f122 in lxcStartup (privileged=1) at lxc_driver.c:1523
#3 0x00007f05103e03c2 in virStateInitialize (privileged=1) at libvirt.c:785
#4 0x00000000004134cf in main (argc=6776272, argv=<value optimized out>) at
qemud.c:2970
________________________________
From: Daniel P. Berrange <berrange(a)redhat.com>
To: Jun Koi <junkoi2004(a)gmail.com>
Cc: libvir-list(a)redhat.com
Sent: Tuesday, August 11, 2009 12:25:25 PM
Subject: Re: [libvirt] Unable to create cgroup for driver
On Tue, Aug 11, 2009 at 06:04:29PM +0900, Jun Koi wrote:
On Tue, Aug 11, 2009 at 6:00 PM, Daniel P.
Berrange<berrange(a)redhat.com> wrote:
> On Tue, Aug 11, 2009 at 10:03:32AM +0900, Jun Koi wrote:
>> Hi,
>>
>> The libvirt 0.7 has a following error when i start libvirtd:
>>
>> warning : qemudStartup:521 : Unable to create cgroup for driver: No
>> such device or address
>
> That is not an error, it is a expected warning if you don't have any
> cgroups mount. It is designed to continue working
>
Could you explain what is that cgroups mount, and why I need that??
Cgroups are principally a resource control mechanism for processes.
There are countless tunables, and a libvirt will use certain ones,
specifically for QEMU it currently uses the 'cpu' and 'devices'
controllers, while LXC also uses 'memory' and 'cpuacct'.
You can activate it by mounting the desired controllers before libvirtd
starts. eg
mkdir /dev/cgroup
mount -t cgroup none /dev/cgroup -o cpu,memory,devices
The fact is that I never had this problem before (with older git
version)
That's because this is a new feature. It is optional, hence why it is
merely a warning message, and not an error message.
>> Then it fails to start.
>>
>> How can I fix this?
>
> You'll need to provide more information than this. What exactly fails
> to start ? The entire daemon, just the QEMU driver, or something else ?
> Does it exit, does it crash ? Get a debug log when it fails, etc
When I run "libvirtd -v", it simply reports error like:
"warning : qemudStartup:521 : Unable to create cgroup for driver: No
such device or address
Segmentation fault"
Can you capture a stack trace in GDB, and/or get the debug logs from
running with LIBVIRT_DEBUG=1. There could be a thousand & one other
things being done between the time the warning message is printed, and
it actually crashes, so we can't assume they're neccessarily related
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
--
Libvir-list mailing list
Libvir-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Attachments:
- attachment.html (text/html — 6.8 KB)