qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	qemu-devel@nongnu.org,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [Xen-devel] RESEND [Xen-unstable][Qemu-xen] HVM Guest reading of Expansion ROM from passthroughed PCI device returns data from emulated VGA rom
Date: Sun, 22 Sep 2013 19:21:40 +0300	[thread overview]
Message-ID: <20130922162140.GC2924@reaktio.net> (raw)
In-Reply-To: <119503463.20130922170058@eikelenboom.it>

On Sun, Sep 22, 2013 at 05:00:58PM +0200, Sander Eikelenboom wrote:
> 
> >> I'm trying to get secondary vga-passthrough on a HVM guest to work with a AMD HD6570 and the native kernel radeon driver and kernel modesetting.
> >> So the guest still gets the emulated stdvga or cirrus device(used in my case here) as primary/boot vga adapter.
> >> 
> >> - When i don't passthrough the radeon card, the linux native radeon driver loads fine.
> >> - When i do passtrough the device to a HVM with the same kernel:
> >>   The driver in the guest tries to read the pci expansion rom from the passthroughed device to get the vbios.
> >>   The driver reports a successful read, but fails because it can't find the right string at the right offset.
> >> 
> 
> > Did you try with qemu-dm-traditional aswell? Does it have the same problem? 
> 
> Hi Pasi,
> 
> Yes i did and yes the same problem.
> From what i recall i used to have succes with vga passthrough with a secondary vga card, but that was some time ago.
> I don't know which of the components (xen, dom0 kernel, domU kernel, radeon driver, qemu has changed in such a way that it fails to work now ...
> 
> 
> But in the mean time i tried to debug it further and from what i can see:
> - Only the io port en mem of the pci device are mapped through the hypervisor.
> - The rom is not, (a hypercall to do the memory mapping is never made) i tried several things to get it to do the mapping, but so far failt to do so.
> - It seems to be a 64bit capable device, some code comments and git commit messages seem to suggest that there were/are some problems with that (in the way the involved components interact)
> 

Yeah, there has been some patches related to that, and I think still some open bugs..

Btw did you try with Xen 4.3? Or 4.2? 

-- Pasi

  reply	other threads:[~2013-09-22 16:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 14:33 [Qemu-devel] RESEND [Xen-unstable][Qemu-xen] HVM Guest reading of Expansion ROM from passthroughed PCI device returns data from emulated VGA rom Sander Eikelenboom
2013-09-22 13:02 ` [Qemu-devel] [Xen-devel] " Pasi Kärkkäinen
2013-09-22 15:00   ` Sander Eikelenboom
2013-09-22 16:21     ` Pasi Kärkkäinen [this message]
2013-09-23  3:03     ` Wu, Feng
2013-09-24 21:24       ` Sander Eikelenboom
2013-10-01 16:15         ` Pasi Kärkkäinen
2013-12-02 19:41 ` Konrad Rzeszutek Wilk
2013-12-02 19:55   ` Sander Eikelenboom
2013-12-02 20:39     ` Konrad Rzeszutek Wilk
2013-12-02 20:59       ` 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=20130922162140.GC2924@reaktio.net \
    --to=pasik@iki.fi \
    --cc=anthony.perard@citrix.com \
    --cc=linux@eikelenboom.it \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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).