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

Re: [Xen-devel] Unable to start hvm guest on cs16998


  • To: "Carb, Brian A" <Brian.Carb@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Mon, 11 Feb 2008 21:29:11 +0000
  • Delivery-date: Mon, 11 Feb 2008 13:28:51 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Achs6bAPG6hNyqYHQGql17KlLttKHgAC3Qgg
  • Thread-topic: [Xen-devel] Unable to start hvm guest on cs16998

Does the error message really look the same whether booting Windows or Linux HVM? It’s unlikely we have the same real-mode emulation problem on both. Or do you boot them both through the same bootloader (e.g., GRUB)?

It would be useful if you could confirm the same problem when you build Xen without modified max_phys_cpus, and gave the HVM guest a ‘normal’ amount of memory (e.g., 1 gigabyte).

And any differences between errors for the Windows and Linux guests do matter, if there are any.

 -- Keir

On 11/2/08 20:07, "Carb, Brian A" <Brian.Carb@xxxxxxxxxx> wrote:

Running Xen Unstable changeset 16998 (pulled  20080208) on Unisys ES7000/one 64x 256gb with SLE10SP1 x64.

Trying to start an hvm guest. Attempted 32x 240gb x64 Windows Datacenter hvm guest and 32x 24gb sles10x64 guest  - both produce a similar error:

XEN) HVM201: Booting from Hard Disk...
(XEN) HVM201: int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) HVM201: int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) HVM201: *** int 15h function AX=00C0, BX=0000 not yet supported!
(XEN) realmode.c:715:d201 Failed to emulate insn.
(XEN) realmode.c:775:d201 Real-mode emulation failed @ 3b5b:0000185c: 07 eb 18 f6 06 f2
(XEN) domain_crash_sync called from realmode.c:776
(XEN) Domain 201 (vcpu#0) crashed on cpu#63:
(XEN) ----[ Xen-3.3-unstable  x86_64  debug=y  Tainted:  M   ]----
(XEN) CPU:    63
(XEN) RIP:    0018:[<000000000000185c>]
(XEN) RFLAGS: 0000000000000002   CONTEXT: hvm
(XEN) rax: 0000000000000011   rbx: 000000000004d160   rcx: 0000000000063f40
(XEN) rdx: 0000000000002c10   rsi: 0000000000000052   rdi: 000000000002c554
(XEN) rbp: 0000000000001ff0   rsp: 0000000000001fd6   r8:  0000000000000000
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000000
(XEN) r15: 0000000000000000   cr0: 0000000000000011   cr4: 0000000000000000
(XEN) cr3: 0000000000000000   cr2: 0000000000000000
(XEN) ds: 0020   es: 0020   fs: 0020   gs: 0020   ss: 0020   cs: 0018
 
Xen was built with max_phys_cpus=64 and debug=y.

The menu.lst entry:title XEN
    root (hd0,0)
    kernel /boot/xen.gz com1=115200,8n1 apic_verbosity=debug dom0_mem=4096M console=com1,vga numa=on xenheap_megabytes=64
    module /boot/vmlinuz-xen root=/dev/disk/by-id/scsi-3600508e000000000ff4df9da7f80cc05-part1 vga=0x314 resume=/dev/sda2 splash=silent showopts debug=y
    module /boot/initrd-xen
Thanks for any ideas.
brian carb
unisys corporation - malvern, pa



_______________________________________________
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®.