All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gordon Messmer <yinyang@eburg.com>
To: unlisted-recipients:; (no To-header on input)
Cc: kvm@vger.kernel.org
Subject: Re: Device pass-through
Date: Sat, 07 Jan 2012 14:21:33 -0800	[thread overview]
Message-ID: <4F08C56D.2040008@eburg.com> (raw)
In-Reply-To: <4F07A8E4.4020700@eburg.com>

On 01/06/2012 06:07 PM, Gordon Messmer wrote:
>
> /usr/libexec/qemu-kvm\
> -vnc 127.0.0.1:0 -vga cirrus \
> -device
> pci-assign,host=05:00.0,id=hostdev1,configfd=27,bus=pci.0,addr=0x7,romfile=/var/lib/libvirt/images/Radeon3470.rom

Snipped a bunch of other args...  I'm certain that qemu-kvm loads both 
/usr/share/qemu-kvm/vgabios-cirrus.bin and 
/var/lib/libvirt/images/Radeon3470.rom, which seems correct.  However, 
in the guest, both the virtual VGA card and the real PCI one have the 
same ROM, from vgabios-cirrus.bin.

I've looked through the qemu-kvm source and don't see anything that 
would obviously cause that sort of problem.  Should I be looking into 
seabios?

00:02.0 0300: 1013:00b8 (prog-if 00 [VGA controller])
	Subsystem: 1af4:1100
	Physical Slot: 2
	Flags: fast devsel
	Memory at f0000000 (32-bit, prefetchable) [size=32M]
	Memory at f2000000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at f2010000 [disabled] [size=64K]
	Kernel modules: cirrusfb

00:07.0 0300: 1002:95c0 (prog-if 00 [VGA controller])
	Subsystem: 1028:3243
	Physical Slot: 7
	Flags: fast devsel, IRQ 11
	Memory at e0000000 (32-bit, prefetchable) [size=256M]
	Memory at f2050000 (32-bit, non-prefetchable) [size=64K]
	I/O ports at c100 [size=256]
	Expansion ROM at f2060000 [disabled] [size=64K]
	Capabilities: [58] Express Legacy Endpoint, MSI 00
	Capabilities: [50] Power Management version 3
	Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit-
	Kernel modules: radeon


# strings /sys/bus/pci/devices/0000\:00\:02.0/rom | head -2
Plex86/Bochs VGABios (PCI)
current-cvs 19 Jul 2011
# strings /sys/bus/pci/devices/0000\:00\:07.0/rom | head -2
Plex86/Bochs VGABios (PCI)
current-cvs 19 Jul 2011

  reply	other threads:[~2012-01-07 22:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-02 19:41 Device pass-through Gordon Messmer
2012-01-03 21:34 ` Alex Williamson
2012-01-04  0:29   ` Gordon Messmer
2012-01-04  3:44     ` Alex Williamson
2012-01-05 19:07       ` Gordon Messmer
2012-01-06  7:25         ` Gordon Messmer
2012-01-06  9:31           ` André Weidemann
2012-01-07  2:07             ` Gordon Messmer
2012-01-07 22:21               ` Gordon Messmer [this message]
2012-01-09  6:22                 ` Gordon Messmer
2012-01-16  6:52                   ` Gordon Messmer

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=4F08C56D.2040008@eburg.com \
    --to=yinyang@eburg.com \
    --cc=kvm@vger.kernel.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.