All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Moore <timothy.moore@expidas.net>
To: 'Keir Fraser' <keir.fraser@eu.citrix.com>,
	Christian Tramnitz <chris.ace@gmx.net>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: RE: Re: VT-D On An Asus P5E-VM DO Motherboard Not Working, Xen 3.4.1
Date: Mon, 28 Sep 2009 14:04:05 +0100	[thread overview]
Message-ID: <14D9C9E2ED61ED41BC3B37ACDF4E880002E0C4B8F68B@heavy-vm03.heavy.org.uk> (raw)
In-Reply-To: <C6E670B2.B0F4%keir.fraser@eu.citrix.com>

If I recall from my testing of an ASUS P6T (before I bought an Intel board) enabling/disabling legacy USB, Firewire and the External SATA controller changed the RMRR ranges and produced different results ... suggest try disable legacy USB and Firewire to see.

-----Original Message-----
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser
Sent: 28 September 2009 13:55
To: Christian Tramnitz; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] Re: VT-D On An Asus P5E-VM DO Motherboard Not Working, Xen 3.4.1

On 28/09/2009 11:38, "Christian Tramnitz" <chris.ace@gmx.net> wrote:

> I'm the one with working VT-d on this board (using the same BIOS version
> than Michael). I was using an older 3.4.0-pre but now switched to the
> latest 3.5-unstable and its still working. I haven't tried to actually
> pass-through a device for some time but it was already working in the past.
> 
> Attached my xm dmesg.

Your BIOS has declared an RMRR range of cf600000-cfffffff, compared with
Sander's invalid d0000000-cfffffff. So the BIOSes must be different, or
differently configured.

 -- Keir



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

  reply	other threads:[~2009-09-28 13:04 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 [this message]
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
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=14D9C9E2ED61ED41BC3B37ACDF4E880002E0C4B8F68B@heavy-vm03.heavy.org.uk \
    --to=timothy.moore@expidas.net \
    --cc=chris.ace@gmx.net \
    --cc=keir.fraser@eu.citrix.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.