From: Richie <listmail@triad.rr.com>
To: Sander Eikelenboom <linux@eikelenboom.it>,
Peter Kay <syllopsium@syllopsium.co.uk>
Cc: xen-devel@lists.xen.org
Subject: Re: Code 12 with VGA passthrough, even with qemu-traditional
Date: Thu, 21 Aug 2014 18:42:13 -0400 [thread overview]
Message-ID: <53F675C5.5000601@triad.rr.com> (raw)
In-Reply-To: <1812080862.20140822000146@eikelenboom.it>
On 8/21/2014 6:01 PM, Sander Eikelenboom wrote:
> I have a system (amd based) with radeon HD6950 that is able to be
> passed through to a linux HVM guest (although you only get output
> after the kernel loads the radeon KMS/DRM driver since it's secondary
> passthrough). This is _not_ the primary graphics card from the host
> (got another radeon for dom0).
Just chiming in here with a side note.
I decided to test out KVM + vfio on 3.16 with acs + intel igd patches
and passed through my secondary card. It was successful and I had the
Seabios screen show up on my secondary VGA card (GTX 660ti). It
maintained video throughout the boot process including the Windows 7
installer. The only catch really was that since the host was on qemu
2.0.0 and did not have the -cpu kvm=off switch (to hide kvm) I had to
use Nvidia driver 335.x (or earlier). Basic 3D tests have proved
sucessfull and pt continues to work after subsequent guest reboots.
Now to be clear, I am partial to Xen. My thinking is that at some
point (or perhaps even now) that using the qemu upstream device model
with Xen will yield this type of capability. I am not so familiar with
vfio or even pt with KVM. There just happened to be the right guide out
there on the net that could fill in the blanks.
next prev parent reply other threads:[~2014-08-21 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 9:14 Code 12 with VGA passthrough, even with qemu-traditional Peter Kay
2014-08-21 22:01 ` Sander Eikelenboom
2014-08-21 22:42 ` Richie [this message]
2014-08-22 11:25 ` Peter Kay
2014-08-25 13:26 ` Konrad Rzeszutek Wilk
2014-08-25 13:49 ` Peter Kay
2014-08-22 7:23 ` Peter Kay
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=53F675C5.5000601@triad.rr.com \
--to=listmail@triad.rr.com \
--cc=linux@eikelenboom.it \
--cc=syllopsium@syllopsium.co.uk \
--cc=xen-devel@lists.xen.org \
/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.