Xen project Mailing List

[Xen-devel] Re: Xen-4.0.x doesn't start on 32bit / pvops 2.6.32.19

From: Pasi Kärkkäinen <pasik@xxxxxx>

Date: Mon, 16 Aug 2010 13:44:13 +0300

Delivery-date: Mon, 16 Aug 2010 03:44:17 -0700

List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Mon, Aug 16, 2010 at 12:15:41PM +0200, Stefan Kuhne wrote: > Hello, > > i start an new Thread because of the old one is a little bit messy. > > I try to get xen-4.0.x running on a Dell R310 with Core i3 CPU ind 32Bit. > > I tried Ubuntu-10.04 Server in 32bit and 64bit. > I use on both Systems the same scripts with code from Wiki: > apt-get install ... > hg clone (from ML) > make install > > On 64bit system boots until mount of rootfs. > So does 64bit kernel boot/work OK? > But 32bit boots until: > (XEN) d0:v0: unhandled page fault (ec=0009) > (XEN) Pagetable walk from c009fc00: > (XEN) L3[0x003] = 0000000039820001 00001820 > (XEN) L2[0x000] = 0000000039fdd067 00001fdd > (XEN) L1[0x09f] = 000007fffffff063 ffffffff > (XEN) d0:v0: reserved bit in page table (ec=0009) > > Is anybody running an 32bit System? > I need 32bit because of my destination Distro is only in 32bit available. > Based on the full bootlog the problem is in the dom0 kernel, not in Xen hypervisor. Did you try earlier versions of the dom0 kernel? Which version introduces this problem? I think 2.6.32.10 booted/worked for me on 32bit.. <snip> > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 32-bit, PAE, lsb > (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x1000000 -> 0x19f5000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000038000000->000000003c000000 (245760 pages > to be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: c1000000->c19f5000 > (XEN) Init. ramdisk: c19f5000->c1ed6800 > (XEN) Phys-Mach map: c1ed7000->c1fd7000 > (XEN) Start info: c1fd7000->c1fd747c > (XEN) Page tables: c1fd8000->c1fef000 > (XEN) Boot stack: c1fef000->c1ff0000 > (XEN) TOTAL: c0000000->c2400000 > (XEN) ENTRY ADDRESS: c1798000 > (XEN) Dom0 has maximum 4 VCPUs > (XEN) Scrubbing Free RAM: .............................done. > (XEN) trace.c:89:d32767 calc_tinfo_first_offset: NR_CPUs 128, > offset_in_bytes 258, t_info_first_offset 65 > (XEN) Xen trace buffers: disabled > (XEN) Std. Loglevel: All > (XEN) Guest Loglevel: All > (XEN) ********************************************** > (XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS > (XEN) ******* This option is intended to aid debugging of Xen by ensuring > (XEN) ******* that all output is synchronously delivered on the serial line. > (XEN) ******* However it can introduce SIGNIFICANT latencies and affect > (XEN) ******* timekeeping. It is NOT recommended for production use! > (XEN) ********************************************** > (XEN) 3... 2... 1... > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch > input to Xen) > (XEN) Freed 152kB init memory. So Xen starts fine, and it boots the dom0 kernel here. > mapping kernel into physical memory > Xen: setup ISA identity maps > about to get started... > [ 0.000000] Reserving virtual address space above 0xf5800000 > [ 0.000000] Initializing cgroup subsys cpuset > [ 0.000000] Initializing cgroup subsys cpu > [ 0.000000] Linux version 2.6.32.19 (root@FB5-Cluster) (gcc version > 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #1 SMP Mon Aug 16 11:19:14 CEST 2010 <snip> > [ 0.000000] NX (Execute Disable) protection: active Did you try without NX? (ie. turn it off in the BIOS). > [ 0.000000] 302MB HIGHMEM available. > [ 0.000000] 721MB LOWMEM available. Does dom0_mem=512M help? > (XEN) d0:v0: unhandled page fault (ec=0009) > (XEN) Pagetable walk from c009fc00: > (XEN) L3[0x003] = 0000000039820001 00001820 > (XEN) L2[0x000] = 0000000039fdd067 00001fdd > (XEN) L1[0x09f] = 000007fffffff063 ffffffff > (XEN) d0:v0: reserved bit in page table (ec=0009) > (XEN) Pagetable walk from c009fc00: > (XEN) L3[0x003] = 0000000039820001 00001820 > (XEN) L2[0x000] = 0000000039fdd067 00001fdd > (XEN) L1[0x09f] = 000007fffffff063 ffffffff > (XEN) ----[ Xen-4.0.1-rc6 x86_32p debug=n Tainted: C ]---- > (XEN) CPU: 0 > (XEN) EIP: e019:[<c17a56a1>] You'd have to use gdb on the kernel vmlinux file to resolve which funtion this address points to.. to see why/where it crashes. -- Pasi > (XEN) EFLAGS: 00010206 EM: 1 CONTEXT: pv guest > (XEN) eax: 0009fc00 ebx: c009fc00 ecx: 00000001 edx: 00000400 > (XEN) esi: 00000400 edi: 00000000 ebp: c170df24 esp: c170df14 > (XEN) cr0: 8005003b cr4: 000026f0 cr3: 3970f000 cr2: c009fc00 > (XEN) ds: e021 es: e021 fs: 00d8 gs: 0000 ss: e021 cs: e019 > (XEN) Guest stack trace from esp=c170df14: > (XEN) 00000001 00000001 2d1fe000 00000000 c170df30 c17a5790 00000000 > c170dfac > (XEN) c179e3c6 c170df9c c106024f 01ed6800 00000000 00000035 019f5000 > 00000000 > (XEN) c170df6d 00000000 205b5000 004e1800 3030302e 019f5000 c17a0020 > c1720fcc > (XEN) 00000002 00000002 00000000 00000000 c1720350 c170df94 c102b2c5 > 00000000 > (XEN) 00000000 c1720350 c170dfac 00000000 00000000 c1720350 c170dfc4 > c17985c6 > (XEN) c162db96 c14bd010 c17d1240 019f5000 c170dfd4 c17980a8 019f5000 > c17cfee0 > (XEN) c170dffc c179bd31 1fc9d3f5 80980281 00100800 00020652 00000001 > 00000000 > (XEN) c1fd7000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) domain_crash_sync called from entry.S (ff1ccc1e) > (XEN) Domain 0 (vcpu#0) crashed on cpu#0: > (XEN) ----[ Xen-4.0.1-rc6 x86_32p debug=n Tainted: C ]---- > (XEN) CPU: 0 > (XEN) EIP: e019:[<c17a56a1>] > (XEN) EFLAGS: 00000206 EM: 1 CONTEXT: pv guest > (XEN) eax: 0009fc00 ebx: c009fc00 ecx: 00000001 edx: 00000400 > (XEN) esi: 00000400 edi: 00000000 ebp: c170df24 esp: c170df04 > (XEN) cr0: 8005003b cr4: 000026f0 cr3: 3970f000 cr2: c009fc00 > (XEN) ds: e021 es: e021 fs: 00d8 gs: 0000 ss: e021 cs: e019 > (XEN) Guest stack trace from esp=c170df04: > (XEN) 00000009 c17a56a1 0001e019 00010006 00000001 00000001 2d1fe000 > 00000000 > (XEN) c170df30 c17a5790 00000000 c170dfac c179e3c6 c170df9c c106024f > 01ed6800 > (XEN) 00000000 00000035 019f5000 00000000 c170df6d 00000000 205b5000 > 004e1800 > (XEN) 3030302e 019f5000 c17a0020 c1720fcc 00000002 00000002 00000000 > 00000000 > (XEN) c1720350 c170df94 c102b2c5 00000000 00000000 c1720350 c170dfac > 00000000 > (XEN) 00000000 c1720350 c170dfc4 c17985c6 c162db96 c14bd010 c17d1240 > 019f5000 > (XEN) c170dfd4 c17980a8 019f5000 c17cfee0 c170dffc c179bd31 1fc9d3f5 > 80980281 > (XEN) 00100800 00020652 00000001 00000000 c1fd7000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > (XEN) Domain 0 crashed: 'noreboot' set - not rebooting. > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.