I had a
little bit of time to
work on this the other night. As the revised passthrough patch had
already been applied to xen-unstable, I only had to apply the qemu
branch.
When I
tried to passthrough my
video device with gfx_passthru=2, the guest BIOS never seemed to
execute.
Xm dmesg, went as far as “Loading ROMBIOS”, but no further. When
guests
successfully start, I can see the bios messages in xm dmesg, and that
was not
the case. I tried leaving the vnc enabled to see if there was any
output,
and all I had was some qemu monitor and it was not clear what I was
supposed to
do there. I was attempting to passthrough my addon card, which is the
only graphics device enabled in my system.
I then
tried to passthrough the
graphics device without the gfx_passthru option just to make sure the
guest
would boot properly. I was immediately hit with a dom0 kernel BUG and
at
that point I had no more time to experiment.
This test
was while I was
running a xenified 2.6.29.6 kernel, which has been perfectly stable for
me in
all my other uses. I want to try with a 2.6.18.8-xen kernel as
well. Hopefully I’ll get a chance this afternoon. I built and
tested a 2.6.31-rc6 dom0 kernel the other day but it was difficult to
use as
there was really high latency over my ssh connection for some reason
and the
machine was generally unresponsive.
When I
have time to fully test
all of these combinations I will report back with the results.
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
That was
the problem, thank
you. Now I’ll work on testing the gfx-passthrough patches.
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
