Mailing List Archive

Error Code on Intel chip when trying to boot hvm
For those with any experience with QNX, I am trying to get QNX working
with Xen. I've going about it in a similar way as installing windows
with Xen, but when I start the guest up to install the OS it hangs on
the line:
'Hit Esc for .altboot.......'

Below is the dmesg that I get. Everything seems fine up until the last
two lines.

If anyone ideas/comments would be greatly appreciated!

Bryan

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

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

Xen version 3.0.2-2 (xenod@cl.cam.ac.uk) (gcc version 3.3.3 20040412
(Red Hat Linux 3.3.3-7)) Thu Apr 13 17:34:06 BST 2006
Latest ChangeSet: Thu Apr 13 15:18:37 2006 +0100 9617:5802713c159b

(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009fc00 (usable)
(XEN) 000000000009fc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007e7a0000 (usable)
(XEN) 000000007e7a0000 - 000000007e7ae000 (ACPI data)
(XEN) 000000007e7ae000 - 000000007e7e0000 (ACPI NVS)
(XEN) 000000007e7e0000 - 000000007e800000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ffb00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2023MB (2071804kB)
(XEN) Xen heap: 10MB (10572kB)
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) PAE disabled.
(XEN) found SMP MP-table at 000ff780
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 ACPIAM ) @
0x000fa9a0
(XEN) ACPI: RSDT (v001 A M I OEMRSDT 0x08000604 MSFT 0x00000097) @
0x7e7a0000
(XEN) ACPI: FADT (v002 A M I OEMFACP 0x08000604 MSFT 0x00000097) @
0x7e7a0200
(XEN) ACPI: MADT (v001 A M I OEMAPIC 0x08000604 MSFT 0x00000097) @
0x7e7a0390
(XEN) ACPI: MCFG (v001 A M I OEMMCFG 0x08000604 MSFT 0x00000097) @
0x7e7a0400
(XEN) ACPI: OEMB (v001 A M I AMI_OEM 0x08000604 MSFT 0x00000097) @
0x7e7ae040
(XEN) ACPI: ASF! (v032 LEGEND I865PASF 0x00000001 INTL 0x20060113) @
0x7e7a73c0
(XEN) ACPI: DSDT (v001 A0518 A0518000 0x00000000 INTL 0x20060113) @
0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 6:15 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 6:15 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 2666.739 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMXON is done
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz stepping 06
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) VMXON is done
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz stepping 06
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 2 CPUs
(XEN) Machine check exception polling timer started.
(XEN) Using IPI Shortcut mode
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Domain 0 kernel supports features = { 0000001f }.
(XEN) Domain 0 kernel requires features = { 00000000 }.
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 03000000->04000000 (474887 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c044a254
(XEN) Init. ramdisk: c044b000->c082da00
(XEN) Phys-Mach map: c082e000->c0a01c1c
(XEN) Start info: c0a02000->c0a03000
(XEN) Page tables: c0a03000->c0a07000
(XEN) Boot stack: c0a07000->c0a08000
(XEN) TOTAL: c0000000->c0c00000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Initrd len 0x3e2a00, start at 0xc044b000
(XEN) Scrubbing Free RAM: .....................done.
(XEN) Xen trace buffers: disabled
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).
(XEN) (GUEST: 1) HVM Loader
(XEN) (GUEST: 1) Loading ROMBIOS ...
(XEN) (GUEST: 1) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 1) Loading VMXAssist ...
(XEN) (GUEST: 1) VMX go ...
(XEN) (GUEST: 1) VMXAssist (Apr 13 2006)
(XEN) (GUEST: 1) Memory size 1024 MB
(XEN) (GUEST: 1) E820 map:
(XEN) (GUEST: 1) 0000000000000000 - 000000000009F800 (RAM)
(XEN) (GUEST: 1) 000000000009F800 - 00000000000A0000 (Reserved)
(XEN) (GUEST: 1) 00000000000A0000 - 00000000000C0000 (Type 16)
(XEN) (GUEST: 1) 00000000000F0000 - 0000000000100000 (Reserved)
(XEN) (GUEST: 1) 0000000000100000 - 000000003FFFE000 (RAM)
(XEN) (GUEST: 1) 000000003FFFE000 - 000000003FFFF000 (Type 18)
(XEN) (GUEST: 1) 000000003FFFF000 - 0000000040000000 (Type 17)
(XEN) (GUEST: 1) 0000000040000000 - 0000000040003000 (ACPI NVS)
(XEN) (GUEST: 1) 0000000040003000 - 000000004000D000 (ACPI Data)
(XEN) (GUEST: 1) 00000000FEC00000 - 0000000100000000 (Type 16)
(XEN) (GUEST: 1)
(XEN) (GUEST: 1) Start BIOS ...
(XEN) (GUEST: 1) Starting emulated 16-bit real-mode: ip=F000:FFF0
(XEN) (GUEST: 1) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) HVM_PIT: guest freq in cycles=133336837
(XEN) (GUEST: 1) Remapping master: ICW2 0x8 -> 0x20
(XEN) (GUEST: 1) Remapping slave: ICW2 0x70 -> 0x28
(XEN) (GUEST: 1) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50
vruppert Exp $
(XEN) (GUEST: 1) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date:
2005/05/07 15:55:26 $
(XEN) (GUEST: 1)
(XEN) (GUEST: 1) ata0-0: PCHS=16383/16/63 translation=lba
LCHS=1024/255/63
(XEN) (GUEST: 1) ata0 master: QEMU HARDDISK ATA-2 Hard-Disk (10240
MBytes)
(XEN) (GUEST: 1) ata0 slave: Unknown device
(XEN) (GUEST: 1) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
(XEN) (GUEST: 1) ata1 slave: Unknown device
(XEN) (GUEST: 1)
(XEN) (GUEST: 1) Booting from CD-Rom...
(XEN) (GUEST: 1) Unknown opcode at 0100:00A8=0x10A8
(XEN) (GUEST: 1) Halt called from %eip 0xD39D1


---------------------------------------------------------------------------------------------------------------
This email and any attachments are confidential and are for the use of the addressee only. If you are not the addressee, you must not use or disclose the contents to any other person. Please immediately notify the sender and delete the email. Statements and opinions expressed here may not represent those of the company.
Email correspondence is monitored by the company.

The parent company of the Renishaw Group is Renishaw plc, registered in England no. 1106260. Registered Office: New Mills, Wotton-under-Edge, Gloucestershire, GL12 8JR, United Kingdom. Tel +44 (0) 1453 524524
---------------------------------------------------------------------------------------------------------------
Re: Error Code on Intel chip when trying to boot hvm [ In reply to ]
On 7/11/06 16:17, "Bryan Prosser" <Bryan.Prosser@Renishaw.com> wrote:

> For those with any experience with QNX, I am trying to get QNX working with
> Xen. I've going about it in a similar way as installing windows with Xen, but
> when I start the guest up to install the OS it hangs on the line:
>
> 'Hit Esc for .altbootŠŠ.'
>
> Below is the dmesg that I get. Everything seems fine up until the last two
> lines.
>
> If anyone ideas/comments would be greatly appreciated!

You¹ve hit a vmxassist limitation. Looks like there¹s an instruction opcode
it doesn¹t know about. You have a few options:
1. Work out what¹s going wrong and fix vmxassist. This assumes that it
really is simply an undecodable opcode and not a more serious problem
(vmxassist simply cannot emulate dome details of real mode).
2. Wait for the new Œv2e¹ method for emulating real mode. This will replace
vmxassist with qemu¹s full cpu emulator, which will give us much more
accurate emulation of real mode. Unfortunately this new approach is not
going to be ready imminently.
3. Try an AMD Pacifica box. It emulates real mode in hardware and does not
use vmxassist at all.

-- Keir