kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Braumann <harry@unheit.net>
To: Sheng Yang <yasker@gmail.com>
Cc: kvm@vger.kernel.org, Joerg Rodel <joerg.roedel@amd.com>
Subject: Re: PCI pass-through: guest can't map memory
Date: Sun, 11 Jan 2009 14:59:15 +0100	[thread overview]
Message-ID: <20090111145915.08d296bc@sbs173> (raw)
In-Reply-To: <20090111043512.GA23652@yukikaze>

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]

On Sun, 11 Jan 2009 12:35:12 +0800
Sheng Yang <yasker@gmail.com> wrote:

> On Sun, Jan 11, 2009 at 01:12:42AM +0100, Harald Braumann wrote:
> > Hi!
> > 
> > (please CC me, as I'm not subscribed)
> > 
> > I try to give the guest (Windows XP) direct access to one of the
> > graphics adaptors. 
> > [...]
> 
> Hi Harry
> 
> I think we at least have one issue here: currently we can't support
> graphics card assignment... Graphics card is more complex than others
> due to video bios we must support. So it's not mature now (for both
> KVM and Xen). Please wait for our future releases(though I have no
> idea when it would be supported, maybe several monthes or
> longer... :( ).

Hi,

thanks for the reply. I've found this on that matter:
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/26785/focus=26971
(device-assignment code doesn't update the cards BAR). Is that the
problem, you're talking about? Or is there something else that's still
missing? So I know what to look for in the changelogs.

Cheers,
harry

PS: I've applied Leendert's patch, but it didn't help

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-01-11 13:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11  0:12 PCI pass-through: guest can't map memory Harald Braumann
2009-01-11  4:35 ` Sheng Yang
2009-01-11 13:59   ` Harald Braumann [this message]
2009-01-12  7:54     ` Sheng Yang

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=20090111145915.08d296bc@sbs173 \
    --to=harry@unheit.net \
    --cc=joerg.roedel@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=yasker@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).