I'm running into a similar issue with a Debian6 system fully updated (standard
and -updates repos).
It's an IBM x3850, 16G of ram
I tried setting max_dom0_mem like stated here [1] but didn't solve the issue,
the server reboots after scrubbing free ram. Still hadn't chance to connect a
serial con
On Thu, 2011-01-06 at 10:17 +0100, Rik Theys wrote:
> Ian,
>
> On 01/06/2011 10:09 AM, Ian Campbell wrote:
> >> I can test some more options on this system for a few more days, but
> >> then I have to reinstall it.
> >
> > If you are able it would be useful to know if the tip of
> > xen-4.0-testin
Ian,
On 01/06/2011 10:09 AM, Ian Campbell wrote:
I can test some more options on this system for a few more days, but
then I have to reinstall it.
If you are able it would be useful to know if the tip of
xen-4.0-testing.hg (which is just about to become 4.0.2-rc1) works or
not. You would only
On Thu, 2011-01-06 at 10:01 +0100, Rik Theys wrote:
> Hi,
>
> I've tried the following combinations:
[...]
Thanks, I'll dig through the logs in a bit and see if anything shows up.
> This looks like a bug in the Xen hypervisor and not a kernel parameter?
I think so, the CONFIG_XEN_MAX_DOMAIN_MEM
On Tue, 2011-01-04 at 21:46 +0100, Rik Theys wrote:
> Iann
>
> >> Now I think of it can you also collect a similar log with the dom0_mem
> >> workaround in place, for comparisons sake.
>
> >Are you able to rebuild the kernel with
> >CONFIG_XEN_MAX_DOMAIN_MEMORY=128? If so then a log of that boo
Iann
Now I think of it can you also collect a similar log with the dom0_mem
workaround in place, for comparisons sake.
Are you able to rebuild the kernel with
CONFIG_XEN_MAX_DOMAIN_MEMORY=128? If so then a log of that boot for
comparison would be very interesting.
If you don't know how le
On Tue, 2011-01-04 at 14:08 +, Ian Campbell wrote:
> Now I think of it can you also collect a similar log with the dom0_mem
> workaround in place, for comparisons sake.
Are you able to rebuild the kernel with
CONFIG_XEN_MAX_DOMAIN_MEMORY=128? If so then a log of that boot for
comparison would
On Mon, 2011-01-03 at 09:59 +0100, Rik Theys wrote:
> Hi,
>
> On 12/22/2010 10:34 AM, Ian Campbell wrote:
> > I was wondering about clamping something in the kernel to correspond to
> > CONFIG_XEN_MAX_DOMAIN_MEMORY and avoid the issue but you say the crash
> > is after "x VCPUS" and before "Scrubb
Hi,
On 12/22/2010 10:34 AM, Ian Campbell wrote:
I was wondering about clamping something in the kernel to correspond to
CONFIG_XEN_MAX_DOMAIN_MEMORY and avoid the issue but you say the crash
is after "x VCPUS" and before "Scrubbing Free RAM" so I'm surprised the
dom0 kernel has run at this point
On Wed, 2010-12-22 at 07:20 +0100, Rik Theys wrote:
> Hi,
>
> On 12/14/2010 02:41 PM, Ian Campbell wrote:
> >> When adding dom0_mem=2G to the boot line, the system boots OK.
> >
> > I expect it will work ok with everything up to and including
> > dom0_mem=32G?
>
> It does.
Thanks.
> > It depend
Hi,
On 12/14/2010 02:41 PM, Ian Campbell wrote:
When adding dom0_mem=2G to the boot line, the system boots OK.
I expect it will work ok with everything up to and including
dom0_mem=32G?
It does.
It depends a bit on your usecase but it is often best recommended to use
dom0_mem= anyway, sinc
On Mon, 2010-12-13 at 11:42 +0100, Rik Theys wrote:
> Package: linux-2.6
> Version: 2.6.32-29
> Severity: normal
>
> When booting Xen 4.0.1 with the Debian dom0 kernel, Xen hangs on startup
> after saying that the
> system has x VCPUS and before starting the "Scrubbing Free RAM".
> This looks re
12 matches
Mail list logo
