Philipp Schmid
2009-Feb-12 22:17 UTC
[Xen-users] Xen 3.3.1 Windows HVM Disk I/O -> domU and dom0 hangs
Hi, we are currently working on getting windows working on your xen servers. but we are facing a severe problem where dom0 and all domus hang for 1-5 seconds from time to time. we think it is probably because of disk i/o, because top sometimes says 100% wa (waiting on io) during the hang. dom0 has cpu 0 for exclusive use and the windows vms use cpu 1 to 7. should we give dom0 more than once cpu? would this prevent the hang? or is this a configuration error? are there some scheduler settings we could experience with (linux kernel i/o scheduler?) we use LVM for HVM domUs on a 6 disk raid 10 array. Lg Philipp Schmid ps: xen 3.3.1 and 2.6.18 are compiled from source _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2009-Feb-12 23:00 UTC
Re: [Xen-users] Xen 3.3.1 Windows HVM Disk I/O -> domU and dom0 hangs
On Fri, Feb 13, 2009 at 5:17 AM, Philipp Schmid <lists@schmidp.com> wrote:> Hi, > > we are currently working on getting windows working on your xen servers. > but we are facing a severe problem where dom0 and all domus hang for 1-5 > seconds from time to time.Are you using PV drivers? What domU storage backend did you use? file:? tap:aio:? phy:? Are you using some kind of LVM snapshot?> > we think it is probably because of disk i/o, because top sometimes says 100% > wa (waiting on io) during the hang.What does iostat say at that time? If i/o wait is 100% but i/o throughput is low, perhaps you''re experiencing the symptoms of disk failure. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper
2009-Feb-13 00:01 UTC
RE: [Xen-users] Xen 3.3.1 Windows HVM Disk I/O -> domU and dom0 hangs
> Hi, > > we are currently working on getting windows working on your xenservers.> but we are facing a severe problem where dom0 and all domus hang for > 1-5 seconds from time to time. > > we think it is probably because of disk i/o, because top sometimes > says 100% wa (waiting on io) during the hang. > > dom0 has cpu 0 for exclusive use and the windows vms use cpu 1 to 7. > should we give dom0 more than once cpu? > would this prevent the hang? > > or is this a configuration error? > are there some scheduler settings we could experience with (linux > kernel i/o scheduler?) > > we use LVM for HVM domUs on a 6 disk raid 10 array. >What hardware and what RAID controller? I had awful problems with a low end (E200 I think) HP RAID adapter. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Philipp Schmid
2009-Feb-13 00:09 UTC
Re: [Xen-users] Xen 3.3.1 Windows HVM Disk I/O -> domU and dom0 hangs
Hi, On Feb 13, 2009, at 12:00 AM, Fajar A. Nugraha wrote:> Are you using PV drivers? > What domU storage backend did you use? file:? tap:aio:? phy:? > Are you using some kind of LVM snapshot?yes, we use the xen gpl pv drivers. the storage backend is phy on a lvm volume this is our config file: kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' name = ''g-hlsan9ib'' memory = ''4096'' vcpus = ''8'' cpu_weight = ''4096'' cpus = "1-7,^0" vif = [ ''ip=172.16.123.109,mac=00:16:3E: 11:32:8F,vifname=00163E11328F,type=,bridge=eth1'', ] disk = [ ''phy:/dev/domU/d-jho6fmdr,hda,w'',''phy:/dev/domU/d- jmishjr5,hdb,w'' ,''file:/root/win2003_r2_64.iso,hdc:cdrom,r'', ] device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' boot="c" # Enable/disable HVM guest PAE, default=1 (enabled) #pae=1 # Enable/disable HVM guest ACPI, default=1 (enabled) #acpi=1 sdl=0 vnc=1 vnclisten="0.0.0.0" vncdisplay=2 vncpasswd='''' stdvga=0 serial=''pty''>> we think it is probably because of disk i/o, because top sometimes >> says 100% >> wa (waiting on io) during the hang. > > What does iostat say at that time? If i/o wait is 100% but i/o > throughput is low, perhaps you''re experiencing the symptoms of disk > failure.I don''t think it has to do with disk failure, as our raid controller reports all disks are "healthy" and there are no errors. Lg Philipp _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Philipp Schmid
2009-Feb-13 00:11 UTC
Re: [Xen-users] Xen 3.3.1 Windows HVM Disk I/O -> domU and dom0 hangs
Hi, we are using dell poweredge 2950 servers with a "PERC 6/i Integrated" hardware raid controller. Lg Philipp On Feb 13, 2009, at 1:01 AM, James Harper wrote:>> we use LVM for HVM domUs on a 6 disk raid 10 array. >> > > What hardware and what RAID controller? > > I had awful problems with a low end (E200 I think) HP RAID adapter. > > James >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel Kao
2009-Feb-13 00:15 UTC
Re: [Xen-users] Xen 3.3.1 Windows HVM Disk I/O -> domU and dom0 hangs
Philipp Schmid wrote:> Hi, > > we are using dell poweredge 2950 servers with a "PERC 6/i Integrated" > hardware raid controller. > > Lg PhilippHow are the read-ahead and write-cache settings set on the PERC6/i and which/whose RAID drivers are you using under dom0 (output from dmesg, etc.) Cheers, Daniel -- Daniel Kao Übermind, Inc. Seattle, WA, U.S.A. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Philipp Schmid
2009-Feb-13 00:29 UTC
Re: [Xen-users] Xen 3.3.1 Windows HVM Disk I/O -> domU and dom0 hangs
Hi, we are using the stock xen 2.6.18 kernel (build form the xen sources). Are there others drivers than in the stock kernel ones available? I think this is the relevant dmsg output for the raid controller:> scsi0 : LSI Logic SAS based MegaRAID driver > > SCSI device sda: 2927099904 512-byte hdwr sectors (1498675 MB) > sda: Write Protect is off > sda: Mode Sense: 1f 00 00 08 > SCSI device sda: drive cache: write back > SCSI device sda: 2927099904 512-byte hdwr sectors (1498675 MB) > sda: Write Protect is off > sda: Mode Sense: 1f 00 00 08 > SCSI device sda: drive cache: write back > sda: sda1 sda2 > sd 0:2:0:0: Attached scsi disk sdaBut what conserns me now is that on all our servers, I just found out that the state of our array says "degraded" and "30% rebuild rate". I just opened a support ticket with dell about this, but has anyone an idea what this could be? Regards, Philipp omreport output:> xen26:~# omreport storage controller > Controller PERC 6/i Integrated (Embedded) > > Controllers > ID : 0 > Status : Non-Critical > Name : PERC 6/i Integrated > Slot ID : Embedded > State : Degraded > Firmware Version : 6.0.3-0002 > Minimum Required Firmware Version : Not Applicable > Driver Version : 00.00.03.01 > Minimum Required Driver Version : 00.00.03.13 > Number of Connectors : 2 > Rebuild Rate : 30% > BGI Rate : 30% > Check Consistency Rate : 30% > Reconstruct Rate : 30% > Alarm State : Not Applicable > Cluster Mode : Not Applicable > SCSI Initiator ID : Not Applicable > Cache Memory Size : 256 MB > Patrol Read Mode : Auto > Patrol Read State : Stopped > Patrol Read Rate : 30% > Patrol Read Iterations : 16 > > xen26:~# omreport storage vdisk controller=0 > List of Virtual Disks on Controller PERC 6/i Integrated (Embedded) > > Controller PERC 6/i Integrated (Embedded) > ID : 0 > Status : Ok > Name : Virtual Disk 0 > State : Ready > Progress : Not Applicable > Layout : RAID-10 > Size : 1,395.75 GB (1498675150848 bytes) > Device Name : /dev/sda > Type : SAS > Read Policy : No Read Ahead > Write Policy : Write Back > Cache Policy : Not Applicable > Stripe Element Size : 64 KB > Disk Cache Policy : Disabledcomplete dmesg output:> Bootdata ok (command line is root=/dev/mapper/domU-root ro > console=tty0) > Linux version 2.6.18.8netmonic-xen0-1.0 > (root@intern2.netmonic.local) (gcc version 4.1.2 20061115 > (prerelease) (Debian 4.1.1-21)) #1 SMP Thu Apr 10 00:13:37 CEST 2008 > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 00000003e9433000 (usable) > DMI 2.5 present. > On node 0 totalpages: 4045101 > DMA zone: 4040 pages, LIFO batch:0 > DMA32 zone: 1030200 pages, LIFO batch:31 > Normal zone: 3010861 pages, LIFO batch:31 > ACPI: RSDP (v002 DELL ) @ > 0x00000000000f2190 > ACPI: XSDT (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ > 0x00000000000f222c > ACPI: FADT (v003 DELL PE_SC3 0x00000001 DELL 0x00000001) @ > 0x00000000bfb83524 > ACPI: MADT (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ > 0x00000000bfb83078 > ACPI: SPCR (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ > 0x00000000bfb83130 > ACPI: HPET (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ > 0x00000000bfb83184 > ACPI: MCFG (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ > 0x00000000bfb831c0 > ACPI: WD__ (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ > 0x00000000bfb83200 > ACPI: SLIC (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ > 0x00000000bfb83338 > ACPI: ERST (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ > 0x00000000bfb6ab18 > ACPI: HEST (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ > 0x00000000bfb6ad28 > ACPI: BERT (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ > 0x00000000bfb6a998 > ACPI: EINJ (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ > 0x00000000bfb6a9c8 > ACPI: TCPA (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ > 0x00000000bfb834bc > ACPI: DSDT (v001 DELL PE_SC3 0x00000001 INTL 0x20050624) @ > 0x0000000000000000 > ACPI: Local APIC address 0xfee00000 > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled) > ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled) > ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) > ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled) > ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled) > ACPI: LAPIC (acpi_id[0x07] lapic_id[0x03] enabled) > ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled) > ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) > ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) > IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > ACPI: IRQ0 used by override. > ACPI: IRQ2 used by override. > ACPI: IRQ9 used by override. > Setting APIC routing to xen > Using ACPI (MADT) for SMP configuration information > Allocating PCI resources starting at c2000000 (gap: c0000000:20000000) > Built 1 zonelists. Total pages: 4045101 > Kernel command line: root=/dev/mapper/domU-root ro console=tty0 > Initializing CPU#0 > PID hash table entries: 4096 (order: 12, 32768 bytes) > Xen reported: 1995.033 MHz processor. > Console: colour VGA+ 80x25 > Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes) > Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes) > Software IO TLB enabled: > Aperture: 64 megabytes > Kernel range: ffff880014d79000 - ffff880018d79000 > Address size: 27 bits > PCI-DMA: Using software bounce buffering for IO (SWIOTLB) > Memory: 15996768k/16404684k available (2380k kernel code, 398812k > reserved, 1814k data, 164k init) > Calibrating delay using timer specific routine.. 3991.67 BogoMIPS > (lpj=7983353) > Security Framework v1.0.0 initialized > Capability LSM initialized > Mount-cache hash table entries: 256 > CPU: L1 I cache: 32K, L1 D cache: 32K > CPU: L2 cache: 6144K > CPU: Physical Processor ID: 0 > CPU: Processor Core ID: 0 > SMP alternatives: switching to UP code > ACPI: Core revision 20060707 > SMP alternatives: switching to SMP code > Initializing CPU#1 > Initializing CPU#2 > CPU: L1 I cache: 32K, L1 D cache: 32K > CPU: L2 cache: 6144K > CPU: Physical Processor ID: 0 > CPU: Processor Core ID: 2 > Initializing CPU#3 > CPU: L1 I cache: 32K, L1 D cache: 32K > CPU: L2 cache: 6144K > CPU: Physical Processor ID: 1 > CPU: Processor Core ID: 2 > Initializing CPU#4 > CPU: L1 I cache: 32K, L1 D cache: 32K > CPU: L2 cache: 6144K > CPU: Physical Processor ID: 0 > CPU: Processor Core ID: 1 > Initializing CPU#5 > CPU: L1 I cache: 32K, L1 D cache: 32K > CPU: L2 cache: 6144K > CPU: Physical Processor ID: 1 > CPU: Processor Core ID: 1 > Initializing CPU#6 > CPU: L1 I cache: 32K, L1 D cache: 32K > CPU: L2 cache: 6144K > CPU: Physical Processor ID: 0 > CPU: Processor Core ID: 3 > Brought up 8 CPUs > Initializing CPU#7 > CPU: L1 I cache: 32K, L1 D cache: 32K > CPU: L2 cache: 6144K > CPU: Physical Processor ID: 1 > CPU: Processor Core ID: 3 > CPU: L1 I cache: 32K, L1 D cache: 32K > CPU: L2 cache: 6144K > CPU: Physical Processor ID: 1 > CPU: Processor Core ID: 0 > migration_cost=12768 > checking if image is initramfs... it is > Freeing initrd memory: 12645k freed > NET: Registered protocol family 16 > ACPI: bus type pci registered > PCI: Using MMCONFIG at e0000000 > ACPI: Interpreter enabled > ACPI: Using IOAPIC for interrupt routing > ACPI: PCI Root Bridge [PCI0] (0000:00) > PCI: Probing PCI hardware (bus 00) > PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 > Boot video device is 0000:0e:0d.0 > PCI: Transparent bridge - 0000:00:1e.0 > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT] > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2.UPST._PRT] > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2.UPST.DWN1._PRT] > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2.UPST.DWN2._PRT] > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3._PRT] > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3.PE2P._PRT] > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT] > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX6._PRT] > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.SBEX._PRT] > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.COMP._PRT] > ACPI: PCI Interrupt Link [LK00] (IRQs 3 4 *5 6 7 10 11 12) > ACPI: PCI Interrupt Link [LK01] (IRQs 3 4 5 6 7 10 11 12) *0, > disabled. > ACPI: PCI Interrupt Link [LK02] (IRQs 3 4 5 6 7 10 11 12) *0, > disabled. > ACPI: PCI Interrupt Link [LK03] (IRQs 3 4 5 6 7 10 *11 12) > ACPI: PCI Interrupt Link [LK04] (IRQs 3 4 5 6 7 *10 11 12) > ACPI: PCI Interrupt Link [LK05] (IRQs 3 4 5 6 7 10 *11 12) > ACPI: PCI Interrupt Link [LK06] (IRQs 3 4 5 6 7 10 11 12) *0, > disabled. > ACPI: PCI Interrupt Link [LK07] (IRQs 3 4 5 6 7 10 11 12) *0, > disabled. > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: PnP ACPI init > pnp: PnP ACPI: found 12 devices > xen_mem: Initialising balloon driver. > SCSI subsystem initialized > usbcore: registered new driver usbfs > usbcore: registered new driver hub > PCI: Using ACPI for IRQ routing > PCI: If a device doesn''t work, try "pci=routeirq". If it helps, > post a report > pnp: 00:08: ioport range 0x800-0x87f could not be reserved > pnp: 00:08: ioport range 0x880-0x8bf has been reserved > pnp: 00:08: ioport range 0x8c0-0x8df has been reserved > pnp: 00:08: ioport range 0x8e0-0x8e3 has been reserved > pnp: 00:08: ioport range 0x900-0x900 has been reserved > pnp: 00:08: ioport range 0xc00-0xc7f has been reserved > pnp: 00:08: ioport range 0xca0-0xca7 has been reserved > pnp: 00:08: ioport range 0xca9-0xcab has been reserved > pnp: 00:09: ioport range 0xca8-0xca8 has been reserved > pnp: 00:09: ioport range 0xcac-0xcac has been reserved > PCI: Bridge: 0000:06:00.0 > IO window: disabled. > MEM window: f4000000-f7ffffff > PREFETCH window: disabled. > PCI: Bridge: 0000:05:00.0 > IO window: disabled. > MEM window: f4000000-f7ffffff > PREFETCH window: disabled. > PCI: Bridge: 0000:05:01.0 > IO window: disabled. > MEM window: disabled. > PREFETCH window: disabled. > PCI: Bridge: 0000:04:00.0 > IO window: disabled. > MEM window: f4000000-f7ffffff > PREFETCH window: disabled. > PCI: Bridge: 0000:04:00.3 > IO window: disabled. > MEM window: disabled. > PREFETCH window: disabled. > PCI: Bridge: 0000:00:02.0 > IO window: disabled. > MEM window: f2000000-f7ffffff > PREFETCH window: disabled. > PCI: Bridge: 0000:00:03.0 > IO window: e000-efff > MEM window: fc300000-fc4fffff > PREFETCH window: disabled. > PCI: Bridge: 0000:00:04.0 > IO window: disabled. > MEM window: disabled. > PREFETCH window: disabled. > PCI: Bridge: 0000:00:05.0 > IO window: disabled. > MEM window: disabled. > PREFETCH window: disabled. > PCI: Bridge: 0000:00:06.0 > IO window: disabled. > MEM window: disabled. > PREFETCH window: disabled. > PCI: Bridge: 0000:00:07.0 > IO window: disabled. > MEM window: disabled. > PREFETCH window: disabled. > PCI: Bridge: 0000:02:00.0 > IO window: disabled. > MEM window: f8000000-fbffffff > PREFETCH window: disabled. > PCI: Bridge: 0000:00:1c.0 > IO window: disabled. > MEM window: f8000000-fbffffff > PREFETCH window: disabled. > PCI: Bridge: 0000:00:1e.0 > IO window: d000-dfff > MEM window: fc100000-fc2fffff > PREFETCH window: d8000000-dfffffff > GSI 16 sharing vector 0xA0 and IRQ 16 > ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16 > PCI: Setting latency timer of device 0000:00:02.0 to 64 > ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 16 (level, low) -> IRQ 16 > PCI: Setting latency timer of device 0000:04:00.0 to 64 > ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 16 (level, low) -> IRQ 16 > PCI: Setting latency timer of device 0000:05:00.0 to 64 > PCI: Setting latency timer of device 0000:06:00.0 to 64 > ACPI: PCI Interrupt 0000:05:01.0[A] -> GSI 16 (level, low) -> IRQ 16 > PCI: Setting latency timer of device 0000:05:01.0 to 64 > PCI: Setting latency timer of device 0000:04:00.3 to 64 > ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 16 (level, low) -> IRQ 16 > PCI: Setting latency timer of device 0000:00:03.0 to 64 > ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level, low) -> IRQ 16 > PCI: Setting latency timer of device 0000:00:04.0 to 64 > PCI: Setting latency timer of device 0000:00:05.0 to 64 > ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 16 (level, low) -> IRQ 16 > PCI: Setting latency timer of device 0000:00:06.0 to 64 > PCI: Setting latency timer of device 0000:00:07.0 to 64 > ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16 > PCI: Setting latency timer of device 0000:00:1c.0 to 64 > PCI: Setting latency timer of device 0000:02:00.0 to 64 > PCI: Setting latency timer of device 0000:00:1e.0 to 64 > NET: Registered protocol family 2 > IP route cache hash table entries: 524288 (order: 10, 4194304 bytes) > TCP established hash table entries: 262144 (order: 10, 4194304 bytes) > TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) > TCP: Hash tables configured (established 262144 bind 65536) > TCP reno registered > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > Initializing Cryptographic API > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > PCI: Setting latency timer of device 0000:00:02.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:02.0:pcie00] > Allocate Port Service[0000:00:02.0:pcie01] > PCI: Setting latency timer of device 0000:00:03.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:03.0:pcie00] > Allocate Port Service[0000:00:03.0:pcie01] > PCI: Setting latency timer of device 0000:00:04.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:04.0:pcie00] > Allocate Port Service[0000:00:04.0:pcie01] > PCI: Setting latency timer of device 0000:00:05.0 to 64 > pcie_portdrv_probe->Dev[25e5:8086] has invalid IRQ. Check vendor BIOS > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:05.0:pcie00] > Allocate Port Service[0000:00:05.0:pcie01] > PCI: Setting latency timer of device 0000:00:06.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:06.0:pcie00] > Allocate Port Service[0000:00:06.0:pcie01] > PCI: Setting latency timer of device 0000:00:07.0 to 64 > pcie_portdrv_probe->Dev[25e7:8086] has invalid IRQ. Check vendor BIOS > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:07.0:pcie00] > Allocate Port Service[0000:00:07.0:pcie01] > PCI: Setting latency timer of device 0000:00:1c.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:1c.0:pcie00] > Allocate Port Service[0000:00:1c.0:pcie03] > PCI: Setting latency timer of device 0000:04:00.0 to 64 > Allocate Port Service[0000:04:00.0:pcie10] > Allocate Port Service[0000:04:00.0:pcie11] > PCI: Setting latency timer of device 0000:05:00.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:05:00.0:pcie20] > Allocate Port Service[0000:05:00.0:pcie21] > PCI: Setting latency timer of device 0000:05:01.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:05:01.0:pcie20] > Allocate Port Service[0000:05:01.0:pcie21] > ACPI: Power Button (FF) [PWRF] > ACPI: CPU0 (power states: C1[C1] C3[C3]) > ACPI: CPU4 (power states: C1[C1] C3[C3]) > ACPI: CPU2 (power states: C1[C1] C3[C3]) > ACPI: CPU6 (power states: C1[C1] C3[C3]) > ACPI: CPU1 (power states: C1[C1] C3[C3]) > ACPI: CPU5 (power states: C1[C1] C3[C3]) > ACPI: CPU3 (power states: C1[C1] C3[C3]) > ACPI: CPU7 (power states: C1[C1] C3[C3]) > Real Time Clock Driver v1.12ac > hpet_acpi_add: no address or irqs in _CRS > floppy0: Unable to grab DMA2 for the floppy driver > floppy0: no floppy controllers found > RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize > forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.56. > PPP generic driver version 2.4.2 > Xen virtual console successfully installed as xvc0 > Event-channel device installed. > Successfully initialized TPM backend driver. > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 33MHz system bus speed for PIO modes; override with > idebus=xx > ESB2: IDE controller at PCI slot 0000:00:1f.1 > ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 16 (level, low) -> IRQ 16 > ESB2: chipset revision 9 > ESB2: not 100% native mode: will probe irqs later > ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio > Probing IDE interface ide0... > hda: TEAC DVD-ROM DV28EV, ATAPI CD/DVD-ROM drive > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > Probing IDE interface ide1... > hda: ATAPI 24X DVD-ROM drive, 198kB Cache, UDMA(33) > Uniform CD-ROM driver Revision: 3.20 > GSI 17 sharing vector 0xA8 and IRQ 17 > ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 21 (level, low) -> IRQ 17 > PCI: Setting latency timer of device 0000:00:1d.7 to 64 > ehci_hcd 0000:00:1d.7: EHCI Host Controller > ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1 > ehci_hcd 0000:00:1d.7: debug port 1 > PCI: cache line size of 32 is not supported by device 0000:00:1d.7 > ehci_hcd 0000:00:1d.7: irq 17, io mem 0xfc500400 > ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 > usb usb1: configuration #1 chosen from 1 choice > hub 1-0:1.0: USB hub found > hub 1-0:1.0: 8 ports detected > ohci_hcd: 2005 April 22 USB 1.1 ''Open'' Host Controller (OHCI) Driver > (PCI) > USB Universal Host Controller Interface driver v3.0 > ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 21 (level, low) -> IRQ 17 > PCI: Setting latency timer of device 0000:00:1d.0 to 64 > uhci_hcd 0000:00:1d.0: UHCI Host Controller > uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2 > uhci_hcd 0000:00:1d.0: irq 17, io base 0x0000cce0 > usb usb2: configuration #1 chosen from 1 choice > hub 2-0:1.0: USB hub found > hub 2-0:1.0: 2 ports detected > GSI 18 sharing vector 0xB0 and IRQ 18 > ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 20 (level, low) -> IRQ 18 > PCI: Setting latency timer of device 0000:00:1d.1 to 64 > uhci_hcd 0000:00:1d.1: UHCI Host Controller > uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3 > uhci_hcd 0000:00:1d.1: irq 18, io base 0x0000ccc0 > usb usb3: configuration #1 chosen from 1 choice > hub 3-0:1.0: USB hub found > hub 3-0:1.0: 2 ports detected > ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 21 (level, low) -> IRQ 17 > PCI: Setting latency timer of device 0000:00:1d.2 to 64 > uhci_hcd 0000:00:1d.2: UHCI Host Controller > uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4 > uhci_hcd 0000:00:1d.2: irq 17, io base 0x0000cca0 > usb usb4: configuration #1 chosen from 1 choice > hub 4-0:1.0: USB hub found > hub 4-0:1.0: 2 ports detected > usb 1-5: new high speed USB device using ehci_hcd and address 2 > ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 20 (level, low) -> IRQ 18 > PCI: Setting latency timer of device 0000:00:1d.3 to 64 > uhci_hcd 0000:00:1d.3: UHCI Host Controller > uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5 > uhci_hcd 0000:00:1d.3: irq 18, io base 0x0000cc80 > usb usb5: configuration #1 chosen from 1 choice > hub 5-0:1.0: USB hub found > hub 5-0:1.0: 2 ports detected > usb 1-5: configuration #1 chosen from 1 choice > hub 1-5:1.0: USB hub found > hub 1-5:1.0: 4 ports detected > usbcore: registered new driver usblp > drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver > Initializing USB Mass Storage driver... > usbcore: registered new driver usb-storage > USB Mass Storage support registered. > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > serio: i8042 AUX port at 0x60,0x64 irq 12 > serio: i8042 KBD port at 0x60,0x64 irq 1 > mice: PS/2 mouse device common for all mice > xenoprofile_init: ret -19, events -12, xenoprof_is_primary 0 > oprofile: using timer interrupt. > TCP bic registered > NET: Registered protocol family 1 > NET: Registered protocol family 17 > ACPI: (supports S0 S4 S5) > Freeing unused kernel memory: 164k freed > megasas: 00.00.03.01 Sun May 14 22:49:52 PDT 2006 > megasas: 0x1000:0x0060:0x1028:0x1f0c: bus 1:slot 0:func 0 > ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 > PCI: Setting latency timer of device 0000:01:00.0 to 64 > scsi0 : LSI Logic SAS based MegaRAID driver > Vendor: SEAGATE Model: ST3500620SS Rev: MS04 > Type: Direct-Access ANSI SCSI revision: 05 > Vendor: SEAGATE Model: ST3500620SS Rev: MS04 > Type: Direct-Access ANSI SCSI revision: 05 > Vendor: SEAGATE Model: ST3500620SS Rev: MS04 > Type: Direct-Access ANSI SCSI revision: 05 > Vendor: SEAGATE Model: ST3500620SS Rev: MS04 > Type: Direct-Access ANSI SCSI revision: 05 > Vendor: SEAGATE Model: ST3500620SS Rev: MS04 > Type: Direct-Access ANSI SCSI revision: 05 > Vendor: SEAGATE Model: ST3500620SS Rev: MS04 > Type: Direct-Access ANSI SCSI revision: 05 > Vendor: DP Model: BACKPLANE Rev: 1.05 > Type: Enclosure ANSI SCSI revision: 05 > Vendor: DELL Model: PERC 6/i Rev: 1.11 > Type: Direct-Access ANSI SCSI revision: 05 > Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.4.44 (August > 10, 2006) > ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 16 (level, low) -> IRQ 16 > eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit > 133MHz found at mem f4000000, IRQ 16, node addr 00221987c97d > ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16 > eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit > 133MHz found at mem f8000000, IRQ 16, node addr 00221987c97b > SCSI device sda: 2927099904 512-byte hdwr sectors (1498675 MB) > sda: Write Protect is off > sda: Mode Sense: 1f 00 00 08 > SCSI device sda: drive cache: write back > SCSI device sda: 2927099904 512-byte hdwr sectors (1498675 MB) > sda: Write Protect is off > sda: Mode Sense: 1f 00 00 08 > SCSI device sda: drive cache: write back > sda: sda1 sda2 > sd 0:2:0:0: Attached scsi disk sda > device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com > Attempting manual resume > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 > intel_rng: FWH not detected > EXT3 FS on dm-1, internal journal > loop: loaded (max 8 devices) > kjournald starting. Commit interval 5 seconds > EXT3 FS on sda1, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > Adding 1048568k swap on /dev/mapper/domU-swap. Priority:-1 extents: > 1 across:1048568kOn Feb 13, 2009, at 1:15 AM, Daniel Kao wrote:> Philipp Schmid wrote: >> Hi, >> >> we are using dell poweredge 2950 servers with a "PERC 6/i >> Integrated" hardware raid controller. >> >> Lg Philipp > How are the read-ahead and write-cache settings set on the PERC6/i > and which/whose RAID drivers are you using under dom0 (output from > dmesg, etc.) > > Cheers, > Daniel_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel Kao
2009-Feb-13 00:43 UTC
Re: [Xen-users] Xen 3.3.1 Windows HVM Disk I/O -> domU and dom0 hangs
Hi Philipp, This seems to be is turning more into a Dell/RAID issue than a Xen issue so if it turns out to be more of a Dell issue, we should probably take this offline the xen-users list and you can just e-mail me directly. "Degraded" is better than "Offline". It looks like you have six Seagate 500GB ES.2 SAS drives on your PERC6/i setup in RAID-10/RAID-01, etc (judging from the approximately 1.5TB physical volume). The RAID controller is rebuilding the array which is a good thing so don''t reboot, etc. until it gets to 100% on the rebuild or if it''s stuck at 30%, wait for Dell to get back to you. If it''s still stuck at 30%, then something has gone horribly wrong. Assuming your BBU for the PERC6/i card is good, "write-back" is good so leave that be. Your "read policy" is set to none and that''ll cause issues to what you''ve described. It happened with me with a batch of PowerEdge 1950 III''s I received from Dell a while back. After you get your array back into a "Ready" or "Online" status, change the read policy to something like "Adaptive Read Ahead" as a starting point. Sometimes, Dell sets the read policy to "Adaptive Read Ahead" or similar straight from the factory. Sometimes... they don''t and they''re shipped turned off if you ask them to configure the array for your from the factory. You''re driver looks fine. So in a nutshell, get the array out of "Degraded" status, turn on "Adaptive Read Ahead" and go from there. You can tweak the read ahead later to whatever suits your needs on the PERC6/i. -- Daniel Kao Übermind, Inc. Seattle, WA, U.S.A. Philipp Schmid wrote:> Hi, > > we are using the stock xen 2.6.18 kernel (build form the xen sources). > Are there others drivers than in the stock kernel ones available? > > I think this is the relevant dmsg output for the raid controller: > >> scsi0 : LSI Logic SAS based MegaRAID driver >> >> SCSI device sda: 2927099904 512-byte hdwr sectors (1498675 MB) >> sda: Write Protect is off >> sda: Mode Sense: 1f 00 00 08 >> SCSI device sda: drive cache: write back >> SCSI device sda: 2927099904 512-byte hdwr sectors (1498675 MB) >> sda: Write Protect is off >> sda: Mode Sense: 1f 00 00 08 >> SCSI device sda: drive cache: write back >> sda: sda1 sda2 >> sd 0:2:0:0: Attached scsi disk sda > > > But what conserns me now is that on all our servers, I just found out > that the state of our array says "degraded" and "30% rebuild rate". > I just opened a support ticket with dell about this, but has anyone an > idea what this could be? > > Regards, > > Philipp > > > > omreport output: > >> xen26:~# omreport storage controller >> Controller PERC 6/i Integrated (Embedded) >> >> Controllers >> ID : 0 >> Status : Non-Critical >> Name : PERC 6/i Integrated >> Slot ID : Embedded >> State : Degraded >> Firmware Version : 6.0.3-0002 >> Minimum Required Firmware Version : Not Applicable >> Driver Version : 00.00.03.01 >> Minimum Required Driver Version : 00.00.03.13 >> Number of Connectors : 2 >> Rebuild Rate : 30% >> BGI Rate : 30% >> Check Consistency Rate : 30% >> Reconstruct Rate : 30% >> Alarm State : Not Applicable >> Cluster Mode : Not Applicable >> SCSI Initiator ID : Not Applicable >> Cache Memory Size : 256 MB >> Patrol Read Mode : Auto >> Patrol Read State : Stopped >> Patrol Read Rate : 30% >> Patrol Read Iterations : 16 >> >> xen26:~# omreport storage vdisk controller=0 >> List of Virtual Disks on Controller PERC 6/i Integrated (Embedded) >> >> Controller PERC 6/i Integrated (Embedded) >> ID : 0 >> Status : Ok >> Name : Virtual Disk 0 >> State : Ready >> Progress : Not Applicable >> Layout : RAID-10 >> Size : 1,395.75 GB (1498675150848 bytes) >> Device Name : /dev/sda >> Type : SAS >> Read Policy : No Read Ahead >> Write Policy : Write Back >> Cache Policy : Not Applicable >> Stripe Element Size : 64 KB >> Disk Cache Policy : Disabled > > > > complete dmesg output: > >> Bootdata ok (command line is root=/dev/mapper/domU-root ro console=tty0) >> Linux version 2.6.18.8netmonic-xen0-1.0 (root@intern2.netmonic.local) >> (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP >> Thu Apr 10 00:13:37 CEST 2008 >> BIOS-provided physical RAM map: >> Xen: 0000000000000000 - 00000003e9433000 (usable) >> DMI 2.5 present. >> On node 0 totalpages: 4045101 >> DMA zone: 4040 pages, LIFO batch:0 >> DMA32 zone: 1030200 pages, LIFO batch:31 >> Normal zone: 3010861 pages, LIFO batch:31 >> ACPI: RSDP (v002 DELL ) @ >> 0x00000000000f2190 >> ACPI: XSDT (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ >> 0x00000000000f222c >> ACPI: FADT (v003 DELL PE_SC3 0x00000001 DELL 0x00000001) @ >> 0x00000000bfb83524 >> ACPI: MADT (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ >> 0x00000000bfb83078 >> ACPI: SPCR (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ >> 0x00000000bfb83130 >> ACPI: HPET (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ >> 0x00000000bfb83184 >> ACPI: MCFG (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ >> 0x00000000bfb831c0 >> ACPI: WD__ (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ >> 0x00000000bfb83200 >> ACPI: SLIC (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ >> 0x00000000bfb83338 >> ACPI: ERST (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ >> 0x00000000bfb6ab18 >> ACPI: HEST (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ >> 0x00000000bfb6ad28 >> ACPI: BERT (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ >> 0x00000000bfb6a998 >> ACPI: EINJ (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ >> 0x00000000bfb6a9c8 >> ACPI: TCPA (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ >> 0x00000000bfb834bc >> ACPI: DSDT (v001 DELL PE_SC3 0x00000001 INTL 0x20050624) @ >> 0x0000000000000000 >> ACPI: Local APIC address 0xfee00000 >> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) >> ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled) >> ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled) >> ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) >> ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled) >> ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled) >> ACPI: LAPIC (acpi_id[0x07] lapic_id[0x03] enabled) >> ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled) >> ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) >> ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) >> IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 >> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) >> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) >> ACPI: IRQ0 used by override. >> ACPI: IRQ2 used by override. >> ACPI: IRQ9 used by override. >> Setting APIC routing to xen >> Using ACPI (MADT) for SMP configuration information >> Allocating PCI resources starting at c2000000 (gap: c0000000:20000000) >> Built 1 zonelists. Total pages: 4045101 >> Kernel command line: root=/dev/mapper/domU-root ro console=tty0 >> Initializing CPU#0 >> PID hash table entries: 4096 (order: 12, 32768 bytes) >> Xen reported: 1995.033 MHz processor. >> Console: colour VGA+ 80x25 >> Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes) >> Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes) >> Software IO TLB enabled: >> Aperture: 64 megabytes >> Kernel range: ffff880014d79000 - ffff880018d79000 >> Address size: 27 bits >> PCI-DMA: Using software bounce buffering for IO (SWIOTLB) >> Memory: 15996768k/16404684k available (2380k kernel code, 398812k >> reserved, 1814k data, 164k init) >> Calibrating delay using timer specific routine.. 3991.67 BogoMIPS >> (lpj=7983353) >> Security Framework v1.0.0 initialized >> Capability LSM initialized >> Mount-cache hash table entries: 256 >> CPU: L1 I cache: 32K, L1 D cache: 32K >> CPU: L2 cache: 6144K >> CPU: Physical Processor ID: 0 >> CPU: Processor Core ID: 0 >> SMP alternatives: switching to UP code >> ACPI: Core revision 20060707 >> SMP alternatives: switching to SMP code >> Initializing CPU#1 >> Initializing CPU#2 >> CPU: L1 I cache: 32K, L1 D cache: 32K >> CPU: L2 cache: 6144K >> CPU: Physical Processor ID: 0 >> CPU: Processor Core ID: 2 >> Initializing CPU#3 >> CPU: L1 I cache: 32K, L1 D cache: 32K >> CPU: L2 cache: 6144K >> CPU: Physical Processor ID: 1 >> CPU: Processor Core ID: 2 >> Initializing CPU#4 >> CPU: L1 I cache: 32K, L1 D cache: 32K >> CPU: L2 cache: 6144K >> CPU: Physical Processor ID: 0 >> CPU: Processor Core ID: 1 >> Initializing CPU#5 >> CPU: L1 I cache: 32K, L1 D cache: 32K >> CPU: L2 cache: 6144K >> CPU: Physical Processor ID: 1 >> CPU: Processor Core ID: 1 >> Initializing CPU#6 >> CPU: L1 I cache: 32K, L1 D cache: 32K >> CPU: L2 cache: 6144K >> CPU: Physical Processor ID: 0 >> CPU: Processor Core ID: 3 >> Brought up 8 CPUs >> Initializing CPU#7 >> CPU: L1 I cache: 32K, L1 D cache: 32K >> CPU: L2 cache: 6144K >> CPU: Physical Processor ID: 1 >> CPU: Processor Core ID: 3 >> CPU: L1 I cache: 32K, L1 D cache: 32K >> CPU: L2 cache: 6144K >> CPU: Physical Processor ID: 1 >> CPU: Processor Core ID: 0 >> migration_cost=12768 >> checking if image is initramfs... it is >> Freeing initrd memory: 12645k freed >> NET: Registered protocol family 16 >> ACPI: bus type pci registered >> PCI: Using MMCONFIG at e0000000 >> ACPI: Interpreter enabled >> ACPI: Using IOAPIC for interrupt routing >> ACPI: PCI Root Bridge [PCI0] (0000:00) >> PCI: Probing PCI hardware (bus 00) >> PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 >> Boot video device is 0000:0e:0d.0 >> PCI: Transparent bridge - 0000:00:1e.0 >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT] >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2.UPST._PRT] >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2.UPST.DWN1._PRT] >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2.UPST.DWN2._PRT] >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3._PRT] >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3.PE2P._PRT] >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT] >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX6._PRT] >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.SBEX._PRT] >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.COMP._PRT] >> ACPI: PCI Interrupt Link [LK00] (IRQs 3 4 *5 6 7 10 11 12) >> ACPI: PCI Interrupt Link [LK01] (IRQs 3 4 5 6 7 10 11 12) *0, disabled. >> ACPI: PCI Interrupt Link [LK02] (IRQs 3 4 5 6 7 10 11 12) *0, disabled. >> ACPI: PCI Interrupt Link [LK03] (IRQs 3 4 5 6 7 10 *11 12) >> ACPI: PCI Interrupt Link [LK04] (IRQs 3 4 5 6 7 *10 11 12) >> ACPI: PCI Interrupt Link [LK05] (IRQs 3 4 5 6 7 10 *11 12) >> ACPI: PCI Interrupt Link [LK06] (IRQs 3 4 5 6 7 10 11 12) *0, disabled. >> ACPI: PCI Interrupt Link [LK07] (IRQs 3 4 5 6 7 10 11 12) *0, disabled. >> Linux Plug and Play Support v0.97 (c) Adam Belay >> pnp: PnP ACPI init >> pnp: PnP ACPI: found 12 devices >> xen_mem: Initialising balloon driver. >> SCSI subsystem initialized >> usbcore: registered new driver usbfs >> usbcore: registered new driver hub >> PCI: Using ACPI for IRQ routing >> PCI: If a device doesn''t work, try "pci=routeirq". If it helps, post >> a report >> pnp: 00:08: ioport range 0x800-0x87f could not be reserved >> pnp: 00:08: ioport range 0x880-0x8bf has been reserved >> pnp: 00:08: ioport range 0x8c0-0x8df has been reserved >> pnp: 00:08: ioport range 0x8e0-0x8e3 has been reserved >> pnp: 00:08: ioport range 0x900-0x900 has been reserved >> pnp: 00:08: ioport range 0xc00-0xc7f has been reserved >> pnp: 00:08: ioport range 0xca0-0xca7 has been reserved >> pnp: 00:08: ioport range 0xca9-0xcab has been reserved >> pnp: 00:09: ioport range 0xca8-0xca8 has been reserved >> pnp: 00:09: ioport range 0xcac-0xcac has been reserved >> PCI: Bridge: 0000:06:00.0 >> IO window: disabled. >> MEM window: f4000000-f7ffffff >> PREFETCH window: disabled. >> PCI: Bridge: 0000:05:00.0 >> IO window: disabled. >> MEM window: f4000000-f7ffffff >> PREFETCH window: disabled. >> PCI: Bridge: 0000:05:01.0 >> IO window: disabled. >> MEM window: disabled. >> PREFETCH window: disabled. >> PCI: Bridge: 0000:04:00.0 >> IO window: disabled. >> MEM window: f4000000-f7ffffff >> PREFETCH window: disabled. >> PCI: Bridge: 0000:04:00.3 >> IO window: disabled. >> MEM window: disabled. >> PREFETCH window: disabled. >> PCI: Bridge: 0000:00:02.0 >> IO window: disabled. >> MEM window: f2000000-f7ffffff >> PREFETCH window: disabled. >> PCI: Bridge: 0000:00:03.0 >> IO window: e000-efff >> MEM window: fc300000-fc4fffff >> PREFETCH window: disabled. >> PCI: Bridge: 0000:00:04.0 >> IO window: disabled. >> MEM window: disabled. >> PREFETCH window: disabled. >> PCI: Bridge: 0000:00:05.0 >> IO window: disabled. >> MEM window: disabled. >> PREFETCH window: disabled. >> PCI: Bridge: 0000:00:06.0 >> IO window: disabled. >> MEM window: disabled. >> PREFETCH window: disabled. >> PCI: Bridge: 0000:00:07.0 >> IO window: disabled. >> MEM window: disabled. >> PREFETCH window: disabled. >> PCI: Bridge: 0000:02:00.0 >> IO window: disabled. >> MEM window: f8000000-fbffffff >> PREFETCH window: disabled. >> PCI: Bridge: 0000:00:1c.0 >> IO window: disabled. >> MEM window: f8000000-fbffffff >> PREFETCH window: disabled. >> PCI: Bridge: 0000:00:1e.0 >> IO window: d000-dfff >> MEM window: fc100000-fc2fffff >> PREFETCH window: d8000000-dfffffff >> GSI 16 sharing vector 0xA0 and IRQ 16 >> ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16 >> PCI: Setting latency timer of device 0000:00:02.0 to 64 >> ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 16 (level, low) -> IRQ 16 >> PCI: Setting latency timer of device 0000:04:00.0 to 64 >> ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 16 (level, low) -> IRQ 16 >> PCI: Setting latency timer of device 0000:05:00.0 to 64 >> PCI: Setting latency timer of device 0000:06:00.0 to 64 >> ACPI: PCI Interrupt 0000:05:01.0[A] -> GSI 16 (level, low) -> IRQ 16 >> PCI: Setting latency timer of device 0000:05:01.0 to 64 >> PCI: Setting latency timer of device 0000:04:00.3 to 64 >> ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 16 (level, low) -> IRQ 16 >> PCI: Setting latency timer of device 0000:00:03.0 to 64 >> ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level, low) -> IRQ 16 >> PCI: Setting latency timer of device 0000:00:04.0 to 64 >> PCI: Setting latency timer of device 0000:00:05.0 to 64 >> ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 16 (level, low) -> IRQ 16 >> PCI: Setting latency timer of device 0000:00:06.0 to 64 >> PCI: Setting latency timer of device 0000:00:07.0 to 64 >> ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16 >> PCI: Setting latency timer of device 0000:00:1c.0 to 64 >> PCI: Setting latency timer of device 0000:02:00.0 to 64 >> PCI: Setting latency timer of device 0000:00:1e.0 to 64 >> NET: Registered protocol family 2 >> IP route cache hash table entries: 524288 (order: 10, 4194304 bytes) >> TCP established hash table entries: 262144 (order: 10, 4194304 bytes) >> TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) >> TCP: Hash tables configured (established 262144 bind 65536) >> TCP reno registered >> VFS: Disk quotas dquot_6.5.1 >> Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >> Initializing Cryptographic API >> io scheduler noop registered >> io scheduler anticipatory registered >> io scheduler deadline registered >> io scheduler cfq registered (default) >> PCI: Setting latency timer of device 0000:00:02.0 to 64 >> assign_interrupt_mode Found MSI capability >> Allocate Port Service[0000:00:02.0:pcie00] >> Allocate Port Service[0000:00:02.0:pcie01] >> PCI: Setting latency timer of device 0000:00:03.0 to 64 >> assign_interrupt_mode Found MSI capability >> Allocate Port Service[0000:00:03.0:pcie00] >> Allocate Port Service[0000:00:03.0:pcie01] >> PCI: Setting latency timer of device 0000:00:04.0 to 64 >> assign_interrupt_mode Found MSI capability >> Allocate Port Service[0000:00:04.0:pcie00] >> Allocate Port Service[0000:00:04.0:pcie01] >> PCI: Setting latency timer of device 0000:00:05.0 to 64 >> pcie_portdrv_probe->Dev[25e5:8086] has invalid IRQ. Check vendor BIOS >> assign_interrupt_mode Found MSI capability >> Allocate Port Service[0000:00:05.0:pcie00] >> Allocate Port Service[0000:00:05.0:pcie01] >> PCI: Setting latency timer of device 0000:00:06.0 to 64 >> assign_interrupt_mode Found MSI capability >> Allocate Port Service[0000:00:06.0:pcie00] >> Allocate Port Service[0000:00:06.0:pcie01] >> PCI: Setting latency timer of device 0000:00:07.0 to 64 >> pcie_portdrv_probe->Dev[25e7:8086] has invalid IRQ. Check vendor BIOS >> assign_interrupt_mode Found MSI capability >> Allocate Port Service[0000:00:07.0:pcie00] >> Allocate Port Service[0000:00:07.0:pcie01] >> PCI: Setting latency timer of device 0000:00:1c.0 to 64 >> assign_interrupt_mode Found MSI capability >> Allocate Port Service[0000:00:1c.0:pcie00] >> Allocate Port Service[0000:00:1c.0:pcie03] >> PCI: Setting latency timer of device 0000:04:00.0 to 64 >> Allocate Port Service[0000:04:00.0:pcie10] >> Allocate Port Service[0000:04:00.0:pcie11] >> PCI: Setting latency timer of device 0000:05:00.0 to 64 >> assign_interrupt_mode Found MSI capability >> Allocate Port Service[0000:05:00.0:pcie20] >> Allocate Port Service[0000:05:00.0:pcie21] >> PCI: Setting latency timer of device 0000:05:01.0 to 64 >> assign_interrupt_mode Found MSI capability >> Allocate Port Service[0000:05:01.0:pcie20] >> Allocate Port Service[0000:05:01.0:pcie21] >> ACPI: Power Button (FF) [PWRF] >> ACPI: CPU0 (power states: C1[C1] C3[C3]) >> ACPI: CPU4 (power states: C1[C1] C3[C3]) >> ACPI: CPU2 (power states: C1[C1] C3[C3]) >> ACPI: CPU6 (power states: C1[C1] C3[C3]) >> ACPI: CPU1 (power states: C1[C1] C3[C3]) >> ACPI: CPU5 (power states: C1[C1] C3[C3]) >> ACPI: CPU3 (power states: C1[C1] C3[C3]) >> ACPI: CPU7 (power states: C1[C1] C3[C3]) >> Real Time Clock Driver v1.12ac >> hpet_acpi_add: no address or irqs in _CRS >> floppy0: Unable to grab DMA2 for the floppy driver >> floppy0: no floppy controllers found >> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize >> forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.56. >> PPP generic driver version 2.4.2 >> Xen virtual console successfully installed as xvc0 >> Event-channel device installed. >> Successfully initialized TPM backend driver. >> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 >> ide: Assuming 33MHz system bus speed for PIO modes; override with >> idebus=xx >> ESB2: IDE controller at PCI slot 0000:00:1f.1 >> ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 16 (level, low) -> IRQ 16 >> ESB2: chipset revision 9 >> ESB2: not 100% native mode: will probe irqs later >> ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio >> Probing IDE interface ide0... >> hda: TEAC DVD-ROM DV28EV, ATAPI CD/DVD-ROM drive >> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 >> Probing IDE interface ide1... >> hda: ATAPI 24X DVD-ROM drive, 198kB Cache, UDMA(33) >> Uniform CD-ROM driver Revision: 3.20 >> GSI 17 sharing vector 0xA8 and IRQ 17 >> ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 21 (level, low) -> IRQ 17 >> PCI: Setting latency timer of device 0000:00:1d.7 to 64 >> ehci_hcd 0000:00:1d.7: EHCI Host Controller >> ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1 >> ehci_hcd 0000:00:1d.7: debug port 1 >> PCI: cache line size of 32 is not supported by device 0000:00:1d.7 >> ehci_hcd 0000:00:1d.7: irq 17, io mem 0xfc500400 >> ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 >> usb usb1: configuration #1 chosen from 1 choice >> hub 1-0:1.0: USB hub found >> hub 1-0:1.0: 8 ports detected >> ohci_hcd: 2005 April 22 USB 1.1 ''Open'' Host Controller (OHCI) Driver >> (PCI) >> USB Universal Host Controller Interface driver v3.0 >> ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 21 (level, low) -> IRQ 17 >> PCI: Setting latency timer of device 0000:00:1d.0 to 64 >> uhci_hcd 0000:00:1d.0: UHCI Host Controller >> uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2 >> uhci_hcd 0000:00:1d.0: irq 17, io base 0x0000cce0 >> usb usb2: configuration #1 chosen from 1 choice >> hub 2-0:1.0: USB hub found >> hub 2-0:1.0: 2 ports detected >> GSI 18 sharing vector 0xB0 and IRQ 18 >> ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 20 (level, low) -> IRQ 18 >> PCI: Setting latency timer of device 0000:00:1d.1 to 64 >> uhci_hcd 0000:00:1d.1: UHCI Host Controller >> uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3 >> uhci_hcd 0000:00:1d.1: irq 18, io base 0x0000ccc0 >> usb usb3: configuration #1 chosen from 1 choice >> hub 3-0:1.0: USB hub found >> hub 3-0:1.0: 2 ports detected >> ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 21 (level, low) -> IRQ 17 >> PCI: Setting latency timer of device 0000:00:1d.2 to 64 >> uhci_hcd 0000:00:1d.2: UHCI Host Controller >> uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4 >> uhci_hcd 0000:00:1d.2: irq 17, io base 0x0000cca0 >> usb usb4: configuration #1 chosen from 1 choice >> hub 4-0:1.0: USB hub found >> hub 4-0:1.0: 2 ports detected >> usb 1-5: new high speed USB device using ehci_hcd and address 2 >> ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 20 (level, low) -> IRQ 18 >> PCI: Setting latency timer of device 0000:00:1d.3 to 64 >> uhci_hcd 0000:00:1d.3: UHCI Host Controller >> uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5 >> uhci_hcd 0000:00:1d.3: irq 18, io base 0x0000cc80 >> usb usb5: configuration #1 chosen from 1 choice >> hub 5-0:1.0: USB hub found >> hub 5-0:1.0: 2 ports detected >> usb 1-5: configuration #1 chosen from 1 choice >> hub 1-5:1.0: USB hub found >> hub 1-5:1.0: 4 ports detected >> usbcore: registered new driver usblp >> drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver >> Initializing USB Mass Storage driver... >> usbcore: registered new driver usb-storage >> USB Mass Storage support registered. >> usbcore: registered new driver usbhid >> drivers/usb/input/hid-core.c: v2.6:USB HID core driver >> PNP: No PS/2 controller found. Probing ports directly. >> serio: i8042 AUX port at 0x60,0x64 irq 12 >> serio: i8042 KBD port at 0x60,0x64 irq 1 >> mice: PS/2 mouse device common for all mice >> xenoprofile_init: ret -19, events -12, xenoprof_is_primary 0 >> oprofile: using timer interrupt. >> TCP bic registered >> NET: Registered protocol family 1 >> NET: Registered protocol family 17 >> ACPI: (supports S0 S4 S5) >> Freeing unused kernel memory: 164k freed >> megasas: 00.00.03.01 Sun May 14 22:49:52 PDT 2006 >> megasas: 0x1000:0x0060:0x1028:0x1f0c: bus 1:slot 0:func 0 >> ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 >> PCI: Setting latency timer of device 0000:01:00.0 to 64 >> scsi0 : LSI Logic SAS based MegaRAID driver >> Vendor: SEAGATE Model: ST3500620SS Rev: MS04 >> Type: Direct-Access ANSI SCSI revision: 05 >> Vendor: SEAGATE Model: ST3500620SS Rev: MS04 >> Type: Direct-Access ANSI SCSI revision: 05 >> Vendor: SEAGATE Model: ST3500620SS Rev: MS04 >> Type: Direct-Access ANSI SCSI revision: 05 >> Vendor: SEAGATE Model: ST3500620SS Rev: MS04 >> Type: Direct-Access ANSI SCSI revision: 05 >> Vendor: SEAGATE Model: ST3500620SS Rev: MS04 >> Type: Direct-Access ANSI SCSI revision: 05 >> Vendor: SEAGATE Model: ST3500620SS Rev: MS04 >> Type: Direct-Access ANSI SCSI revision: 05 >> Vendor: DP Model: BACKPLANE Rev: 1.05 >> Type: Enclosure ANSI SCSI revision: 05 >> Vendor: DELL Model: PERC 6/i Rev: 1.11 >> Type: Direct-Access ANSI SCSI revision: 05 >> Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.4.44 (August >> 10, 2006) >> ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 16 (level, low) -> IRQ 16 >> eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit >> 133MHz found at mem f4000000, IRQ 16, node addr 00221987c97d >> ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16 >> eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit >> 133MHz found at mem f8000000, IRQ 16, node addr 00221987c97b >> SCSI device sda: 2927099904 512-byte hdwr sectors (1498675 MB) >> sda: Write Protect is off >> sda: Mode Sense: 1f 00 00 08 >> SCSI device sda: drive cache: write back >> SCSI device sda: 2927099904 512-byte hdwr sectors (1498675 MB) >> sda: Write Protect is off >> sda: Mode Sense: 1f 00 00 08 >> SCSI device sda: drive cache: write back >> sda: sda1 sda2 >> sd 0:2:0:0: Attached scsi disk sda >> device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: >> dm-devel@redhat.com >> Attempting manual resume >> kjournald starting. Commit interval 5 seconds >> EXT3-fs: mounted filesystem with ordered data mode. >> pci_hotplug: PCI Hot Plug PCI Core version: 0.5 >> shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 >> intel_rng: FWH not detected >> EXT3 FS on dm-1, internal journal >> loop: loaded (max 8 devices) >> kjournald starting. Commit interval 5 seconds >> EXT3 FS on sda1, internal journal >> EXT3-fs: mounted filesystem with ordered data mode. >> Adding 1048568k swap on /dev/mapper/domU-swap. Priority:-1 extents:1 >> across:1048568k > > > On Feb 13, 2009, at 1:15 AM, Daniel Kao wrote: > >> Philipp Schmid wrote: >>> Hi, >>> >>> we are using dell poweredge 2950 servers with a "PERC 6/i >>> Integrated" hardware raid controller. >>> >>> Lg Philipp >> How are the read-ahead and write-cache settings set on the PERC6/i >> and which/whose RAID drivers are you using under dom0 (output from >> dmesg, etc.) >> >> Cheers, >> Daniel > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Steven Timm
2009-Feb-13 01:16 UTC
Re: [Xen-users] Xen 3.3.1 Windows HVM Disk I/O -> domU and dom0 hangs
I have the same hardware and raid controller but right now just running xen 3.1.2. Make sure there are no Dell raid management stuff running in any of the domU''s, that is one thing that could certainly cause a hang of that magnitude, also make sure there is no heavy I/O in dom0 itself. Steve timm On Fri, 13 Feb 2009, Philipp Schmid wrote:> Hi, > > we are using dell poweredge 2950 servers with a "PERC 6/i Integrated" > hardware raid controller. > > Lg Philipp > > On Feb 13, 2009, at 1:01 AM, James Harper wrote: > >>> we use LVM for HVM domUs on a 6 disk raid 10 array. >>> >> >> What hardware and what RAID controller? >> >> I had awful problems with a low end (E200 I think) HP RAID adapter. >> >> James >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov http://home.fnal.gov/~timm/ Fermilab Computing Division, Scientific Computing Facilities, Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users