On Thu, Nov 25, 2010 at 12:16:19AM +0100, Marek Kaszycki wrote:
> 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 http://wiki.xen.org/xenwiki/XenParavirtOps
> 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 locations:
Try adding "dom0_mem=1024M loglvl=all guest_loglvl=all" for xen.gz.
> Thanks in advance for all your help.
You need to set up a serial console, enable all debugging output options
from both Xen and dom0 kernel, and then paste the full serial log here.
Also check chapter "Are there more debugging options I could enable to
troubleshoot booting problems?"
from XenParavirtOps wiki page.
Xen-users mailing list