thr3ads.net - Xen users - [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1 [Nov 2010]

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

chris

2010-Nov-29 16:13 UTC

[Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

Hello,

I''m having problems with VTD on this board. The board/cpu/bios all
support vt-d and I think maybe I''m just missing something?
Any feedback would be much appreciated :)

Output below:

root@vm:~# xm create /etc/xen/vm-nine.cfg
Using config file "/etc/xen/vm-nine.cfg".
Error: Failed to assign device to IOMMU
(0000:05:00.0@100,msitranslate=1,power_mgmt=0)

root@vm:~# lspci -s 05:00
05:00.0 USB Controller: NEC Corporation USB (rev 43)
05:00.1 USB Controller: NEC Corporation USB (rev 43)
05:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04)

root@vm:~# cat /etc/xen/vm-nine.cfg
kernel = ''/usr/lib/xen/boot/hvmloader''
builder = ''hvm''
memory = ''1024''
device_model=''/usr/lib/xen/bin/qemu-dm''
# Disks
disk = [ ''phy:/dev/storage/vm-nine,ioemu:hda,w'',
''phy:/dev/sr0,ioemu:hdc:cdrom,r''
]

# Hostname
name = ''vm-nine''

# Networking
vif = [''type=ioemu, bridge=eth0, mac=00:16:3D:37:A2:38'']

# Behaviour
boot=''dc''
vcpus=1
acpi=1
ahci=1
vnc=1
vncviewer=1
sdl=0
timer_mode=1
usb=1
usbdevice=''tablet''
localtime=1
viridian=1
pci=[''05:00.0'',''05:00.1'',''05:00.2'']

root@vm:~# dmesg | grep seiz
[    1.880424] pciback 0000:05:00.0: seizing device
[    1.880482] pciback 0000:05:00.1: seizing device
[    1.880539] pciback 0000:05:00.2: seizing device

root@vm:~# cat /boot/grub/grub.cfg  | grep pciback
        module  /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
root=UUID=aebc8747-abb3-413a-b808-b345a9a19111 ro
pci=resource_alignment=05:00.0 xen-pciback.permissive
xen-pciback.hide=(05:00.0)(05:00.1)(05:00.2)

root@vm:~# xm info
host                   : vm
release                : 2.6.32-5-xen-amd64
version                : #1 SMP Sat Oct 30 17:04:10 UTC 2010
machine                : x86_64
nr_cpus                : 8
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 3066
hw_caps                :
bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000
virt_caps              : hvm hvm_directio
total_memory           : 8180
free_memory            : 1493
node_to_cpu            : node0:0-7
node_to_memory         : node0:1493
node_to_dma32_mem      : node0:743
max_node_id            : 0
xen_major              : 4
xen_minor              : 0
xen_extra              : .1
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          : unavailable
xen_commandline        : placeholder
cc_compiler            : gcc version 4.4.5 20100824 (prerelease)
(Debian 4.4.4-11)
cc_compile_by          : waldi
cc_compile_domain      : debian.org
cc_compile_date        : Fri Sep  3 15:38:12 UTC 2010
xend_config_format     : 4

- chris

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

Konrad Rzeszutek Wilk

2010-Nov-29 17:13 UTC

head link

Re: [Xen-devel] VTD not working on Intel DX58SO w/ Xen 4.0.1

On Mon, Nov 29, 2010 at 11:13:18AM -0500, chris wrote:> Hello,
> 
> I''m having problems with VTD on this board. The board/cpu/bios all
> support vt-d and I think maybe I''m just missing something?
> Any feedback would be much appreciated :)
Please follow the steps outlined in
http://wiki.xensource.com/xenwiki/XenParavirtOps
in the sections with the word "troubleshoot". We need the full Xen
serial output.

Also look in http://wiki.xensource.com/xenwiki/XenCommonProblems.
> 
> Output below:
> 
> root@vm:~# xm create /etc/xen/vm-nine.cfg
> Using config file "/etc/xen/vm-nine.cfg".
> Error: Failed to assign device to IOMMU
> (0000:05:00.0@100,msitranslate=1,power_mgmt=0)
> 
> root@vm:~# lspci -s 05:00
> 05:00.0 USB Controller: NEC Corporation USB (rev 43)
> 05:00.1 USB Controller: NEC Corporation USB (rev 43)
> 05:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
> 
> root@vm:~# cat /etc/xen/vm-nine.cfg
> kernel = ''/usr/lib/xen/boot/hvmloader''
> builder = ''hvm''
> memory = ''1024''
> device_model=''/usr/lib/xen/bin/qemu-dm''
> # Disks
> disk = [ ''phy:/dev/storage/vm-nine,ioemu:hda,w'',
> ''phy:/dev/sr0,ioemu:hdc:cdrom,r''
> ]
> 
> # Hostname
> name = ''vm-nine''
> 
> # Networking
> vif = [''type=ioemu, bridge=eth0, mac=00:16:3D:37:A2:38'']
> 
> # Behaviour
> boot=''dc''
> vcpus=1
> acpi=1
> ahci=1
> vnc=1
> vncviewer=1
> sdl=0
> timer_mode=1
> usb=1
> usbdevice=''tablet''
> localtime=1
> viridian=1
>
pci=[''05:00.0'',''05:00.1'',''05:00.2'']
> 
> root@vm:~# dmesg | grep seiz
> [    1.880424] pciback 0000:05:00.0: seizing device
> [    1.880482] pciback 0000:05:00.1: seizing device
> [    1.880539] pciback 0000:05:00.2: seizing device
> 
> root@vm:~# cat /boot/grub/grub.cfg  | grep pciback
>         module  /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
> root=UUID=aebc8747-abb3-413a-b808-b345a9a19111 ro
> pci=resource_alignment=05:00.0 xen-pciback.permissive
> xen-pciback.hide=(05:00.0)(05:00.1)(05:00.2)
> 
> root@vm:~# xm info
> host                   : vm
> release                : 2.6.32-5-xen-amd64
> version                : #1 SMP Sat Oct 30 17:04:10 UTC 2010
> machine                : x86_64
> nr_cpus                : 8
> nr_nodes               : 1
> cores_per_socket       : 4
> threads_per_core       : 2
> cpu_mhz                : 3066
> hw_caps                :
> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000
> virt_caps              : hvm hvm_directio
> total_memory           : 8180
> free_memory            : 1493
> node_to_cpu            : node0:0-7
> node_to_memory         : node0:1493
> node_to_dma32_mem      : node0:743
> max_node_id            : 0
> xen_major              : 4
> xen_minor              : 0
> xen_extra              : .1
> 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          : unavailable
> xen_commandline        : placeholder
> cc_compiler            : gcc version 4.4.5 20100824 (prerelease)
> (Debian 4.4.4-11)
> cc_compile_by          : waldi
> cc_compile_domain      : debian.org
> cc_compile_date        : Fri Sep  3 15:38:12 UTC 2010
> xend_config_format     : 4
> 
> - chris
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

alarson@ddci.com

2010-Nov-29 17:31 UTC

head link

Re: [Xen-devel] VTD not working on Intel DX58SO w/ Xen 4.0.1

xen-devel-bounces@lists.xensource.com wrote on 11/29/2010 10:13:18 AM:
> I''m having problems with VTD on this board. The board/cpu/bios all
> support vt-d and I think maybe I''m just missing something?
Interesting that you should mention this today.  Just last night 
I was getting ready to order the dx58so as recommended on the 
VTdHwoTo wiki page (http://wiki.xen.org/xenwiki/VTdHowTo).  But when I 
went to 
the Intel "compare products" site, it says the dx58so does *not*
support
VT-d
(http://ark.intel.com/Compare.aspx?ids=36888,42486,)

I was just going to post to see if anyone knew for sure that it did work, 
or if the wiki was wrong.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

chris

2010-Nov-29 17:39 UTC

head link

Re: [Xen-devel] VTD not working on Intel DX58SO w/ Xen 4.0.1

just fyi it definitely supports vt-d i have it working on another
machine with a older version of xen (3.3) and a i7 950. I remember at
that time 3.4 was the latest and i had much worse problems trying at
3.4. i am now building a new machine and wanted to give 4.x a whirl to
see if the issues had been fixed :)

i am building more a current dom0 kernel as we speak so i will post
more details fairly soon along with serial output

On Mon, Nov 29, 2010 at 12:31 PM,  <alarson@ddci.com>
wrote:> xen-devel-bounces@lists.xensource.com wrote on 11/29/2010 10:13:18 AM:
>
>> I''m having problems with VTD on this board. The board/cpu/bios
all
>> support vt-d and I think maybe I''m just missing something?
>
> Interesting that you should mention this today.  Just last night
> I was getting ready to order the dx58so as recommended on the
> VTdHwoTo wiki page (http://wiki.xen.org/xenwiki/VTdHowTo).  But when I
> went to
> the Intel "compare products" site, it says the dx58so does *not*
support
> VT-d
> (http://ark.intel.com/Compare.aspx?ids=36888,42486,)
>
> I was just going to post to see if anyone knew for sure that it did work,
> or if the wiki was wrong.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Mike Viau

2010-Nov-29 17:46 UTC

head link

RE: [Xen-users] Re: [Xen-devel] VTD not working on Intel DX58SO w/ Xen 4.0.1

> On Mon, 29 Nov 2010 12:39:22 -0500 <tknchris@gmail.com> wrote:
>
> just fyi it definitely supports vt-d i have it working on another
> machine with a older version of xen (3.3) and a i7 950. I remember at
> that time 3.4 was the latest and i had much worse problems trying at
> 3.4. i am now building a new machine and wanted to give 4.x a whirl to
> see if the issues had been fixed :)
>
> i am building more a current dom0 kernel as we speak so i will post
> more details fairly soon along with serial output
>
What should one look for in their output to determine if VT-d is working and
detect.

My system board also claims to not support the technology, but I thought it was
working in my 4.0.1 setup.

http://ark.intel.com/Product.aspx?id=40078


Thanks.

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

Pasi Kärkkäinen

2010-Nov-29 18:42 UTC

head link

[Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

On Mon, Nov 29, 2010 at 11:13:18AM -0500, chris wrote:> Hello,
> 
> I''m having problems with VTD on this board. The board/cpu/bios all
> support vt-d and I think maybe I''m just missing something?
> Any feedback would be much appreciated :)
> 
> Output below:
> 
Please add "iommu=verbose" option for xen.gz in grub.cfg,
then reboot and then paste full Xen hypervisor "xm dmesg" output.

-- Pasi
> root@vm:~# xm create /etc/xen/vm-nine.cfg
> Using config file "/etc/xen/vm-nine.cfg".
> Error: Failed to assign device to IOMMU
> (0000:05:00.0@100,msitranslate=1,power_mgmt=0)
> 
> root@vm:~# lspci -s 05:00
> 05:00.0 USB Controller: NEC Corporation USB (rev 43)
> 05:00.1 USB Controller: NEC Corporation USB (rev 43)
> 05:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
> 
> root@vm:~# cat /etc/xen/vm-nine.cfg
> kernel = ''/usr/lib/xen/boot/hvmloader''
> builder = ''hvm''
> memory = ''1024''
> device_model=''/usr/lib/xen/bin/qemu-dm''
> # Disks
> disk = [ ''phy:/dev/storage/vm-nine,ioemu:hda,w'',
> ''phy:/dev/sr0,ioemu:hdc:cdrom,r''
> ]
> 
> # Hostname
> name = ''vm-nine''
> 
> # Networking
> vif = [''type=ioemu, bridge=eth0, mac=00:16:3D:37:A2:38'']
> 
> # Behaviour
> boot=''dc''
> vcpus=1
> acpi=1
> ahci=1
> vnc=1
> vncviewer=1
> sdl=0
> timer_mode=1
> usb=1
> usbdevice=''tablet''
> localtime=1
> viridian=1
>
pci=[''05:00.0'',''05:00.1'',''05:00.2'']
> 
> root@vm:~# dmesg | grep seiz
> [    1.880424] pciback 0000:05:00.0: seizing device
> [    1.880482] pciback 0000:05:00.1: seizing device
> [    1.880539] pciback 0000:05:00.2: seizing device
> 
> root@vm:~# cat /boot/grub/grub.cfg  | grep pciback
>         module  /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
> root=UUID=aebc8747-abb3-413a-b808-b345a9a19111 ro
> pci=resource_alignment=05:00.0 xen-pciback.permissive
> xen-pciback.hide=(05:00.0)(05:00.1)(05:00.2)
> 
> root@vm:~# xm info
> host                   : vm
> release                : 2.6.32-5-xen-amd64
> version                : #1 SMP Sat Oct 30 17:04:10 UTC 2010
> machine                : x86_64
> nr_cpus                : 8
> nr_nodes               : 1
> cores_per_socket       : 4
> threads_per_core       : 2
> cpu_mhz                : 3066
> hw_caps                :
> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000
> virt_caps              : hvm hvm_directio
> total_memory           : 8180
> free_memory            : 1493
> node_to_cpu            : node0:0-7
> node_to_memory         : node0:1493
> node_to_dma32_mem      : node0:743
> max_node_id            : 0
> xen_major              : 4
> xen_minor              : 0
> xen_extra              : .1
> 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          : unavailable
> xen_commandline        : placeholder
> cc_compiler            : gcc version 4.4.5 20100824 (prerelease)
> (Debian 4.4.4-11)
> cc_compile_by          : waldi
> cc_compile_domain      : debian.org
> cc_compile_date        : Fri Sep  3 15:38:12 UTC 2010
> xend_config_format     : 4
> 
> - chris
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

chris

2010-Nov-29 19:48 UTC

head link

[Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

ok here is the logs with 2.6.32.26 using pasi''s config for 2.6.32.25
and iommu=verbose at boot. unfortunately this board doesnt have serial
and i dont have a spare serial card handy, so hopefully this will help
us figure it out :)

On Mon, Nov 29, 2010 at 1:42 PM, Pasi Kärkkäinen <pasik@iki.fi>
wrote:> On Mon, Nov 29, 2010 at 11:13:18AM -0500, chris wrote:
>> Hello,
>>
>> I''m having problems with VTD on this board. The board/cpu/bios
all
>> support vt-d and I think maybe I''m just missing something?
>> Any feedback would be much appreciated :)
>>
>> Output below:
>>
>
> Please add "iommu=verbose" option for xen.gz in grub.cfg,
> then reboot and then paste full Xen hypervisor "xm dmesg" output.
>
> -- Pasi
>
>> root@vm:~# xm create /etc/xen/vm-nine.cfg
>> Using config file "/etc/xen/vm-nine.cfg".
>> Error: Failed to assign device to IOMMU
>> (0000:05:00.0@100,msitranslate=1,power_mgmt=0)
>>
>> root@vm:~# lspci -s 05:00
>> 05:00.0 USB Controller: NEC Corporation USB (rev 43)
>> 05:00.1 USB Controller: NEC Corporation USB (rev 43)
>> 05:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
>>
>> root@vm:~# cat /etc/xen/vm-nine.cfg
>> kernel = ''/usr/lib/xen/boot/hvmloader''
>> builder = ''hvm''
>> memory = ''1024''
>> device_model=''/usr/lib/xen/bin/qemu-dm''
>> # Disks
>> disk = [ ''phy:/dev/storage/vm-nine,ioemu:hda,w'',
>> ''phy:/dev/sr0,ioemu:hdc:cdrom,r''
>> ]
>>
>> # Hostname
>> name = ''vm-nine''
>>
>> # Networking
>> vif = [''type=ioemu, bridge=eth0,
mac=00:16:3D:37:A2:38'']
>>
>> # Behaviour
>> boot=''dc''
>> vcpus=1
>> acpi=1
>> ahci=1
>> vnc=1
>> vncviewer=1
>> sdl=0
>> timer_mode=1
>> usb=1
>> usbdevice=''tablet''
>> localtime=1
>> viridian=1
>>
pci=[''05:00.0'',''05:00.1'',''05:00.2'']
>>
>> root@vm:~# dmesg | grep seiz
>> [    1.880424] pciback 0000:05:00.0: seizing device
>> [    1.880482] pciback 0000:05:00.1: seizing device
>> [    1.880539] pciback 0000:05:00.2: seizing device
>>
>> root@vm:~# cat /boot/grub/grub.cfg  | grep pciback
>>         module  /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
>> root=UUID=aebc8747-abb3-413a-b808-b345a9a19111 ro
>> pci=resource_alignment=05:00.0 xen-pciback.permissive
>> xen-pciback.hide=(05:00.0)(05:00.1)(05:00.2)
>>
>> root@vm:~# xm info
>> host                   : vm
>> release                : 2.6.32-5-xen-amd64
>> version                : #1 SMP Sat Oct 30 17:04:10 UTC 2010
>> machine                : x86_64
>> nr_cpus                : 8
>> nr_nodes               : 1
>> cores_per_socket       : 4
>> threads_per_core       : 2
>> cpu_mhz                : 3066
>> hw_caps                :
>> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000
>> virt_caps              : hvm hvm_directio
>> total_memory           : 8180
>> free_memory            : 1493
>> node_to_cpu            : node0:0-7
>> node_to_memory         : node0:1493
>> node_to_dma32_mem      : node0:743
>> max_node_id            : 0
>> xen_major              : 4
>> xen_minor              : 0
>> xen_extra              : .1
>> 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          : unavailable
>> xen_commandline        : placeholder
>> cc_compiler            : gcc version 4.4.5 20100824 (prerelease)
>> (Debian 4.4.4-11)
>> cc_compile_by          : waldi
>> cc_compile_domain      : debian.org
>> cc_compile_date        : Fri Sep  3 15:38:12 UTC 2010
>> xend_config_format     : 4
>>
>> - chris
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Mike Viau

2010-Nov-29 20:01 UTC

head link

[Xen-devel] RE: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

On Mon, 29 Nov 2010 14:48:08 -0500 <tknchris@gmail.com> wrote:

ok here is the logs with 2.6.32.26 using pasi''s config for 2.6.32.25
and iommu=verbose at boot. unfortunately this board doesnt have serial
and i dont have a spare serial card handy, so hopefully this will help
us figure it out :)

-------------

For reference here is what my Intel® Desktop Board DP55WG
(http://ark.intel.com/Product.aspx?id=40078) reported:


(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) EPT supports 2MB super page.
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) Intel VT-d Snoop Control supported.
(XEN) Intel VT-d DMA Passthrough not supported.
(XEN) Intel VT-d Queued Invalidation supported.
(XEN) Intel VT-d Interrupt Remapping not supported.
(XEN) I/O virtualisation enabled



Also stating no support for Intel® Virtualization Technology (Intel® VT) for
Directed I/O (Intel® VT-d) on Intel''s website


Intel® Virtualization Technology (Intel® VT) for Directed I/O (Intel®
VT-d)Intel®
Virtualization Technology for Directed I/O (VT-d) extends Intel''s
Virtualization Technology (VT) roadmap by providing hardware assists
for virtualization solution. VT-d continues from the existing support
for IA-32 (VT-x) and Itanium® processor (VT-i) virtualization adding
new support for I/O-device virtualization. Intel VT-d can help end
users improve security and reliability of the systems and also improve
performance of I/O devices in virtualized environment. These inherently
helps IT managers reduce the overall total cost of ownership by
reducing potential down time and increasing productive throughput by
better utilization of the data center resources.

 		 	   		  
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

chris

2010-Nov-29 20:06 UTC

head link

Re: [Xen-devel] RE: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

please start a new thread for your board if you need help.

pasi/konrad any ideas?

On Mon, Nov 29, 2010 at 3:01 PM, Mike Viau <viaum@sheridanc.on.ca>
wrote:>
> On Mon, 29 Nov 2010 14:48:08 -0500 <tknchris@gmail.com> wrote:
>
> ok here is the logs with 2.6.32.26 using pasi''s config for
2.6.32.25
> and iommu=verbose at boot. unfortunately this board doesnt have serial
> and i dont have a spare serial card handy, so hopefully this will help
> us figure it out :)
>
> -------------
>
> For reference here is what my Intel® Desktop Board DP55WG
(http://ark.intel.com/Product.aspx?id=40078) reported:
>
>
> (XEN) VMX: Supported advanced features:
> (XEN)  - APIC MMIO access virtualisation
> (XEN)  - APIC TPR shadow
> (XEN)  - Extended Page Tables (EPT)
> (XEN)  - Virtual-Processor Identifiers (VPID)
> (XEN)  - Virtual NMI
> (XEN)  - MSR direct-access bitmap
> (XEN) EPT supports 2MB super page.
> (XEN) HVM: ASIDs enabled.
> (XEN) HVM: VMX enabled
> (XEN) HVM: Hardware Assisted Paging detected.
> (XEN) Intel VT-d Snoop Control supported.
> (XEN) Intel VT-d DMA Passthrough not supported.
> (XEN) Intel VT-d Queued Invalidation supported.
> (XEN) Intel VT-d Interrupt Remapping not supported.
> (XEN) I/O virtualisation enabled
>
>
>
> Also stating no support for Intel® Virtualization Technology (Intel® VT)
for Directed I/O (Intel® VT-d) on Intel''s website
>
>
> Intel® Virtualization Technology (Intel® VT) for Directed I/O (Intel®
VT-d)Intel®
> Virtualization Technology for Directed I/O (VT-d) extends Intel''s
> Virtualization Technology (VT) roadmap by providing hardware assists
> for virtualization solution. VT-d continues from the existing support
> for IA-32 (VT-x) and Itanium® processor (VT-i) virtualization adding
> new support for I/O-device virtualization. Intel VT-d can help end
> users improve security and reliability of the systems and also improve
> performance of I/O devices in virtualized environment. These inherently
> helps IT managers reduce the overall total cost of ownership by
> reducing potential down time and increasing productive throughput by
> better utilization of the data center resources.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2010-Nov-29 20:28 UTC

head link

[Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

On Mon, Nov 29, 2010 at 02:48:08PM -0500, chris wrote:> ok here is the logs with 2.6.32.26 using pasi''s config for
2.6.32.25
> and iommu=verbose at boot. unfortunately this board doesnt have serial
> and i dont have a spare serial card handy, so hopefully this will help
> us figure it out :)
> 
Yep, this is the needed info.

> On Mon, Nov 29, 2010 at 1:42 PM, Pasi Kärkkäinen <pasik@iki.fi>
wrote:
> > On Mon, Nov 29, 2010 at 11:13:18AM -0500, chris wrote:
> >> Hello,
> >>
> >> I''m having problems with VTD on this board. The
board/cpu/bios all
> >> support vt-d and I think maybe I''m just missing
something?
> >> Any feedback would be much appreciated :)
> >>
> >> Output below:
> >>
> >
> > Please add "iommu=verbose" option for xen.gz in grub.cfg,
> > then reboot and then paste full Xen hypervisor "xm dmesg"
output.
> >
> > -- Pasi
> >
> >> root@vm:~# xm create /etc/xen/vm-nine.cfg
> >> Using config file "/etc/xen/vm-nine.cfg".
> >> Error: Failed to assign device to IOMMU
> >> (0000:05:00.0@100,msitranslate=1,power_mgmt=0)
> >>
> >>
pci=[''05:00.0'',''05:00.1'',''05:00.2'']
> >>
> >> root@vm:~# dmesg | grep seiz
> >> [    1.880424] pciback 0000:05:00.0: seizing device
> >> [    1.880482] pciback 0000:05:00.1: seizing device
> >> [    1.880539] pciback 0000:05:00.2: seizing device
> >>
> >> root@vm:~# cat /boot/grub/grub.cfg  | grep pciback
> >>         module  /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
> >> root=UUID=aebc8747-abb3-413a-b808-b345a9a19111 ro
> >> pci=resource_alignment=05:00.0 xen-pciback.permissive
> >> xen-pciback.hide=(05:00.0)(05:00.1)(05:00.2)
> >>
> (XEN) Xen version 4.0.1 (Debian 4.0.1-1) (waldi@debian.org) (gcc version
4.4.5 20100824 (prerelease) (Debian 4.4.4-11) ) Fri Sep  3 15:38:12 UTC 2010
> (XEN) Bootloader: GRUB 1.98+20100804-8
> (XEN) Command line: placeholder iommu=verbose
..
> (XEN) [VT-D]dmar.c:687: Host address width 39
> (XEN) [VT-D]dmar.c:702: found ACPI_DMAR_DRHD:
> (XEN) [VT-D]dmar.c:398:   dmaru->address = fe711000
> (XEN) [VT-D]iommu.c:1081: drhd->address = fe711000 iommu->reg =
ffff82c3fff57000
> (XEN) [VT-D]iommu.c:1083: cap = c9008010e60262 ecap = f0207a
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1b.0
> (XEN) [VT-D]dmar.c:702: found ACPI_DMAR_DRHD:
> (XEN) [VT-D]dmar.c:398:   dmaru->address = fe710000
> (XEN) [VT-D]iommu.c:1081: drhd->address = fe710000 iommu->reg =
ffff82c3fff56000
> (XEN) [VT-D]iommu.c:1083: cap = c90780106f0462 ecap = f020fa
> (XEN) [VT-D]dmar.c:341:   IOAPIC: f0:1f.7
> (XEN) [VT-D]dmar.c:412:   flags: INCLUDE_ALL
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1d.0
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr e9000 end_address e9fff
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1d.1
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr ea000 end_address eafff
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1d.2
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr eb000 end_address ebfff
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1a.0
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr e6000 end_address e6fff
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1a.1
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr e7000 end_address e7fff
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1a.2
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr e8000 end_address e8fff
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1d.0
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr ec000 end_address eefff
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Detected 3066.868 MHz processor.
> (XEN) Initing memory sharing.
> (XEN) VMX: Supported advanced features:
> (XEN)  - APIC MMIO access virtualisation
> (XEN)  - APIC TPR shadow
> (XEN)  - Extended Page Tables (EPT)
> (XEN)  - Virtual-Processor Identifiers (VPID)
> (XEN)  - Virtual NMI
> (XEN)  - MSR direct-access bitmap
> (XEN) EPT supports 2MB super page.
> (XEN) HVM: ASIDs enabled.
> (XEN) HVM: VMX enabled
> (XEN) HVM: Hardware Assisted Paging detected.
> (XEN) Intel VT-d Snoop Control not supported.
> (XEN) Intel VT-d DMA Passthrough not supported.
> (XEN) Intel VT-d Queued Invalidation supported.
> (XEN) Intel VT-d Interrupt Remapping supported.
> (XEN) I/O virtualisation enabled
> (XEN)  - Dom0 mode: Relaxed
..
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:0.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:10.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:10.1
> (XEN) [VT-D]iommu.c:1332: d0:PCIe: map bdf = 0:14.0
> (XEN) [VT-D]iommu.c:1332: d0:PCIe: map bdf = 0:14.1
> (XEN) [VT-D]iommu.c:1332: d0:PCIe: map bdf = 0:14.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:14.3
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:19.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1a.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1a.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1a.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1a.7
> (XEN) [VT-D]iommu.c:1332: d0:PCIe: map bdf = 0:1b.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1d.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1d.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1d.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1d.7
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1f.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1f.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1f.3
> (XEN) [VT-D]iommu.c:1332: d0:PCIe: map bdf = 3:0.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 5:0.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 5:0.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 5:0.2
> (XEN) [VT-D]iommu.c:1332: d0:PCIe: map bdf = 7:0.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:2.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:2.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.3
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.4
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.5
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.6
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.7
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:0.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:0.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:2.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:2.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:3.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:3.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:3.4
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:4.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:4.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:4.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:4.3
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:5.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:5.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:5.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:5.3
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:6.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:6.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:6.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:6.3
> (XEN) [VT-D]iommu.c:698: iommu_enable_translation: iommu->reg =
ffff82c3fff57000
> (XEN) [VT-D]iommu.c:698: iommu_enable_translation: iommu->reg =
ffff82c3fff56000
...
> (XEN) [VT-D]iommu.c:1468: d0:PCI: unmap bdf = 5:0.0
> (XEN) [VT-D]iommu.c:1339: d1:PCI: map bdf = 5:0.0
> (XEN) domctl.c:846:d0 XEN_DOMCTL_assign_device: assign device (5:0.0)
failed

-- Pasi


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Jan Beulich

2010-Nov-30 08:31 UTC

head link

[Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

>>> On 29.11.10 at 20:48, chris <tknchris@gmail.com> wrote:
> ok here is the logs with 2.6.32.26 using pasi''s config for
2.6.32.25
> and iommu=verbose at boot. unfortunately this board doesnt have serial
> and i dont have a spare serial card handy, so hopefully this will help
> us figure it out :)
With this, you could give -unstable c/s 22348
(http://xenbits.xensource.com/xen-unstable.hg?rev/2dfba250c50b)
a try (backported already as c/s 21379,
http://xenbits.xensource.com/xen-4.0-testing.hg?rev/4bd91466a085).

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

chris

2010-Dec-02 15:25 UTC

head link

Re: [Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

sorry but can you tell me how to pull this from git?

On Tue, Nov 30, 2010 at 3:31 AM, Jan Beulich <JBeulich@novell.com>
wrote:>>>> On 29.11.10 at 20:48, chris <tknchris@gmail.com> wrote:
>> ok here is the logs with 2.6.32.26 using pasi''s config for
2.6.32.25
>> and iommu=verbose at boot. unfortunately this board doesnt have serial
>> and i dont have a spare serial card handy, so hopefully this will help
>> us figure it out :)
>
> With this, you could give -unstable c/s 22348
> (http://xenbits.xensource.com/xen-unstable.hg?rev/2dfba250c50b)
> a try (backported already as c/s 21379,
> http://xenbits.xensource.com/xen-4.0-testing.hg?rev/4bd91466a085).
>
> Jan
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

chris

2010-Dec-07 18:46 UTC

head link

Re: [Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

I''m willing/wanting to test if this fixes it, but how do I pull the
sources? Is this is a fix for the hypervisor or dom0?

On Thu, Dec 2, 2010 at 10:25 AM, chris <tknchris@gmail.com>
wrote:> sorry but can you tell me how to pull this from git?
>
> On Tue, Nov 30, 2010 at 3:31 AM, Jan Beulich <JBeulich@novell.com>
wrote:
>>>>> On 29.11.10 at 20:48, chris <tknchris@gmail.com>
wrote:
>>> ok here is the logs with 2.6.32.26 using pasi''s config for
2.6.32.25
>>> and iommu=verbose at boot. unfortunately this board doesnt have
serial
>>> and i dont have a spare serial card handy, so hopefully this will
help
>>> us figure it out :)
>>
>> With this, you could give -unstable c/s 22348
>> (http://xenbits.xensource.com/xen-unstable.hg?rev/2dfba250c50b)
>> a try (backported already as c/s 21379,
>> http://xenbits.xensource.com/xen-4.0-testing.hg?rev/4bd91466a085).
>>
>> Jan
>>
>>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

chris

2011-Jan-22 03:52 UTC

head link

Re: [Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

hey Jan,

I was finally able to test that changeset, and I''ve made it a little
further. Now upon starting the domain I get:

# xm create vm-nine.cfg
Using config file "./vm-nine.cfg".
Error: Timed out waiting for device model action

Some background:

# xm pci-list-assignable-devices
0000:02:00.0
0000:02:00.1
0000:02:00.2

# xm dmesg
(XEN) [VT-D]iommu.c:1785: VT-d page table not sharing with EPT table
(XEN) [VT-D]iommu.c:1500: d0:PCI: unmap bdf = 2:0.0
(XEN) [VT-D]iommu.c:1373: d4:PCI: map bdf = 2:0.0

What can I do to help troubleshoot further?

On Tue, Dec 7, 2010 at 1:46 PM, chris <tknchris@gmail.com>
wrote:> I''m willing/wanting to test if this fixes it, but how do I pull
the
> sources? Is this is a fix for the hypervisor or dom0?
>
> On Thu, Dec 2, 2010 at 10:25 AM, chris <tknchris@gmail.com> wrote:
>> sorry but can you tell me how to pull this from git?
>>
>> On Tue, Nov 30, 2010 at 3:31 AM, Jan Beulich
<JBeulich@novell.com> wrote:
>>>>>> On 29.11.10 at 20:48, chris <tknchris@gmail.com>
wrote:
>>>> ok here is the logs with 2.6.32.26 using pasi''s config
for 2.6.32.25
>>>> and iommu=verbose at boot. unfortunately this board doesnt have
serial
>>>> and i dont have a spare serial card handy, so hopefully this
will help
>>>> us figure it out :)
>>>
>>> With this, you could give -unstable c/s 22348
>>> (http://xenbits.xensource.com/xen-unstable.hg?rev/2dfba250c50b)
>>> a try (backported already as c/s 21379,
>>> http://xenbits.xensource.com/xen-4.0-testing.hg?rev/4bd91466a085).
>>>
>>> Jan
>>>
>>>
>>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Possibly Parallel Threads

Search for more apparently analagous threads

Xen users - Nov 2010 - VTD not working on Intel DX58SO w/ Xen 4.0.1

[Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

Re: [Xen-devel] VTD not working on Intel DX58SO w/ Xen 4.0.1

Re: [Xen-devel] VTD not working on Intel DX58SO w/ Xen 4.0.1

Re: [Xen-devel] VTD not working on Intel DX58SO w/ Xen 4.0.1

RE: [Xen-users] Re: [Xen-devel] VTD not working on Intel DX58SO w/ Xen 4.0.1

[Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

[Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

[Xen-devel] RE: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

Re: [Xen-devel] RE: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

[Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

[Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

Re: [Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

Re: [Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

Re: [Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

Possibly Parallel Threads