Bug 660402
| Summary: | Sometimes cannot start a VM without restarting libvirtd first ('Unable to create cgroup') | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> |
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | berrange, crobinso, hbrock, jforbes, mcepl, mcepl, virt-maint, wd |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-03-23 21:55:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Me too (restart of libvirtd service helps) and this has a duplicate in bug 666130. Duping to the libvirt bug *** This bug has been marked as a duplicate of bug 666130 *** |
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): File "/usr/share/virt-manager/virtManager/engine.py", line 878, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 1321, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 333, in create 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.