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

Re: [Xen-users] cannot boot any domU - case #2

To: xen-users@xxxxxxxxxxxxxxxxxxx
From: Jamie Clark <jamie@xxxxxxxxxx>
Date: Sat, 27 Aug 2005 19:15:32 +0800
Delivery-date: Sat, 27 Aug 2005 11:13:43 +0000
List-id: Xen user discussion <xen-users.lists.xensource.com>

Just an update on this. Interesting. Xen 2.0.6 and later do not workon some mainboards.

I changed my mainboard from MSI 865PE Neo2 (Intel 865 Chipset) to anold Intel 865 PERL I had in the cupboard.

After the change:  Xen 2.0.7 can boot a domU on my machine.

Recap:

MSI Neo2 mainboard: Runs Xen 2.0.5. Xen 2.0.6+ boots but thenhangs when starting domU.

  Intel 865PERL works for all Xen

So it appears there is some incompatibility or bug regression in Xen2.0.6+

With watchdog enabled on the MSI board I see an unrecoverable hangmessage on the serial console with the MSI board.

Hope the helps someone. Xen 2.0.6+ may be incompatible with yourmainboard. Don't waste your time. In my case I moved everything(RAM, CPU, disks, ethernet) to the older mainboard and all works OK.Must be BIOS or southbridge incompatible. Both mainboards Intel 865PE.


-Jamie

On 09 Aug 2005, at 10:15 AM, Jamie Clark wrote:

Hi,

I noticed the earlier thread on this started by Scott Koranda(sorry - was reading off gmane so I can't reply to thread)

I have exactly the same symptoms: machine hangs as soon as Iattempt to start a single domU, just after emitting "using configfile..."At that point the machine appears completely wedged. The sequenceof 3 ^A on the console no longer does anything. Dead.

What is interesting is that 2.0.5 works fine. I was have beenrunning that since back when (April??) with 5 domains. Typicallyconfigured like this:


kernel  = "/boot/vmlinuz-2.4.30-xenU"
memory  = 512
name    = "neon-ofs-t"
disk    = [ 'phy:/dev/evms/xen-root-2,hda1,w',
            'phy:/dev/evms/xen-swap-2,hda2,w'  ]
hostname= "neon-ofs-t"
root    = "/dev/hda1 ro"
restart = 'onreboot'

I tried 2.0.6 in late May, careful to point my domUs at the newlybuilt kernels and had this problem, so reverted to 2.0.5.


Tried 2.0.7 last night. Same problem.

Machine is single P4, Intel 865 chipset, dmesg follows.

I might give unstable a try.

-jamie

__  __            ____    ___  _____
\ \/ /___ _ __   |___ \  / _ \|___  |
  \  // _ \ '_ \    __) || | | |  / /
  /  \  __/ | | |  / __/ | |_| | / /
/_/\_\___|_| |_| |_____(_)___(_)_/

http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory

Xen version 2.0.7 (root@xxxxxxxxxx) (gcc version 3.3.5 (Debian1:3.3.5-8)) Mon Aug 8 17:42:36 SGT 2005

Latest ChangeSet:

(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000ce000 - 00000000000d8014 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000e7ef0000 (usable)
(XEN)  00000000e7ef0000 - 00000000e7ef8000 (ACPI data)
(XEN)  00000000e7ef8000 - 00000000e7f00000 (ACPI NVS)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000fff00000 - 0000000100000000 (reserved)
(XEN) System RAM: 3710MB (3799612kB)
(XEN) Xen heap: 10MB (10680kB)

(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000,vendor = 0

(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) found SMP MP-table at 000fc0f0

(XEN) ACPI: RSDP (v000 AMI )@ 0x000fa320(XEN) ACPI: RSDT (v001 AMIINT INTEL865 0x00000010 MSFT 0x00000097)@ 0xe7ef0000(XEN) ACPI: FADT (v001 AMIINT INTEL865 0x00000011 MSFT 0x00000097)@ 0xe7ef0030(XEN) ACPI: MADT (v001 AMIINT INTEL865 0x00000009 MSFT 0x00000097)@ 0xe7ef00c0(XEN) ACPI: DSDT (v001 INTEL I865G 0x00001000 MSFT 0x0100000d)@ 0x00000000

(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 Pentium 4(tm) XEON(tm) APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled)
(XEN) Using ACPI for processor (LAPIC) configuration information
(XEN) Intel MultiProcessor Specification v1.4
(XEN)     Virtual Wire compatibility mode.
(XEN) OEM ID: INTEL    Product ID: I865G/GE/PE  APIC at: 0xFEE00000
(XEN) I/O APIC #2 Version 32 at 0xFEC00000.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Processors: 1
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 2600.173 MHz processor.

(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000,vendor = 0

(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) CPU0 booted
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) Error: only one processor found.
(XEN) ENABLING IO-APIC IRQs
(XEN) Setting 2 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 2 ... ok.
(XEN) init IO_APIC IRQs
(XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 2600.0929 MHz.
(XEN) ..... Bus speed is 200.0070 MHz.
(XEN) ..... bus_scale = 0x0000CCD7
(XEN) Time init:
(XEN) .... System Time: 20000524ns
(XEN) .... cpu_freq:    00000000:9AFB7DF0
(XEN) .... scale:       00000001:89D1E7D3
(XEN) .... Wall Clock:  1123496577s 180000us
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xfdb81, last bus=3
(XEN) PCI: Using configuration type 1
(XEN) PCI: Probing PCI hardware
(XEN) PCI: Probing PCI hardware (bus 00)
(XEN) PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
(XEN) Transparent bridge - PCI device 8086:244e
(XEN) PCI: Using IRQ router PIIX/ICH [8086/24d0] at 00:1f.0
(XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16
(XEN) PCI->APIC IRQ transform: (B0,I29,P1) -> 19
(XEN) PCI->APIC IRQ transform: (B0,I29,P2) -> 18
(XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16
(XEN) PCI->APIC IRQ transform: (B0,I29,P3) -> 23
(XEN) PCI->APIC IRQ transform: (B0,I31,P0) -> 18
(XEN) PCI->APIC IRQ transform: (B0,I31,P0) -> 18
(XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17
(XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17
(XEN) PCI->APIC IRQ transform: (B1,I0,P0) -> 16
(XEN) PCI->APIC IRQ transform: (B2,I1,P0) -> 17
(XEN) PCI->APIC IRQ transform: (B2,I3,P0) -> 19
(XEN) PCI->APIC IRQ transform: (B3,I4,P0) -> 17
(XEN) PCI->APIC IRQ transform: (B3,I5,P0) -> 18
(XEN) PCI->APIC IRQ transform: (B3,I6,P0) -> 19
(XEN) PCI->APIC IRQ transform: (B3,I7,P0) -> 16
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***

(XEN) Xen-ELF header found:'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'

(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Kernel image:  00c00000->0103f584
(XEN)  Initrd image:  00000000->00000000
(XEN)  Dom0 alloc.:   01400000->21400000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0100000->c0570ac4
(XEN)  Init. ramdisk: c0571000->c0571000
(XEN)  Phys-Mach map: c0571000->c05f1000
(XEN)  Page tables:   c05f1000->c05f4000
(XEN)  Start info:    c05f4000->c05f5000
(XEN)  Boot stack:    c05f5000->c05f6000
(XEN)  TOTAL:         c0000000->c0800000
(XEN)  ENTRY ADDRESS: c0100000
(XEN) Scrubbing DOM0 RAM: ......done.
(XEN) Scrubbing Free RAM: ......................................done.

(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switchinput to Xen).(XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switchinput to DOM0).



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



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

References:
- [Xen-users] cannot boot any domU - case #2
  - From: Jamie Clark

Prev by Date: Re: [Xen-users] Trying to build a stable XEN server
Next by Date: [Xen-users] Counting Bandwidth usage
Previous by thread: [Xen-users] cannot boot any domU - case #2
Next by thread: [Xen-users] New user question...
Index(es):
- Date
- Thread

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