Gavin Jones
2011-Mar-25 16:55 UTC
[Xen-users] Cannot boot Linux as HVM domU from physical disk
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! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,
I''m having some real hard time with the gplpv driver and Windows2k3
DomU
on xen 4.0
This is a xen 4 install from debian squeeze withour much changes in the
configuration
I''ve install the gplpv driver in the DomU, everything seems to work
fine
but I''m having slow data transfert between two windows DomU (even on
the
same physical host). I barely reach 100Mbps on a Gbit interface (usualy
around 8 - 10 MBytes / s).
I have read quite a lot on this "issue" on the list and various other
sources. I have tried to disable "Checksum offload" and "Large
Send
Offload" in the DomU but nothing changed.
By the way, this doesn''t affect the Linux DomU (I get full Gbit data
speed there)
I''m running out of ideas, any advice would be much appreciated.
Below is my DomU config file and network configuration :
Cheers
Olivier
DomU :
kernel = "/usr/lib/xen-4.0/boot/hvmloader"
builder=''hvm''
acpi=1
apic=1
vcpus = 8
memory = 12288
shadow_memory = 8
name = "patologix"
vif = [ ''type=paravirtualized, bridge=eth0'' ]
disk = [
''phy:/dev/datastore1/patologix-hda,hda,w'',
''phy:/dev/datastore1/patologix-hdb,hdb,w'',
''phy:/dev/datastore1/patologix-hdd,hdd,w'',
''phy:/dev/datastore1/patologix-hde,hde,w'',
#
''file:/mnt/SW_CD_Windows_Svr_Std_2003_R2_32-BIT_X64_English_ISO_x64_1_MLF_X13-73750.ISO,hdc:cdrom,r'',
]
device_model = ''/usr/lib64/xen-4.0/bin/qemu-dm''
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot="dc"
vfb = [
''type=vnc,vncdisplay=19,vncpasswd=s3cr3t,vnclisten=0.0.0.0,keymap=fr''
]
#sdl=0
#vnc=1
#vncconsole=1
#vncpasswd=''''
stdvga=0
serial=''pty''
usbdevice=''tablet''
in my xend-config.sxp the network configuration looks like :
(network-script network-bridge)
and the bridge configured on the server :
root@furax:~# brctl show
bridge name bridge id STP enabled interfaces
eth0 8000.0025900ce62c no peth0
vif10.0
vif12.0
vif15.0
vif17.0
vif20.0
vif3.0
vif4.0
vif6.0
vif7.0
vif8.0
vif9.0
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Dustin Marquess
2011-Mar-28 17:41 UTC
Re: [Xen-users] Slow network with Win2k3, HVM and GPLPV
While this might not be the problem, on anything older than Vista, 7, 2008/2008R2, you''re going to have to manually tweak your TCP stack to get decent speeds. This includes 2003/2003 R2. The new autotuning TCP stack isn''t in it. -Dustin On Mon, Mar 28, 2011 at 8:37 AM, Olivier Cant <olivier@exxoss.com> wrote:> Hi, > > I''m having some real hard time with the gplpv driver and Windows2k3 DomU on > xen 4.0 > > This is a xen 4 install from debian squeeze withour much changes in the > configuration > > I''ve install the gplpv driver in the DomU, everything seems to work fine but > I''m having slow data transfert between two windows DomU (even on the same > physical host). I barely reach 100Mbps on a Gbit interface (usualy around 8 > - 10 MBytes / s). > > I have read quite a lot on this "issue" on the list and various other > sources. I have tried to disable "Checksum offload" and "Large Send > Offload" in the DomU but nothing changed. > > By the way, this doesn''t affect the Linux DomU (I get full Gbit data speed > there) > > I''m running out of ideas, any advice would be much appreciated. > > Below is my DomU config file and network configuration : > > Cheers > > Olivier > > DomU : > kernel = "/usr/lib/xen-4.0/boot/hvmloader" > > builder=''hvm'' > acpi=1 > apic=1 > vcpus = 8 > > memory = 12288 > shadow_memory = 8 > name = "patologix" > vif = [ ''type=paravirtualized, bridge=eth0'' ] > disk = [ > ''phy:/dev/datastore1/patologix-hda,hda,w'', > ''phy:/dev/datastore1/patologix-hdb,hdb,w'', > ''phy:/dev/datastore1/patologix-hdd,hdd,w'', > ''phy:/dev/datastore1/patologix-hde,hde,w'', > > # > ''file:/mnt/SW_CD_Windows_Svr_Std_2003_R2_32-BIT_X64_English_ISO_x64_1_MLF_X13-73750.ISO,hdc:cdrom,r'', > > ] > device_model = ''/usr/lib64/xen-4.0/bin/qemu-dm'' > > # boot on floppy (a), hard disk (c) or CD-ROM (d) > # default: hard disk, cd-rom, floppy > boot="dc" > > vfb = [ > ''type=vnc,vncdisplay=19,vncpasswd=s3cr3t,vnclisten=0.0.0.0,keymap=fr'' ] > > > #sdl=0 > #vnc=1 > #vncconsole=1 > #vncpasswd='''' > stdvga=0 > serial=''pty'' > usbdevice=''tablet'' > > in my xend-config.sxp the network configuration looks like : > > (network-script network-bridge) > > and the bridge configured on the server : > root@furax:~# brctl show > bridge name bridge id STP enabled interfaces > eth0 8000.0025900ce62c no peth0 > vif10.0 > vif12.0 > vif15.0 > vif17.0 > vif20.0 > vif3.0 > vif4.0 > vif6.0 > vif7.0 > vif8.0 > vif9.0 > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Matthieu Lejeune
2011-Mar-28 18:04 UTC
Re: [Xen-users] Slow network with Win2k3, HVM and GPLPV
Hi, I have the same problems between two Windows 2008 R2 on a Xen 4.0 Dom0, I have install the GPLV driver on Windows 2008 in test mode and configure the Gigabit xen net device and disable de "Checksum Offload" and "Large Send Offload" The transfert between the two DomU are like 10 Mbytes/s I have make the same configuration like Olivier. I have exluded the disk performance. Cheers Matthieu Le 28/03/2011 19:41, Dustin Marquess a écrit :> While this might not be the problem, on anything older than Vista, 7, > 2008/2008R2, you''re going to have to manually tweak your TCP stack to > get decent speeds. This includes 2003/2003 R2. The new autotuning > TCP stack isn''t in it. > > -Dustin > > On Mon, Mar 28, 2011 at 8:37 AM, Olivier Cant<olivier@exxoss.com> wrote: >> Hi, >> >> I''m having some real hard time with the gplpv driver and Windows2k3 DomU on >> xen 4.0 >> >> This is a xen 4 install from debian squeeze withour much changes in the >> configuration >> >> I''ve install the gplpv driver in the DomU, everything seems to work fine but >> I''m having slow data transfert between two windows DomU (even on the same >> physical host). I barely reach 100Mbps on a Gbit interface (usualy around 8 >> - 10 MBytes / s). >> >> I have read quite a lot on this "issue" on the list and various other >> sources. I have tried to disable "Checksum offload" and "Large Send >> Offload" in the DomU but nothing changed. >> >> By the way, this doesn''t affect the Linux DomU (I get full Gbit data speed >> there) >> >> I''m running out of ideas, any advice would be much appreciated. >> >> Below is my DomU config file and network configuration : >> >> Cheers >> >> Olivier >> >> DomU : >> kernel = "/usr/lib/xen-4.0/boot/hvmloader" >> >> builder=''hvm'' >> acpi=1 >> apic=1 >> vcpus = 8 >> >> memory = 12288 >> shadow_memory = 8 >> name = "patologix" >> vif = [ ''type=paravirtualized, bridge=eth0'' ] >> disk = [ >> ''phy:/dev/datastore1/patologix-hda,hda,w'', >> ''phy:/dev/datastore1/patologix-hdb,hdb,w'', >> ''phy:/dev/datastore1/patologix-hdd,hdd,w'', >> ''phy:/dev/datastore1/patologix-hde,hde,w'', >> >> # >> ''file:/mnt/SW_CD_Windows_Svr_Std_2003_R2_32-BIT_X64_English_ISO_x64_1_MLF_X13-73750.ISO,hdc:cdrom,r'', >> >> ] >> device_model = ''/usr/lib64/xen-4.0/bin/qemu-dm'' >> >> # boot on floppy (a), hard disk (c) or CD-ROM (d) >> # default: hard disk, cd-rom, floppy >> boot="dc" >> >> vfb = [ >> ''type=vnc,vncdisplay=19,vncpasswd=s3cr3t,vnclisten=0.0.0.0,keymap=fr'' ] >> >> >> #sdl=0 >> #vnc=1 >> #vncconsole=1 >> #vncpasswd='''' >> stdvga=0 >> serial=''pty'' >> usbdevice=''tablet'' >> >> in my xend-config.sxp the network configuration looks like : >> >> (network-script network-bridge) >> >> and the bridge configured on the server : >> root@furax:~# brctl show >> bridge name bridge id STP enabled interfaces >> eth0 8000.0025900ce62c no peth0 >> vif10.0 >> vif12.0 >> vif15.0 >> vif17.0 >> vif20.0 >> vif3.0 >> vif4.0 >> vif6.0 >> vif7.0 >> vif8.0 >> vif9.0 >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Olivier, in your vif statement you have "paravirtualized". "vif = [ ''type=paravirtualized, bridge=eth0'' ]" Did you try it without the paravirtualized option? Shouldn''t HVM domu vif statements look like this: vif = [ "mac=00:16:36:6d:e9:16,bridge=eth0"] Here another case with bad performance: On a physical w2k3 sbs server: A file copy from win xp clients to other linux machines on the same net (switch) results in 60-70 Mbyte/s. The same action with the w2k3 server as a target gave me a data rate of 8-10 Mbyte/s. The nic in the w2k3 server is an intel pro 1000 server adapter. All readings (and doings) concerning SMB Protocol issues and smb signing problems didn''t solve the problem until now. Perhaps you have the same issue, only in virtual environment... Here some of the readings: http://support.microsoft.com/kb/321098/en-us http://support.microsoft.com/default.aspx?kbid=328890 http://support.microsoft.com/kb/321169 Another case, performance on a w2k8 sbs server (also a physical machine): After hours of analyzing network-issues I found the solution in disc configuration. Enabling the writecache of the raid-controller gave a great performance push.>From 10-12 Mbyte/s to 70-85 Mbyte/s.The bottleneck wasn''t the network at all, it was the disk config! Here I found a little tool to examine disk or net throughput in windows environments: http://download.heise.de/software/d3dc048dbbbc713e5383d1757783658f/4d90b287/3582/h2testw_1.4.zip Hope I could help a little on this... Regards, Guido -----Ursprüngliche Nachricht----- Von: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] Im Auftrag von Olivier Cant Gesendet: Montag, 28. März 2011 17:38 An: xen-users@lists.xensource.com Betreff: [Xen-users] Slow network with Win2k3, HVM and GPLPV Hi, I''m having some real hard time with the gplpv driver and Windows2k3 DomU on xen 4.0 This is a xen 4 install from debian squeeze withour much changes in the configuration I''ve install the gplpv driver in the DomU, everything seems to work fine but I''m having slow data transfert between two windows DomU (even on the same physical host). I barely reach 100Mbps on a Gbit interface (usualy around 8 - 10 MBytes / s). I have read quite a lot on this "issue" on the list and various other sources. I have tried to disable "Checksum offload" and "Large Send Offload" in the DomU but nothing changed. By the way, this doesn''t affect the Linux DomU (I get full Gbit data speed there) I''m running out of ideas, any advice would be much appreciated. Below is my DomU config file and network configuration : Cheers Olivier DomU : kernel = "/usr/lib/xen-4.0/boot/hvmloader" builder=''hvm'' acpi=1 apic=1 vcpus = 8 memory = 12288 shadow_memory = 8 name = "patologix" vif = [ ''type=paravirtualized, bridge=eth0'' ] disk = [ ''phy:/dev/datastore1/patologix-hda,hda,w'', ''phy:/dev/datastore1/patologix-hdb,hdb,w'', ''phy:/dev/datastore1/patologix-hdd,hdd,w'', ''phy:/dev/datastore1/patologix-hde,hde,w'', # ''file:/mnt/SW_CD_Windows_Svr_Std_2003_R2_32-BIT_X64_English_ISO_x64_1_MLF_X13-73750.ISO,hdc:cdrom,r'', ] device_model = ''/usr/lib64/xen-4.0/bin/qemu-dm'' # boot on floppy (a), hard disk (c) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot="dc" vfb = [ ''type=vnc,vncdisplay=19,vncpasswd=s3cr3t,vnclisten=0.0.0.0,keymap=fr'' ] #sdl=0 #vnc=1 #vncconsole=1 #vncpasswd='''' stdvga=0 serial=''pty'' usbdevice=''tablet'' in my xend-config.sxp the network configuration looks like : (network-script network-bridge) and the bridge configured on the server : root@furax:~# brctl show bridge name bridge id STP enabled interfaces eth0 8000.0025900ce62c no peth0 vif10.0 vif12.0 vif15.0 vif17.0 vif20.0 vif3.0 vif4.0 vif6.0 vif7.0 vif8.0 vif9.0 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users