Anthony Wright
2011-Sep-05 10:31 UTC
[Xen-devel] VM hangs during boot on 3.0.4 dom0 kernel, works on alternative hardware
I have two machines with identical Dom0''s and DomUs, but different hardware. The Dom0 has a patch which I produced myself based on the "Re: [Xen-devel] Kernel bug from 3.0 (was phy disks and vifs timing out in DomU)" thread. The patch calls vmalloc_sync_all after every alloc_vm_area, and I realise this isn''t the best solution, but it allowed me to move forward. The patch fixes the problem I had on one machine, so that now the VMs boot correctly, but I have another system with an identical setup (identical Dom0 & DomU kernels, identical startup for DomU) and the VM fails to start. I have attached a copy of the console log from the good VM and the bad VM. Anthony. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Sep-06 16:16 UTC
Re: [Xen-devel] VM hangs during boot on 3.0.4 dom0 kernel, works on alternative hardware
On Mon, Sep 05, 2011 at 11:31:16AM +0100, Anthony Wright wrote:> I have two machines with identical Dom0''s and DomUs, but different > hardware. The Dom0 has a patch which I produced myself based on the "Re: > [Xen-devel] Kernel bug from 3.0 (was phy disks and vifs timing out in > DomU)" thread. The patch calls vmalloc_sync_all after every > alloc_vm_area, and I realise this isn''t the best solution, but it > allowed me to move forward.<nods>> > The patch fixes the problem I had on one machine, so that now the VMs > boot correctly, but I have another system with an identical setup > (identical Dom0 & DomU kernels, identical startup for DomU) and the VM > fails to start. I have attached a copy of the console log from the good > VM and the bad VM.And what does the dom0 and xen hypervisor log give you? It looks to be hanging at identifying the CPU - is the hardware quite different from one setup to another? Have you toyed with using the cpuid flag in the guest to mimic the lowest CPU type?> > Anthony. > >> [ 3.226308] Reserving virtual address space above 0xf5800000 > [ 3.226308] Linux version 2.6.30.1 (root@deb-builder) (gcc version 4.3.2 (GCC) ) #2 SMP Mon Jul 18 12:06:12 GMT 2011 > [ 3.226308] KERNEL supported cpus: > [ 3.226308] Intel GenuineIntel > [ 3.226308] AMD AuthenticAMD > [ 3.226308] NSC Geode by NSC > [ 3.226308] Cyrix CyrixInstead > [ 3.226308] Centaur CentaurHauls > [ 3.226308] Transmeta GenuineTMx86 > [ 3.226308] Transmeta TransmetaCPU > [ 3.226308] UMC UMC UMC UMC > [ 3.226308] BIOS-provided physical RAM map: > [ 3.226308] Xen: 0000000000000000 - 00000000000a0000 (usable) > [ 3.226308] Xen: 00000000000a0000 - 0000000000100000 (reserved) > [ 3.226308] Xen: 0000000000100000 - 000000000065c000 (usable) > [ 3.226308] Xen: 000000000065c000 - 0000000000759000 (reserved) > [ 3.226308] Xen: 0000000000759000 - 000000003e800000 (usable) > [ 3.226308] DMI not present or invalid. > [ 3.226308] last_pfn = 0x3e800 max_arch_pfn = 0x1000000 > [ 3.226308] init_memory_mapping: 0000000000000000-00000000229fe000 > [ 3.226308] NX (Execute Disable) protection: active > [ 3.226308] 446MB HIGHMEM available. > [ 3.226308] 553MB LOWMEM available. > [ 3.226308] mapped low ram: 0 - 229fe000 > [ 3.226308] low ram: 0 - 229fe000 > [ 3.226308] node 0 low ram: 00000000 - 229fe000 > [ 3.226308] node 0 bootmap 00007000 - 0000b540 > [ 3.226308] (7 early reservations) ==> bootmem [0000000000 - 00229fe000] > [ 3.226308] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] > [ 3.226308] #1 [0000759000 - 000075f000] XEN PAGETABLES ==> [0000759000 - 000075f000] > [ 3.226308] #2 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000] > [ 3.226308] #3 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000] > [ 3.226308] #4 [0000100000 - 00005366f4] TEXT DATA BSS ==> [0000100000 - 00005366f4] > [ 3.226308] #5 [0000537000 - 0000645000] PGTABLE ==> [0000537000 - 0000645000] > [ 3.226308] #6 [0000007000 - 000000c000] BOOTMAP ==> [0000007000 - 000000c000] > [ 3.226308] Zone PFN ranges: > [ 3.226308] DMA 0x00000000 -> 0x00001000 > [ 3.226308] Normal 0x00001000 -> 0x000229fe > [ 3.226308] HighMem 0x000229fe -> 0x0003e800 > [ 3.226308] Movable zone start PFN for each node > [ 3.226308] early_node_map[3] active PFN ranges > [ 3.226308] 0: 0x00000000 -> 0x000000a0 > [ 3.226308] 0: 0x00000100 -> 0x0000065c > [ 3.226308] 0: 0x00000759 -> 0x0003e800 > [ 3.226308] Using APIC driver default > [ 3.226308] SMP: Allowing 1 CPUs, 0 hotplug CPUs > [ 3.226308] Local APIC disabled by BIOS -- you can enable it with "lapic" > [ 3.226308] Allocating PCI resources starting at 40000000 (gap: 3e800000:c1800000) > [ 3.226308] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1 > [ 3.226308] PERCPU: Allocated 6 4k pages, static data 22940 bytes > [ 3.810521] Xen: using vcpu_info placement > [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 253650 > [ 0.000000] Kernel command line: root=/dev/xvda1 > [ 0.000000] Enabling fast FPU save and restore... done. > [ 0.000000] Enabling unmasked SIMD FPU exception support... done. > [ 0.000000] Initializing CPU#0 > [ 0.000000] NR_IRQS:512 > [ 0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes) > [ 0.000000] Detected 2533.458 MHz processor. > [ 0.010000] Console: colour dummy device 80x25 > [ 0.010000] console [tty0] enabled > [ 0.010000] console [hvc0] enabled > [ 0.010000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) > [ 0.010000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) > [ 0.010000] Initializing HighMem for node 0 (000229fe:0003e800) > [ 0.010000] Memory: 1007448k/1024000k available (2539k kernel code, 14292k reserved, 1067k data, 244k init, 456712k highmem) > [ 0.010000] virtual kernel memory layout: > [ 0.010000] fixmap : 0xf574f000 - 0xf57ff000 ( 704 kB) > [ 0.010000] pkmap : 0xf5200000 - 0xf5400000 (2048 kB) > [ 0.010000] vmalloc : 0xe31fe000 - 0xf51fe000 ( 288 MB) > [ 0.010000] lowmem : 0xc0000000 - 0xe29fe000 ( 553 MB) > [ 0.010000] .init : 0xc0490000 - 0xc04cd000 ( 244 kB) > [ 0.010000] .data : 0xc037ae1d - 0xc0485e18 (1067 kB) > [ 0.010000] .text : 0xc0100000 - 0xc037ae1d (2539 kB) > [ 0.010000] Checking if this processor honours the WP bit even in supervisor mode...Ok. > [ 0.010000] installing Xen timer for CPU 0 > [ 0.010000] Calibrating delay loop (skipped), value calculated using timer frequency.. 5066.91 BogoMIPS (lpj=25334580) > [ 0.010000] Mount-cache hash table entries: 512> [ 3.226308] Reserving virtual address space above 0xf5800000 > [ 3.226308] Linux version 2.6.30.1 (root@deb-builder) (gcc version 4.3.2 (GCC) ) #2 SMP Mon Jul 18 12:06:12 GMT 2011 > [ 3.226308] KERNEL supported cpus: > [ 3.226308] Intel GenuineIntel > [ 3.226308] AMD AuthenticAMD > [ 3.226308] NSC Geode by NSC > [ 3.226308] Cyrix CyrixInstead > [ 3.226308] Centaur CentaurHauls > [ 3.226308] Transmeta GenuineTMx86 > [ 3.226308] Transmeta TransmetaCPU > [ 3.226308] UMC UMC UMC UMC > [ 3.226308] BIOS-provided physical RAM map: > [ 3.226308] Xen: 0000000000000000 - 00000000000a0000 (usable) > [ 3.226308] Xen: 00000000000a0000 - 0000000000100000 (reserved) > [ 3.226308] Xen: 0000000000100000 - 000000000065c000 (usable) > [ 3.226308] Xen: 000000000065c000 - 0000000000759000 (reserved) > [ 3.226308] Xen: 0000000000759000 - 000000003e800000 (usable) > [ 3.226308] DMI not present or invalid. > [ 3.226308] last_pfn = 0x3e800 max_arch_pfn = 0x1000000 > [ 3.226308] init_memory_mapping: 0000000000000000-00000000229fe000 > [ 3.226308] NX (Execute Disable) protection: active > [ 3.226308] 446MB HIGHMEM available. > [ 3.226308] 553MB LOWMEM available. > [ 3.226308] mapped low ram: 0 - 229fe000 > [ 3.226308] low ram: 0 - 229fe000 > [ 3.226308] node 0 low ram: 00000000 - 229fe000 > [ 3.226308] node 0 bootmap 00007000 - 0000b540 > [ 3.226308] (7 early reservations) ==> bootmem [0000000000 - 00229fe000] > [ 3.226308] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] > [ 3.226308] #1 [0000759000 - 000075f000] XEN PAGETABLES ==> [0000759000 - 000075f000] > [ 3.226308] #2 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000] > [ 3.226308] #3 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000] > [ 3.226308] #4 [0000100000 - 00005366f4] TEXT DATA BSS ==> [0000100000 - 00005366f4] > [ 3.226308] #5 [0000537000 - 0000645000] PGTABLE ==> [0000537000 - 000 default > [ 3.226308] SMP: Allowing 1 CPUs, 0 hotplug CPUs > [ 3.226308] Local APIC disabled by BIOS -- you can enable it with "lapic" > [ 3.226308] Allocating PCI resources starting at 40000000 (gap: 3e800000:c1800000) > [ 3.226308] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1 > [ 3.226308] PERCPU: Allocated 6 4k pages, static data 22940 bytes > [ 3.810521] Xen: using vcpu_info placement > [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 253650 > [ 0.000000] Kernel command line: root=/dev/xvda1 > [ 0.000000] Enabling fast FPU save and restore... done. > [ 0.000000] Enabling unmasked SIMD FPU exception support... done. > [ 0.000000] Initializing CPU#0 > [ 0.000000] NR_IRQS:512 > [ 0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes) > [ 0.000000] Detected 3013.788 MHz processor. > [ 0.010000] Console: colour dummy device 80x25 > [ 0.010000] console [tty0] enabled > [ 0.010000] console [hvc0] enabled > [ 0.010000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) > [ 0.010000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) > [ 0.010000] Initializing HighMem for node 0 (000229fe:0003e800) > [ 0.010000] Memory: 1007448k/1024000k available (2539k kernel code, 14292k reserved, 1067k data, 244k init, 456712k highmem) > [ 0.010000] virtual kernel memory layout: > [ 0.010000] fixmap : 0xf574f000 - 0xf57ff000 ( 704 kB) > [ 0.010000] pkmap : 0xf5200000 - 0xf5400000 (2048 kB) > [ 0.010000] vmalloc : 0xe31fe000 - 0xf51fe000 ( 288 MB) > [ 0.010000] lowmem : 0xc0000000 - 0xe29fe000 ( 553 MB) > [ 0.010000] .init : 0xc0490000 - 0xc04cd000 ( 244 kB) > [ 0.010000] .data : 0xc037ae1d - 0xc0485e18 (1067 kB) > [ 0.010000] .text : 0xc0100000 - 0xc037ae1d (2539 kB) > [ 0.010000] Checking if this processor honours the WP bit even in supervisor mode...Ok. > [ 0.010000] installing Xen timer for CPU 0 > [ 0.010000] Calibrating delay loop (skipped), value calculated using timer frequency.. 6027.57 BogoMIPS (lpj=30137880) > [ 0.010000] Mount-cache hash table entries: 512 > [ 0.010000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > [ 0.010000] CPU: L2 Cache: 1024K (64 bytes/line) > [ 0.010000] CPU: Physical Processor ID: 0 > [ 0.010000] CPU: Processor Core ID: 0 > [ 0.010000] SMP alternatives: switching to UP code > [ 0.010000] Freeing SMP alternatives: 28k freed > [ 0.010180] Brought up 1 CPUs > [ 0.010394] net_namespace: 452 bytes > [ 0.010403] Booting paravirtualized kernel on Xen > [ 0.010408] Xen version: 4.1.1 (preserve-AD) > [ 0.010445] xor: automatically using best checksumming function: pIII_sse > [ 0.060003] pIII_sse : 2499.200 MB/sec > [ 0.060011] xor: using function: pIII_sse (2499.200 MB/sec) > [ 0.060054] Grant table initialized > [ 0.060094] NET: Registered protocol family 16 > [ 0.062835] bio: create slab <bio-0> at 0 > [ 0.063164] xen_balloon: Initialising balloon driver. > [ 0.230016] raid6: int32x1 774 MB/s > [ 0.400011] raid6: int32x2 1342 MB/s > [ 0.570087] raid6: int32x4 649 MB/s > [ 0.740008] raid6: int32x8 802 MB/s > [ 0.910011] raid6: mmxx1 2348 MB/s > [ 1.080015] raid6: mmxx2 4362 MB/s > [ 1.250030] raid6: sse1x1 1907 MB/s > [ 1.420018] raid6: sse1x2 2746 MB/s > [ 1.590025] raid6: sse2x1 3313 MB/s > [ 1.760017] raid6: sse2x2 4325 MB/s > [ 1.760033] raid6: using algorithm sse2x2 (4325 MB/s) > [ 1.760643] NET: Registered protocol family 2 > [ 1.760683] IP route cache hash table entries: 32768 (order: 5, 131072 bytes) > [ 1.760767] TCP established hash table entries: 131072 (order: 8, 1048576 bytes) > [ 1.761182] TCP bind hash table entries: 65536 (order: 7, 524288 bytes) > [ 1.761437] TCP: Hash tables configured (established 131072 bind 65536) > [ 1.761445] TCP reno registered > [ 1.761513] NET: Registered protocol family 1 > [ 1.761732] platform rtc_cmos: registered platform RTC device (no PNP device found) > [ 1.762311] highmem bounce pool size: 64 pages > [ 1.762325] HugeTLB registered 2 MB page size, pre-allocated 0 pages > [ 1.762389] VFS: Disk quotas dquot_6.5.2 > [ 1.762401] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > [ 1.762499] squashfs: version 4.0 (2009/01/31) Phillip Lougher > [ 1.762596] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). > [ 1.762940] msgmni has been set to 1107 > [ 1.763134] alg: No test for stdrng (krng) > [ 1.763146] async_tx: api initialized (sync-only) > [ 1.763155] io scheduler noop registered > [ 1.763160] io scheduler anticipatory registered (default) > [ 1.763165] io scheduler deadline registered > [ 1.763180] io scheduler cfq registered > [ 1.766472] loop: module loaded > [ 1.783564] Initialising Xen virtual ethernet driver. > [ 1.785475] blkfront: xvda1: barriers enabled > [ 1.788158] blkfront: xvda2: barriers enabled > [ 1.789731] i8042.c: No controller found. > [ 1.790197] mice: PS/2 mouse device common for all mice > [ 1.790238] md: linear personality registered for level -1 > [ 1.790244] md: raid0 personality registered for level 0 > [ 1.790249] md: raid1 personality registered for level 1 > [ 1.790254] md: raid10 personality registered for level 10 > [ 1.790259] md: raid6 personality registered for level 6 > [ 1.790264] md: raid5 personality registered for level 5 > [ 1.790268] md: raid4 personality registered for level 4 > [ 1.790273] md: multipath personality registered for level -4 > [ 1.790278] md: faulty personality registered for level -5 > [ 1.790305] device-mapper: uevent: version 1.0.3 > [ 1.790378] device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com > [ 1.790454] device-mapper: multipath: version 1.0.5 loaded > [ 1.790460] device-mapper: multipath round-robin: version 1.0.0 loaded > [ 1.790554] oprofile: using timer interrupt. > [ 1.790565] Netfilter messages via NETLINK v0.30. > [ 1.790604] xt_time: kernel timezone is -0000 > [ 1.790625] ip_tables: (C) 2000-2006 Netfilter Core Team > [ 1.790646] arp_tables: (C) 2002 David S. Miller > [ 1.790656] TCP cubic registered > [ 1.790661] NET: Registered protocol family 17 > [ 1.790680] Bridge firewalling registered > [ 1.790742] RPC: Registered udp transport module. > [ 1.790747] RPC: Registered tcp transport module. > [ 1.790766] Using IPI No-Shortcut mode > [ 1.890171] md: Waiting for all devices to be available before autodetect > [ 1.890188] md: If you don''t use raid, use raid=noautodetect > [ 1.890361] md: Autodetecting RAID arrays. > [ 1.890367] md: Scanned 0 and added 0 devices. > [ 1.890371] md: autorun ... > [ 1.890374] md: ... autorun DONE. > [ 1.892999] VFS: Mounted root (squashfs filesystem) readonly on device 202:1. > [ 1.893048] Freeing unused kernel memory: 244k freed> _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Anthony Wright
2011-Sep-07 12:29 UTC
Re: [Xen-devel] VM hangs during boot on 3.0.4 dom0 kernel, works on alternative hardware
Anthony Wright
2011-Sep-10 20:50 UTC
Re: [Xen-devel] VM hangs during boot on 3.0.4 dom0 kernel, works on alternative hardware
On 06/09/2011 17:16, Konrad Rzeszutek Wilk wrote:> On Mon, Sep 05, 2011 at 11:31:16AM +0100, Anthony Wright wrote: >> I have two machines with identical Dom0''s and DomUs, but different >> hardware. The Dom0 has a patch which I produced myself based on the "Re: >> [Xen-devel] Kernel bug from 3.0 (was phy disks and vifs timing out in >> DomU)" thread. The patch calls vmalloc_sync_all after every >> alloc_vm_area, and I realise this isn''t the best solution, but it >> allowed me to move forward. > <nods> >> The patch fixes the problem I had on one machine, so that now the VMs >> boot correctly, but I have another system with an identical setup >> (identical Dom0 & DomU kernels, identical startup for DomU) and the VM >> fails to start. I have attached a copy of the console log from the good >> VM and the bad VM. > And what does the dom0 and xen hypervisor log give you? > > It looks to be hanging at identifying the CPU - is the hardware > quite different from one setup to another? Have you toyed with > using the cpuid flag in the guest to mimic the lowest CPU type?I''ve found a solution to my problem. The PV DomU was running a 32 bit linux kernel version 2.6.30.1. I hoped that a new kernel would be able to handle to CPU more effectively, and so I upgraded my DomU kernel to 3.0.4, and now the DomU boots. This solves the problem for me, but I''m slightly concerned that my original kernel wouldn''t work with this CPU (the CPU type for the kernel builds is set to Pentium Pro). I''ll try the 2.6.30.1 kernel on bare metal on monday to try to see if this is a xen/Dom0 kernel issue or a CPU/DomU issue. Anthony _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Anthony Wright
2011-Sep-13 09:52 UTC
Re: [Xen-devel] VM hangs during boot on 3.0.4 dom0 kernel, works on alternative hardware
----- Original Message -----> On 06/09/2011 17:16, Konrad Rzeszutek Wilk wrote: > > On Mon, Sep 05, 2011 at 11:31:16AM +0100, Anthony Wright wrote: > >> I have two machines with identical Dom0''s and DomUs, but different > >> hardware. The Dom0 has a patch which I produced myself based on the > >> "Re: > >> [Xen-devel] Kernel bug from 3.0 (was phy disks and vifs timing out > >> in > >> DomU)" thread. The patch calls vmalloc_sync_all after every > >> alloc_vm_area, and I realise this isn''t the best solution, but it > >> allowed me to move forward. > > <nods> > >> The patch fixes the problem I had on one machine, so that now the > >> VMs > >> boot correctly, but I have another system with an identical setup > >> (identical Dom0 & DomU kernels, identical startup for DomU) and the > >> VM > >> fails to start. I have attached a copy of the console log from the > >> good > >> VM and the bad VM. > > And what does the dom0 and xen hypervisor log give you? > > > > It looks to be hanging at identifying the CPU - is the hardware > > quite different from one setup to another? Have you toyed with > > using the cpuid flag in the guest to mimic the lowest CPU type? > I''ve found a solution to my problem. The PV DomU was running a 32 bit > linux kernel version 2.6.30.1. I hoped that a new kernel would be able > to handle to CPU more effectively, and so I upgraded my DomU kernel to > 3.0.4, and now the DomU boots. > > This solves the problem for me, but I''m slightly concerned that my > original kernel wouldn''t work with this CPU (the CPU type for the > kernel > builds is set to Pentium Pro). I''ll try the 2.6.30.1 kernel on bare > metal on monday to try to see if this is a xen/Dom0 kernel issue or a > CPU/DomU issue. > > AnthonyI''ve tried the 2.6.30.1 kernel on bare metal and it boots correctly, so it looks like some xen/Dom0 interaction is causing it to fail when run as a DomU. I have a work around (upgrading to 3.0.4 kernel), so it''s not affecting me but I''m happy to do any diagnostics to help identify the cause of the problem. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Sep-14 22:28 UTC
Re: [Xen-devel] VM hangs during boot on 3.0.4 dom0 kernel, works on alternative hardware
On Tue, Sep 13, 2011 at 10:52:40AM +0100, Anthony Wright wrote:> > > ----- Original Message ----- > > On 06/09/2011 17:16, Konrad Rzeszutek Wilk wrote: > > > On Mon, Sep 05, 2011 at 11:31:16AM +0100, Anthony Wright wrote: > > >> I have two machines with identical Dom0''s and DomUs, but different > > >> hardware. The Dom0 has a patch which I produced myself based on the > > >> "Re: > > >> [Xen-devel] Kernel bug from 3.0 (was phy disks and vifs timing out > > >> in > > >> DomU)" thread. The patch calls vmalloc_sync_all after every > > >> alloc_vm_area, and I realise this isn''t the best solution, but it > > >> allowed me to move forward. > > > <nods> > > >> The patch fixes the problem I had on one machine, so that now the > > >> VMs > > >> boot correctly, but I have another system with an identical setup > > >> (identical Dom0 & DomU kernels, identical startup for DomU) and the > > >> VM > > >> fails to start. I have attached a copy of the console log from the > > >> good > > >> VM and the bad VM. > > > And what does the dom0 and xen hypervisor log give you? > > > > > > It looks to be hanging at identifying the CPU - is the hardware > > > quite different from one setup to another? Have you toyed with > > > using the cpuid flag in the guest to mimic the lowest CPU type? > > I''ve found a solution to my problem. The PV DomU was running a 32 bit > > linux kernel version 2.6.30.1. I hoped that a new kernel would be able > > to handle to CPU more effectively, and so I upgraded my DomU kernel to > > 3.0.4, and now the DomU boots. > > > > This solves the problem for me, but I''m slightly concerned that my > > original kernel wouldn''t work with this CPU (the CPU type for the > > kernel > > builds is set to Pentium Pro). I''ll try the 2.6.30.1 kernel on bare > > metal on monday to try to see if this is a xen/Dom0 kernel issue or a > > CPU/DomU issue. > > > > Anthony > I''ve tried the 2.6.30.1 kernel on bare metal and it boots correctly, so it looks like some xen/Dom0 interaction is causing it to fail when run as a DomU. I have a work around (upgrading to 3.0.4 kernel), so it''s not affecting me but I''m happy to do any diagnostics to help identify the cause of the problem. >That is OK. I don''t we would have the time to actually figure out such and old kernel, or to backport the patch. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel