[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-bugs] [Bug 1417] [VT-d] Xen hypervisor will crash at booting if vt-d is enabled
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1417 ------- Comment #1 from haicheng.li@xxxxxxxxx 2009-02-15 23:49 ------- XEN) Intel machine check reporting enabled on CPU#4. (XEN) mce_init: init bank2 (XEN) mce_init: init bank3 (XEN) mce_init: init bank4 (XEN) mce_init: init bank5 (XEN) CPU4: Thermal monitoring enabled (TM2) (XEN) CMCI: CPU4 has no CMCI support (XEN) CPU4: Intel(R) Xeon(R) CPU X5376 @ 2.80GHz stepping 0b (XEN) Booting processor 5/6 eip 8c000 (XEN) Initializing CPU#5 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 4096K (XEN) CPU: Physical Processor ID: 1 (XEN) CPU: Processor Core ID: 2 (XEN) MCE: Intel newly family MC Init (XEN) Intel machine check reporting enabled on CPU#5. (XEN) mce_init: init bank2 (XEN) mce_init: init bank3 (XEN) mce_init: init bank4 (XEN) mce_init: init bank5 (XEN) CPU5: Thermal monitoring enabled (TM2) (XEN) CMCI: CPU5 has no CMCI support (XEN) CPU5: Intel(R) Xeon(R) CPU X5376 @ 2.80GHz stepping 0b (XEN) Booting processor 6/3 eip 8c000 (XEN) Initializing CPU#6 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 4096K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 3 (XEN) MCE: Intel newly family MC Init (XEN) Intel machine check reporting enabled on CPU#6. (XEN) mce_init: init bank2 (XEN) mce_init: init bank4 (XEN) mce_init: init bank5 (XEN) CPU6: Thermal monitoring enabled (TM2) (XEN) CMCI: CPU6 has no CMCI support (XEN) CPU6: Intel(R) Xeon(R) CPU X5376 @ 2.80GHz stepping 0b (XEN) Booting processor 7/7 eip 8c000 (XEN) Initializing CPU#7 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 4096K (XEN) CPU: Physical Processor ID: 1 (XEN) CPU: Processor Core ID: 3 (XEN) MCE: Intel newly family MC Init (XEN) Intel machine check reporting enabled on CPU#7. (XEN) mce_init: init bank2 (XEN) mce_init: init bank4 (XEN) mce_init: init bank5 (XEN) CPU7: Thermal monitoring enabled (TM2) (XEN) CMCI: CPU7 has no CMCI support (XEN) CPU7: Intel(R) Xeon(R) CPU X5376 @ 2.80GHz stepping 0b (XEN) Total of 8 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 8 CPUs: passed. (XEN) Platform timer is 3.579MHz ACPI PM Timer (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) microcode.c:73:d32767 microcode: CPU6 resumed (XEN) microcode.c:73:d32767 microcode: CPU3 resumed (XEN) microcode.c:73:d32767 microcode: CPU4 resumed (XEN) microcode.c:73:d32767 microcode: CPU2 resumed (XEN) Brought up 8 CPUs (XEN) microcode.c:73:d32767 microcode: CPU5 resumed (XEN) [VT-D]iommu.c:1707: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1707: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1707: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1707: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1707: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1715: Interrupt Remapping hardware not found (XEN) microcode.c:73:d32767 microcode: CPU7 resumed (XEN) [VT-D]iommu.c:1715: Interrupt Remapping hardware not found (XEN) [VT-D]iommu.c:1715: Interrupt Remapping hardware not found (XEN) [VT-D]iommu.c:1715: Interrupt Remapping hardware not found (XEN) [VT-D]iommu.c:1715: Interrupt Remapping hardware not found (XEN) Intel VT-d snoop control disabled (XEN) I/O virtualisation enabled (XEN) I/O virtualisation for PV guests disabled (XEN) HPET broadcast init failed, turn to PIT broadcast. (XEN) ACPI sleep modes: S3 (XEN) mcheck_poll: Init_mcheck_timer (XEN) mcheck_poll: Machine check polling timer started. (XEN) [VT-D]iommu.c:1246:d32767 domain_context_mapping:PCIe: bdf = 0:0.0 (XEN) [VT-D]iommu.c:1246:d32767 domain_context_mapping:PCIe: bdf = 0:f.0 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:10.0 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:10.1 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:10.2 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:10.3 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:10.4 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:11.0 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:15.0 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:15.1 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:16.0 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:16.1 (XEN) [VT-D]iommu.c:1246:d32767 domain_context_mapping:PCIe: bdf = 0:1b.0 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1d.0 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1d.1 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1d.2 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1d.3 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1d.7 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1f.0 (XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = -- Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ Xen-bugs mailing list Xen-bugs@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-bugs
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |