Xen project Mailing List

Re: [Xen-devel] fail to detect VT-D on Dell (optiplex 760)

To: "Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx>

From: "Dennis Lan (dlan)" <dennis.yxun@xxxxxxxxx>

Date: Thu, 1 Aug 2013 16:16:50 +0800

Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, IAN DELANEY <della5@xxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>

Delivery-date: Thu, 01 Aug 2013 08:17:16 +0000

List-id: Xen developer discussion <xen-devel.lists.xen.org>

On Thu, Aug 1, 2013 at 2:34 PM, Zhang, Yang Z <yang.z.zhang@xxxxxxxxx> wrote: > Dennis Lan (dlan) wrote on 2013-08-01: >> HI Zhang, Andrew: >> Here is my report. >> I upgrade the BIOS from version A00 to A15, and the configuration >> of "VT-D" is gone (also there is no kind of virtualization setting). >> I'm not sure whether this feature is removed or enabled by default. >> and I haven't seen the error messages from the Xen log [1] >> (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000 >> ...(lines between this two are gone) >> (XEN) ERST table was not found >> > (XEN) I/O virtualisation disabled > This means the VT-d is disabled by BIOS. Did you ever successfully to boot > Xen in this machine? > > >> Dennis Lan (dlan) >> >> On Thu, Aug 1, 2013 at 11:08 AM, Zhang, Yang Z <yang.z.zhang@xxxxxxxxx> >> wrote: >>> Andrew Cooper wrote on 2013-07-31: >>>> On 31/07/13 12:13, Dennis Lan (dlan) wrote: >>>>> HI Devs: >>>>> I have problem to boot with VT-D enabled on my machine, with >>>>> Xen-4.3.0, it just hangs[0]. But with 4.4-unstable version, it >>>>> boot successfully but still fail to detect iommu. >>>>> >>>>> I'm using xen-git master branch,commit: >>>>> 6072b7c808043b6886c33f896e06fc32ee28346e >>>>> >>>>> also you can refer [1] for more information. >>>>> interesting bits from xen-4.4-unstable, full log is here[2] >>>>> >>>>> (XEN) vmap(ffff82c000201000:0x1) >>>>> (XEN) [VT-D]iommu.c:1167: IOMMU: unsupported >>>>> (XEN) ---- print_iommu_regs ---- >>>>> (XEN) drhd->address = fedc1000 >>>>> (XEN) VER = ffffffff >>>>> (XEN) CAP = ffffffffffffffff >>>>> (XEN) n_fault_reg = 100 >>>>> (XEN) fault_recording_offset = 3ff0 >>>>> (XEN) ECAP = ffffffffffffffff >>>>> (XEN) GCMD = ffffffff >>>>> (XEN) GSTS = ffffffff >>>>> (XEN) RTADDR = ffffffffffffffff >>>>> (XEN) CCMD = ffffffffffffffff >>>>> (XEN) FSTS = ffffffff >>>>> (XEN) FECTL = ffffffff >>>>> (XEN) FEDATA = ffffffff >>>>> (XEN) FEADDR = ffffffff >>>>> (XEN) FEUADDR = ffffffff >>>>> (XEN) vunmap(ffff82c000201000:0x1) >>>>> (XEN) Failed to parse ACPI DMAR. Disabling VT-d. >>>>> (XEN) ERST table was not found >>>>> (XEN) Using ACPI (MADT) for SMP configuration information >>>> >>>> According to this, the DMAR table is problematic. This is the ACPI >>>> table which describes the IOMMU functionality. Do you have a BIOS >> upgrade available? >>> Yes, the ACPI table is broken. It's better to dump the DMAR to have a >>> double chek. >>> >> >> Still, is this a software issue (the BIOS?) or the hardware issue (the >> mainboard) ? >> Is there any documents about how to dump DMAR register? >> thanks >> >> >>>>> >>>>> btw, Ian, I also keep you CCed. >>>>> >>>>> [0] https://bugs.gentoo.org/show_bug.cgi?id=479082#c3 >>>>> [1] https://bugs.gentoo.org/show_bug.cgi?id=479082 >>>>> [2] https://479082.bugs.gentoo.org/attachment.cgi?id=354706 >>>>> >>>>> Dennis Lan (dlan) >>>>> >>>>> _______________________________________________ >>>>> Xen-devel mailing list >>>>> Xen-devel@xxxxxxxxxxxxx >>>>> http://lists.xen.org/xen-devel >>>> >>>> >>>> _______________________________________________ >>>> Xen-devel mailing list >>>> Xen-devel@xxxxxxxxxxxxx >>>> http://lists.xen.org/xen-devel >>> >>> >>> Best regards, >>> Yang >>> >>> >> >> >> XEN full log >> >> _ >> \ \/ /___ _ __ | || | | || | _ _ _ __ ___| |_ __ _| |__ | | ___ >> \ // _ \ '_ \ | || |_| || |_ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \ >> / \ __/ | | | |__ _|__ _|__| |_| | | | \__ \ || (_| | |_) | | __/ >> /_/\_\___|_| |_| |_|(_) |_| \__,_|_| >> |_|___/\__\__,_|_.__/|_|\___| >> >> (XEN) Xen version 4.4-unstable (@) (gcc (Gentoo 4.8.1 p1.0, pie-0.5.6) >> 4.8.1) debug=y Wed Jul 31 18:44:00 CST 2013 (XEN) Latest ChangeSet: Tue >> Jul 30 00:18:28 2013 +0100 git:6072b7c-dirty (XEN) Bootloader: GRUB 2.00 >> (XEN) Command line: loglvl=all guest_loglvl=all com1=115200,8n1 >> console=com1 (XEN) Video information: (XEN) VGA is text mode 80x25, >> font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds >> (XEN) Disc information: (XEN) Found 4 MBR signatures (XEN) Found 4 EDD >> information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - >> 000000000009ec00 (usable) (XEN) 00000000000f0000 - 0000000000100000 >> (reserved) (XEN) 0000000000100000 - 00000000bdbffc00 (usable) (XEN) >> 00000000bdbffc00 - 00000000bdc53c00 (ACPI NVS) (XEN) 00000000bdc53c00 - >> 00000000bdc55c00 (ACPI data) (XEN) 00000000bdc55c00 - 00000000c0000000 >> (reserved) (XEN) 00000000f8000000 - 00000000fc000000 (reserved) (XEN) >> 00000000fec00000 - 00000000fed00400 (reserved) (XEN) 00000000fed20000 - >> 00000000feda0000 (reserved) (XEN) 00000000fee00000 - 00000000fef00000 >> (reserved) (XEN) 00000000ffb00000 - 0000000100000000 (reserved) (XEN) >> 0000000100000000 - 0000000238000000 (usable) (XEN) ACPI: RSDP 000FEC00, >> 0024 (r2 DELL ) (XEN) ACPI: XSDT 000FC924, 0094 (r1 DELL B10K >> 15 ASL 61) (XEN) ACPI: FACP 000FCA4C, 00F4 (r3 DELL B10K >> 15 ASL 61) (XEN) ACPI: DSDT FFF20BAB, 5655 (r1 DELL dt_ex 1000 >> INTL 20050624) (XEN) ACPI: FACS BDBFFC00, 0040 (XEN) ACPI: SSDT >> FFF2631F, 00AA (r1 DELL st_ex 1000 INTL 20050624) (XEN) ACPI: >> APIC 000FCB40, 0092 (r1 DELL B10K 15 ASL 61) (XEN) ACPI: >> BOOT 000FCBD2, 0028 (r1 DELL B10K 15 ASL 61) (XEN) ACPI: >> ASF! 000FCBFA, 0096 (r32 DELL B10K 15 ASL 61) (XEN) ACPI: >> MCFG 000FCC90, 003C (r1 DELL B10K 15 ASL 61) (XEN) ACPI: >> HPET 000FCCCC, 0038 (r1 DELL B10K 15 ASL 61) (XEN) ACPI: >> TCPA 000FCF28, 0032 (r1 DELL B10K 15 ASL 61) (XEN) ACPI: >> SLIC 000FCD04, 0176 (r1 DELL B10K 15 ASL 61) (XEN) ACPI: >> SSDT BDBFFC40, 0175 (r1 DpgPmm Cpu0Ist 11 INTL 20050624) (XEN) >> ACPI: SSDT BDC00049, 0175 (r1 DpgPmm Cpu1Ist 11 INTL 20050624) >> (XEN) ACPI: SSDT BDC00452, 0175 (r1 DpgPmm Cpu2Ist 11 INTL >> 20050624) (XEN) ACPI: SSDT BDC0085B, 0175 (r1 DpgPmm Cpu3Ist 11 >> INTL 20050624) (XEN) ACPI: SSDT BDC00C64, 0190 (r1 DpgPmm CpuPm >> 10 INTL 20050624) (XEN) System RAM: 8027MB (8220276kB) (XEN) No NUMA >> configuration found (XEN) Faking a node at >> 0000000000000000-0000000238000000 (XEN) Domain heap initialised (XEN) >> found SMP MP-table at 000fe710 (XEN) DMI 2.5 present. (XEN) Using APIC >> driver default (XEN) ACPI: PM-Timer IO Port: 0x808 (XEN) ACPI: SLEEP >> INFO: pm1x_cnt[804,0], pm1x_evt[800,0] (XEN) ACPI: >> wakeup_vec[bdbffc0c], 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] enabled) (XEN) Processor #2 >> 7:7 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] >> enabled) (XEN) Processor #3 7:7 APIC version 20 (XEN) ACPI: LAPIC >> (acpi_id[0x05] lapic_id[0x00] disabled) (XEN) ACPI: LAPIC (acpi_id[0x06] >> lapic_id[0x01] disabled) (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x02] >> disabled) (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x03] disabled) >> (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1]) (XEN) ACPI: >> IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: >> apic_id 8, 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) ACPI: HPET id: 0x8086a701 base: 0xfed00000 (XEN) ERST table was >> not found (XEN) Using ACPI (MADT) for SMP configuration information >> (XEN) SMP: Allowing 8 CPUs (4 hotplug CPUs) (XEN) IRQ limits: 24 GSI, >> 760 MSI/MSI-X (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) >> Detected 2327.242 MHz processor. (XEN) Initing memory sharing. (XEN) >> mce_intel.c:717: MCA Capability: BCAST 1 SER 0 CMCI 0 firstbank 1 >> extended MCE MSR 0 (XEN) Intel machine check reporting enabled (XEN) >> PCI: MCFG configuration 0: base f8000000 segment 0000 buses 00 - 3f >> (XEN) PCI: MCFG area at f8000000 reserved in E820 (XEN) PCI: Using MCFG >> for segment 0000 bus 00-3f (XEN) I/O virtualisation disabled (XEN) >> ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: >> vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) Platform timer is >> 14.318MHz HPET (XEN) Allocated console ring of 32 KiB. (XEN) mwait-idle: >> does not run on family 6 model 23 (XEN) Brought up 4 CPUs (XEN) HPET: 8 >> timers (8 will be used for broadcast) (XEN) ACPI sleep modes: S3 (XEN) >> mcheck_poll: Machine check polling timer started. (XEN) *** LOADING >> DOMAIN 0 *** (XEN) elf_parse_binary: phdr: paddr=0x1000000 >> memsz=0x947000 (XEN) elf_parse_binary: phdr: paddr=0x1947000 >> memsz=0xca0f0 (XEN) elf_parse_binary: phdr: paddr=0x1a12000 >> memsz=0x145c0 (XEN) elf_parse_binary: phdr: paddr=0x1a27000 >> memsz=0x659000 (XEN) elf_parse_binary: memory: 0x1000000 -> 0x2080000 >> (XEN) elf_xen_parse_note: GUEST_OS = "linux" (XEN) elf_xen_parse_note: >> GUEST_VERSION = "2.6" (XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0" >> (XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000 (XEN) >> elf_xen_parse_note: ENTRY = 0xffffffff81a271e0 (XEN) elf_xen_parse_note: >> HYPERCALL_PAGE = 0xffffffff81001000 (XEN) elf_xen_parse_note: FEATURES = >> "!writable_page_tables|pae_pgdir_above_4gb" (XEN) elf_xen_parse_note: >> PAE_MODE = "yes" (XEN) elf_xen_parse_note: LOADER = "generic" (XEN) >> elf_xen_parse_note: unknown xen elf note (0xd) (XEN) elf_xen_parse_note: >> SUSPEND_CANCEL = 0x1 (XEN) elf_xen_parse_note: HV_START_LOW = >> 0xffff800000000000 (XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0 (XEN) >> elf_xen_addr_calc_check: addresses: (XEN) virt_base = >> 0xffffffff80000000 (XEN) elf_paddr_offset = 0x0 (XEN) >> virt_offset = 0xffffffff80000000 (XEN) virt_kstart = >> 0xffffffff81000000 (XEN) virt_kend = 0xffffffff82080000 (XEN) >> virt_entry = 0xffffffff81a271e0 (XEN) p2m_base = >> 0xffffffffffffffff (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 >> kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2080000 (XEN) PHYSICAL >> MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: >> 000000022c000000->0000000230000000 (1981399 pages to be allocated) (XEN) >> Init. ramdisk: 0000000237cb0000->0000000237fffcbc (XEN) VIRTUAL MEMORY >> ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff82080000 >> (XEN) Init. ramdisk: ffffffff82080000->ffffffff823cfcbc (XEN) >> Phys-Mach map: ffffffff823d0000->ffffffff8330f938 (XEN) Start info: >> ffffffff83310000->ffffffff833104b4 (XEN) Page tables: >> ffffffff83311000->ffffffff8332e000 (XEN) Boot stack: >> ffffffff8332e000->ffffffff8332f000 (XEN) TOTAL: >> ffffffff80000000->ffffffff83400000 (XEN) ENTRY ADDRESS: >> ffffffff81a271e0 (XEN) Dom0 has maximum 4 VCPUs (XEN) elf_load_binary: >> phdr 0 at 0xffffffff81000000 -> 0xffffffff81947000 (XEN) >> elf_load_binary: phdr 1 at 0xffffffff81947000 -> 0xffffffff81a110f0 >> (XEN) elf_load_binary: phdr 2 at 0xffffffff81a12000 -> >> 0xffffffff81a265c0 (XEN) elf_load_binary: phdr 3 at 0xffffffff81a27000 >> -> 0xffffffff81b47000 (XEN) Scrubbing Free RAM: .done. (XEN) Initial low >> memory virq threshold set at 0x4000 pages. (XEN) Std. Loglevel: All >> (XEN) Guest Loglevel: All (XEN) *** Serial input -> DOM0 (type 'CTRL-a' >> three times to switch input to Xen) (XEN) Freed 252kB init memory. >> mapping kernel into physical memory about to get started... (XEN) >> vmap(ffff82c000201000:0x1) (XEN) vmap(ffff82c000203000:0x1) (XEN) >> vmap(ffff82c000205000:0x1) (XEN) vmap(ffff82c000207000:0x1) (XEN) >> vmap(ffff82c000209000:0x1) (XEN) PCI add device 0000:00:00.0 (XEN) PCI >> add device 0000:00:01.0 (XEN) PCI add device 0000:00:02.0 (XEN) PCI add >> device 0000:00:02.1 (XEN) PCI add device 0000:00:03.0 (XEN) PCI add >> device 0000:00:03.2 (XEN) PCI add device 0000:00:03.3 (XEN) PCI add >> device 0000:00:19.0 (XEN) PCI add device 0000:00:1a.0 (XEN) PCI add >> device 0000:00:1a.1 (XEN) PCI add device 0000:00:1a.2 (XEN) PCI add >> device 0000:00:1a.7 (XEN) PCI add device 0000:00:1b.0 (XEN) PCI add >> device 0000:00:1c.0 (XEN) PCI add device 0000:00:1c.1 (XEN) PCI add >> device 0000:00:1d.0 (XEN) PCI add device 0000:00:1d.1 (XEN) PCI add >> device 0000:00:1d.2 (XEN) PCI add device 0000:00:1d.7 (XEN) PCI add >> device 0000:00:1e.0 (XEN) PCI add device 0000:00:1f.0 (XEN) PCI add >> device 0000:00:1f.2 (XEN) PCI add device 0000:00:1f.3 > > > Best regards, > Yang > > Hi Yang: I could boot successfully (with xen), either with my current BIOS (version A15) or prevous one (A00) on condition of the latest xen code base (4.4-unstable). but I have problem with xen-4.3.0 when using old BIOS (version A00) with VT-D enabled. if I diable VT-D, the system can boot successfully. I'd consider this is hardware issue(BIOS, motherboard), rather than the software (Xen side). so, I would rather not to dig further Thanks. Dennis Lan (dlan) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.