All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Phung Te Ha <phungte@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ross Philipson <Ross.Philipson@citrix.com>,
	Kamala Narasimhan <Kamala.Narasimhan@citrix.com>
Subject: Re: XCI: can we get to the demo state?
Date: Fri, 14 Aug 2009 12:04:57 +0100	[thread overview]
Message-ID: <4A8544D9.9070204@eu.citrix.com> (raw)
In-Reply-To: <f6cf36180908111733x7af559bbr27c1682c7d760319@mail.gmail.com>

Phung Te Ha wrote:
> Hi Vincent,
>
> I tried your suggestion, adding pci = 0,bind,0000:00:02.0 in the config
> on 2 different machines, the HP6930 and on an Intel MB DQ35OJ.
>
> On both machines, I got the samething, the guest run as shown by 
> xenops list_domains:
>
>  id |  state |    cpu_time |                                 uuid
>  0 |     R  | 54203470658 | 00000000-0000-0000-0000-000000000000
>  1 |    B H | 12214238864 | 00000000-0000-0000-0000-000000000002
>
> But nothing shows on the screen.
>
> I checked the logs and found in xenops dmesg:
>
> ...
> (XEN) Intel VT-d Snoop Control not supported.
> (XEN) Intel VT-d DMA Passthrough not supported.
> (XEN) Intel VT-d Queued Invalidation not supported.
> (XEN) Intel VT-d Interrupt Remapping not supported.
> (XEN) I/O virtualisation enabled
> (XEN) I/O virtualisation for PV guests disabled
>
>
> And when the guest is started:
>
> ...
>  _fault:DMA Write: 0:2.0 addr faddf7000 REASON 5 iommu->reg = 
> ffff828bfff56000
> (XEN) print_vtd_entries: iommu = ffff83007dcfb320 bdf = 0:2:0 gmfn = 
> faddf7
> (XEN)     root_entry = ffff83007e0ce000
> (XEN)     root_entry[0] = 7e066001
> (XEN)     context = ffff83007e066000
> (XEN)     context[10] = 201_7da02001
> (XEN)     l3 = ffff83007da02000
> (XEN)     l3_index = 3e
> (XEN)     l3[3e] = 0
> (XEN)     l3[3e] not present
> (XEN) [VT-D]iommu.c:722: iommu_page_fault: iommu->reg = ffff828bfff56000
> (XEN) [VT-D]iommu.c:691: iommu_fault_status: Fault Overflow
> (XEN) [VT-D]iommu.c:694: iommu_fault_status: Primary Pending Fault
> (XEN) [VT-D]iommu.c:676: iommu_fault:DMA Write: 0:2.0 addr faddf7000 
> REASON 5 iommu->reg = ffff828bfff56000
> (XEN) print_vtd_entries: iommu = ffff83007dcfb320 bdf = 0:2:0 gmfn = 
> faddf7
> (XEN)     root_entry = ffff83007e0ce000
> (XEN)     root_entry[0] = 7e066001
> (XEN)     context = ffff83007e066000
> ...
>
> Do you think these 2 machines have enough of VT-d features to get the 
> graphics passed-through?
> Do you have a preferred desktop board, known to work for graphisc 
> passed-through?
I'm not really familiar with thoses VT-d errors. Kamala/Ross do you have 
any idea, what this previous errors means ?

thanks,
-- 
Vincent

  reply	other threads:[~2009-08-14 11:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 14:10 XCI: can we get to the demo state? Phung Te Ha
2009-08-10 13:19 ` Vincent Hanquez
2009-08-10 22:01   ` Tim Moore
2009-08-11 16:46     ` Vincent Hanquez
2009-08-12  0:33       ` Phung Te Ha
2009-08-14 11:04         ` Vincent Hanquez [this message]
2009-08-14 14:13           ` Ross Philipson
2009-08-14 15:32             ` Phung Te Ha
2009-08-14 18:08               ` Ross Philipson
2009-08-14 20:17                 ` Phung Te Ha
2009-08-14 21:15                   ` Ross Philipson
2009-08-14 23:51                     ` Phung Te Ha
2009-08-15 17:38                     ` Tom Rotenberg
2009-08-17 19:17                       ` Phung Te Ha
2009-08-17 19:09                     ` Phung Te Ha
2009-08-18 21:17                       ` Phung Te Ha
2009-08-18 21:28                         ` Tom Rotenberg
2009-08-18 23:49                           ` Phung Te Ha
2009-08-26 21:54                         ` Phung Te Ha

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=4A8544D9.9070204@eu.citrix.com \
    --to=vincent.hanquez@eu.citrix.com \
    --cc=Kamala.Narasimhan@citrix.com \
    --cc=Ross.Philipson@citrix.com \
    --cc=phungte@gmail.com \
    --cc=xen-devel@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.