[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] problem using compiled kernel -- Sisu
I download them directly from kernel.org and configured it following the tutorial. I have also tried both the 2.6.32.16 kernel and the 2.6.31.13 kernel from git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git, they all give the same error message thanks very much! Best! Yours, Sisu On Mon, Jul 26, 2010 at 10:05 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote: > ÂOn 07/26/2010 07:15 PM, Sisu Xi wrote: >> >> Sorry I forgot to attach the file. >> >> Here they are. >> > > Which branch/source are these from? ÂThe xen/stable-2.6.32.x branch is the > most supported for dom0 use at the moment. > >  ÂJ > >> Thanks! >> >> On Mon, Jul 26, 2010 at 9:13 PM, Sisu Xi<xisisu@xxxxxxxxx> Âwrote: >>> >>> Hi, Jeremy: >>> >>> Thanks for the reply! >>> >>> I am using screen on Mac to show the serial debug info, >>> >>> my .config file and vmlinux file are in the attachment. >>> >>> Thanks very much! >>> >>> Best! >>> >>> Yours, >>> Sisu >>> >>> >>> >>> On Mon, Jul 26, 2010 at 9:02 PM, Jeremy Fitzhardinge<jeremy@xxxxxxxx> >>> Âwrote: >>>> >>>> ÂOn 07/26/2010 02:57 PM, Sisu Xi wrote: >>>>> >>>>> Hi, all: >>>>> >>>>> I have compiled Xen 4.0 from the source. it goes as the tutorials says. >>>>> >>>>> Then I download the kernel to compile it, (tried 2.6.34.1, 2.6.31.13, >>>>> 2.6.32.16), following the instructions to configure the kernel, and >>>>> tried on Fedora 13 and Ubuntu 10.04. The kernel compiles with no >>>>> error, and I configured the grub to show the debug info through a >>>>> serial port. >>>>> >>>>> But I got the same error message, which is: >>>>> >>>>> (XEN) ÂXen Âkernel: 32-bit, PAE, lsb >>>>> (XEN) ÂDom0 kernel: 32-bit, PAE, lsb, paddr 0x100000 ->  Â0xa45000 >>>>> (XEN) PHYSICAL MEMORY ARRANGEMENT: >>>>> (XEN) ÂDom0 alloc.:  0000000020000000->0000000030000000 (419388 pages >>>>> to be allocated) >>>>> (XEN) VIRTUAL MEMORY ARRANGEMENT: >>>>> (XEN) ÂLoaded kernel: c0100000->c0a45000 >>>>> (XEN) ÂInit. ramdisk: c0a45000->ca662000 >>>>> (XEN) ÂPhys-Mach map: ca662000->ca83b8f0 >>>>> (XEN) ÂStart info:  Âca83c000->ca83c47c >>>>> (XEN) ÂPage tables:  ca83d000->ca898000 >>>>> (XEN) ÂBoot stack:  Âca898000->ca899000 >>>>> (XEN) ÂTOTAL:     c0000000->cac00000 >>>>> (XEN) ÂENTRY ADDRESS: c07ca000 >>>>> (XEN) Dom0 has maximum 2 VCPUs >>>>> (XEN) Scrubbing Free RAM: .done. >>>>> (XEN) Xen trace buffers: disabled >>>>> (XEN) Std. Loglevel: Errors and warnings >>>>> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) >>>>> (XEN) *** Serial input ->  ÂDOM0 (type 'CTRL-a' three times to switch >>>>> input to Xen) >>>>> (XEN) Freed 156kB init memory. >>>>> mapping kernel into physical memory >>>>> about to get started... >>>>> [  Â0.000000] Reserving virtual address space above 0xf5800000 >>>>> (XEN) d0:v0: unhandled page fault (ec=0000) >>>>> (XEN) Pagetable walk from 15555c08: >>>>> (XEN) ÂL3[0x000] = 000000002a83e001 0000a83e >>>>> (XEN) ÂL2[0x0aa] = 0000000000000000 ffffffff >>>>> (XEN) domain_crash_sync called from entry.S (ff1cbe3e) >>>>> (XEN) Domain 0 (vcpu#0) crashed on cpu#0: >>>>> (XEN) ----[ Xen-4.0.1-rc5-pre Âx86_32p Âdebug=n ÂNot tainted ]---- >>>>> (XEN) CPU:  Â0 >>>>> (XEN) EIP:  Âe019:[<c03dcc4d>] >>>>> (XEN) EFLAGS: 00000206  EM: 1  CONTEXT: pv guest >>>>> (XEN) eax: 00000000  ebx: 00000000  ecx: 00000008  edx: c0710d3d >>>>> (XEN) esi: 15555000  edi: c07c6a24  ebp: c0777dac  esp: c0777d50 >>>>> (XEN) cr0: 8005003b  cr4: 000026f0  cr3: 20779000  cr2: 15555c08 >>>>> (XEN) ds: e021  es: e021  fs: 00d8  gs: 00e0  ss: e021  cs: e019 >>>>> (XEN) Guest stack trace from esp=c0777d50: >>>>> (XEN)  Â00000000 c03dcc4d 0001e019 00010006 00000000 c0777d7c c0777d84 >>>>> 00000008 >>>>> (XEN)  Âc0710d3d 00000000 00000008 c0777dc0 c01315ce 00000000 00000000 >>>>> 08dabc4e >>>>> (XEN)  Â00000001 00000000 00000000 00000000 00000000 00000000 c07c6a24 >>>>> c0777dd0 >>>>> (XEN)  Âc03dce01 c089af63 00000040 c089af63 00000040 c07ac7e0 c03dcda0 >>>>> c07c6a24 >>>>> (XEN)  Âc0777dec c0151b84 00000040 00000003 00000043 00000043 00000006 >>>>> c0777dfc >>>>> (XEN)  Âc0151bee 00000043 0000023d c0777e24 c0152065 0001ffff 367ac7e0 >>>>> fffffdc3 >>>>> (XEN)  Â00000006 00000000 00000000 c07ac7e0 c089aec0 c0777e50 c0152a30 >>>>> 00000000 >>>>> (XEN)  Â00000000 c08baf83 00000034 006ce332 00000000 c0804fac 00000000 >>>>> c0804fac >>>>> (XEN)  Âc0777e60 c012d796 00000000 c0804fac c0777e70 c07de331 c0850d28 >>>>> c0804fa0 >>>>> (XEN)  Âc0777e8c c07ca9f4 b1b5e716 c088e9c0 c0804fa0 0000005f fffffffe >>>>> c0777ecc >>>>> (XEN)  Âc016c20f c0777ea4 c0777ecc c07d0a11 c06ce332 c06ccf4b 00000000 >>>>> 00000000 >>>>> (XEN)  Âc0804fac c0804faf c0804faf 0000000b 00000000 c080964c c088e8cc >>>>> c0777edc >>>>> (XEN)  Âc07ca298 00000000 c07ca9a8 c0777ee4 c07ca631 c0777f84 c07cf64f >>>>> 00000095 >>>>> (XEN)  Âc0777f41 c0777f74 c0106a9e ffffffff c0152585 c0777f32 c06dc201 >>>>> 00000000 >>>>> (XEN)  Â00000000 c0777f32 00000000 00000000 c08baf83 00000035 0000000f >>>>> 00000000 >>>>> (XEN)  Â205b0000 30202020 3030302e c0777fa8 00000020 00000000 c08bcb3c >>>>> 00000000 >>>>> (XEN)  Â00000000 0a662000 c0777f6c c0106a9e 00000000 b1b5e716 00000000 >>>>> 00000000 >>>>> (XEN)  Â0a662000 b1b5e716 00000000 00000000 0a662000 c0777fb0 c07ca70f >>>>> c06ccfca >>>>> (XEN)  Âc05aa040 00000000 08d30cf4 00000001 b1b5e716 577d377b c0807f60 >>>>> 00a45000 >>>>> (XEN)  Âc0777fd0 c07ca0ef 0a662000 00000000 c06ce77d 00a45000 ca83c000 >>>>> c078c960 >>>>> (XEN) Domain 0 crashed: rebooting machine in 5 seconds. >>>>> >>>>> >>>>> Does anyone know how to solve this prob? >>>> >>>> Could you post the full boot log from Xen, your vmlinux file and your >>>> .config? >>>> >>>> Thanks, >>>>  ÂJ >>>> > > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |