xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Liwei <xieliwei@gmail.com>
To: konrad.wilk@oracle.com
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: VGA passthrough on unstable
Date: Wed, 18 May 2011 07:14:10 +0800	[thread overview]
Message-ID: <BANLkTikuf0w-gck7hvhN2eeimsLOG=g-=A@mail.gmail.com> (raw)

>Date: Tue, 10 May 2011 13:55:04 -0400
>From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>Subject: Re: [Xen-devel] Re: VGA passthrough on unstable
>To: JavMV <javiapple@hotmail.com>
>Cc: xen-devel@lists.xensource.com
>Message-ID: <20110510175504.GA15697@dumpdata.com>
>Content-Type: text/plain; charset=us-ascii
>
>> How can i fix this?
>> Is the patch hvmloader already applied in xen-unstable4.2?
>> Is there any difference between using pci-stub instead of pciback?
>
>Not for HVM guests.
>>
>> With these 2 patches applied I cannot run the virtual machine neither with
>> gfx_passthru = 0, but without those patches i was able to do it and was able
>> to see the Nvidia Card inside Windows but with error code43 and a yellow
>> exclamation symbol...
>
>Hmm, Does the error code show up anything on Google?

Whoops, I didn't notice there was a response to my post.

I did do a search but that is a pretty generic error Windows gives
when the driver decides something is wrong. No way of knowing
precisely what unless the driver spews some information somewhere
(which I think is unlikely).

However come to think of it, I did encounter that message twice
before. Once when I tested with PCI passthrough in ESXi and the other
time when the stock xen corrupted my card's firmware (I think, had to
reflash the backup firmware with nvflash for the card to work again).

So I guess in this case it may be due to the card being in an unknown
state when the driver is loaded? What if I made a change in xen to
execute card firmware even if gfx_passthrough = 0, without all the
modifications required for VGA passthrough? Though I suspect the
firmware expects some of the special VGA address mapping?

             reply	other threads:[~2011-05-17 23:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 23:14 Liwei [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-05-31 14:59 VGA passthrough on unstable Liwei
2011-05-24 15:35 Liwei
2011-05-24 15:44 ` Liwei
2011-05-03  6:29 Liwei
2011-05-03 15:20 ` Liwei
2011-05-05 11:33 ` Liwei
2011-05-05 15:20   ` Pasi Kärkkäinen
2011-05-05 16:56     ` Liwei
2011-05-05 17:06       ` Pasi Kärkkäinen
2011-05-05 17:59         ` Liwei
2011-05-05 18:12           ` Pasi Kärkkäinen
2011-05-05 18:28             ` Liwei
2011-05-05 18:33               ` Pasi Kärkkäinen
2011-05-05 18:42                 ` Liwei
2011-05-05 18:49                   ` Pasi Kärkkäinen
2011-05-09  0:26                     ` Liwei
2011-05-09 17:14     ` Javier
2011-05-10 13:12       ` JavMV
2011-05-10 13:12       ` JavMV
2011-05-10 13:12       ` JavMV

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='BANLkTikuf0w-gck7hvhN2eeimsLOG=g-=A@mail.gmail.com' \
    --to=xieliwei@gmail.com \
    --cc=konrad.wilk@oracle.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 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).