xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: John Wargo <wargo.john25@gmail.com>
Cc: Gordan Bobic <gordan@bobich.net>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Windows 8 VGA Passthrough
Date: Mon, 28 Oct 2013 13:07:03 -0400	[thread overview]
Message-ID: <20131028170703.GI4353@phenom.dumpdata.com> (raw)
In-Reply-To: <526D4B8A.3000307@gmail.com>

On Sun, Oct 27, 2013 at 12:21:14PM -0500, John Wargo wrote:
> I've made quite a bit of changes since my last email, and so far
> here's what I've got:
> 
> AMD FX6300
> ASUS M5A99X evo r2.0
> ASUS Radeon 6670 (Dom0)
> XFX Radeon 7850 (Win8)
> 
> Right now I've got AMD Catalyst (latest stable) installed in windows
> 8, and device manager shows my Radeon 7850 reporting no issues.
> 
> I'm currently passing it through as secondary (gfx_passthrough=0),
> however I cannot plug my monitor into it.
> 
> After taking debugging steps, I've come up with the attached debugging info:
> info - xl info
> dmesg - xl dmesg
> grub - a copy of '/etc/default/grub'
> win8.cfg - the configuration I'm using to launch windows 8
> 
> Fedora bug reporting tool caught a kernel bug at
> 'drivers/gpu/drm/ttm/ttm_bo.c:210', I have compiled xen from source,
> and I'm using it as a kernel (or really part of it).

OK, what was the rest of it? And what version of the kernel?

You also seem to have a debug.zip attached - but it has nothing it it?
> 
> Is there some sort of AMD Radeon patch I need to use (I saw one on
> the wiki, but it appeared to be several years old), or is it a
> needed configuration?
> 
> Thanks for your time,
> -John


> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2013-10-28 17:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-26 20:58 Windows 8 VGA Passthrough John Wargo
2013-10-27  9:30 ` Gordan Bobic
2013-10-27 14:27   ` John Wargo
2013-10-27 16:21     ` John Wargo
2013-10-27 17:21       ` John Wargo
2013-10-28 17:07         ` Konrad Rzeszutek Wilk [this message]
2013-10-28 21:32           ` John Wargo
2013-10-29 13:09             ` Zytaruk, Kelly
2013-10-28 19:30         ` Zytaruk, Kelly
2013-10-28 20:31           ` John Wargo
2013-10-28 20:46             ` Gordan Bobic
2013-10-28 21:29               ` John Wargo
2013-10-27 19:35       ` Gordan Bobic
2013-10-27 19:45         ` John Wargo
2013-10-27 20:05         ` John Wargo
2013-10-27 21:01         ` John Wargo
2013-10-27 22:51           ` Gordan Bobic
2013-10-28 11:06             ` John Wargo
2013-10-27 19:31     ` Gordan Bobic
     [not found]   ` <526D1FBA.10708@gmail.com>
2013-10-27 19:28     ` Gordan Bobic

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=20131028170703.GI4353@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=gordan@bobich.net \
    --cc=wargo.john25@gmail.com \
    --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 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).