WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [vt-d][xen4-rc6] Hangs on startup

To: Łukasz Oleś <lukaszoles@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [vt-d][xen4-rc6] Hangs on startup
From: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Date: Wed, 17 Mar 2010 16:02:27 +0800
Accept-language: zh-CN, en-US
Acceptlanguage: zh-CN, en-US
Cc:
Delivery-date: Wed, 17 Mar 2010 01:03:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <cb0d70421003161641x3f413623x11c82083e1c30ce9@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <cb0d70421003161641x3f413623x11c82083e1c30ce9@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcrFYn3lF0se2+Y2Qn2x03VRBm9l3QARRZaQ
Thread-topic: [Xen-devel] [vt-d][xen4-rc6] Hangs on startup
This issue was reported last year in this mailing list: 
http://lists.xensource.com/archives/html/xen-devel/2009-05/msg00917.html
It turned out to be a BIOS issue.
Please update to the latest BIOS to see if the issue is still there or not. The 
link above also supplies a workaround patch.

Thanks,
-- Dexuan
 

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of ?ukasz Ole?
Sent: 2010年3月17日 7:42
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [vt-d][xen4-rc6] Hangs on startup

Hi,

I'm trying to run xen4-rc6 with iommu=1 option, but it hangs during the startup.

When I run it with option iommu=0, it starts ok, and I'm able to run
HVM guests(didn't try PV yet).
I have Intel Q45 chipset on the motherboard so it should have vt-d
support. As dom0 I tried jeremy's 2.6.31 and 2.6.32 kernels.
The same thing happens on two identical machines. All vt and vt-d
options are enabled in BIOS.

Here is Serial Consol log:


(XEN) Xen version 4.0.0-rc6 (root@(none)) (gcc version 4.4.3 (Debian
4.4.3-2) ) Sun Mar 14 15:51:45 UTC 2010
(XEN) Latest ChangeSet: Thu Mar 11 17:40:35 2010 +0000
21028:4152a3ce90a7
(XEN) Console output is synchronous.
(XEN) Command line: iommu=1 dom0_mem=1024288 loglvl=all
guest_loglvl=all sync_console console_to_ring com1=115200,8n1,0xe1c0,0
console=com1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method
detected
(XEN) Disc information:
(XEN)  Found 3 MBR signatures
(XEN)  Found 3 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd3e2000 (usable)
(XEN)  00000000bd3e2000 - 00000000bd424000 (ACPI NVS)
(XEN)  00000000bd424000 - 00000000bd542000 (reserved)
(XEN)  00000000bd542000 - 00000000bd545000 (ACPI NVS)
(XEN)  00000000bd545000 - 00000000bd645000 (reserved)
(XEN)  00000000bd645000 - 00000000bd646000 (ACPI NVS)
(XEN)  00000000bd646000 - 00000000bd64b000 (reserved)
(XEN)  00000000bd64b000 - 00000000bd653000 (ACPI data)
(XEN)  00000000bd653000 - 00000000bd66e000 (ACPI NVS)
(XEN)  00000000bd66e000 - 00000000bd68c000 (reserved)
(XEN)  00000000bd68c000 - 00000000bd692000 (ACPI NVS)
(XEN)  00000000bd692000 - 00000000bd800000 (usable)
(XEN)  00000000bd800000 - 00000000bdb00000 (reserved)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000013c000000 (usable)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD651E18, 005C (r1 INTEL  DQ45CB         3B MSFT
10013)
(XEN) ACPI: FACP BD650D98, 00F4 (r4  INTEL    A M I  6222004 MSFT
10013)
(XEN) ACPI: DSDT BD64B018, 4E98 (r1 INTEL  DQ45CB         3B INTL
20051117)
(XEN) ACPI: FACS BD659F40, 0040
(XEN) ACPI: APIC BD650F18, 006C (r2 INTEL  DQ45CB         3B MSFT
10013)
(XEN) ACPI: MCFG BD65BE18, 003C (r1 INTEL  DQ45CB         3B MSFT
 97)
(XEN) ACPI: ASF! BD65AD18, 00A0 (r32 INTEL  DQ45CB         3B TFSM
F4240)
(XEN) ACPI: SPCR BD65BD18, 0050 (r1 INTEL  DQ45CB         3B AMI.
  3)
(XEN) ACPI: TCPA BD65BC98, 0032 (r2 INTEL  DQ45CB         3B MSFT
1000013)
(XEN) ACPI: DMAR BD645C18, 0120 (r1 INTEL  DQ45CB         3B INTL
  1)
(XEN) System RAM: 3949MB (4044048kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-000000013c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI: 32/64X FACS address mismatch in FADT -
bd654f40/00000000bd659f40, using 32
(XEN) ACPI:                  wakeup_vec[bd654f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] disabled)
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, 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) [VT-D]dmar.c:643: Host address width 36
(XEN) [VT-D]dmar.c:652: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:379:   dmaru->address = fed90000
(XEN) [VT-D]dmar.c:331:   endpoint: 0:1b.0
(XEN) [VT-D]dmar.c:652: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:379:   dmaru->address = fed91000
(XEN) [VT-D]dmar.c:331:   endpoint: 0:2.0
(XEN) [VT-D]dmar.c:331:   endpoint: 0:2.1
(XEN) [VT-D]dmar.c:652: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:379:   dmaru->address = fed92000
(XEN) [VT-D]dmar.c:331:   endpoint: 0:3.0
(XEN) [VT-D]dmar.c:331:   endpoint: 0:3.2
(XEN) [VT-D]dmar.c:331:   endpoint: 0:3.3
(XEN) [VT-D]dmar.c:652: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:379:   dmaru->address = fed93000
(XEN) [VT-D]dmar.c:391:   flags: INCLUDE_ALL
(XEN) [VT-D]dmar.c:656: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:331:   endpoint: 0:1d.0
(XEN) [VT-D]dmar.c:331:   endpoint: 0:1d.1
(XEN) [VT-D]dmar.c:331:   endpoint: 0:1d.2
(XEN) [VT-D]dmar.c:331:   endpoint: 0:1d.7
(XEN) [VT-D]dmar.c:331:   endpoint: 0:1a.0
(XEN) [VT-D]dmar.c:331:   endpoint: 0:1a.1
(XEN) [VT-D]dmar.c:331:   endpoint: 0:1a.2
(XEN) [VT-D]dmar.c:331:   endpoint: 0:1a.7
(XEN) [VT-D]dmar.c:546:   RMRR region: base_addr bd62f000 end_address
bd642fff
(XEN) [VT-D]dmar.c:656: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:481:   RMRR address range not in reserved memory
base = bdc00000 end = ffffffffbfffffff; iommu_inclusive_mapping=1
parameter may be needed.
(XEN) [VT-D]dmar.c:331:   endpoint: 0:2.0
(XEN) [VT-D]dmar.c:331:   endpoint: 0:2.1
(XEN) [VT-D]dmar.c:546:   RMRR region: base_addr bdc00000 end_address
ffffffffbfffffff
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
(XEN) PCI: Not using MMCONFIG.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2800.206 MHz processor.
(XEN) Initing memory sharing.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 2048K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: ASIDs disabled.
(XEN) HVM: VMX enabled
(XEN) xsave_init: cpu0: cntxt_max_size: 0x240 and states:
00000000:00000003
(XEN) xsave_init: using cntxt_size: 0x240 and states:
00000000:00000003
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) [VT-D]iommu.c:1075: drhd->address = fed92000 iommu->reg =
ffff82c3fff57000
(XEN) [VT-D]iommu.c:1077: cap = c0000020630272 ecap = 1000
(XEN) [VT-D]iommu.c:1075: drhd->address = fed91000 iommu->reg =
ffff82c3fff56000
(XEN) [VT-D]iommu.c:1077: cap = c0000020630272 ecap = 1000
(XEN) [VT-D]iommu.c:1075: drhd->address = fed90000 iommu->reg =
ffff82c3fff55000
(XEN) [VT-D]iommu.c:1077: cap = c9008020e30272 ecap = 1000
(XEN) [VT-D]iommu.c:1075: drhd->address = fed93000 iommu->reg =
ffff82c3fff54000
(XEN) [VT-D]iommu.c:1077: cap = c9008020630272 ecap = 1000
(XEN) Intel VT-d Snoop Control not supported.
(XEN) Intel VT-d DMA Passthrough not supported.
(XEN) Intel VT-d Queued Invalidation not supported.
(XEN) Intel VT-d Interrupt Remapping not supported.
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) CPU0: Intel Pentium(R) Dual-Core  CPU      E6300  @ 2.80GHz
stepping 0a
(XEN) Booting processor 1/1 eip 88000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 2048K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) HVM: ASIDs disabled.
(XEN) xsave_init: cpu1: cntxt_max_size: 0x240 and states:
00000000:00000003
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel Pentium(R) Dual-Core  CPU      E6300  @ 2.80GHz
stepping 0a
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) Brought up 2 CPUs
(XEN) microcode.c:73:d32767 microcode: CPU1 resumed
(XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'.
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:0.0
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:0.0:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:2.0
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:2.0:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:2.1
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:2.1:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:3.0
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:3.0:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:3.2
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:3.2:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:3.3
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:3.3:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:19.0
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:19.0:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:1a.0
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1a.0:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:1a.1
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1a.1:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:1a.2
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1a.2:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:1a.7
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1a.7:  no extended config
(XEN) [VT-D]iommu.c:1321:d32767 domain_context_mapping:PCIe: bdf = 0:1b.0
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1b.0:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:1d.0
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1d.0:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:1d.1
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1d.1:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:1d.2
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1d.2:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:1d.7
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1d.7:  no extended config
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1e.0:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:1f.0
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1f.0:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:1f.2
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1f.2:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:1f.3
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1f.3:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 0:1f.5
(XEN) [VT-D]mmconfig-shared.c:460: next cap:0:1f.5:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 1:0.0
(XEN) [VT-D]mmconfig-shared.c:460: next cap:1:0.0:  no extended config
(XEN) [VT-D]iommu.c:1328:d32767 domain_context_mapping:PCI: bdf = 1:1.0
(XEN) [VT-D]mmconfig-shared.c:460: next cap:1:1.0:  no extended config


Regards
Łukasz Oleś

_______________________________________________
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