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

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

  • To: Jan Beulich <JBeulich@xxxxxxxxxx>
  • From: chris <tknchris@xxxxxxxxx>
  • Date: Fri, 21 Jan 2011 22:52:37 -0500
  • Cc: Xen-Devel List <xen-devel@xxxxxxxxxxxxxxxxxxx>, Xen-Users List <xen-users@xxxxxxxxxxxxxxxxxxx>, pasik@xxxxxx
  • Delivery-date: Fri, 21 Jan 2011 19:53:46 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Xk4ivk2ZbyLShW4G7ul6NRfJi8cW347+pDNLgTHSHDw1p4Vw0Orjk27sAAN+LTchU6 AZEBcLHw6LO4EGdNOsoVEYTH8aowcf4Jx/v7IVdd7xjDi38tE6mOaHtdtx4rd302u14V iYL+I5BhKk/6UeFVwBa31T09Pm5m1oycvuS2c=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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

# 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@xxxxxxxxx> 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@xxxxxxxxx> 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@xxxxxxxxxx> wrote:
>>>>>> On 29.11.10 at 20:48, chris <tknchris@xxxxxxxxx> wrote:
>>>> ok here is the logs with using pasi's config for
>>>> 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



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