I saw this effect on some recent pv_ops kernels (esp. after 126.96.36.199);
try enabling "optimize for size" in the kernel config (general options)
if it's not enabled already. It solved the problem for me, but I've got
no time to investigate this issue now.
Would be interesting if it is the reason for you reboots, too.
If this is reproducible, it seems like some XEN code fails on -O2 or
whichever is used without this option.
Am 25.11.2010 00:16, schrieb Marek Kaszycki:
> Hi Everyone
> I have sorted out the initial issues I've had and decided to give Xen
> another go.
> I'm trying to run Xen using kernel 2.6.37-rc3 (previous attempt with
> rc1 failed, and when I gave it a second go, rc3 was already out).
> As previously, 2.6.37-rc3 boots fine natively. 2.6.32 boots natively
> and under Xen as dom0, but I have reservations against running 2.6.32,
> please bear with me.
> Booting 2.6.37-rc3 under Xen (4.0.1-1, squeeze) causes a reboot right
> after "Scrubbing free RAM" appears -- I believe some tables appear
> just to blink on the screen right afterwards, but I am unable to
> confirm just what exactly is there -- I don't have a serial console
> attached -- so I am unable to capture the output from Xen or dom0.
> I am at a loss as to what causes this. I have compiled the kernel
> myself, following the advice on
> Since there are additional lines after the error message, I believe
> the hypervisor completes its init and the reboot happens just when the
> hypervisor wants to boot dom0.
> I have checked the threads:
> My system has just 8 GB of RAM and just one CPU. Following the advice,
> I have added 'noreboot' to Xen entry in grub.cfg, but even though Xen
> doesn't reboot the system now, it's worse because right after
> "Scrubbing free RAM", the screen goes blank, no cursor or anything,
> and just stays this way.
> I have uploaded the grub.cfg and kernel .config to the following
> Thanks in advance for all your help.
> Xen-users mailing list
Xen-users mailing list