Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 714407 - virt-manager fails to start a guest
virt-manager fails to start a guest
Status: CLOSED DUPLICATE of bug 678555
Product: Fedora
Classification: Fedora
Component: virt-manager (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Cole Robinson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2011-06-18 22:54 EDT by Sam Varshavchik
Modified: 2011-07-01 10:29 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-07-01 10:29:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sam Varshavchik 2011-06-18 22:54:55 EDT
Occasionally, after the host running for a while without any guest VMs running, an attempt to start a VM fails with the following error dialog:

Error starting domain: Unable to create cgroup for VWIN: No such file or directory

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/engine.py", line 959, in asyncfunc
  File "/usr/share/virt-manager/virtManager/domain.py", line 1128, in startup
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 330, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: Unable to create cgroup for VWIN: No such file or directory

Once this error occurs, every attempt to start the VM fails with this error. Rebooting the host clears it up, and the VM can be started without any issues after the reboot.
Comment 1 Scott Dowdle 2011-06-20 15:10:01 EDT
I get this error too... both trying to create a new VM or trying to start an existing one.
Comment 2 Scott Dowdle 2011-06-20 15:11:33 EDT
Restarting libvirtd seems to fix the issue.
Comment 3 Cole Robinson 2011-07-01 10:29:19 EDT

*** This bug has been marked as a duplicate of bug 678555 ***

Note You need to log in before you can comment on or make changes to this bug.