[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Advice on compiling Xen 4.1.2 on Debian 6.0.4 Kernel 3.1.12

On 4/12/2012 3:14 AM, Ian Campbell wrote:
On Wed, 2012-04-11 at 16:56 +0100, cyberhawk001@xxxxxxxxx wrote:
I am still trying to get Xen to run on my machine. This time around i
did the following:

1.) installed a clean Debian Squeeze
2.) Compiled and installed Kernel 3.3.1 (Config was setup with all
defaults using menuconfig AND all xen options were set to Y)
3.) Rebooted into Kernel 3.3.1
4.) Upgraded to Debian Wheezy
5.) Setup Serial output to a second PC using null-model cable and
added the following to /etc/default/grub
GRUB_CMDLINE_XEN="loglvl=all guest_loglvl=all com1=115200,8n1,0x3f8,4 
GRUB_CMDLINE_LINUX="console=hvc0 earlyprintk=xen"
6.) Using Synaptic, installed xen-hypervisor-4.1-amd64, xen-tools
4.2.1-1, and it installed all additional dependent packages.

7.) Added the following to /etc/default/grub
GRUB_CMDLINE_XEN="loglvl=all guest_loglvl=all com1=115200,8n1,0x3f8,4 
GRUB_CMDLINE_LINUX="console=hvc0 earlyprintk=xen"

The downside is that once i add those lines above, i can't boot back
into the normal non-Xen kernel anymore....
Not sure what this issue is

You might have wanted to use GRUB_CMDLINE_LINUX_XEN_REPLACE instead of
GRUB_CMDLINE_LINUX since the options you have used there are not going
to work with native, although I'd expect it to silently boot with no
console and then become available on the network.

Ya, when i modified those those two lines above in the /etc/default/grub, i was just following the Wiki Page on enabling the Serial Console on Xen so i could view or troubleshoot why Xen was not booting. Just using the line GRUB_CMDLINE_XEN, adds all of those commands to the end of the multiboot line in the grub.cfg for only the XEN menuentries. If i also use the line GRUB_CMDLINE_LINUX, it adds those lines to just to the end of the kernel line for all non-Xen menuentries. Which in this case, prevents those kernels from booting. SO I don't think those are important to use anyways so i just omit the changes to GRUB_CMDLINE_LINUX and it works just fine.

8.) Rebooted into kernel 3.3.1 with Xen 4.1 AND recorded the trace
log, which ended with a KERNEL PANIC
A bug was introduce into 3.1.12. A fix is in the pipeline for the next
update but in the meantime you can try reverting:

commit 73d63d038ee9f769f5e5b46792d227fe20e442c5
Author: Suresh Siddha<suresh.b.siddha@xxxxxxxxx>
Date:   Mon Mar 12 11:36:33 2012 -0700

     x86/ioapic: Add register level checks to detect bogus io-apic entries

(I don't seem to see anything newer than 3.1.10 in the git tree, how


AHH ok i see, so this bug goes back that far in the Kernel revisions. So, the kernel that comes compiled with Debian Wheezy is Kernel, is that bug in that version as well or it has been patched / fixed. I have tried before to use Wheezy with the kernel they have for it, and install Xen 4.1 from Synaptic and all that, still didn't boot. BUT, that was before when i didn't have the Serial Console Setup yet, so don't know what the error messages where.

IF Kernel 3.1.10 does not have those kind of bugs, i suppose i can just mess around with that version instead. Really do not know how much XEN options or etc have changed from kernel 3.1.10 to 3.3.1 as those are the only things i am concerned about, but if they haven't, than Kernel 3.1.10 sounds perfectly ok for me

REALLY, wish this was a bit easier, BUT all i want to find is just ONE stable kernel that perfectly plays nice with XEN and is in the 3.xx.xx range

I am not experienced with reading trace logs, SO i have attached it
here as a TXT file. I am hoping someone can take a quick peek at it as
it is not that long and see if it reveals anything of useful to why
the kernel panics.......

AS always thanks to all...


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.