Bug#732666: about libvirt commit 96f9aae6a

2013-12-31 Thread Guido Günther
On Mon, Dec 30, 2013 at 11:35:48PM +0100, phep wrote: > Le 30/12/2013 16:34, Guido Günther a écrit : > >Current git will not mount the memory cgroup anymore by default - only > >with the cgroup_enable=memory cmdline. > > OK, thank you Guido, I think I got the whole thing clearer now; I > misinterp

Bug#732666: about libvirt commit 96f9aae6a

2013-12-30 Thread phep
Le 30/12/2013 16:34, Guido Günther a écrit : Current git will not mount the memory cgroup anymore by default - only with the cgroup_enable=memory cmdline. OK, thank you Guido, I think I got the whole thing clearer now; I misinterpreted your answer to Mike in message #20 in believing modifying

Bug#732666: about libvirt commit 96f9aae6a

2013-12-30 Thread Guido Günther
On Mon, Dec 30, 2013 at 02:52:49PM +0100, phep wrote: [..snip..] > Paramétrage de libvirt-bin (1.2.0-1) ... > [ ok ] Stopping libvirt management daemon: libvirtd not running. > [] Starting libvirt management daemon: libvirtdmount: special > device cgroup_memory does not exist But only iff you

Bug#732666: about libvirt commit 96f9aae6a

2013-12-30 Thread phep
Hi, Le 30/12/2013 13:19, Guido Günther a écrit : On Mon, Dec 30, 2013 at 11:23:57AM +0100, phep wrote: Hi, Thank you for packaging libvirt, Since I just hit the problem this morning while upgrading my laptop, I tried applying the changes referenced in the subject line. Alas, as I feared as I

Bug#732666: about libvirt commit 96f9aae6a

2013-12-30 Thread Guido Günther
On Mon, Dec 30, 2013 at 11:23:57AM +0100, phep wrote: > Hi, > > Thank you for packaging libvirt, > > Since I just hit the problem this morning while upgrading my laptop, > I tried applying the changes referenced in the subject line. > > Alas, as I feared as I read it, the patch does not fix the

Bug#732666: about libvirt commit 96f9aae6a

2013-12-30 Thread phep
Hi, Thank you for packaging libvirt, Since I just hit the problem this morning while upgrading my laptop, I tried applying the changes referenced in the subject line. Alas, as I feared as I read it, the patch does not fix the issue : "memory" was already in the mount list. One still has to