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

Re: [Xen-devel] problem using compiled kernel -- Sisu



On Tue, Jul 27, 2010 at 11:26:27AM -0500, Sisu Xi wrote:
> Hi, Pasi:
> 
> Thanks for the reply. I have tried the configuration file there.
> OS is Ubuntu 10.04, Xen is compiled from source, 4.0
> kernel is using jeremy git, branch changed to 2.6.32.x
> 
> configured to using serial port to show the debug info, it says:
> 

This doesn't look like the full serial console capture..

please paste your grub.conf and also paste the *full* serial console capture,
including Xen hypervisor messages and dom0 Linux kernel messages.

-- Pasi

> Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 481039
> Kernel command line: earlyprintk=xen
> PID hash table entries: 4096 (order: 2, 16384 bytes)
> Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Initializing CPU#0
> DMA: Placing 64MB software IO TLB between c9aeb000 - cdaeb000
> DMA: software IO TLB at phys 0x9aeb000 - 0xdaeb000
> xen_swiotlb_fixup: buf=c9aeb000 size=67108864
> xen_swiotlb_fixup: buf=cdb4b000 size=32768
> Initializing HighMem for node 0 (0002d1fe:0007663c)
> Memory: 1717960k/1939696k available (2999k kernel code, 220500k
> reserved, 1680k data, 472k init, 1200376k highmem)
> virtual kernel memory layout:
>     fixmap  : 0xf567e000 - 0xf57ff000   (1540 kB)
>     pkmap   : 0xf5200000 - 0xf5400000   (2048 kB)
>     vmalloc : 0xed9fe000 - 0xf51fe000   ( 120 MB)
>     lowmem  : 0xc0000000 - 0xed1fe000   ( 721 MB)
>       .init : 0xc0893000 - 0xc0909000   ( 472 kB)
>       .data : 0xc06ede20 - 0xc08920f8   (1680 kB)
>       .text : 0xc0400000 - 0xc06ede20   (2999 kB)
> SLUB: Genslabs=13, HWalign=128, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
> Hierarchical RCU implementation.
> NR_IRQS:2304 nr_irqs:768
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> xen: sci override: source_irq=9 global_irq=9 trigger=c polarity=1
> xen_allocate_pirq: returning irq 9 for gsi 9
> xen: acpi sci 9
> Console: colour VGA+ 80x25
> console [tty0] enabled, bootconsole disabled
> (XEN) PCI add device 00:00.0
> (XEN) PCI add device 00:01.0
> (XEN) PCI add device 00:1c.0
> (XEN) PCI add device 00:1c.1
> (XEN) PCI add device 00:1d.0
> (XEN) PCI add device 00:1d.1
> (XEN) PCI add device 00:1d.2
> (XEN) PCI add device 00:1d.3
> (XEN) PCI add device 00:1d.7
> (XEN) PCI add device 00:1e.0
> (XEN) PCI add device 00:1e.2
> (XEN) PCI add device 00:1f.0
> (XEN) PCI add device 00:1f.1
> (XEN) PCI add device 00:1f.2
> (XEN) PCI add device 00:1f.3
> (XEN) PCI add device 01:00.0
> (XEN) PCI add device 01:00.1
> (XEN) PCI add device 02:00.0
> (XEN) PCI add device 04:00.0
> (XEN) irq.c:1139:d0 Cannot bind IRQ 4 to guest. In use by 'ns16550'.
> (XEN) irq.c:1139:d0 Cannot bind IRQ 2 to guest. In use by 'cascade'.
> (XEN) irq.c:1139:d0 Cannot bind IRQ 4 to guest. In use by 'ns16550'.
> (XEN) irq.c:1139:d0 Cannot bind IRQ 2 to guest. In use by 'cascade'.
> (XEN) irq.c:1139:d0 Cannot bind IRQ 4 to guest. In use by 'ns16550'.
> (XEN) irq.c:1139:d0 Cannot bind IRQ 2 to guest. In use by 'cascade'.
> (XEN) irq.c:1139:d0 Cannot bind IRQ 4 to guest. In use by 'ns16550'.
> (XEN) irq.c:1139:d0 Cannot bind IRQ 2 to guest. In use by 'cascade'.
> 
> 
> at the same time, the target machine would stop at
> usbhid: v2.6: USB HID core driver
> Gave up waiting for root device. Common problems:
> - Boot args (cat /proc/cmdline)
>  -check rootdelay= (did the system wait long enough?)
>  -check root= (did the system wait for the right device?)
> - Missing modules (cat /proc/modules; ls /dev)
> ALERT! does not exist. Dropping to a shell!
> 
> BusyBox built-in shell (ash)
> 
> (initramfs)
> 
> 
> Have you encountered this before?
> 
> Thanks very much!
> 
> Best!
> 
> Yours,
> Sisu
> 
> 
> 
> On Tue, Jul 27, 2010 at 1:09 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> > On Mon, Jul 26, 2010 at 04:57:32PM -0500, 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.
> >>
> >
> > So you've read this wiki page?:
> > http://wiki.xensource.com/xenwiki/XenParavirtOps
> >
> > Did you try the example .config files provided in the troubleshooting 
> > section?
> >
> > -- Pasi
> >
> >
> >> 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?
> >>
> >> Thanks very much!
> >>
> >> Best!
> >>
> >> Yours,
> >> Sisu
> >>
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@xxxxxxxxxxxxxxxxxxx
> >> http://lists.xensource.com/xen-devel
> >

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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