From: Alex Williamson <alex.williamson@redhat.com>
To: Bhushan Bharat-R65777 <R65777@freescale.com>
Cc: "avi@redhat.com" <avi@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Isuue assiging devices using VFIO on x86
Date: Wed, 29 Aug 2012 12:08:57 -0700 [thread overview]
Message-ID: <1346267337.2225.26.camel@ul30vt.home> (raw)
In-Reply-To: <6A3DF150A5B70D4F9B66A25E3F7C888D0644EB31@039-SN2MPN1-022.039d.mgd.msft.net>
On Wed, 2012-08-29 at 18:42 +0000, Bhushan Bharat-R65777 wrote:
> PFA file which have full dmeg and lspci of assigned device
> On Aug 29, 2012 11:03 AM, "Bhushan Bharat-R65777" <R65777@freescale.com<mailto:R65777@freescale.com>> wrote:
> > Guest>lspci
> > 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
> > 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
> > 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
> > 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
> > 00:02.0 VGA compatible controller: Cirrus Logic GD 5446
> > 00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 03) ----- QEMU emulated
> > 00:04.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network Connection (rev 02) ----- directly assigned
>From attachment:
00:04.0 Ethernet controller: SysKonnect SK-9E21D 10/100/1000Base-T Adapter, Copper RJ-45 (rev 17)
Subsystem: SysKonnect SK-9E21D 10/100/1000Base-T Adapter
Physical Slot: 4
Flags: fast devsel, IRQ 11
Memory at febf0000 (64-bit, non-prefetchable) [size=16K]
I/O ports at c000 [size=256]
Expansion ROM at febc0000 [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [5c] MSI: Enable- Count=1/2 Maskable- 64bit+
Capabilities: [e0] Express Legacy Endpoint, MSI 00
This isn't the 82567LM device reported previously, are we now switching
to this device being assigned? I don't know what driver this device is
supposed to use nor do I see any attempt to load a driver for this
device in the guest dmesg. Are you sure the driver is loaded? Thanks,
Alex
prev parent reply other threads:[~2012-08-29 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 9:23 [Qemu-devel] Isuue assiging devices using VFIO on x86 Bhushan Bharat-R65777
2012-08-28 15:57 ` Alex Williamson
2012-08-28 17:10 ` Bhushan Bharat-R65777
2012-08-29 6:46 ` Alex Williamson
2012-08-29 7:11 ` Bhushan Bharat-R65777
2012-08-29 15:13 ` Alex Williamson
2012-08-29 18:02 ` Bhushan Bharat-R65777
2012-08-29 18:22 ` Alex Williamson
2012-08-29 18:42 ` Bhushan Bharat-R65777
2012-08-29 19:08 ` Alex Williamson [this message]
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=1346267337.2225.26.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=R65777@freescale.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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).