On Wednesday, 27.05.2015 at 10:05, Martin Lucina wrote:
> > Does "xl mem-set 0 4051" make the messages stop? If not what about using
> > 4050?
>
> I'm not sure if this is due to my rebooting the dom0 since I reported this
> issue, it now appears to be using a
On Sunday, 17.05.2015 at 15:19, Ian Campbell wrote:
> One last thing... If you are able to try it then it would be interesting
> to know if the 4.0.x kernel from sid exhibits this behaviour too.
I can try this at some point next week when I have time to go and
physically kick the box in case it do
On Sunday, 17.05.2015 at 15:14, Ian Campbell wrote:
> On Thu, 2015-05-07 at 21:02 +0200, Martin Lucina wrote:
> > Note that despite the memory setting above, the dom0 has not been allocated
> > exactly the amount asked for:
> >
> > # xl list 0
> > Name
Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt9-3~deb8u1
Severity: normal
Dear maintainer,
my Xen dom0 is printing thousands of these messages to its logs:
# journalctl -b |grep "xen:balloon: Cannot add additional memory (-17)" | wc -l
126892
# uptime
20:50:08 up 3 days, 8:28, 7 user
i...@debian.org said:
> They are being uploaded to
> https://people.debian.org/~ijc/tmp/linux/3.16.7-ckt2-2~xen0/ right now.
> I've not booted them myself.
I have just tested these and netfront is working again for me so they're
good to go.
Thanks,
Martin
--
To UNSUBSCRIBE, email to debian-ke
i...@debian.org said:
> On Mon, 2014-12-29 at 12:56 +, Ian Campbell wrote:
>
> > > Should I reopen #767261 or file a new bug for this?
> >
> > A new bug would be best please.
>
> Actually, no need for this, I've applied the fixes locally and am just
> building them before pushing.
Note that
i...@debian.org said:
> On Mon, 2014-12-29 at 12:56 +, Ian Campbell wrote:
>
> > > Should I reopen #767261 or file a new bug for this?
> >
> > A new bug would be best please.
>
> Actually, no need for this, I've applied the fixes locally and am just
> building them before pushing.
Thanks. I
(Cc-ing debian-kernel, note I am not subscribed to this list, please Cc me
on replies)
Hi,
after updating linux-image-3.16.0-4-amd64 from 3.16.7-2 to the latest
3.16.7-ckt2-1 networking on my rumprun-xen [1] domUs stopped working.
Here is an excerpt of the failure during Mini-OS boot:
net TX rin
Hi,
following up on this bug, I tried booting the generic
linux-image-3.2.0-4-itanium kernel and this does not boot on my zx6000
either, with the exact same symptoms as the -mckinley kernel.
This means that none of the kernels supplied with wheezy boot :-(
Martin
signature.asc
Description: Dig
Hi,
I've just ran into this exact same problem after upgrading a zx6000 system
I run from squeeze.
The machine has two identical 1.4Ghz processors installed:
processor : 0
vendor : GenuineIntel
arch : IA-64
family : 31
model : 1
model name : Madison
revision : 5
archrev
10 matches
Mail list logo
