[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Error: failed to assign device...VT-d isn't enabled properly(?)


  • To: "Ralf Hornik Mailings" <ralf@xxxxxxxxxxxxxxxxx>
  • From: "Todd Deshane" <deshantm@xxxxxxxxx>
  • Date: Fri, 14 Nov 2008 21:01:39 -0500
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 14 Nov 2008 18:02:20 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=w65nhRKTfL4AXeqjL5C58QRGsxxZqQdrdhmxqyKiIlZ7/lDLTq+q2SSw8P92Cq+a9H 35wywS4de48Knhik4Ew/8tT3Or4EnKTrjAEqidk/MfMtL++h/wqvsiOF9xdMbahHwKgN 8iIQqEBQiL68+3np9ILD1EUxq1mPJFJoWub08=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

HVM guest passthrough requires VT-d

see: http://wiki.xensource.com/xenwiki/VTdHowTo

On Fri, Nov 14, 2008 at 6:38 AM, Ralf Hornik Mailings
<ralf@xxxxxxxxxxxxxxxxx> wrote:
> Dear List,
>
> I need to make an Aladdin eToken Pro visible in a Linux guest HVM, but I
> cannot assign the device to any domU, while it's being blocked by the dom0.
>
> To avoid this trouble I would like to pass the whole USB bus to the domU
> directly, via PCI passthrough.
>
> Now I use xen 3.3.0 from xensource and xen kernel from Ubuntu 8.04
> 2.6.24-19-xen, because the xensource xen kernel (2.6.18) does not support my
> hardware completely.
>
> while installing xen and tools anything seems to by fine:
>
> *** PCI passthrough capability has been enabled ***
>
> But when I hide the PCI which does the kernel:
>
> [    0.000000] Command line: root=/dev/mapper/sys_vol-sys_root ro
> console=tty0 it821x_noraid=1 selinux=0 pci=routeirq pciback.hide=(00:1d.0)
> [    1.179637] Kernel command line: root=/dev/mapper/sys_vol-sys_root ro
> console=tty0 it821x_noraid=1 selinux=0 pci=routeirq pciback.hide=(00:1d.0)
> [    0.114939] ACPI: bus type pci registered
> [    0.149559] PCI: Routing PCI interrupts for all devices because
> "pci=routeirq" specified
> [    0.177791] pciback 0000:00:1d.0: seizing device
> [    0.141957] Allocate Port Service[0000:00:1c.0:pcie00]
>
> I can not use it in domU:
>
> ~# xm create domU
> Error: failed to assign device: maybe the platform doesn't support VT-d, or
> VT-d isn't enabled properly?
>
> As I googled, I figured out, that only a couple of boards support vt-d or
> iommu, but pci passthrough is widely common.
>
> xm dmesg shows:
>
> (XEN) I/O virtualisation disabled
>
> Also, a friend told me, on its (pci passthrough working) machine the same
> message appears. AND, any documantation regarding this feature dosn't
> mention vt-d at all:
>
> http://www.wlug.org.nz/XenPciPassthrough
> http://www.google.de/search?q=xen+pci+passthrough
>
> So, what does the error mentioned in my subject mean? Is it a wrong
> interpreted issue by the kernel, or do I really need vt-d, which my board
> obviously does not support? (ECS G31T-M with core 2 quad q6600)
>
> OR, is there another (more easy) solution to make the usb eToken visible in
> domU HVM?
>
> One more question: Is there a newer Kernel available soon (>2.6.22) from
> xensource?
>
> Thank you and best regards
>
>
> Ralf
> --
> alles bleibt anders...
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>



-- 
Todd Deshane
http://todddeshane.net
http://runningxen.com

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.