Il 03/03/2015 12:47, Fabio Fantoni ha scritto:
Il 03/03/2015 12:09, David Vrabel ha scritto:
On 03/03/15 09:05, Fabio Fantoni wrote:
Il 02/03/2015 17:31, David Vrabel ha scritto:
On 02/03/15 16:23, Jan Beulich wrote:
On 02.03.15 at 16:52, wrote:
On systems with wheezy as dom0 and kernel 3.2
Il 03/03/2015 12:09, David Vrabel ha scritto:
On 03/03/15 09:05, Fabio Fantoni wrote:
Il 02/03/2015 17:31, David Vrabel ha scritto:
On 02/03/15 16:23, Jan Beulich wrote:
On 02.03.15 at 16:52, wrote:
On systems with wheezy as dom0 and kernel 3.2 it seems there are no
visible problems.
After u
On 03/03/15 09:05, Fabio Fantoni wrote:
> Il 02/03/2015 17:31, David Vrabel ha scritto:
>> On 02/03/15 16:23, Jan Beulich wrote:
>> On 02.03.15 at 16:52, wrote:
On systems with wheezy as dom0 and kernel 3.2 it seems there are no
visible problems.
After updating the kernel to 3.
Il 02/03/2015 17:31, David Vrabel ha scritto:
On 02/03/15 16:23, Jan Beulich wrote:
On 02.03.15 at 16:52, wrote:
On systems with wheezy as dom0 and kernel 3.2 it seems there are no
visible problems.
After updating the kernel to 3.16 (from backports repository), after
starting the domUs, I get
On 02/03/15 16:23, Jan Beulich wrote:
On 02.03.15 at 16:52, wrote:
>> On systems with wheezy as dom0 and kernel 3.2 it seems there are no
>> visible problems.
>> After updating the kernel to 3.16 (from backports repository), after
>> starting the domUs, I get many of these errors in syslog
>>> On 02.03.15 at 16:52, wrote:
> On systems with wheezy as dom0 and kernel 3.2 it seems there are no
> visible problems.
> After updating the kernel to 3.16 (from backports repository), after
> starting the domUs, I get many of these errors in syslog and kern.log
> (infinite loop):
> xen:ball
