All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: chris <tknchris@gmail.com>
Cc: Xen-Devel List <xen-devel@lists.xensource.com>,
	Xen-Users List <xen-users@lists.xensource.com>
Subject: Re: VTD not working on Intel DX58SO w/ Xen 4.0.1
Date: Mon, 29 Nov 2010 12:13:36 -0500	[thread overview]
Message-ID: <20101129171336.GC20952@dumpdata.com> (raw)
In-Reply-To: <AANLkTika_RqMaPcZUVoiRN_p1dMza7+rf8=wZMXVSOE4@mail.gmail.com>

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

  reply	other threads:[~2010-11-29 17:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29 16:13 VTD not working on Intel DX58SO w/ Xen 4.0.1 chris
2010-11-29 17:13 ` Konrad Rzeszutek Wilk [this message]
2010-11-29 17:31 ` alarson
2010-11-29 17:39   ` chris
2010-11-29 17:46     ` Re: [Xen-devel] " Mike Viau
2010-11-29 18:42 ` [Xen-users] " Pasi Kärkkäinen
2010-11-29 19:48   ` chris
2010-11-29 20:01     ` Mike Viau
2010-11-29 20:06       ` chris
2010-11-29 20:28     ` Pasi Kärkkäinen
2010-11-30  8:31     ` Jan Beulich
2010-12-02 15:25       ` [Xen-devel] " chris
2010-12-07 18:46         ` chris
2011-01-22  3:52           ` chris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101129171336.GC20952@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=tknchris@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.