All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Tramnitz <chris.ace@gmx.net>
To: xen-devel@lists.xensource.com
Subject: Re: VT-D On An Asus P5E-VM DO Motherboard Not Working, Xen 3.4.1
Date: Wed, 30 Sep 2009 13:12:40 +0200	[thread overview]
Message-ID: <h9vefq$6dm$4@ger.gmane.org> (raw)
In-Reply-To: <e8f0b580909281835n36f3f719ua200f4d62c3bb5df@mail.gmail.com>

Michael MacLeod wrote:
> We have a bit of joy now folks. It appears to have been the Initiate 
> Graphics Adapter setting in the BIOS. It was set to use my PCIe graphics 
> card as the first option (which is the default value). I set it to use 
> integrated graphics (Intel 82Q35 Express) and now VT-d is enabled at 
> boot (even without Dexuan's patch). It's still a BIOS bug, as I believe 
> I should be able to use a PCIe graphics card and have VT-d work 
> correctly at the same time.
> 
> Unfortunately, 2.6.18.8-xen does not appear to have support for the 
> Intel graphics card that is the integrated graphics chip, so I lose my X 
> display. Oh, and when I try and actually launch a domU, I get this: 
> Error: pci: PCI Backend and pci-stub don't own device 0000:03:00.0. I 
> haven't had time to play with any of this yet though, so hopefully I can 
> surmount these obstacles as well.
> 
> Thanks everyone,
> Mike.


I could reproduce the error when completely disabling the IGD, but not 
by changing the init order.
I.e. I could successfully but with my Radeon as primary VGA device (with 
the IGD enabled but as secondary and unused device) and VT-d was still 
enabled.

This could be different when using PCIe because due to the limit of PCIe 
lanes the IGD might be disabled completely when using a PCIe video 
card... not sure about this though, so you may give it a try with IGD 
enabled but PEG/IGD init order.


Best regards,
    Christian

  reply	other threads:[~2009-09-30 11:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-26 20:17 VT-D On An Asus P5E-VM DO Motherboard Not Working, Xen 3.4.1 Michael MacLeod
2009-09-27  7:14 ` Han, Weidong
2009-09-27  7:34   ` Michael MacLeod
2009-09-27  7:45     ` Han, Weidong
2009-09-27 15:35       ` Michael MacLeod
2009-09-27 17:30         ` Keir Fraser
2009-09-28  0:47           ` Han, Weidong
2009-09-28 10:38             ` Christian Tramnitz
2009-09-28 12:54               ` Keir Fraser
2009-09-28 13:04                 ` Tim Moore
2009-09-28 13:09                   ` Christian Tramnitz
2009-09-28 13:47                     ` Christian Tramnitz
2009-09-29  1:35                       ` Michael MacLeod
2009-09-30 11:12                         ` Christian Tramnitz [this message]
2009-10-01  0:01                           ` Michael MacLeod
2009-09-28 13:08               ` Han, Weidong
2009-09-27  7:39 ` Sander Eikelenboom
2009-09-27 15:33   ` Michael MacLeod
2009-09-28  2:33 ` Cui, Dexuan
2009-09-28  9:56   ` Sander Eikelenboom

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='h9vefq$6dm$4@ger.gmane.org' \
    --to=chris.ace@gmx.net \
    --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.