Hi
Weidong,
Thank you for all your hard work
;)
I have just successfully passed
through my Nvidia Geforce GTX260 as a fully functional card to my WinXP DomU
!!!!!
My findings so
far:
1) Tried with my 9500 GT
(Secondary card) which DOES load the driver successfully but NO output on the
Monitor (VGA is sized correctly but monitor is OFF)
2) GTX260 (Primary card) (Dom0
boot VGA) starting DomU from remote SSH console, VGA Loads and Display works
!!!!
In both cases I am using the
NVidia binary driver in the WinXP DomU.
The 9500GT (Secondary card)
passthrough still has issues, the driver loads without the Monitor displaying
anything (DPMS?) and if I make ANY changes to the DomU Graphics then the DomU
locks up hard.
[Weidong]: I
didn't try 9500GT. Seems it needs extra
hacks.
In both cases the VGA card only
works the FIRST time, I.e. FLR is required to reset the card for re-use, display
become corrupt on second boot of DomU. Restart Dom0 and the VGA will work again
the first time DomU is started.
[Weidong]: Yes, it's
not reset well. I suspect it's still in graphics mode, so cannot display the
boot messages in VGA mode. In my experiments, WinXP guest can still
boot into graphics mode, although you cannot see booting
progress.
Is there anyway we can
impletement the d3r, sbr or flr functionality that is in XCI? I would like to
see if a sbr will enable to Card to be reset.
[Weidong]: these
reset functions are already in xen-unstable, but no one can really
reset gfx. In my feeling, it needs vendor specific method to reset
it.
I would also like to debug the
issue with Secondary passthrough as it seems that this is nearly there too
...
Regards,
Tim
From:
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Teo En Ming
(Zhang Enming)
Sent: 03 September 2009 05:12
To:
djmagee@xxxxxxxxxxxx; 'Han, Weidong';
xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] RE:
xen-unstable pci passthrough
Dear
Magee,
Any luck
with the Intel vga passthrough patches to xen 3.5-unstable on Intel DQ45CB with
extra PCI-e x16 graphics card? Are you using pvops dom 0 kernels 2.6.30-rc3 and
2.6.31-rc6?
Regards,
Mr. Teo En Ming (Zhang
Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)
Technical Support
Engineer
Information Technology
Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines
Plaza
Singapore 529541
Republic of
Singapore
Mobile:
+65-9648-9798
MSN:
teoenming@xxxxxxxxxxx
From:
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
djmagee@xxxxxxxxxxxx
Sent: Wednesday, September 02, 2009 6:59
PM
To: Han, Weidong; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject:
RE: [Xen-devel] RE: xen-unstable pci passthrough
That was the problem,
thank you. Now I’ll work on testing the gfx-passthrough
patches.
From:
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Han,
Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To:
djmagee@xxxxxxxxxxxx; 'xen-devel@xxxxxxxxxxxxxxxxxxx'
Subject:
[Xen-devel] RE: xen-unstable pci passthrough
I suspect you are
using old hvm config file. The device_model is changes in config
file.
in old config
file:
# New
stuff
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
in new config
file:
# Device Model to be
used
device_model = 'qemu-dm'
Pls check it, and use
the latest config file to create guest.
Regards,
Weidong
From:
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
djmagee@xxxxxxxxxxxx
Sent: 2009年9月2日 6:40
To:
xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xen-unstable pci
passthrough
I have not been able to passthrough any PCI
devices using the latest xen-unstable. I have a DQ45CB, and have
successfully passed devices to guests using 3.4.1.
The latest c/s in my copy of xen-unstable is
20145. I just started playing around with unstable yesterday, so I can’t
tell you if earlier revisions worked. I’ve tried with various dom0
kernels, the current 2.6.18.8-xen branch, a xenified 2.6.29.6, and a pvops
2.6.31-rc6, and in every case I get the same error. I’ve tried both
putting pci= in the config file, and hot-adding the device using xm
pci-attach. In every case, the xm command (either create or pci-attach)
fails with the message “Error: Timed out waiting for device model action”.
The guests in every case are HVM guests, some flavors of Windows, as well as the
Knoppix 5.3.1 DVD.
The relevant xm dmesg output is:
(XEN)
PCI add device 00:1b.0
(XEN) [VT-D]iommu.c:1292:d0
domain_context_unmap:PCIe: bdf = 0:1b.0
(XEN) [VT-D]iommu.c:1178:d0
domain_context_mapping:PCIe: bdf = 0:1b.0
(XEN) [VT-D]io.c:284:d0 VT-d irq bind: m_irq
= 37 device = 3 intx = 0
(XEN) [VT-D]iommu.c:1292:d0
domain_context_unmap:PCIe: bdf = 0:1b.0
(XEN) [VT-D]iommu.c:1178:d0
domain_context_mapping:PCIe: bdf = 0:1b.0
And the messages from
qemu-log:
dm-command: hot insert pass-through pci
dev
hot add pci slot -2
exceed.
Please let me know what else I need to
supply to help resolve this problem. If I need to enable debugging
messages, let me know the best way to do this.
Doug Magee
djmagee@xxxxxxxxxxxx
No virus
found in this incoming message.
Checked by AVG - www.avg.com
Version:
8.5.409 / Virus Database: 270.13.75/2340 - Release Date: 09/01/09
20:03:00
