thr3ads.net - Xen users - I/O virtualisation disabled

If this information is useful, please help other people find it:
Share via:

Jami Bradley

2013-Dec-04 01:03 UTC

I/O virtualisation disabled - ACPI issue?

I just started using Xen and am trying to come up to speed.  I am trying to
configure a desktop PC to boot Xen, then passthrough VGA, Keyboard, and
Mouse to a VM for development.  I have a Win7 DomU working beautifully
without the passthrough, so I have the basics working.

Here is my configuration (please let me know if I missed something
important):
ASUS P9X79 Pro motherboard, current BIOS, with VT-D enabled.
Intel I7-4930K processor

I installed CentOS 6.5 minimal for Dom0, plus a couple packages to get
things working (e.g., Perl).  I have xend turned off and I am trying to do
everything using the XL toolkit.

I have installed Xen 4.2.3 stable and have built and installed the current
head from GIT (post 4.3.1) with identical results.

After some debugging, I believe it is failing to parse the ACPI table
(acpi_drhd_units is empty in intel_vtd_setup) and disabling IOMMU.

Any tips on how to proceed?

Thanks!

Here is xl info:
host                   : r4
release                : 3.10.20-11.el6.centos.alt.x86_64
version                : #1 SMP Sat Nov 23 23:08:56 UTC 2013
machine                : x86_64
nr_cpus                : 12
max_cpu_id             : 11
nr_nodes               : 1
cores_per_socket       : 6
threads_per_core       : 2
cpu_mhz                : 3400
hw_caps                :
bfebfbff:2c100800:00000000:00007f00:77bee3bf:00000000:00000001:00000281
virt_caps              : hvm
total_memory           : 65477
free_memory            : 63740
sharing_freed_memory   : 0
sharing_used_memory    : 0
outstanding_claims     : 0
free_cpus              : 0
xen_major              : 4
xen_minor              : 4
xen_extra              : -unstable
xen_version            : 4.4-unstable
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Mon Nov 25 11:20:06 2013 +0100 git:e439e0b-dirty
xen_commandline        : dom0_mem=1024M,max:1024M loglvl=all
guest_loglvl=all iommu=on,verbose acpi=verbose apic=bigsmp,verbose
apic_verbosity=debug
cc_compiler            : gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4)
cc_compile_by          : root
cc_compile_domain      : (none)
cc_compile_date        : Mon Dec  2 22:36:29 MST 2013
xend_config_format     : 4


Here is my current grub.conf:
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (3.10.20-11.el6.centos.alt.x86_64)
        root (hd0,0)
        kernel /xen.gz dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all
iommu=on,verbose acpi=verbose apic=bigsmp,verbose apic_verbosity=debug
        module /vmlinuz-3.10.20-11.el6.centos.alt.x86_64 ro
root=UUID=65dee24c-3094-49aa-b64c-2859e964052f rd_NO_LUKS rd_NO_LVM
LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto
 KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet
xen-pciback.hide=(01:00.0)(01:00.1)
        module /initramfs-3.10.20-11.el6.centos.alt.x86_64.img

And finally the rather verbose xl dmesg:

(XEN) Xen version 4.4-unstable (root@(none)) (gcc (GCC) 4.4.7 20120313 (Red
Hat 4.4.7-4)) debug=y Mon Dec  2 22:36:29 MST 2013
(XEN) Latest ChangeSet: Mon Nov 25 11:20:06 2013 +0100 git:e439e0b-dirty
(XEN) Bootloader: GNU GRUB 0.97
(XEN) Command line: dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all
iommu=on,verbose acpi=verbose apic=bigsmp,verbose apic_verbosity=debug
(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 2 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000cc15f000 (usable)
(XEN)  00000000cc15f000 - 00000000cc445000 (reserved)
(XEN)  00000000cc445000 - 00000000cc553000 (ACPI data)
(XEN)  00000000cc553000 - 00000000cc777000 (ACPI NVS)
(XEN)  00000000cc777000 - 00000000cd721000 (reserved)
(XEN)  00000000cd721000 - 00000000cd722000 (usable)
(XEN)  00000000cd722000 - 00000000cd7a8000 (ACPI NVS)
(XEN)  00000000cd7a8000 - 00000000cdbe8000 (usable)
(XEN)  00000000cdbe8000 - 00000000cdff4000 (reserved)
(XEN)  00000000cdff4000 - 00000000ce000000 (usable)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000001030000000 (usable)
(XEN) ACPI: RSDP 000F0490, 0024 (r2 ALASKA)
(XEN) ACPI: XSDT CC47B070, 005C (r1 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: FACP CC485108, 010C (r5 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: DSDT CC47B168, 9F9A (r2 ALASKA    A M I       16 INTL 20051117)
(XEN) ACPI: FACS CC76E080, 0040
(XEN) ACPI: APIC CC485218, 0100 (r3 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: FPDT CC485318, 0044 (r1 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: MCFG CC485360, 003C (r1 ALASKA OEMMCFG.  1072009 MSFT       97)
(XEN) ACPI: HPET CC4853A0, 0038 (r1 ALASKA    A M I  1072009 AMI.        5)
(XEN) ACPI: BGRT CC552558, 0038 (r0 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: SSDT CC485430, CD128 (r2  INTEL    CpuPm     4000 INTL 20051117)
(XEN) System RAM: 65477MB (67048744kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-0000001030000000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000fd8b0
(XEN) DMI 2.7 present.
(XEN) APIC boot state is ''xapic''
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: v5 SLEEP INFO: control[0:0], status[0:0]
(XEN) ACPI: SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI: 32/64X FACS address mismatch in FADT -
cc76e080/0000000000000000, using 32
(XEN) ACPI:             wakeup_vec[cc76e08c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
(XEN) Processor #4 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled)
(XEN) Processor #6 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
(XEN) Processor #8 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
(XEN) Processor #10 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
(XEN) Processor #1 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
(XEN) Processor #3 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
(XEN) Processor #5 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
(XEN) Processor #7 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
(XEN) Processor #9 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
(XEN) Processor #11 7:14 APIC version 21
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
(XEN) Overriding APIC driver with bigsmp
(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: IOAPIC (id[0x02] address[0xfec01000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 2, version 32, address 0xfec01000, GSI 24-47
(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:  Phys.  Using 2 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 12 CPUs (0 hotplug CPUs)
(XEN) mapped APIC to ffff82cfffdfb000 (fee00000)
(XEN) mapped IOAPIC to ffff82cfffdfa000 (fec00000)
(XEN) mapped IOAPIC to ffff82cfffdf9000 (fec01000)
(XEN) IRQ limits: 48 GSI, 2272 MSI/MSI-X
(XEN) Not enabling x2APIC: depends on iommu_supports_eim.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3400.165 MHz processor.
(XEN) Initing memory sharing.
(XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7
(XEN) mce_intel.c:717: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0
extended MCE MSR 0
(XEN) Intel machine check reporting enabled
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff
(XEN) PCI: MCFG area at e0000000 reserved in E820
(XEN) PCI: Using MCFG for segment 0000 bus 00-ff
(XEN) I/O virtualisation disabled
...


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Jami Bradley

2013-Dec-12 04:47 UTC

head link

Re: I/O virtualisation disabled - ACPI issue?

On Wed, Dec 4, 2013 at 5:00 AM, Jami Bradley
<bradleyfamily.jami@gmail.com> wrote:
> From: Jami Bradley <bradleyfamily.jami@gmail.com>
> To: xen-users@lists.xen.org
> Cc:
> Date: Tue, 3 Dec 2013 18:03:36 -0700
> Subject: [Xen-users] I/O virtualisation disabled - ACPI issue?
> I just started using Xen and am trying to come up to speed.  I am trying
> to configure a desktop PC to boot Xen, then passthrough VGA, Keyboard, and
> Mouse to a VM for development.  I have a Win7 DomU working beautifully
> without the passthrough, so I have the basics working.
>
> Here is my configuration (please let me know if I missed something
> important):
> ASUS P9X79 Pro motherboard, current BIOS, with VT-D enabled.
> Intel I7-4930K processor
>
> I installed CentOS 6.5 minimal for Dom0, plus a couple packages to get
> things working (e.g., Perl).  I have xend turned off and I am trying to do
> everything using the XL toolkit.
>
> I have installed Xen 4.2.3 stable and have built and installed the current
> head from GIT (post 4.3.1) with identical results.
>
> After some debugging, I believe it is failing to parse the ACPI table
> (acpi_drhd_units is empty in intel_vtd_setup) and disabling IOMMU.
>
> Any tips on how to proceed?
>
> Thanks!
>
> I just wanted to follow up on my research on my issue.  What I found isthat the ASUS P9X79 Pro motherboard does *not* support VT-d.  It supports
"Virtualization" by Vanderpool (aka. VT-x).  Looking at the BIOS
releases
they have had, version 0906 added support for VT-d. Apparently at some
point they dropped/disabled it.

But, here is the last response I received from ASUS, I will cross my
fingers!!!

I have checked with the relative department, and they mentioned a new
bios> will be released to solve the VT-D option not exist in the bios with the
> Ivy bridge-E cpu installed, may be in one month.
> Please pay attention to our website for updating.
> Sorry for the inconvenience.
>
> Best Regards,
> Carter
> ASUS Product Support Team

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Alex Aune

2013-Dec-13 16:10 UTC

head link

Re: I/O virtualisation disabled - ACPI issue?

On 12.12.2013 05:47, Jami Bradley wrote:> On Wed, Dec 4, 2013 at 5:00 AM, Jami Bradley
> <bradleyfamily.jami@gmail.com> wrote:
> 
>> From: Jami Bradley <bradleyfamily.jami@gmail.com>
>> To: xen-users@lists.xen.org
>> Cc: 
>> Date: Tue, 3 Dec 2013 18:03:36 -0700
>> Subject: [Xen-users] I/O virtualisation disabled - ACPI issue?
>> 
>> I just started using Xen and am trying to come up to speed.  I am
>> trying to configure a desktop PC to boot Xen, then passthrough VGA,
>> Keyboard, and Mouse to a VM for development.  I have a Win7 DomU
>> working beautifully without the passthrough, so I have the basics
>> working.
>> 
>> Here is my configuration (please let me know if I missed something
>> important):
>> ASUS P9X79 Pro motherboard, current BIOS, with VT-D enabled.
>> Intel I7-4930K processor
>> 
>> I installed CentOS 6.5 minimal for Dom0, plus a couple packages to
>> get things working (e.g., Perl).  I have xend turned off and I am
>> trying to do everything using the XL toolkit.
>> 
>> I have installed Xen 4.2.3 stable and have built and installed the
>> current head from GIT (post 4.3.1) with identical results.
>> 
>> After some debugging, I believe it is failing to parse the ACPI
>> table (acpi_drhd_units is empty in intel_vtd_setup) and disabling
>> IOMMU.
>> 
>> Any tips on how to proceed?
>> 
>> Thanks!
> 
> I just wanted to follow up on my research on my issue.  What I found
> is that the ASUS P9X79 Pro motherboard does *not* support VT-d.  It
> supports "Virtualization" by Vanderpool (aka. VT-x).  Looking at
the
> BIOS releases they have had, version 0906 added support for VT-d.
> Apparently at some point they dropped/disabled it.
> 
> But, here is the last response I received from ASUS, I will cross my
> fingers!!!
> 
>> I have checked with the relative department, and they mentioned a
>> new bios will be released to solve the VT-D option not exist in the
>> bios with the Ivy bridge-E cpu installed, may be in one month.
>> Please pay attention to our website for updating.
>> Sorry for the inconvenience.
>> 
>> Best Regards,
>> Carter
>> ASUS Product Support Team
I had a similar exprience with the Asus Rampage IV Extreme motherboard 
with an Ivy Bridge-E CPU, but Asus Support couldn't confirm whether or 
not VT-d was being worked on or not by the BIOS engineers.

Here's what they had to say:> we have had talks with R&D regarding the matter multiple times but i 
> cant say for sure if anything will come out of them. I cant get a clear 
> answer from them.
Luckily I was able to get my hands on a beta version through the ROG 
forums. A user there had acquired the same motherboard/CPU through a 
system manufacturer who in turn had forwarded his request for VT-d to 
Asus for him. In response Asus had provided the beta version I ended up 
getting my hands on.

In their current state I wouldn't recommend Asus boards with Ivy 
Bridge-E CPU's...

Alex

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Xen users - Dec 2013 - I/O virtualisation disabled - ACPI issue?

I/O virtualisation disabled - ACPI issue?

Re: I/O virtualisation disabled - ACPI issue?

Re: I/O virtualisation disabled - ACPI issue?