Hi Edward,
thanks for your feedback!
On Sun, Jun 16, 2013 at 03:50:59AM +0300, Edward J. Shornock wrote:
[..snip..]
> Trying to start an existing VM in virt-manager:
>
> 2013-06-16 03:34:26,075 (engine:878): Starting vm 'wheezy'
> 2013-06-16 03:34:26,082 (asyncjob:184): Creating async job for function
> cb=<function tmpcb at 0x35ccb18>
> 2013-06-16 03:34:26,320 (error:80): dialog message: Error starting domain:
> Unable to initialize /machine cgroup: Invalid argument: Error starting
> domain: Unable to initialize /machine cgroup: Invalid argument
That's from virt-manger itself. It's not the daemon's log (see either
syslog or /var/log/libvirt/libvirtd.log). No need to provide more
feedback at this point. I'll try to reproduce with the version
information you gave (won't happen in the near future unfortunately
though).
Thanks again!
-- Guido
>
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in
> cb_wrapper
> callback(asyncjob, *args, **kwargs)
> File "/usr/share/virt-manager/virtManager/asyncjob.py", line 117, in tmpcb
> callback(*args, **kwargs)
> File "/usr/share/virt-manager/virtManager/domain.py", line 1160, in startup
> self._backend.create()
> File "/usr/lib/python2.7/dist-packages/libvirt.py", line 698, in create
> if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: Unable to initialize /machine cgroup: Invalid argument
>
>
> Running libvirt in debug mode doesn't show anything more.
>
> > I do think this is related to libvirtd changing cgroup layout but
> > without any detail this is impossible to tell.
>
> I think so too.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
