cgred should be started before libvirt-bin
Bug #644669 reported by
Philippe Clérié
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libcgroup (Fedora) |
Invalid
|
Medium
|
|||
libcgroup (Ubuntu) |
Fix Released
|
Medium
|
Jon Bernard |
Bug Description
This bug was reported against libvirt-bin as #577264. There was a request to file a bug against libcgroup and 577264 was closed. The bug was not filed against libcgroup so I am filing it.
The bug description in 577264 is correct. Right now for example any VM started automatically at boot time works perfectly but anything started after that will trigger the reported error. The work around proposed also works.
I am running Lucid and my systems are up to date as of today (21-Sep-2010).
Regards
Philippe
Changed in libcgroup (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in libcgroup (Ubuntu): | |
assignee: | nobody → Serge Hallyn (serge-hallyn) |
tags: | added: upstart |
Changed in libcgroup (Fedora): | |
importance: | Unknown → Medium |
status: | Unknown → Invalid |
To post a comment you must log in.
Sometimes, on Rawhide, when I try to run a VM - that is, actually when I hit the Run button - it fails to run. An error dialog pops up, which says:
"Error starting domain: Unable to create cgroup for Fedora13: No such file or directory"
There's a Details drop-down. When dropped down, it says:
Traceback (most recent call last): virt-manager/ virtManager/ engine. py", line 878, in run_domain virt-manager/ virtManager/ domain. py", line 1321, in startup _backend. create( ) python2. 7/site- packages/ libvirt. py", line 333, in create
File "/usr/share/
vm.startup()
File "/usr/share/
self.
File "/usr/lib64/
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: Unable to create cgroup for Fedora13: No such file or directory
This doesn't *always* happen. I think it happens when the system's been running for a while before I try to run a VM, or possibly after a suspend/resume cycle.
When this happens, I can solve it by restarting libvirtd. I don't have to quit/resume virt-manager; I can restart libvirtd with virt-manager running, re-connect to localhost in virt-manager, and then successfully start the VM.