[Xen-users] Cannot boot Linux as HVM domU from physical disk

Gavin Jones
2011-03-25T16:55:15Z

Hi,

I''m attempting to virtualize some legacy application servers as Xen HVM
domUs.  My hope/goal is to be able to remove the drive from the old server,
put it in the Xen dom0, and fire it up as an HVM domU.  However, that''s
not
quite working out for me.

dom0:
2xOpteron 2218
48GB RAM
OpenSuSE 11.3, all latest updates
Xen 4.0

domU:
Debian 3.1 installed on SATA drive

I''ve modified the example Xen HVM configuration file to my needs, as
below:

kernel = "hvmloader"
builder=''hvm''
memory = 1024
name = "ExampleHVMDomain"
vcpus=1
acpi=0
apic=0
vif = [ ''type=ioemu, bridge=br0'' ]
disk = [ ''phy:/dev/sdd,hda,w'' ]
device_model = ''qemu-dm''
boot="c"
vnc=1
vnclisten="0.0.0.0"
vncunused=1
vncpasswd=''''
serial=''pty''
tsc_mode=0

When I "xm create -c" the domain, I do not get any output from the
console,
but I can see the following via "xm dmesg":

(XEN) HVM14: HVM Loader
(XEN) HVM14: Detected Xen v4.0.1_21326_02-0.5
(XEN) HVM14: CPU speed is 2613 MHz
(XEN) irq.c:243: Dom14 PCI link 0 changed 0 -> 5
(XEN) HVM14: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:243: Dom14 PCI link 1 changed 0 -> 10
(XEN) HVM14: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:243: Dom14 PCI link 2 changed 0 -> 11
(XEN) HVM14: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:243: Dom14 PCI link 3 changed 0 -> 5
(XEN) HVM14: PCI-ISA link 3 routed to IRQ5
(XEN) HVM14: pci dev 01:3 INTA->IRQ10
(XEN) HVM14: pci dev 03:0 INTA->IRQ5
(XEN) HVM14: pci dev 04:0 INTA->IRQ5
(XEN) HVM14: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM14: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM14: pci dev 02:0 bar 14 size 00001000: f3000000
(XEN) HVM14: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM14: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM14: pci dev 04:0 bar 14 size 00000100: f3001000
(XEN) HVM14: pci dev 01:1 bar 20 size 00000010: 0000c201
(XEN) HVM14: Multiprocessor initialisation:
(XEN) HVM14:  - CPU0 ... 40-bit phys ... fixed MTRRs ... var MTRRs [2/8] ...
done.
(XEN) HVM14: Writing SMBIOS tables ...
(XEN) HVM14: Loading ROMBIOS ...
(XEN) HVM14: 10492 bytes of ROMBIOS high-memory extensions:
(XEN) HVM14:   Relocating to 0xfc000000-0xfc0028fc ... done
(XEN) HVM14: Loading Cirrus VGABIOS ...
(XEN) HVM14: Loading PCI Option ROM ...
(XEN) HVM14:  - Manufacturer: http://etherboot.org
(XEN) HVM14:  - Product name: gPXE
(XEN) HVM14: vm86 TSS at fc002c00
(XEN) HVM14: BIOS map:
(XEN) HVM14:  c0000-c8fff: VGA BIOS
(XEN) HVM14:  c9000-d57ff: Etherboot ROM
(XEN) HVM14:  eb000-eb158: SMBIOS tables
(XEN) HVM14:  f0000-fffff: Main BIOS
(XEN) HVM14: Invoking ROMBIOS ...
(XEN) HVM14: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) HVM14: VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert Exp
$
(XEN) HVM14: Bochs BIOS - build: 06/23/99
(XEN) HVM14: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) HVM14: Options: apmbios pcibios eltorito PMM
(XEN) HVM14:
(XEN) HVM14: ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
(XEN) HVM14: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk ( 111 GBytes)
(XEN) HVM14: IDE time out
(XEN) HVM14:
(XEN) HVM14:
(XEN) HVM14:
(XEN) HVM14: Press F12 for boot menu.
(XEN) HVM14:
(XEN) HVM14: Booting from Hard Disk...
(XEN) HVM14: Booting from 0000:7c00
(XEN) HVM14: int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) HVM14: KBD: unsupported int 16h function 03
(XEN) HVM14: int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) HVM14: int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) vlapic.c:704:d14 Local APIC Write to read-only register 0x30
(XEN) vlapic.c:704:d14 Local APIC Write to read-only register 0x20
(XEN) vlapic.c:704:d14 Local APIC Write to read-only register 0x20
(XEN) multi.c:3470:d14 write to pagetable during event injection:
cr2=0xf78bfffc, mfn=0x1c2bf
(XEN) multi.c:3470:d14 write to pagetable during event injection:
cr2=0xf7e73ffc, mfn=0x1bc73
(XEN) multi.c:3470:d14 write to pagetable during event injection:
cr2=0xf76d1ffc, mfn=0x1c4d1
(XEN) multi.c:3470:d14 write to pagetable during event injection:
cr2=0xf7bcfffc, mfn=0x1c1cf
(XEN) multi.c:3470:d14 write to pagetable during event injection:
cr2=0xf7ba5ffc, mfn=0x1c1a5
(XEN) multi.c:3470:d14 write to pagetable during event injection:
cr2=0xf7babffc, mfn=0x1c1ab

The domU then seems to hang there, and does not come up.  As far as I can
tell, there is later output from "xm dmesg".

I suppose I''m wondering a few things:
1.  are those messages/errors causing my apparent no boot?
2.  what must I do to wrangle this thing into booting?

My apologies if this is obvious/trivial; I''ve been working on it for 2
or 3
days now with no success, and google hasn''t come to my rescue yet.

Thank you!