From: "Teo En Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com>
To: "xen-users@lists.xen.org" <xen-users@lists.xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"Teo En Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com>,
Dariusz Krempa <imperiaonline4@gmail.com>,
Casey DeLorme <cdelorme@gmail.com>,
Tobias Geiger <tobias.geiger@vido.info>
Subject: Is Xen VGA Passthrough to CentOS 6.3 x86-64 HVM domU successful?
Date: Sat, 27 Oct 2012 22:59:59 +0800 [thread overview]
Message-ID: <508BF6EF.2050908@gmail.com> (raw)
Hi,
I have just passed through my NVIDIA Geforce GTX 560 to CentOS 6.3
x86-64 HVM domU. I am wondering whether the Xen VGA Passthrough is
successful.
The following information is obtained from inside CentOS 6.3 x86-64 HVM
domU:
00:05.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX
560] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Giga-byte Technology Device 3527
Physical Slot: 5
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64
Interrupt: pin A routed to IRQ 36
Region 0: Memory at dc000000 (32-bit, non-prefetchable) [size=32M]
Region 1: Memory at d0000000 (64-bit, prefetchable) [size=128M]
Region 3: Memory at d8000000 (64-bit, prefetchable) [size=64M]
Region 5: I/O ports at e000 [size=128]
[virtual] Expansion ROM at f1080000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [78] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us,
L1 <64us
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr-
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1,
Latency L0 <256ns, L1 <4us
ClockPM+ Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
Capabilities: [b4] Vendor Specific Information <?>
Kernel driver in use: nouveau
Kernel modules: nvidia, nouveau, nvidiafb
[root@centos63 ~]# lsmod | grep nouveau
nouveau 791165 2
ttm 82562 1 nouveau
drm_kms_helper 34122 1 nouveau
drm 250067 4 nouveau,ttm,drm_kms_helper
i2c_core 31276 14
tuner_simple,tda9887,tda8290,wm8775,tuner,cx25840,pvrusb2,v4l2_common,videodev,tveeprom,i2c_piix4,nouveau,drm_kms_helper,drm
mxm_wmi 1925 1 nouveau
video 21032 1 nouveau
wmi 6287 2 nouveau,mxm_wmi
Notice that the nouveau VGA driver is loaded and is in use. Is Xen VGA
Passthrough 100% successful? I have successfully installed the NVIDIA
driver but I couldn't get it to load, so I reverted back to the nouveau
driver.
I have such tough time getting Xen VGA Passthrough to work successfully
on Windows HVM domU that I am giving up on Xen VGA Passthrough to
Windows HVM domU!!! Windows 7 and Windows 8 HVM domU device manager
always report error code 43 with a yellow triangle. Windows XP HVM domU
device manager always report error code 10 with a yellow circle.
--
Yours sincerely,
Mr. Teo En Ming (Zhang Enming)
Singapore
next reply other threads:[~2012-10-27 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-27 14:59 Teo En Ming (Zhang Enming) [this message]
2012-10-27 15:35 ` Is Xen VGA Passthrough to CentOS 6.3 x86-64 HVM domU successful? Teo En Ming (Zhang Enming)
2012-10-27 15:40 ` Teo En Ming (Zhang Enming)
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=508BF6EF.2050908@gmail.com \
--to=singapore.mr.teo.en.ming@gmail.com \
--cc=cdelorme@gmail.com \
--cc=imperiaonline4@gmail.com \
--cc=tobias.geiger@vido.info \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@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.