* Guido Günther [16-06-2013 10:07 EEST]:
> Hi Edward,
> thanks for your feedback!
No problem.
> That's from virt-manger itself. It's not the daemon's log (see either
> syslog or /var/log/libvirt/libvirtd.log).
I got the debug output from libvirt (it was sent to stderr) from these
runs but I did
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 fu
* Guido Günther [15-06-2013 16:26 EEST]:
> It would be awesome if you guys would provide some information to
> reproduce like:
>
> * which version you were upgrading from
0.9.12-11 -> 1.0.5-3
> * which VMs were running
It happens when trying to create a new vm and also when trying to start an
On Sat, Jun 15, 2013 at 12:37:06PM +1000, Dean Hamstead wrote:
> I am experiencing the same problem.
>
> umounting cgroups solves the problem but almost certainly results in
> the machines having no cgroup enforced boundaries.
>
> perhaps this is a permissions problem and libvirt cant create a
>
I am experiencing the same problem.
umounting cgroups solves the problem but almost certainly results in
the machines having no cgroup enforced boundaries.
perhaps this is a permissions problem and libvirt cant create a
'machines' group? or perhaps its not actually creating one at all and
fa
5 matches
Mail list logo
