* xen-unstable pci passthrough
@ 2009-09-01 22:40 djmagee
2009-09-01 22:55 ` Han, Weidong
0 siblings, 1 reply; 39+ messages in thread
From: djmagee @ 2009-09-01 22:40 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1593 bytes --]
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@mageenet.net
[-- Attachment #1.2: Type: text/html, Size: 6546 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: xen-unstable pci passthrough
2009-09-01 22:40 xen-unstable pci passthrough djmagee
@ 2009-09-01 22:55 ` Han, Weidong
2009-09-02 0:30 ` Mr. Teo En Ming (Zhang Enming)
2009-09-02 10:58 ` djmagee
0 siblings, 2 replies; 39+ messages in thread
From: Han, Weidong @ 2009-09-01 22:55 UTC (permalink / raw)
To: 'djmagee@mageenet.net', 'xen-devel@lists.xensource.com'
[-- Attachment #1.1: Type: text/plain, Size: 2190 bytes --]
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net<mailto:djmagee@mageenet.net>
[-- Attachment #1.2: Type: text/html, Size: 9105 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: RE: xen-unstable pci passthrough
2009-09-01 22:55 ` Han, Weidong
@ 2009-09-02 0:30 ` Mr. Teo En Ming (Zhang Enming)
2009-09-02 3:31 ` Teo En Ming (Zhang Enming)
2009-09-02 10:58 ` djmagee
1 sibling, 1 reply; 39+ messages in thread
From: Mr. Teo En Ming (Zhang Enming) @ 2009-09-02 0:30 UTC (permalink / raw)
To: weidong.han
Cc: 'xen-devel@lists.xensource.com', 'djmagee@mageenet.net'
[-- Attachment #1.1: Type: text/plain, Size: 4113 bytes --]
Hi,
I changed to using device_model = 'qemu-dm' but it still doesn't work.
Here is my Win XP Home HVM Dom U configuration:
import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir = 'lib64'
else:
arch_libdir = 'lib'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 2048
# Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
shadow_memory = 8
name = "winxphome32"
vif = [ 'bridge=eth0' ]
acpi = 1
apic = 1
disk = [ 'phy:/dev/virtualmachines/winxphome32,hda,w',
'phy:/dev/sr0,hdc:cdrom,r' ]
#device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
#device_model = '/usr/' + 'lib' + '/xen/bin/qemu-dm'
device_model = 'qemu-dm'
#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot="cd"
sdl=0
vnc=1
vncconsole=1
vncpasswd=''
serial='pty'
usbdevice='tablet'
pci = [ '01:00.0' ]
vcpus=1
gfx_passthru=2
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/02/2009 06:55 AM, Han, Weidong wrote:
> 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@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net
> *Sent:* 2009年9月2日 6:40
> *To:* xen-devel@lists.xensource.com
> *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@mageenet.net <mailto:djmagee@mageenet.net>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
[-- Attachment #1.2: Type: text/html, Size: 9081 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-02 0:30 ` Mr. Teo En Ming (Zhang Enming)
@ 2009-09-02 3:31 ` Teo En Ming (Zhang Enming)
0 siblings, 0 replies; 39+ messages in thread
From: Teo En Ming (Zhang Enming) @ 2009-09-02 3:31 UTC (permalink / raw)
To: enming.teo, weidong.han; +Cc: xen-devel, djmagee
If I use device_model = 'qemu-dm', I need to use vcpus=1. Using vcpus=2 will
cause Win XP Home domU to crash. The situation is reversed.
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@hotmail.com
-----Original Message-----
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of Mr. Teo En Ming (Zhang Enming)
Sent: Wednesday, September 02, 2009 8:31 AM
To: weidong.han@intel.com
Cc: 'xen-devel@lists.xensource.com'; 'djmagee@mageenet.net'
Subject: Re: [Xen-devel] RE: xen-unstable pci passthrough
Hi,
I changed to using device_model = 'qemu-dm' but it still doesn't work.
Here is my Win XP Home HVM Dom U configuration:
import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir = 'lib64'
else:
arch_libdir = 'lib'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 2048
# Should be at least 2KB per MB of domain memory, plus a few MB per
vcpu.
shadow_memory = 8
name = "winxphome32"
vif = [ 'bridge=eth0' ]
acpi = 1
apic = 1
disk = [ 'phy:/dev/virtualmachines/winxphome32,hda,w',
'phy:/dev/sr0,hdc:cdrom,r' ]
#device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
#device_model = '/usr/' + 'lib' + '/xen/bin/qemu-dm'
device_model = 'qemu-dm'
#-----------------------------------------------------------------------
------
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot="cd"
sdl=0
vnc=1
vncconsole=1
vncpasswd=''
serial='pty'
usbdevice='tablet'
pci = [ '01:00.0' ]
vcpus=1
gfx_passthru=2
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/02/2009 06:55 AM, Han, Weidong wrote:
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@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of
djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net
________________________________
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.73/2338 - Release Date: 08/31/09
17:52:00
No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.73/2338 - Release Date: 08/31/09
17:52:00
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-01 22:55 ` Han, Weidong
2009-09-02 0:30 ` Mr. Teo En Ming (Zhang Enming)
@ 2009-09-02 10:58 ` djmagee
2009-09-03 4:12 ` Teo En Ming (Zhang Enming)
1 sibling, 1 reply; 39+ messages in thread
From: djmagee @ 2009-09-02 10:58 UTC (permalink / raw)
To: Han, Weidong, xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 2586 bytes --]
That was the problem, thank you. Now I’ll work on testing the gfx-passthrough patches.
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net
[-- Attachment #1.2: Type: text/html, Size: 11728 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-02 10:58 ` djmagee
@ 2009-09-03 4:12 ` Teo En Ming (Zhang Enming)
2009-09-03 9:03 ` Tim Moore
2009-09-03 15:07 ` djmagee
0 siblings, 2 replies; 39+ messages in thread
From: Teo En Ming (Zhang Enming) @ 2009-09-03 4:12 UTC (permalink / raw)
To: djmagee, 'Han, Weidong', xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 3517 bytes --]
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@hotmail.com
_____
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net
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
[-- Attachment #1.2: Type: text/html, Size: 19641 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-03 4:12 ` Teo En Ming (Zhang Enming)
@ 2009-09-03 9:03 ` Tim Moore
2009-09-03 9:14 ` Teo En Ming (Zhang Enming)
2009-09-03 9:42 ` Han, Weidong
2009-09-03 15:07 ` djmagee
1 sibling, 2 replies; 39+ messages in thread
From: Tim Moore @ 2009-09-03 9:03 UTC (permalink / raw)
To: 'Han, Weidong'
Cc: xen-devel, djmagee, 'enming.teo@asiasoftsea.net'
[-- Attachment #1.1: Type: text/plain, Size: 5163 bytes --]
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.
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.
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.
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
________________________________
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net<mailto:djmagee@mageenet.net>
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
[-- Attachment #1.2: Type: text/html, Size: 19953 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-03 9:03 ` Tim Moore
@ 2009-09-03 9:14 ` Teo En Ming (Zhang Enming)
2009-09-03 9:18 ` Teo En Ming (Zhang Enming)
2009-09-03 14:18 ` Tim Moore
2009-09-03 9:42 ` Han, Weidong
1 sibling, 2 replies; 39+ messages in thread
From: Teo En Ming (Zhang Enming) @ 2009-09-03 9:14 UTC (permalink / raw)
To: timothy.moore, 'Han, Weidong'; +Cc: xen-devel, djmagee
[-- Attachment #1.1: Type: text/plain, Size: 6488 bytes --]
Hi Tim,
Are you using xen 3.5-unstable? Which changeset are you using?
What Intel gfx passthrough patches are you using?
1. xen-gfx-passthrough.patch
2. qemu-gfx-passthrough.patch
3. xen-load-vbios-file.patch
4. xen-vbar-pbar.patch
5. qemu-vbar-pbar.patch
6. secondary-gfx-passthrough.patch
How do you apply the patches and compile xen and tools?
What pvops dom 0 kernel are you using?
When I do a “xm list”, I see win xp domU running. But I am always shown a
QEMU monitor and couldn’t proceed any further on the matter.
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@hotmail.com
_____
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: Thursday, September 03, 2009 5:03 PM
To: 'Han, Weidong'
Cc: 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net;
xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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.
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.
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.
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
_____
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net
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
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
[-- Attachment #1.2: Type: text/html, Size: 35973 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-03 9:14 ` Teo En Ming (Zhang Enming)
@ 2009-09-03 9:18 ` Teo En Ming (Zhang Enming)
2009-09-03 14:18 ` Tim Moore
1 sibling, 0 replies; 39+ messages in thread
From: Teo En Ming (Zhang Enming) @ 2009-09-03 9:18 UTC (permalink / raw)
To: enming.teo, timothy.moore, 'Han, Weidong'; +Cc: xen-devel, djmagee
[-- Attachment #1.1: Type: text/plain, Size: 7639 bytes --]
Perhaps I need to get a dual PCI-e x16 VT-d capable motherboard instead of a
motherboard with only 1 PCI-e x16 and onboard graphics?
Magee was telling me vga passthrough won’t work on Intel DQ45CB when you
boot dom 0 on onboard Intel gma4500 graphics and want to passthrough pci-e
x16 graphics to win xp domU.
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@hotmail.com
_____
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: Thursday, September 03, 2009 5:15 PM
To: timothy.moore@expidas.net; 'Han, Weidong'
Cc: xen-devel@lists.xensource.com; djmagee@mageenet.net
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
Hi Tim,
Are you using xen 3.5-unstable? Which changeset are you using?
What Intel gfx passthrough patches are you using?
1. xen-gfx-passthrough.patch
2. qemu-gfx-passthrough.patch
3. xen-load-vbios-file.patch
4. xen-vbar-pbar.patch
5. qemu-vbar-pbar.patch
6. secondary-gfx-passthrough.patch
How do you apply the patches and compile xen and tools?
What pvops dom 0 kernel are you using?
When I do a “xm list”, I see win xp domU running. But I am always shown a
QEMU monitor and couldn’t proceed any further on the matter.
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@hotmail.com
_____
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: Thursday, September 03, 2009 5:03 PM
To: 'Han, Weidong'
Cc: 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net;
xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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.
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.
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.
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
_____
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net
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
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
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
[-- Attachment #1.2: Type: text/html, Size: 41070 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-03 9:03 ` Tim Moore
2009-09-03 9:14 ` Teo En Ming (Zhang Enming)
@ 2009-09-03 9:42 ` Han, Weidong
2009-09-03 9:50 ` Teo En Ming (Zhang Enming)
` (2 more replies)
1 sibling, 3 replies; 39+ messages in thread
From: Han, Weidong @ 2009-09-03 9:42 UTC (permalink / raw)
To: 'Tim Moore'
Cc: 'xen-devel@lists.xensource.com',
'djmagee@mageenet.net',
'enming.teo@asiasoftsea.net'
[-- Attachment #1.1: Type: text/plain, Size: 5879 bytes --]
Tim,
See my comments belew.
________________________________
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: 2009年9月3日 17:03
To: Han, Weidong
Cc: 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net; xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
________________________________
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net<mailto:djmagee@mageenet.net>
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
[-- Attachment #1.2: Type: text/html, Size: 22770 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-03 9:42 ` Han, Weidong
@ 2009-09-03 9:50 ` Teo En Ming (Zhang Enming)
2009-09-03 13:40 ` Tim Moore
2009-09-03 19:07 ` Tim Moore
2009-09-10 10:20 ` Tim Moore
2 siblings, 1 reply; 39+ messages in thread
From: Teo En Ming (Zhang Enming) @ 2009-09-03 9:50 UTC (permalink / raw)
To: weidong.han, 'Tim Moore'; +Cc: xen-devel, djmagee
[-- Attachment #1.1: Type: text/plain, Size: 6662 bytes --]
Hi Weidong,
Do you have any ideas why gfx passthrough couldn’t work in my case?
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@hotmail.com
_____
From: Han, Weidong [mailto:weidong.han@intel.com]
Sent: Thursday, September 03, 2009 5:43 PM
To: 'Tim Moore'
Cc: 'enming.teo@asiasoftsea.net'; 'djmagee@mageenet.net';
'xen-devel@lists.xensource.com'
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
Tim,
See my comments belew.
_____
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: 2009年9月3日 17:03
To: Han, Weidong
Cc: 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net;
xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
_____
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net
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
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
[-- Attachment #1.2: Type: text/html, Size: 34945 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-03 9:50 ` Teo En Ming (Zhang Enming)
@ 2009-09-03 13:40 ` Tim Moore
2009-09-03 14:11 ` Mr. Teo En Ming (Zhang Enming)
0 siblings, 1 reply; 39+ messages in thread
From: Tim Moore @ 2009-09-03 13:40 UTC (permalink / raw)
To: 'enming.teo@asiasoftsea.net'; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 7791 bytes --]
hi Teo,
I believe it is due to your motherboard - In a previous post to xen-devel, as user said to YOU that the chipset does not have enough PCI Lanes to use both Internal IGFX and PCIe card at the same time (simultaneously). Primary (IGFX) will need to be disabled in your BIOS for PCIe card to work, can you get them both enabled in native WinXP?
If I were you, I would try and pass through the Primary (IGFX) VGA controller to DomU with the specific changes needed to memory addresses in the v1 patches .. see if that works.
Dont think you will have much luck with your secondary PCIe card - (I couldnt get PCIe secondary working either, and my secondary does work in native WinXP)
Tim
From: Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
Sent: 03 September 2009 10:50
To: weidong.han@intel.com; Tim Moore
Cc: djmagee@mageenet.net; xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
Hi Weidong,
Do you have any ideas why gfx passthrough couldn’t work in my case?
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@hotmail.com
________________________________
From: Han, Weidong [mailto:weidong.han@intel.com]
Sent: Thursday, September 03, 2009 5:43 PM
To: 'Tim Moore'
Cc: 'enming.teo@asiasoftsea.net'; 'djmagee@mageenet.net'; 'xen-devel@lists.xensource.com'
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
Tim,
See my comments belew.
________________________________
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: 2009年9月3日 17:03
To: Han, Weidong
Cc: 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net; xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
________________________________
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net<mailto:djmagee@mageenet.net>
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
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
[-- Attachment #1.2: Type: text/html, Size: 28753 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: RE: xen-unstable pci passthrough
2009-09-03 13:40 ` Tim Moore
@ 2009-09-03 14:11 ` Mr. Teo En Ming (Zhang Enming)
[not found] ` <14D9C9E2ED61ED41BC3B37ACDF4E880002E0C4B8F667@heavy-vm03.heavy.org.uk>
0 siblings, 1 reply; 39+ messages in thread
From: Mr. Teo En Ming (Zhang Enming) @ 2009-09-03 14:11 UTC (permalink / raw)
To: timothy.moore; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 9307 bytes --]
Hi Tim,
I am aware that Magee told me that onboard GMA4500 and PCI-e x16
graphics cannot work simultaneously.
But Weidong told me in earlier postings that he could get secondary gfx
to work in the labs, so I am still holding out some hope of getting my
secondary gfx to be passed through to windows xp hvm domU.
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/03/2009 09:40 PM, Tim Moore wrote:
>
> hi Teo,
>
> I believe it is due to your motherboard - In a previous post to
> xen-devel, as user said to YOU that the chipset does not have enough
> PCI Lanes to use both Internal IGFX and PCIe card at the same time
> (simultaneously). Primary (IGFX) will need to be disabled in your BIOS
> for PCIe card to work, can you get them both enabled in native WinXP?
>
> If I were you, I would try and pass through the Primary (IGFX) VGA
> controller to DomU with the specific changes needed to memory
> addresses in the v1 patches .. see if that works.
>
> Dont think you will have much luck with your secondary PCIe card - (I
> couldnt get PCIe secondary working either, and my secondary does work
> in native WinXP)
>
> Tim
>
> *From:* Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
> *Sent:* 03 September 2009 10:50
> *To:* weidong.han@intel.com; Tim Moore
> *Cc:* djmagee@mageenet.net; xen-devel@lists.xensource.com
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> Hi Weidong,
>
> Do you have any ideas why gfx passthrough couldn’t work in my case?
>
> 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@hotmail.com
>
> ------------------------------------------------------------------------
>
> *From:* Han, Weidong [mailto:weidong.han@intel.com]
> *Sent:* Thursday, September 03, 2009 5:43 PM
> *To:* 'Tim Moore'
> *Cc:* 'enming.teo@asiasoftsea.net'; 'djmagee@mageenet.net';
> 'xen-devel@lists.xensource.com'
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> Tim,
>
> See my comments belew.
>
> ------------------------------------------------------------------------
>
> *From:* Tim Moore [mailto:timothy.moore@expidas.net]
> *Sent:* 2009年9月3日 17:03
> *To:* Han, Weidong
> *Cc:* 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net;
> xen-devel@lists.xensource.com
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> 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@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Teo En
> Ming (Zhang Enming)
> *Sent:* 03 September 2009 05:12
> *To:* djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
> *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@hotmail.com
>
> ------------------------------------------------------------------------
>
> *From:* xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net
> *Sent:* Wednesday, September 02, 2009 6:59 PM
> *To:* Han, Weidong; xen-devel@lists.xensource.com
> *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@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Han, Weidong
> *Sent:* Tuesday, September 01, 2009 6:55 PM
> *To:* djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
> *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@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net
> *Sent:* 2009年9月2日 6:40
> *To:* xen-devel@lists.xensource.com
> *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@mageenet.net <mailto:djmagee@mageenet.net>
>
> 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
>
> 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
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
[-- Attachment #1.2: Type: text/html, Size: 32870 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-03 9:14 ` Teo En Ming (Zhang Enming)
2009-09-03 9:18 ` Teo En Ming (Zhang Enming)
@ 2009-09-03 14:18 ` Tim Moore
2009-09-03 14:24 ` Mr. Teo En Ming (Zhang Enming)
1 sibling, 1 reply; 39+ messages in thread
From: Tim Moore @ 2009-09-03 14:18 UTC (permalink / raw)
To: 'enming.teo@asiasoftsea.net'; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 7757 bytes --]
Teo,
See below ...
Tim
From: Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
Sent: 03 September 2009 10:15
To: Tim Moore; 'Han, Weidong'
Cc: djmagee@mageenet.net; xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
Hi Tim,
Are you using xen 3.5-unstable? YES
Which changeset are you using? (no clue at the moment, was the one that v1 patches apply to)
What Intel gfx passthrough patches are you using? (all)
1. xen-gfx-passthrough.patch YES
2. qemu-gfx-passthrough.patch YES
3. xen-load-vbios-file.patch YES
4. xen-vbar-pbar.patch YES
5. qemu-vbar-pbar.patch YES
6. secondary-gfx-passthrough.patch YES
7. revert MMIO allocation back to 0xf0000000 (examine the patches, it's obvious)
How do you apply the patches and compile xen and tools?
1) Applied the v1 patches to relevant changeset (I've not updated my HG repo since v2 patches released)
2) Amended memory addresses as Weidong Han recommended for Secondary or Primary VGA as appropriate
3) Run "make" on the hvmloader
4) Run "make install-tools" on xen-unstable
Don't forget to reboot Dom0 after every attempt at assigning card to DomU, the card needs resetting to work each time.
What pvops dom 0 kernel are you using?
both 2.6.30-rc6 and 2.6.18-xen works for me
When I do a “xm list”, I see win xp domU running. But I am always shown a QEMU monitor and couldn’t proceed any further on the matter.
I also get QEMU Monitor in vncviewer, this is because Cirrus VGA is not loaded. You should have VGA on your passthrough card, if not you will need vncviewer in the DomU (which will only be accessible when WinXP has booted successfully)
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@hotmail.com
________________________________
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: Thursday, September 03, 2009 5:03 PM
To: 'Han, Weidong'
Cc: 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net; xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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.
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.
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.
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
________________________________
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net<mailto:djmagee@mageenet.net>
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
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
[-- Attachment #1.2: Type: text/html, Size: 33777 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: RE: xen-unstable pci passthrough
2009-09-03 14:18 ` Tim Moore
@ 2009-09-03 14:24 ` Mr. Teo En Ming (Zhang Enming)
0 siblings, 0 replies; 39+ messages in thread
From: Mr. Teo En Ming (Zhang Enming) @ 2009-09-03 14:24 UTC (permalink / raw)
To: timothy.moore; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 9034 bytes --]
Hi Tim,
Thank you for sharing your procedures.
I have a vnc server installed in my Win XP Home DomU. The fact that I
cannot vnc into my Win XP dom U shows that my domU did not boot
successfully.
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/03/2009 10:18 PM, Tim Moore wrote:
>
> Teo,
>
> See below ...
>
> Tim
>
> *From:* Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
> *Sent:* 03 September 2009 10:15
> *To:* Tim Moore; 'Han, Weidong'
> *Cc:* djmagee@mageenet.net; xen-devel@lists.xensource.com
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> Hi Tim,
>
> Are you using xen 3.5-unstable? YES
>
> Which changeset are you using? (no clue at the moment, was the one
> that v1 patches apply to)
>
> What Intel gfx passthrough patches are you using? (all)
>
> 1. xen-gfx-passthrough.patch YES
>
> 2. qemu-gfx-passthrough.patch YES
>
> 3. xen-load-vbios-file.patch YES
>
> 4. xen-vbar-pbar.patch YES
>
> 5. qemu-vbar-pbar.patch YES
>
> 6. secondary-gfx-passthrough.patch YES
>
> 7. revert MMIO allocation back to 0xf0000000 (examine the patches,
> it's obvious)
>
> How do you apply the patches and compile xen and tools?
>
> 1) Applied the v1 patches to relevant changeset (I've not updated my
> HG repo since v2 patches released)
>
> 2) Amended memory addresses as Weidong Han recommended for Secondary
> or Primary VGA as appropriate
>
> 3) Run "make" on the hvmloader
>
> 4) Run "make install-tools" on xen-unstable
>
> Don't forget to reboot Dom0 after every attempt at assigning card to
> DomU, the card needs resetting to work each time.
>
> What pvops dom 0 kernel are you using?
>
> both 2.6.30-rc6 and 2.6.18-xen works for me
>
> When I do a “xm list”, I see win xp domU running. But I am always
> shown a QEMU monitor and couldn’t proceed any further on the matter.
>
> I also get QEMU Monitor in vncviewer, this is because Cirrus VGA is
> not loaded. You should have VGA on your passthrough card, if not you
> will need vncviewer in the DomU (which will only be accessible when
> WinXP has booted successfully)
>
> 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@hotmail.com
>
> ------------------------------------------------------------------------
>
> *From:* Tim Moore [mailto:timothy.moore@expidas.net]
> *Sent:* Thursday, September 03, 2009 5:03 PM
> *To:* 'Han, Weidong'
> *Cc:* 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net;
> xen-devel@lists.xensource.com
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> 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.
>
> 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.
>
> 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.
>
> 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@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Teo En
> Ming (Zhang Enming)
> *Sent:* 03 September 2009 05:12
> *To:* djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
> *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@hotmail.com
>
> ------------------------------------------------------------------------
>
> *From:* xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net
> *Sent:* Wednesday, September 02, 2009 6:59 PM
> *To:* Han, Weidong; xen-devel@lists.xensource.com
> *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@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Han, Weidong
> *Sent:* Tuesday, September 01, 2009 6:55 PM
> *To:* djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
> *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@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net
> *Sent:* 2009年9月2日 6:40
> *To:* xen-devel@lists.xensource.com
> *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@mageenet.net <mailto:djmagee@mageenet.net>
>
> 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
>
> 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
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
[-- Attachment #1.2: Type: text/html, Size: 38728 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: RE: xen-unstable pci passthrough
[not found] ` <14D9C9E2ED61ED41BC3B37ACDF4E880002E0C4B8F667@heavy-vm03.heavy.org.uk>
@ 2009-09-03 14:28 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 15:33 ` Mr. Teo En Ming (Zhang Enming)
0 siblings, 1 reply; 39+ messages in thread
From: Mr. Teo En Ming (Zhang Enming) @ 2009-09-03 14:28 UTC (permalink / raw)
To: timothy.moore, xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 11620 bytes --]
Hi Tim,
I have downloaded linux-2.6.18.8-xen source code. I am compiling it now.
If I still cannot get nVidia Geforce 8400 GS PCI-e x16 secondary gfx to
be passed through to Win XP HVM dom U with xen 3.5-unstable with intel
gfx passthrough patches applied with xenlinux 2.6.18.8, I will give up
the attempt on the secondary gfx.
I will then focus on getting the primary gfx (either onboard or pci-e)
to be passed through.
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/03/2009 10:19 PM, Tim Moore wrote:
>
> Try and get native WinXP to boot and initialise both cards at the same
> time .. acid test .. you`ll know if you are wasting your time or not !
>
> *From:* Mr. Teo En Ming (Zhang Enming)
> [mailto:enming.teo@asiasoftsea.net]
> *Sent:* 03 September 2009 15:12
> *To:* Tim Moore
> *Cc:* xen-devel@lists.xensource.com
> *Subject:* Re: [Xen-devel] RE: xen-unstable pci passthrough
>
> Hi Tim,
>
> I am aware that Magee told me that onboard GMA4500 and PCI-e x16
> graphics cannot work simultaneously.
>
> But Weidong told me in earlier postings that he could get secondary
> gfx to work in the labs, so I am still holding out some hope of
> getting my secondary gfx to be passed through to windows xp hvm domU.
>
> --
> 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
> Company Website: http://www.asiasoft.sg/
> Mobile: +65-9648-9798
> MSN: teoenming@hotmail.com <mailto:teoenming@hotmail.com>
> Alma Maters: Singapore Polytechnic, National University of Singapore
>
>
>
> On 09/03/2009 09:40 PM, Tim Moore wrote:
>
> hi Teo,
>
> I believe it is due to your motherboard - In a previous post to
> xen-devel, as user said to YOU that the chipset does not have enough
> PCI Lanes to use both Internal IGFX and PCIe card at the same time
> (simultaneously). Primary (IGFX) will need to be disabled in your BIOS
> for PCIe card to work, can you get them both enabled in native WinXP?
>
> If I were you, I would try and pass through the Primary (IGFX) VGA
> controller to DomU with the specific changes needed to memory
> addresses in the v1 patches .. see if that works.
>
> Dont think you will have much luck with your secondary PCIe card - (I
> couldnt get PCIe secondary working either, and my secondary does work
> in native WinXP)
>
> Tim
>
> *From:* Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
> *Sent:* 03 September 2009 10:50
> *To:* weidong.han@intel.com <mailto:weidong.han@intel.com>; Tim Moore
> *Cc:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>;
> xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> Hi Weidong,
>
> Do you have any ideas why gfx passthrough couldn’t work in my case?
>
> 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@hotmail.com <mailto:teoenming@hotmail.com>
>
> ------------------------------------------------------------------------
>
> *From:* Han, Weidong [mailto:weidong.han@intel.com]
> *Sent:* Thursday, September 03, 2009 5:43 PM
> *To:* 'Tim Moore'
> *Cc:* 'enming.teo@asiasoftsea.net
> <mailto:enming.teo@asiasoftsea.net>'; 'djmagee@mageenet.net
> <mailto:djmagee@mageenet.net>'; 'xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>'
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> Tim,
>
> See my comments belew.
>
> ------------------------------------------------------------------------
>
> *From:* Tim Moore [mailto:timothy.moore@expidas.net]
> *Sent:* 2009年9月3日 17:03
> *To:* Han, Weidong
> *Cc:* 'enming.teo@asiasoftsea.net
> <mailto:enming.teo@asiasoftsea.net>'; djmagee@mageenet.net
> <mailto:djmagee@mageenet.net>; xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> 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@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Teo En
> Ming (Zhang Enming)
> *Sent:* 03 September 2009 05:12
> *To:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>; 'Han,
> Weidong'; xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
> *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@hotmail.com <mailto:teoenming@hotmail.com>
>
> ------------------------------------------------------------------------
>
> *From:* xen-devel-bounces@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net <mailto:djmagee@mageenet.net>
> *Sent:* Wednesday, September 02, 2009 6:59 PM
> *To:* Han, Weidong; xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
> *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@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Han, Weidong
> *Sent:* Tuesday, September 01, 2009 6:55 PM
> *To:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>;
> 'xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>'
> *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@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net <mailto:djmagee@mageenet.net>
> *Sent:* 2009年9月2日 6:40
> *To:* xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>
> *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@mageenet.net <mailto:djmagee@mageenet.net>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date:
> 09/01/09 20:03:00
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date:
> 09/01/09 20:03:00
>
>
> ------------------------------------------------------------------------
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com <mailto:Xen-devel@lists.xensource.com>
> http://lists.xensource.com/xen-devel
>
>
[-- Attachment #1.2: Type: text/html, Size: 34328 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-03 4:12 ` Teo En Ming (Zhang Enming)
2009-09-03 9:03 ` Tim Moore
@ 2009-09-03 15:07 ` djmagee
2009-09-03 15:58 ` Mr. Teo En Ming (Zhang Enming)
2009-09-09 19:02 ` RE: xen-unstable gfx passthrough (was xen-unstable pci passthrough) djmagee
1 sibling, 2 replies; 39+ messages in thread
From: djmagee @ 2009-09-03 15:07 UTC (permalink / raw)
To: enming.teo, Han, Weidong, xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 5315 bytes --]
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.
From: Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
Sent: Thursday, September 03, 2009 12:12 AM
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
________________________________
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net
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
[-- Attachment #1.2: Type: text/html, Size: 17875 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: RE: xen-unstable pci passthrough
2009-09-03 14:28 ` Mr. Teo En Ming (Zhang Enming)
@ 2009-09-03 15:33 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 15:39 ` Mr. Teo En Ming (Zhang Enming)
0 siblings, 1 reply; 39+ messages in thread
From: Mr. Teo En Ming (Zhang Enming) @ 2009-09-03 15:33 UTC (permalink / raw)
To: enming.teo; +Cc: xen-devel, timothy.moore
[-- Attachment #1.1: Type: text/plain, Size: 13393 bytes --]
OK, although I have successfully configured, compiled and installed
linux-2.6.18.8-xen-dom0 kernel, I cannot use it at all.
When I tried to boot up kernel 2.6.18.8-xen which I have just compiled
and installed, I get the "kernel panic not syncing attempted to kill
init" message.
The real reason is because I am using ext4 filesystems. ext4 is only
supported in kernel 2.6.28 onwards. 2.6.18 only supports ext3. And I
can't mount ext4 as ext3. I have tried it. It doesn't work. Since I
can't mount ext4 as ext3, I can't do testing with 2.6.18.8 xenified
non-pvops dom0 xen kernel already.
Unless I can patch 2.6.18.8-xen to support ext4. I shouldn't have used
ext4 in the first place.
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/03/2009 10:28 PM, Mr. Teo En Ming (Zhang Enming) wrote:
> Hi Tim,
>
> I have downloaded linux-2.6.18.8-xen source code. I am compiling it
> now. If I still cannot get nVidia Geforce 8400 GS PCI-e x16 secondary
> gfx to be passed through to Win XP HVM dom U with xen 3.5-unstable
> with intel gfx passthrough patches applied with xenlinux 2.6.18.8, I
> will give up the attempt on the secondary gfx.
>
> I will then focus on getting the primary gfx (either onboard or pci-e)
> to be passed through.
>
> --
> 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
> Company Website: http://www.asiasoft.sg/
> Mobile: +65-9648-9798
> MSN: teoenming@hotmail.com
> Alma Maters: Singapore Polytechnic, National University of Singapore
>
>
> On 09/03/2009 10:19 PM, Tim Moore wrote:
>>
>> Try and get native WinXP to boot and initialise both cards at the
>> same time .. acid test .. you`ll know if you are wasting your time or
>> not !
>>
>> *From:* Mr. Teo En Ming (Zhang Enming)
>> [mailto:enming.teo@asiasoftsea.net]
>> *Sent:* 03 September 2009 15:12
>> *To:* Tim Moore
>> *Cc:* xen-devel@lists.xensource.com
>> *Subject:* Re: [Xen-devel] RE: xen-unstable pci passthrough
>>
>> Hi Tim,
>>
>> I am aware that Magee told me that onboard GMA4500 and PCI-e x16
>> graphics cannot work simultaneously.
>>
>> But Weidong told me in earlier postings that he could get secondary
>> gfx to work in the labs, so I am still holding out some hope of
>> getting my secondary gfx to be passed through to windows xp hvm domU.
>>
>> --
>> 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
>> Company Website: http://www.asiasoft.sg/
>> Mobile: +65-9648-9798
>> MSN: teoenming@hotmail.com <mailto:teoenming@hotmail.com>
>> Alma Maters: Singapore Polytechnic, National University of Singapore
>>
>>
>>
>> On 09/03/2009 09:40 PM, Tim Moore wrote:
>>
>> hi Teo,
>>
>> I believe it is due to your motherboard - In a previous post to
>> xen-devel, as user said to YOU that the chipset does not have enough
>> PCI Lanes to use both Internal IGFX and PCIe card at the same time
>> (simultaneously). Primary (IGFX) will need to be disabled in your
>> BIOS for PCIe card to work, can you get them both enabled in native
>> WinXP?
>>
>> If I were you, I would try and pass through the Primary (IGFX) VGA
>> controller to DomU with the specific changes needed to memory
>> addresses in the v1 patches .. see if that works.
>>
>> Dont think you will have much luck with your secondary PCIe card - (I
>> couldnt get PCIe secondary working either, and my secondary does work
>> in native WinXP)
>>
>> Tim
>>
>> *From:* Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
>> *Sent:* 03 September 2009 10:50
>> *To:* weidong.han@intel.com <mailto:weidong.han@intel.com>; Tim Moore
>> *Cc:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>;
>> xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>
>> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>>
>> Hi Weidong,
>>
>> Do you have any ideas why gfx passthrough couldn’t work in my case?
>>
>> 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@hotmail.com <mailto:teoenming@hotmail.com>
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Han, Weidong [mailto:weidong.han@intel.com]
>> *Sent:* Thursday, September 03, 2009 5:43 PM
>> *To:* 'Tim Moore'
>> *Cc:* 'enming.teo@asiasoftsea.net
>> <mailto:enming.teo@asiasoftsea.net>'; 'djmagee@mageenet.net
>> <mailto:djmagee@mageenet.net>'; 'xen-devel@lists.xensource.com
>> <mailto:xen-devel@lists.xensource.com>'
>> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>>
>> Tim,
>>
>> See my comments belew.
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Tim Moore [mailto:timothy.moore@expidas.net]
>> *Sent:* 2009年9月3日 17:03
>> *To:* Han, Weidong
>> *Cc:* 'enming.teo@asiasoftsea.net
>> <mailto:enming.teo@asiasoftsea.net>'; djmagee@mageenet.net
>> <mailto:djmagee@mageenet.net>; xen-devel@lists.xensource.com
>> <mailto:xen-devel@lists.xensource.com>
>> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>>
>> 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@lists.xensource.com
>> <mailto:xen-devel-bounces@lists.xensource.com>
>> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Teo En
>> Ming (Zhang Enming)
>> *Sent:* 03 September 2009 05:12
>> *To:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>; 'Han,
>> Weidong'; xen-devel@lists.xensource.com
>> <mailto:xen-devel@lists.xensource.com>
>> *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@hotmail.com <mailto:teoenming@hotmail.com>
>>
>> ------------------------------------------------------------------------
>>
>> *From:* xen-devel-bounces@lists.xensource.com
>> <mailto:xen-devel-bounces@lists.xensource.com>
>> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
>> *djmagee@mageenet.net <mailto:djmagee@mageenet.net>
>> *Sent:* Wednesday, September 02, 2009 6:59 PM
>> *To:* Han, Weidong; xen-devel@lists.xensource.com
>> <mailto:xen-devel@lists.xensource.com>
>> *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@lists.xensource.com
>> <mailto:xen-devel-bounces@lists.xensource.com>
>> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Han,
>> Weidong
>> *Sent:* Tuesday, September 01, 2009 6:55 PM
>> *To:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>;
>> 'xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>'
>> *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@lists.xensource.com
>> <mailto:xen-devel-bounces@lists.xensource.com>
>> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
>> *djmagee@mageenet.net <mailto:djmagee@mageenet.net>
>> *Sent:* 2009年9月2日 6:40
>> *To:* xen-devel@lists.xensource.com
>> <mailto:xen-devel@lists.xensource.com>
>> *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@mageenet.net <mailto:djmagee@mageenet.net>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com <http://www.avg.com>
>> Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date:
>> 09/01/09 20:03:00
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com <http://www.avg.com>
>> Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date:
>> 09/01/09 20:03:00
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com <mailto:Xen-devel@lists.xensource.com>
>> http://lists.xensource.com/xen-devel
>>
>>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
[-- Attachment #1.2: Type: text/html, Size: 36884 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: RE: xen-unstable pci passthrough
2009-09-03 15:33 ` Mr. Teo En Ming (Zhang Enming)
@ 2009-09-03 15:39 ` Mr. Teo En Ming (Zhang Enming)
0 siblings, 0 replies; 39+ messages in thread
From: Mr. Teo En Ming (Zhang Enming) @ 2009-09-03 15:39 UTC (permalink / raw)
To: enming.teo; +Cc: xen-devel, timothy.moore
[-- Attachment #1.1: Type: text/plain, Size: 14438 bytes --]
Anyway, here is my kernel configuration for 2.6.18.8-xen non-pvops dom 0
kernel on Fedora 11 64-bit host operating system. Please check email
attachment.
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/03/2009 11:33 PM, Mr. Teo En Ming (Zhang Enming) wrote:
> OK, although I have successfully configured, compiled and installed
> linux-2.6.18.8-xen-dom0 kernel, I cannot use it at all.
>
> When I tried to boot up kernel 2.6.18.8-xen which I have just compiled
> and installed, I get the "kernel panic not syncing attempted to kill
> init" message.
>
> The real reason is because I am using ext4 filesystems. ext4 is only
> supported in kernel 2.6.28 onwards. 2.6.18 only supports ext3. And I
> can't mount ext4 as ext3. I have tried it. It doesn't work. Since I
> can't mount ext4 as ext3, I can't do testing with 2.6.18.8 xenified
> non-pvops dom0 xen kernel already.
>
> Unless I can patch 2.6.18.8-xen to support ext4. I shouldn't have used
> ext4 in the first place.
> --
> 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
> Company Website: http://www.asiasoft.sg/
> Mobile: +65-9648-9798
> MSN: teoenming@hotmail.com
> Alma Maters: Singapore Polytechnic, National University of Singapore
>
>
> On 09/03/2009 10:28 PM, Mr. Teo En Ming (Zhang Enming) wrote:
>> Hi Tim,
>>
>> I have downloaded linux-2.6.18.8-xen source code. I am compiling it
>> now. If I still cannot get nVidia Geforce 8400 GS PCI-e x16 secondary
>> gfx to be passed through to Win XP HVM dom U with xen 3.5-unstable
>> with intel gfx passthrough patches applied with xenlinux 2.6.18.8, I
>> will give up the attempt on the secondary gfx.
>>
>> I will then focus on getting the primary gfx (either onboard or
>> pci-e) to be passed through.
>>
>> --
>> 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
>> Company Website: http://www.asiasoft.sg/
>> Mobile: +65-9648-9798
>> MSN: teoenming@hotmail.com
>> Alma Maters: Singapore Polytechnic, National University of Singapore
>>
>>
>> On 09/03/2009 10:19 PM, Tim Moore wrote:
>>>
>>> Try and get native WinXP to boot and initialise both cards at the
>>> same time .. acid test .. you`ll know if you are wasting your time
>>> or not !
>>>
>>> *From:* Mr. Teo En Ming (Zhang Enming)
>>> [mailto:enming.teo@asiasoftsea.net]
>>> *Sent:* 03 September 2009 15:12
>>> *To:* Tim Moore
>>> *Cc:* xen-devel@lists.xensource.com
>>> *Subject:* Re: [Xen-devel] RE: xen-unstable pci passthrough
>>>
>>> Hi Tim,
>>>
>>> I am aware that Magee told me that onboard GMA4500 and PCI-e x16
>>> graphics cannot work simultaneously.
>>>
>>> But Weidong told me in earlier postings that he could get secondary
>>> gfx to work in the labs, so I am still holding out some hope of
>>> getting my secondary gfx to be passed through to windows xp hvm domU.
>>>
>>> --
>>> 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
>>> Company Website: http://www.asiasoft.sg/
>>> Mobile: +65-9648-9798
>>> MSN: teoenming@hotmail.com <mailto:teoenming@hotmail.com>
>>> Alma Maters: Singapore Polytechnic, National University of Singapore
>>>
>>>
>>>
>>> On 09/03/2009 09:40 PM, Tim Moore wrote:
>>>
>>> hi Teo,
>>>
>>> I believe it is due to your motherboard - In a previous post to
>>> xen-devel, as user said to YOU that the chipset does not have enough
>>> PCI Lanes to use both Internal IGFX and PCIe card at the same time
>>> (simultaneously). Primary (IGFX) will need to be disabled in your
>>> BIOS for PCIe card to work, can you get them both enabled in native
>>> WinXP?
>>>
>>> If I were you, I would try and pass through the Primary (IGFX) VGA
>>> controller to DomU with the specific changes needed to memory
>>> addresses in the v1 patches .. see if that works.
>>>
>>> Dont think you will have much luck with your secondary PCIe card -
>>> (I couldnt get PCIe secondary working either, and my secondary does
>>> work in native WinXP)
>>>
>>> Tim
>>>
>>> *From:* Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
>>> *Sent:* 03 September 2009 10:50
>>> *To:* weidong.han@intel.com <mailto:weidong.han@intel.com>; Tim Moore
>>> *Cc:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>;
>>> xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>
>>> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>>>
>>> Hi Weidong,
>>>
>>> Do you have any ideas why gfx passthrough couldn’t work in my case?
>>>
>>> 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@hotmail.com <mailto:teoenming@hotmail.com>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* Han, Weidong [mailto:weidong.han@intel.com]
>>> *Sent:* Thursday, September 03, 2009 5:43 PM
>>> *To:* 'Tim Moore'
>>> *Cc:* 'enming.teo@asiasoftsea.net
>>> <mailto:enming.teo@asiasoftsea.net>'; 'djmagee@mageenet.net
>>> <mailto:djmagee@mageenet.net>'; 'xen-devel@lists.xensource.com
>>> <mailto:xen-devel@lists.xensource.com>'
>>> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>>>
>>> Tim,
>>>
>>> See my comments belew.
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* Tim Moore [mailto:timothy.moore@expidas.net]
>>> *Sent:* 2009年9月3日 17:03
>>> *To:* Han, Weidong
>>> *Cc:* 'enming.teo@asiasoftsea.net
>>> <mailto:enming.teo@asiasoftsea.net>'; djmagee@mageenet.net
>>> <mailto:djmagee@mageenet.net>; xen-devel@lists.xensource.com
>>> <mailto:xen-devel@lists.xensource.com>
>>> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>>>
>>> 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@lists.xensource.com
>>> <mailto:xen-devel-bounces@lists.xensource.com>
>>> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Teo En
>>> Ming (Zhang Enming)
>>> *Sent:* 03 September 2009 05:12
>>> *To:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>; 'Han,
>>> Weidong'; xen-devel@lists.xensource.com
>>> <mailto:xen-devel@lists.xensource.com>
>>> *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@hotmail.com <mailto:teoenming@hotmail.com>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* xen-devel-bounces@lists.xensource.com
>>> <mailto:xen-devel-bounces@lists.xensource.com>
>>> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
>>> *djmagee@mageenet.net <mailto:djmagee@mageenet.net>
>>> *Sent:* Wednesday, September 02, 2009 6:59 PM
>>> *To:* Han, Weidong; xen-devel@lists.xensource.com
>>> <mailto:xen-devel@lists.xensource.com>
>>> *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@lists.xensource.com
>>> <mailto:xen-devel-bounces@lists.xensource.com>
>>> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Han,
>>> Weidong
>>> *Sent:* Tuesday, September 01, 2009 6:55 PM
>>> *To:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>;
>>> 'xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>'
>>> *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@lists.xensource.com
>>> <mailto:xen-devel-bounces@lists.xensource.com>
>>> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
>>> *djmagee@mageenet.net <mailto:djmagee@mageenet.net>
>>> *Sent:* 2009年9月2日 6:40
>>> *To:* xen-devel@lists.xensource.com
>>> <mailto:xen-devel@lists.xensource.com>
>>> *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@mageenet.net <mailto:djmagee@mageenet.net>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com <http://www.avg.com>
>>> Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date:
>>> 09/01/09 20:03:00
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com <http://www.avg.com>
>>> Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date:
>>> 09/01/09 20:03:00
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com <mailto:Xen-devel@lists.xensource.com>
>>> http://lists.xensource.com/xen-devel
>>>
>>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>
>
[-- Attachment #1.2: Type: text/html, Size: 38532 bytes --]
[-- Attachment #2: config-2.6.18.8-enming.teo --]
[-- Type: text/plain, Size: 58482 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.18.8-enming.teo
# Thu Sep 3 22:16:54 2009
#
CONFIG_X86_64=y
CONFIG_64BIT=y
CONFIG_X86=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_CMPXCHG=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_AUDIT_ARCH=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
#
# General setup
#
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
# CONFIG_IKCONFIG is not set
CONFIG_CPUSETS=y
CONFIG_RELAY=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
#
# Block layer
#
# CONFIG_LBD is not set
CONFIG_BLK_DEV_IO_TRACE=y
# CONFIG_LSF is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VSMP is not set
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_64_XEN=y
CONFIG_X86_NO_TSS=y
CONFIG_X86_NO_IDT=y
CONFIG_X86_L1_CACHE_BYTES=128
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_INTERNODE_CACHE_BYTES=128
CONFIG_X86_GOOD_APIC=y
CONFIG_MICROCODE=m
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_XEN_GENAPIC=y
CONFIG_X86_LOCAL_APIC=y
# CONFIG_MTRR is not set
CONFIG_SMP=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_NR_CPUS=64
CONFIG_HOTPLUG_CPU=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_SWIOTLB=y
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x200000
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_REORDER=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_ISA_DMA_API=y
CONFIG_GENERIC_PENDING_IRQ=y
#
# Power management options
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND is not set
CONFIG_SUSPEND_SMP=y
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_SLEEP_PROC_SLEEP is not set
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
# CONFIG_ACPI_VIDEO is not set
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=y
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_ACPI_CONTAINER=y
# CONFIG_ACPI_SBS is not set
CONFIG_ACPI_PV_SLEEP=y
CONFIG_PROCESSOR_EXTERNAL_CONTROL=y
#
# CPU Frequency scaling
#
#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_MMCONFIG is not set
CONFIG_XEN_PCIDEV_FRONTEND=y
# CONFIG_XEN_PCIDEV_FE_DEBUG is not set
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=m
# CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE is not set
CONFIG_PCIEAER=y
# CONFIG_PCI_MSI is not set
CONFIG_PCI_REASSIGN=y
# CONFIG_PCI_DEBUG is not set
CONFIG_PCI_GUESTDEV=y
# CONFIG_PCI_IOV is not set
#
# PCCARD (PCMCIA/CardBus) support
#
CONFIG_PCCARD=y
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=y
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y
#
# PC-card bridges
#
CONFIG_YENTA=y
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_PD6729=m
CONFIG_I82092=m
CONFIG_PCCARD_NONSTATIC=y
#
# PCI Hotplug Support
#
CONFIG_HOTPLUG_PCI=y
CONFIG_HOTPLUG_PCI_FAKE=m
# CONFIG_HOTPLUG_PCI_ACPI is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
CONFIG_HOTPLUG_PCI_SHPC=m
# CONFIG_HOTPLUG_PCI_SHPC_POLL_EVENT_MODE is not set
#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_IA32_EMULATION=y
# CONFIG_IA32_AOUT is not set
CONFIG_COMPAT=y
CONFIG_SYSVIPC_COMPAT=y
#
# Networking
#
CONFIG_NET=y
#
# Networking options
#
# CONFIG_NETDEBUG is not set
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
CONFIG_NET_KEY=m
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
# CONFIG_IP_ROUTE_FWMARK is not set
CONFIG_IP_ROUTE_MULTIPATH=y
# CONFIG_IP_ROUTE_MULTIPATH_CACHED is not set
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_TCP_CONG_ADVANCED=y
#
# TCP congestion control
#
CONFIG_TCP_CONG_BIC=y
CONFIG_TCP_CONG_CUBIC=m
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
CONFIG_TCP_CONG_SCALABLE=m
CONFIG_TCP_CONG_LP=m
CONFIG_TCP_CONG_VENO=m
#
# IP: Virtual Server Configuration
#
CONFIG_IP_VS=m
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12
#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y
#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m
#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_IPV6_TUNNEL=m
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CT_ACCT=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CT_PROTO_SCTP=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
#
# IP: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV4=m
# CONFIG_IP_NF_CONNTRACK is not set
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
# CONFIG_IP_NF_MATCH_DSCP is not set
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
# CONFIG_IP_NF_MATCH_HASHLIMIT is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
# CONFIG_IP_NF_TARGET_TCPMSS is not set
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
# CONFIG_IP_NF_TARGET_DSCP is not set
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
#
# IPv6: Netfilter Configuration (EXPERIMENTAL)
#
CONFIG_NF_CONNTRACK_IPV6=m
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_OWNER=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_RAW=m
#
# DECnet: Netfilter Configuration
#
# CONFIG_DECNET_NF_GRABULATOR is not set
#
# Bridge: Netfilter Configuration
#
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m
#
# DCCP Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
CONFIG_IP_DCCP_ACKVEC=y
#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP_CCID2=m
CONFIG_IP_DCCP_CCID3=m
CONFIG_IP_DCCP_TFRC_LIB=m
#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
#
# TIPC Configuration (EXPERIMENTAL)
#
CONFIG_TIPC=m
# CONFIG_TIPC_ADVANCED is not set
# CONFIG_TIPC_DEBUG is not set
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set
CONFIG_ATM_LANE=m
# CONFIG_ATM_MPOA is not set
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=m
CONFIG_DECNET=m
CONFIG_DECNET_ROUTER=y
# CONFIG_DECNET_ROUTE_FWMARK is not set
CONFIG_LLC=y
# CONFIG_LLC2 is not set
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
CONFIG_ATALK=m
CONFIG_DEV_APPLETALK=m
CONFIG_IPDDP=m
CONFIG_IPDDP_ENCAP=y
CONFIG_IPDDP_DECAP=y
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
CONFIG_WAN_ROUTER=m
#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
# CONFIG_NET_SCH_CLK_JIFFIES is not set
CONFIG_NET_SCH_CLK_GETTIMEOFDAY=y
# CONFIG_NET_SCH_CLK_CPU is not set
#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_INGRESS=m
#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
CONFIG_NET_CLS_IND=y
CONFIG_NET_ESTIMATOR=y
#
# Network testing
#
CONFIG_NET_PKTGEN=m
# CONFIG_NET_TCPPROBE is not set
# CONFIG_HAMRADIO is not set
CONFIG_IRDA=m
#
# IrDA protocols
#
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
# CONFIG_IRDA_ULTRA is not set
#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
# CONFIG_IRDA_DEBUG is not set
#
# Infrared-port device drivers
#
#
# SIR device drivers
#
CONFIG_IRTTY_SIR=m
#
# Dongle support
#
CONFIG_DONGLE=y
CONFIG_ESI_DONGLE=m
CONFIG_ACTISYS_DONGLE=m
CONFIG_TEKRAM_DONGLE=m
CONFIG_TOIM3232_DONGLE=m
CONFIG_LITELINK_DONGLE=m
CONFIG_MA600_DONGLE=m
CONFIG_GIRBIL_DONGLE=m
CONFIG_MCP2120_DONGLE=m
CONFIG_OLD_BELKIN_DONGLE=m
CONFIG_ACT200L_DONGLE=m
#
# Old SIR device drivers
#
#
# Old Serial dongle support
#
#
# FIR device drivers
#
CONFIG_USB_IRDA=m
CONFIG_SIGMATEL_FIR=m
CONFIG_NSC_FIR=m
CONFIG_WINBOND_FIR=m
CONFIG_SMC_IRCC_FIR=m
CONFIG_ALI_FIR=m
CONFIG_VLSI_FIR=m
CONFIG_VIA_FIR=m
CONFIG_MCS_FIR=m
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_CMTP=m
CONFIG_BT_HIDP=m
#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUSB_SCO=y
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
CONFIG_IEEE80211=m
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m
CONFIG_IEEE80211_SOFTMAC=m
CONFIG_IEEE80211_SOFTMAC_DEBUG=y
CONFIG_WIRELESS_EXT=y
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_DEBUG_DRIVER is not set
CONFIG_SYS_HYPERVISOR=y
#
# Connector - unified userspace <-> kernelspace linker
#
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_CONCAT=m
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_REDBOOT_PARTS=m
CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1
# CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set
# CONFIG_MTD_REDBOOT_PARTS_READONLY is not set
# CONFIG_MTD_CMDLINE_PARTS is not set
#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=m
CONFIG_MTD_BLOCK=m
CONFIG_MTD_BLOCK_RO=m
CONFIG_FTL=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y
CONFIG_INFTL=m
CONFIG_RFD_FTL=m
#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_GEN_PROBE=m
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_CFI_STAA=m
CONFIG_MTD_CFI_UTIL=m
CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=m
CONFIG_MTD_ABSENT=m
# CONFIG_MTD_OBSOLETE_CHIPS is not set
#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_PNC2000 is not set
CONFIG_MTD_SC520CDP=m
CONFIG_MTD_NETSC520=m
CONFIG_MTD_TS5500=m
# CONFIG_MTD_SBC_GXX is not set
# CONFIG_MTD_AMD76XROM is not set
# CONFIG_MTD_ICHXROM is not set
CONFIG_MTD_SCB2_FLASH=m
# CONFIG_MTD_NETtel is not set
# CONFIG_MTD_DILNETPC is not set
# CONFIG_MTD_L440GX is not set
CONFIG_MTD_PCI=m
# CONFIG_MTD_PLATRAM is not set
#
# Self-contained MTD device drivers
#
CONFIG_MTD_PMC551=m
# CONFIG_MTD_PMC551_BUGFIX is not set
# CONFIG_MTD_PMC551_DEBUG is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
CONFIG_MTD_BLOCK2MTD=m
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
#
# NAND Flash Device Drivers
#
CONFIG_MTD_NAND=m
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
CONFIG_MTD_NAND_ECC_SMC=y
CONFIG_MTD_NAND_IDS=m
CONFIG_MTD_NAND_DISKONCHIP=m
# CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
# CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set
CONFIG_MTD_NAND_NANDSIM=m
#
# OneNAND Flash Device Drivers
#
# CONFIG_MTD_ONENAND is not set
#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
CONFIG_PARPORT_PC_PCMCIA=m
CONFIG_PARPORT_NOT_PC=y
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
CONFIG_PARPORT_1284=y
#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set
#
# Protocols
#
CONFIG_PNPACPI=y
#
# Block devices
#
CONFIG_BLK_DEV_FD=m
CONFIG_PARIDE=m
CONFIG_PARIDE_PARPORT=m
#
# Parallel IDE high-level drivers
#
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m
CONFIG_PARIDE_PG=m
#
# Parallel IDE protocol modules
#
CONFIG_PARIDE_ATEN=m
CONFIG_PARIDE_BPCK=m
CONFIG_PARIDE_COMM=m
CONFIG_PARIDE_DSTR=m
CONFIG_PARIDE_FIT2=m
CONFIG_PARIDE_FIT3=m
CONFIG_PARIDE_EPAT=m
CONFIG_PARIDE_EPATC8=y
CONFIG_PARIDE_EPIA=m
CONFIG_PARIDE_FRIQ=m
CONFIG_PARIDE_FRPW=m
CONFIG_PARIDE_KBIC=m
CONFIG_PARIDE_KTTI=m
CONFIG_PARIDE_ON20=m
CONFIG_PARIDE_ON26=m
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
CONFIG_CISS_SCSI_TAPE=y
CONFIG_BLK_DEV_DAC960=m
CONFIG_BLK_DEV_UMEM=m
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_SX8=m
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
CONFIG_BLK_DEV_RAM_BLOCKSIZE=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_ATA_OVER_ETH=m
#
# ATA/ATAPI/MFM/RLL support
#
# CONFIG_IDE is not set
#
# SCSI device support
#
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
CONFIG_CHR_DEV_SCH=m
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
#
# SCSI low-level drivers
#
CONFIG_ISCSI_TCP=m
CONFIG_BLK_DEV_3W_XXXX_RAID=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=4
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
# CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set
CONFIG_SCSI_AIC7XXX_OLD=m
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=4
CONFIG_AIC79XX_RESET_DELAY_MS=15000
# CONFIG_AIC79XX_ENABLE_RD_STRM is not set
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
CONFIG_MEGARAID_LEGACY=m
CONFIG_MEGARAID_SAS=m
# CONFIG_SCSI_SATA is not set
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
CONFIG_SCSI_GDTH=m
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
CONFIG_SCSI_INIA100=m
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
# CONFIG_SCSI_IPR is not set
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA_FC=m
CONFIG_SCSI_LPFC=m
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
# CONFIG_SCSI_DEBUG is not set
#
# PCMCIA SCSI adapter support
#
# CONFIG_PCMCIA_FDOMAIN is not set
CONFIG_PCMCIA_QLOGIC=m
CONFIG_PCMCIA_SYM53C500=m
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
CONFIG_MD_RAID5_RESHAPE=y
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=m
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
CONFIG_DM_MULTIPATH_EMC=m
#
# Fusion MPT device support
#
CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=40
CONFIG_FUSION_CTL=m
CONFIG_FUSION_LAN=m
#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
CONFIG_I2O=m
# CONFIG_I2O_LCT_NOTIFY_ON_CHANGES is not set
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_EXT_ADAPTEC_DMA64=y
CONFIG_I2O_CONFIG=m
CONFIG_I2O_CONFIG_OLD_IOCTL=y
CONFIG_I2O_BUS=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m
#
# Network device support
#
CONFIG_NETDEVICES=y
CONFIG_IFB=m
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_EQUALIZER=m
CONFIG_TUN=m
# CONFIG_NET_SB1000 is not set
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# PHY device support
#
CONFIG_PHYLIB=m
#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=m
CONFIG_DAVICOM_PHY=m
CONFIG_QSEMI_PHY=m
CONFIG_LXT_PHY=m
CONFIG_CICADA_PHY=m
CONFIG_VITESSE_PHY=m
CONFIG_SMSC_PHY=m
CONFIG_FIXED_PHY=m
CONFIG_FIXED_MII_10_FDX=y
CONFIG_FIXED_MII_100_FDX=y
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_CASSINI=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
#
# Tulip family network device support
#
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
CONFIG_TULIP_MMIO=y
# CONFIG_TULIP_NAPI is not set
CONFIG_DE4X5=m
CONFIG_WINBOND_840=m
CONFIG_DM9102=m
CONFIG_ULI526X=m
CONFIG_PCMCIA_XIRCOM=m
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
CONFIG_PCNET32=m
CONFIG_AMD8111_ETH=m
CONFIG_AMD8111E_NAPI=y
CONFIG_ADAPTEC_STARFIRE=m
CONFIG_ADAPTEC_STARFIRE_NAPI=y
CONFIG_B44=m
CONFIG_FORCEDETH=m
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
CONFIG_E100=m
CONFIG_FEALNX=m
CONFIG_NATSEMI=m
CONFIG_NE2K_PCI=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_SIS900=m
CONFIG_EPIC100=m
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
CONFIG_VIA_RHINE=m
CONFIG_VIA_RHINE_MMIO=y
CONFIG_VIA_RHINE_NAPI=y
CONFIG_NET_POCKET=y
CONFIG_ATP=m
CONFIG_DE600=m
CONFIG_DE620=m
#
# Ethernet (1000 Mbit)
#
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I is not set
CONFIG_DL2K=m
CONFIG_E1000=m
CONFIG_E1000_NAPI=y
# CONFIG_E1000_DISABLE_PACKET_SPLIT is not set
# CONFIG_IGB is not set
# CONFIG_E1000E is not set
CONFIG_NS83820=m
CONFIG_HAMACHI=m
CONFIG_YELLOWFIN=m
CONFIG_R8169=m
CONFIG_R8169_NAPI=y
CONFIG_R8169_VLAN=y
CONFIG_SIS190=m
CONFIG_SKGE=m
CONFIG_SKY2=m
# CONFIG_SK98LIN is not set
CONFIG_VIA_VELOCITY=m
CONFIG_TIGON3=m
CONFIG_BNX2=m
#
# Ethernet (10000 Mbit)
#
CONFIG_CHELSIO_T1=m
# CONFIG_IXGBE is not set
CONFIG_IXGB=m
CONFIG_IXGB_NAPI=y
CONFIG_S2IO=m
CONFIG_S2IO_NAPI=y
CONFIG_MYRI10GE=m
# CONFIG_SFC is not set
#
# Token Ring devices
#
CONFIG_TR=y
CONFIG_IBMOL=m
CONFIG_3C359=m
# CONFIG_TMS380TR is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# PCMCIA network device support
#
CONFIG_NET_PCMCIA=y
CONFIG_PCMCIA_3C589=m
CONFIG_PCMCIA_3C574=m
CONFIG_PCMCIA_FMVJ18X=m
CONFIG_PCMCIA_PCNET=m
CONFIG_PCMCIA_NMCLAN=m
CONFIG_PCMCIA_SMC91C92=m
CONFIG_PCMCIA_XIRC2PS=m
CONFIG_PCMCIA_AXNET=m
#
# Wan interfaces
#
# CONFIG_WAN is not set
#
# ATM drivers
#
# CONFIG_ATM_DUMMY is not set
CONFIG_ATM_TCP=m
CONFIG_ATM_LANAI=m
CONFIG_ATM_ENI=m
# CONFIG_ATM_ENI_DEBUG is not set
# CONFIG_ATM_ENI_TUNE_BURST is not set
CONFIG_ATM_FIRESTREAM=m
# CONFIG_ATM_ZATM is not set
CONFIG_ATM_IDT77252=m
# CONFIG_ATM_IDT77252_DEBUG is not set
# CONFIG_ATM_IDT77252_RCV_ALL is not set
CONFIG_ATM_IDT77252_USE_SUNI=y
CONFIG_ATM_AMBASSADOR=m
# CONFIG_ATM_AMBASSADOR_DEBUG is not set
CONFIG_ATM_HORIZON=m
# CONFIG_ATM_HORIZON_DEBUG is not set
CONFIG_ATM_FORE200E_MAYBE=m
# CONFIG_ATM_FORE200E_PCA is not set
CONFIG_ATM_HE=m
# CONFIG_ATM_HE_USE_SUNI is not set
CONFIG_FDDI=y
# CONFIG_DEFXX is not set
CONFIG_SKFP=m
# CONFIG_HIPPI is not set
CONFIG_PLIP=m
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
# CONFIG_PPP_BSDCOMP is not set
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
# CONFIG_SLIP_MODE_SLIP6 is not set
CONFIG_NET_FC=y
# CONFIG_SHAPER is not set
CONFIG_NETCONSOLE=m
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_RX is not set
CONFIG_NETPOLL_TRAP=y
CONFIG_NET_POLL_CONTROLLER=y
#
# ISDN subsystem
#
CONFIG_ISDN=m
#
# Old ISDN4Linux
#
CONFIG_ISDN_I4L=m
CONFIG_ISDN_PPP=y
CONFIG_ISDN_PPP_VJ=y
CONFIG_ISDN_MPP=y
CONFIG_IPPP_FILTER=y
# CONFIG_ISDN_PPP_BSDCOMP is not set
CONFIG_ISDN_AUDIO=y
CONFIG_ISDN_TTY_FAX=y
#
# ISDN feature submodules
#
CONFIG_ISDN_DIVERSION=m
#
# ISDN4Linux hardware drivers
#
#
# Passive cards
#
CONFIG_ISDN_DRV_HISAX=m
#
# D-channel protocol features
#
CONFIG_HISAX_EURO=y
CONFIG_DE_AOC=y
CONFIG_HISAX_NO_SENDCOMPLETE=y
CONFIG_HISAX_NO_LLC=y
CONFIG_HISAX_NO_KEYPAD=y
CONFIG_HISAX_1TR6=y
CONFIG_HISAX_NI1=y
CONFIG_HISAX_MAX_CARDS=8
#
# HiSax supported cards
#
CONFIG_HISAX_16_3=y
CONFIG_HISAX_TELESPCI=y
CONFIG_HISAX_S0BOX=y
CONFIG_HISAX_FRITZPCI=y
CONFIG_HISAX_AVM_A1_PCMCIA=y
CONFIG_HISAX_ELSA=y
CONFIG_HISAX_DIEHLDIVA=y
CONFIG_HISAX_SEDLBAUER=y
CONFIG_HISAX_NETJET=y
CONFIG_HISAX_NETJET_U=y
CONFIG_HISAX_NICCY=y
CONFIG_HISAX_BKM_A4T=y
CONFIG_HISAX_SCT_QUADRO=y
CONFIG_HISAX_GAZEL=y
CONFIG_HISAX_HFC_PCI=y
CONFIG_HISAX_W6692=y
CONFIG_HISAX_HFC_SX=y
CONFIG_HISAX_ENTERNOW_PCI=y
# CONFIG_HISAX_DEBUG is not set
#
# HiSax PCMCIA card service modules
#
CONFIG_HISAX_SEDLBAUER_CS=m
CONFIG_HISAX_ELSA_CS=m
CONFIG_HISAX_AVM_A1_CS=m
CONFIG_HISAX_TELES_CS=m
#
# HiSax sub driver modules
#
CONFIG_HISAX_ST5481=m
# CONFIG_HISAX_HFCUSB is not set
CONFIG_HISAX_HFC4S8S=m
CONFIG_HISAX_FRITZ_PCIPNP=m
CONFIG_HISAX_HDLC=y
#
# Active cards
#
#
# Siemens Gigaset
#
CONFIG_ISDN_DRV_GIGASET=m
CONFIG_GIGASET_BASE=m
CONFIG_GIGASET_M105=m
# CONFIG_GIGASET_DEBUG is not set
# CONFIG_GIGASET_UNDOCREQ is not set
#
# CAPI subsystem
#
CONFIG_ISDN_CAPI=m
CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON=y
CONFIG_ISDN_CAPI_MIDDLEWARE=y
CONFIG_ISDN_CAPI_CAPI20=m
CONFIG_ISDN_CAPI_CAPIFS_BOOL=y
CONFIG_ISDN_CAPI_CAPIFS=m
CONFIG_ISDN_CAPI_CAPIDRV=m
#
# CAPI hardware drivers
#
#
# Active AVM cards
#
CONFIG_CAPI_AVM=y
CONFIG_ISDN_DRV_AVMB1_B1PCI=m
CONFIG_ISDN_DRV_AVMB1_B1PCIV4=y
CONFIG_ISDN_DRV_AVMB1_B1PCMCIA=m
CONFIG_ISDN_DRV_AVMB1_AVM_CS=m
CONFIG_ISDN_DRV_AVMB1_T1PCI=m
CONFIG_ISDN_DRV_AVMB1_C4=m
#
# Active Eicon DIVA Server cards
#
# CONFIG_CAPI_EICON is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_VSXXXAA=m
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
CONFIG_JOYSTICK_A3D=m
CONFIG_JOYSTICK_ADI=m
CONFIG_JOYSTICK_COBRA=m
CONFIG_JOYSTICK_GF2K=m
CONFIG_JOYSTICK_GRIP=m
CONFIG_JOYSTICK_GRIP_MP=m
CONFIG_JOYSTICK_GUILLEMOT=m
CONFIG_JOYSTICK_INTERACT=m
CONFIG_JOYSTICK_SIDEWINDER=m
CONFIG_JOYSTICK_TMDC=m
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_USB=y
CONFIG_JOYSTICK_IFORCE_232=y
CONFIG_JOYSTICK_WARRIOR=m
CONFIG_JOYSTICK_MAGELLAN=m
CONFIG_JOYSTICK_SPACEORB=m
CONFIG_JOYSTICK_SPACEBALL=m
CONFIG_JOYSTICK_STINGER=m
CONFIG_JOYSTICK_TWIDJOY=m
CONFIG_JOYSTICK_DB9=m
CONFIG_JOYSTICK_GAMECON=m
CONFIG_JOYSTICK_TURBOGRAFX=m
CONFIG_JOYSTICK_JOYDUMP=m
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_GUNZE=m
CONFIG_TOUCHSCREEN_ELO=m
CONFIG_TOUCHSCREEN_MTOUCH=m
CONFIG_TOUCHSCREEN_MK712=m
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_UINPUT=m
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
CONFIG_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
CONFIG_GAMEPORT_L4=m
CONFIG_GAMEPORT_EMU10K1=m
CONFIG_GAMEPORT_FM801=m
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
CONFIG_ROCKETPORT=m
CONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
CONFIG_SYNCLINK=m
CONFIG_SYNCLINKMP=m
CONFIG_SYNCLINK_GT=m
CONFIG_N_HDLC=m
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
# CONFIG_STALDRV is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=m
CONFIG_SERIAL_8250_PCI=m
CONFIG_SERIAL_8250_PNP=m
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=m
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_PRINTER=m
CONFIG_LP_CONSOLE=y
CONFIG_PPDEV=m
CONFIG_TIPAR=m
#
# IPMI
#
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
CONFIG_ALIM1535_WDT=m
CONFIG_ALIM7101_WDT=m
# CONFIG_SC520_WDT is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
CONFIG_IBMASR=m
# CONFIG_WAFER_WDT is not set
CONFIG_I6300ESB_WDT=m
# CONFIG_I8XX_TCO is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SBC8360_WDT is not set
# CONFIG_CPU5_WDT is not set
CONFIG_W83627HF_WDT=m
CONFIG_W83877F_WDT=m
CONFIG_W83977F_WDT=m
CONFIG_MACHZ_WDT=m
# CONFIG_SBC_EPX_C3_WATCHDOG is not set
#
# PCI-based Watchdog Cards
#
CONFIG_PCIPCWATCHDOG=m
CONFIG_WDTPCI=m
CONFIG_WDT_501_PCI=y
#
# USB-based Watchdog Cards
#
CONFIG_USBPCWATCHDOG=m
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
# CONFIG_HW_RANDOM_GEODE is not set
CONFIG_NVRAM=y
CONFIG_RTC=y
CONFIG_DTLK=m
CONFIG_R3964=m
# CONFIG_APPLICOM is not set
#
# Ftape, the floppy tape device driver
#
CONFIG_AGP=y
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=y
CONFIG_AGP_SIS=y
CONFIG_AGP_VIA=y
CONFIG_DRM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
CONFIG_DRM_VIA=m
CONFIG_DRM_SAVAGE=m
#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
CONFIG_CARDMAN_4000=m
CONFIG_CARDMAN_4040=m
CONFIG_MWAVE=m
CONFIG_PC8736x_GPIO=m
CONFIG_NSC_GPIO=m
# CONFIG_RAW_DRIVER is not set
CONFIG_HANGCHECK_TIMER=m
#
# TPM devices
#
CONFIG_TCG_TPM=m
# CONFIG_TCG_TIS is not set
# CONFIG_TCG_NSC is not set
CONFIG_TCG_ATMEL=m
# CONFIG_TCG_INFINEON is not set
# CONFIG_TCG_XEN is not set
# CONFIG_TELCLOCK is not set
#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m
#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m
#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD756_S4882=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_I801=m
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_PIIX4 is not set
CONFIG_I2C_ISA=m
CONFIG_I2C_NFORCE2=m
# CONFIG_I2C_OCORES is not set
CONFIG_I2C_PARPORT=m
CONFIG_I2C_PARPORT_LIGHT=m
CONFIG_I2C_PROSAVAGE=m
CONFIG_I2C_SAVAGE4=m
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
CONFIG_I2C_SIS96X=m
CONFIG_I2C_STUB=m
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
CONFIG_I2C_VOODOO3=m
CONFIG_I2C_PCA_ISA=m
#
# Miscellaneous I2C Chip support
#
CONFIG_SENSORS_DS1337=m
CONFIG_SENSORS_DS1374=m
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_PCF8574=m
CONFIG_SENSORS_PCA9539=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_MAX6875=m
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# Hardware Monitoring support
#
CONFIG_HWMON=m
CONFIG_HWMON_VID=m
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_FSCHER=m
CONFIG_SENSORS_FSCPOS=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
CONFIG_SENSORS_HDAPS=m
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Misc devices
#
# CONFIG_IBM_ASM is not set
#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_VIDEO_V4L2=y
#
# Video Capture Adapters
#
#
# Video Capture Adapters
#
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_VIVI is not set
CONFIG_VIDEO_BT848=m
CONFIG_VIDEO_BT848_DVB=y
CONFIG_VIDEO_SAA6588=m
CONFIG_VIDEO_BWQCAM=m
CONFIG_VIDEO_CQCAM=m
CONFIG_VIDEO_W9966=m
CONFIG_VIDEO_CPIA=m
CONFIG_VIDEO_CPIA_PP=m
CONFIG_VIDEO_CPIA_USB=m
CONFIG_VIDEO_CPIA2=m
CONFIG_VIDEO_SAA5246A=m
CONFIG_VIDEO_SAA5249=m
CONFIG_TUNER_3036=m
CONFIG_VIDEO_STRADIS=m
CONFIG_VIDEO_ZORAN=m
CONFIG_VIDEO_ZORAN_BUZ=m
CONFIG_VIDEO_ZORAN_DC10=m
CONFIG_VIDEO_ZORAN_DC30=m
CONFIG_VIDEO_ZORAN_LML33=m
CONFIG_VIDEO_ZORAN_LML33R10=m
CONFIG_VIDEO_ZORAN_AVS6EYES=m
CONFIG_VIDEO_SAA7134=m
CONFIG_VIDEO_SAA7134_ALSA=m
CONFIG_VIDEO_SAA7134_DVB=m
CONFIG_VIDEO_SAA7134_DVB_ALL_FRONTENDS=y
CONFIG_VIDEO_MXB=m
CONFIG_VIDEO_DPC=m
CONFIG_VIDEO_HEXIUM_ORION=m
CONFIG_VIDEO_HEXIUM_GEMINI=m
CONFIG_VIDEO_CX88_VP3054=m
CONFIG_VIDEO_CX88=m
CONFIG_VIDEO_CX88_ALSA=m
CONFIG_VIDEO_CX88_BLACKBIRD=m
CONFIG_VIDEO_CX88_DVB=m
CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=y
#
# Encoders and Decoders
#
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_CS53L32A=m
CONFIG_VIDEO_TLV320AIC23B=m
CONFIG_VIDEO_WM8775=m
CONFIG_VIDEO_WM8739=m
CONFIG_VIDEO_CX2341X=m
CONFIG_VIDEO_CX25840=m
CONFIG_VIDEO_SAA711X=m
CONFIG_VIDEO_SAA7127=m
CONFIG_VIDEO_UPD64031A=m
CONFIG_VIDEO_UPD64083=m
#
# V4L USB devices
#
CONFIG_VIDEO_PVRUSB2=m
CONFIG_VIDEO_PVRUSB2_24XXX=y
CONFIG_VIDEO_PVRUSB2_SYSFS=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set
CONFIG_VIDEO_EM28XX=m
CONFIG_VIDEO_USBVIDEO=m
CONFIG_USB_VICAM=m
CONFIG_USB_IBMCAM=m
CONFIG_USB_KONICAWC=m
CONFIG_USB_QUICKCAM_MESSENGER=m
CONFIG_USB_ET61X251=m
CONFIG_VIDEO_OVCAMCHIP=m
CONFIG_USB_W9968CF=m
CONFIG_USB_OV511=m
CONFIG_USB_SE401=m
CONFIG_USB_SN9C102=m
CONFIG_USB_STV680=m
CONFIG_USB_ZC0301=m
CONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not set
#
# Radio Adapters
#
CONFIG_RADIO_GEMTEK_PCI=m
CONFIG_RADIO_MAXIRADIO=m
CONFIG_RADIO_MAESTRO=m
CONFIG_USB_DSBR=m
#
# Digital Video Broadcasting Devices
#
CONFIG_DVB=y
CONFIG_DVB_CORE=m
#
# Supported SAA7146 based PCI Adapters
#
CONFIG_DVB_AV7110=m
CONFIG_DVB_AV7110_OSD=y
CONFIG_DVB_BUDGET=m
CONFIG_DVB_BUDGET_CI=m
CONFIG_DVB_BUDGET_AV=m
CONFIG_DVB_BUDGET_PATCH=m
#
# Supported USB Adapters
#
CONFIG_DVB_USB=m
# CONFIG_DVB_USB_DEBUG is not set
CONFIG_DVB_USB_A800=m
CONFIG_DVB_USB_DIBUSB_MB=m
# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set
CONFIG_DVB_USB_DIBUSB_MC=m
CONFIG_DVB_USB_UMT_010=m
CONFIG_DVB_USB_CXUSB=m
CONFIG_DVB_USB_DIGITV=m
CONFIG_DVB_USB_VP7045=m
CONFIG_DVB_USB_VP702X=m
CONFIG_DVB_USB_GP8PSK=m
CONFIG_DVB_USB_NOVA_T_USB2=m
CONFIG_DVB_USB_DTT200U=m
CONFIG_DVB_TTUSB_BUDGET=m
CONFIG_DVB_TTUSB_DEC=m
CONFIG_DVB_CINERGYT2=m
CONFIG_DVB_CINERGYT2_TUNING=y
CONFIG_DVB_CINERGYT2_STREAM_URB_COUNT=32
CONFIG_DVB_CINERGYT2_STREAM_BUF_SIZE=512
CONFIG_DVB_CINERGYT2_QUERY_INTERVAL=250
CONFIG_DVB_CINERGYT2_ENABLE_RC_INPUT_DEVICE=y
CONFIG_DVB_CINERGYT2_RC_QUERY_INTERVAL=100
#
# Supported FlexCopII (B2C2) Adapters
#
CONFIG_DVB_B2C2_FLEXCOP=m
CONFIG_DVB_B2C2_FLEXCOP_PCI=m
CONFIG_DVB_B2C2_FLEXCOP_USB=m
# CONFIG_DVB_B2C2_FLEXCOP_DEBUG is not set
#
# Supported BT878 Adapters
#
CONFIG_DVB_BT8XX=m
#
# Supported Pluto2 Adapters
#
CONFIG_DVB_PLUTO2=m
#
# Supported DVB Frontends
#
#
# Customise DVB Frontends
#
#
# DVB-S (satellite) frontends
#
CONFIG_DVB_STV0299=m
CONFIG_DVB_CX24110=m
CONFIG_DVB_CX24123=m
CONFIG_DVB_TDA8083=m
CONFIG_DVB_MT312=m
CONFIG_DVB_VES1X93=m
CONFIG_DVB_S5H1420=m
#
# DVB-T (terrestrial) frontends
#
CONFIG_DVB_SP8870=m
CONFIG_DVB_SP887X=m
CONFIG_DVB_CX22700=m
CONFIG_DVB_CX22702=m
CONFIG_DVB_L64781=m
CONFIG_DVB_TDA1004X=m
CONFIG_DVB_NXT6000=m
CONFIG_DVB_MT352=m
CONFIG_DVB_ZL10353=m
CONFIG_DVB_DIB3000MB=m
CONFIG_DVB_DIB3000MC=m
#
# DVB-C (cable) frontends
#
CONFIG_DVB_VES1820=m
CONFIG_DVB_TDA10021=m
CONFIG_DVB_STV0297=m
#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends
#
CONFIG_DVB_NXT200X=m
CONFIG_DVB_OR51211=m
CONFIG_DVB_OR51132=m
CONFIG_DVB_BCM3510=m
CONFIG_DVB_LGDT330X=m
#
# Miscellaneous devices
#
CONFIG_DVB_PLL=m
CONFIG_DVB_LNBP21=m
CONFIG_DVB_ISL6421=m
CONFIG_VIDEO_SAA7146=m
CONFIG_VIDEO_SAA7146_VV=m
CONFIG_VIDEO_VIDEOBUF=m
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEO_BUF=m
CONFIG_VIDEO_BUF_DVB=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_IR=m
CONFIG_VIDEO_TVEEPROM=m
CONFIG_USB_DABUSB=m
#
# Graphics support
#
# CONFIG_FIRMWARE_EDID is not set
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
CONFIG_FB_CIRRUS=m
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=m
CONFIG_FB_VESA=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
CONFIG_FB_NVIDIA=m
CONFIG_FB_NVIDIA_I2C=y
CONFIG_FB_RIVA=m
# CONFIG_FB_RIVA_I2C is not set
# CONFIG_FB_RIVA_DEBUG is not set
CONFIG_FB_INTEL=m
# CONFIG_FB_INTEL_DEBUG is not set
CONFIG_FB_MATROX=m
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MAVEN=m
CONFIG_FB_MATROX_MULTIHEAD=y
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=m
CONFIG_FB_ATY=m
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_SAVAGE=m
CONFIG_FB_SAVAGE_I2C=y
CONFIG_FB_SAVAGE_ACCEL=y
# CONFIG_FB_SIS is not set
CONFIG_FB_NEOMAGIC=m
CONFIG_FB_KYRO=m
CONFIG_FB_3DFX=m
CONFIG_FB_3DFX_ACCEL=y
# CONFIG_FB_VOODOO1 is not set
CONFIG_FB_TRIDENT=m
CONFIG_FB_TRIDENT_ACCEL=y
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Logo configuration
#
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_DEVICE=y
CONFIG_LCD_CLASS_DEVICE=m
CONFIG_LCD_DEVICE=y
#
# Sound
#
CONFIG_SOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
CONFIG_SND_DYNAMIC_MINORS=y
# CONFIG_SND_SUPPORT_OLD_API is not set
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_OPL3_LIB=m
CONFIG_SND_VX_LIB=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_AC97_BUS=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
# CONFIG_SND_SERIAL_U16550 is not set
CONFIG_SND_MPU401=m
#
# PCI devices
#
CONFIG_SND_AD1889=m
CONFIG_SND_ALS300=m
CONFIG_SND_ALS4000=m
CONFIG_SND_ALI5451=m
CONFIG_SND_ATIIXP=m
CONFIG_SND_ATIIXP_MODEM=m
CONFIG_SND_AU8810=m
CONFIG_SND_AU8820=m
CONFIG_SND_AU8830=m
CONFIG_SND_AZT3328=m
CONFIG_SND_BT87X=m
# CONFIG_SND_BT87X_OVERCLOCK is not set
CONFIG_SND_CA0106=m
CONFIG_SND_CMIPCI=m
CONFIG_SND_CS4281=m
CONFIG_SND_CS46XX=m
CONFIG_SND_CS46XX_NEW_DSP=y
CONFIG_SND_DARLA20=m
CONFIG_SND_GINA20=m
CONFIG_SND_LAYLA20=m
CONFIG_SND_DARLA24=m
CONFIG_SND_GINA24=m
CONFIG_SND_LAYLA24=m
CONFIG_SND_MONA=m
CONFIG_SND_MIA=m
CONFIG_SND_ECHO3G=m
CONFIG_SND_INDIGO=m
CONFIG_SND_INDIGOIO=m
CONFIG_SND_INDIGODJ=m
CONFIG_SND_EMU10K1=m
CONFIG_SND_EMU10K1X=m
CONFIG_SND_ENS1370=m
CONFIG_SND_ENS1371=m
CONFIG_SND_ES1938=m
CONFIG_SND_ES1968=m
CONFIG_SND_FM801=m
CONFIG_SND_FM801_TEA575X_BOOL=y
CONFIG_SND_FM801_TEA575X=m
CONFIG_SND_HDA_INTEL=m
CONFIG_SND_HDSP=m
CONFIG_SND_HDSPM=m
CONFIG_SND_ICE1712=m
CONFIG_SND_ICE1724=m
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
CONFIG_SND_KORG1212=m
CONFIG_SND_MAESTRO3=m
CONFIG_SND_MIXART=m
CONFIG_SND_NM256=m
CONFIG_SND_PCXHR=m
CONFIG_SND_RIPTIDE=m
CONFIG_SND_RME32=m
CONFIG_SND_RME96=m
CONFIG_SND_RME9652=m
CONFIG_SND_SONICVIBES=m
CONFIG_SND_TRIDENT=m
CONFIG_SND_VIA82XX=m
CONFIG_SND_VIA82XX_MODEM=m
CONFIG_SND_VX222=m
CONFIG_SND_YMFPCI=m
#
# USB devices
#
CONFIG_SND_USB_AUDIO=m
CONFIG_SND_USB_USX2Y=m
#
# PCMCIA devices
#
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_PDAUDIOCF is not set
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_ISP116X_HCD=m
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_SL811_HCD=m
CONFIG_USB_SL811_CS=m
#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#
#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_STORAGE_ALAUDA=y
# CONFIG_USB_LIBUSUAL is not set
#
# USB Input Devices
#
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
CONFIG_HID_FF=y
CONFIG_HID_PID=y
CONFIG_LOGITECH_FF=y
CONFIG_THRUSTMASTER_FF=y
CONFIG_USB_HIDDEV=y
CONFIG_USB_AIPTEK=m
CONFIG_USB_WACOM=m
CONFIG_USB_ACECAD=m
CONFIG_USB_KBTAB=m
CONFIG_USB_POWERMATE=m
CONFIG_USB_TOUCHSCREEN=m
CONFIG_USB_TOUCHSCREEN_EGALAX=y
CONFIG_USB_TOUCHSCREEN_PANJIT=y
CONFIG_USB_TOUCHSCREEN_3M=y
CONFIG_USB_TOUCHSCREEN_ITM=y
# CONFIG_USB_YEALINK is not set
CONFIG_USB_XPAD=m
CONFIG_USB_ATI_REMOTE=m
CONFIG_USB_ATI_REMOTE2=m
CONFIG_USB_KEYSPAN_REMOTE=m
CONFIG_USB_APPLETOUCH=m
#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m
#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_NET_ZAURUS=m
CONFIG_USB_MON=y
#
# USB port drivers
#
CONFIG_USB_USS720=m
#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_AIRPRIME=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP2101=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_FUNSOFT=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KEYSPAN_MPR=y
CONFIG_USB_SERIAL_KEYSPAN_USA28=y
CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
CONFIG_USB_SERIAL_KEYSPAN_USA19=y
CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_HP4X=m
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_EZUSB=y
#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_AUERSWALD=m
CONFIG_USB_RIO500=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
CONFIG_USB_LED=m
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
CONFIG_USB_PHIDGETKIT=m
CONFIG_USB_PHIDGETSERVO=m
CONFIG_USB_IDMOUSE=m
CONFIG_USB_APPLEDISPLAY=m
CONFIG_USB_SISUSBVGA=m
CONFIG_USB_SISUSBVGA_CON=y
CONFIG_USB_LD=m
# CONFIG_USB_TEST is not set
#
# USB DSL modem support
#
CONFIG_USB_ATM=m
CONFIG_USB_SPEEDTOUCH=m
CONFIG_USB_CXACRU=m
CONFIG_USB_UEAGLEATM=m
CONFIG_USB_XUSBATM=m
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# MMC/SD Card support
#
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
CONFIG_MMC_BLOCK=m
CONFIG_MMC_SDHCI=m
CONFIG_MMC_WBSD=m
#
# LED devices
#
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
#
# LED drivers
#
#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_HEARTBEAT=m
#
# InfiniBand support
#
CONFIG_INFINIBAND=m
CONFIG_INFINIBAND_USER_MAD=m
CONFIG_INFINIBAND_USER_ACCESS=m
CONFIG_INFINIBAND_ADDR_TRANS=y
CONFIG_INFINIBAND_MTHCA=m
CONFIG_INFINIBAND_MTHCA_DEBUG=y
CONFIG_INFINIBAND_IPOIB=m
CONFIG_INFINIBAND_IPOIB_DEBUG=y
CONFIG_INFINIBAND_IPOIB_DEBUG_DATA=y
CONFIG_INFINIBAND_SRP=m
CONFIG_INFINIBAND_ISER=m
#
# EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
#
CONFIG_EDAC=y
#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_MM_EDAC=m
CONFIG_EDAC_E752X=m
CONFIG_EDAC_POLL=y
#
# Real Time Clock
#
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=m
CONFIG_RTC_INTF_PROC=m
CONFIG_RTC_INTF_DEV=m
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
#
# RTC drivers
#
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_PCF8563=m
# CONFIG_RTC_DRV_PCF8583 is not set
CONFIG_RTC_DRV_RS5C372=m
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_TEST is not set
CONFIG_RTC_DRV_V3020=m
#
# DMA Engine support
#
CONFIG_DMA_ENGINE=y
#
# DMA Clients
#
CONFIG_NET_DMA=y
#
# DMA Devices
#
CONFIG_INTEL_IOATDMA=m
#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
#
# File systems
#
CONFIG_EXT2_FS=m
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT2_FS_XIP=y
CONFIG_FS_XIP=y
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=m
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
CONFIG_XFS_QUOTA=y
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
# CONFIG_XFS_RT is not set
CONFIG_OCFS2_FS=m
# CONFIG_OCFS2_DEBUG_MASKLOG is not set
CONFIG_MINIX_FS=m
CONFIG_ROMFS_FS=m
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="ascii"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
CONFIG_CONFIGFS_FS=m
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
CONFIG_AFFS_FS=m
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_BEFS_FS=m
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=m
CONFIG_EFS_FS=m
# CONFIG_JFFS_FS is not set
CONFIG_JFFS2_FS=m
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
CONFIG_JFFS2_SUMMARY=y
CONFIG_JFFS2_FS_XATTR=y
CONFIG_JFFS2_FS_POSIX_ACL=y
CONFIG_JFFS2_FS_SECURITY=y
# CONFIG_JFFS2_COMPRESSION_OPTIONS is not set
CONFIG_JFFS2_ZLIB=y
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
CONFIG_CRAMFS=m
CONFIG_VXFS_FS=m
# CONFIG_HPFS_FS is not set
CONFIG_QNX4FS_FS=m
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_UFS_DEBUG is not set
#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_RPCSEC_GSS_SPKM3=m
# CONFIG_SMB_FS is not set
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
CONFIG_CIFS_WEAK_PW_HASH=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
CONFIG_NCP_FS=m
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
CONFIG_NCPFS_SMALLDOS=y
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
CONFIG_CODA_FS=m
# CONFIG_CODA_FS_OLD_API is not set
# CONFIG_AFS_FS is not set
CONFIG_9P_FS=m
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
CONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not set
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m
#
# Instrumentation Support
#
CONFIG_PROFILING=y
CONFIG_OPROFILE=m
CONFIG_KPROBES=y
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_LOG_BUF_SHIFT=17
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHEDSTATS=y
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_RWSEMS is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_FS=y
# CONFIG_DEBUG_VM is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_UNWIND_INFO is not set
# CONFIG_FORCED_INLINING is not set
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_DEBUG_RODATA=y
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_STACK_USAGE is not set
#
# Security options
#
CONFIG_KEYS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=y
CONFIG_SECURITY_CAPABILITIES=y
# CONFIG_SECURITY_ROOTPLUG is not set
# CONFIG_SECURITY_SECLVL is not set
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
# CONFIG_SECURITY_SELINUX_ENABLE_SECMARK_DEFAULT is not set
#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_X86_64=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_TEST is not set
#
# Hardware crypto devices
#
CONFIG_XEN=y
CONFIG_XEN_INTERFACE_VERSION=0x00030207
#
# XEN
#
CONFIG_XEN_PRIVILEGED_GUEST=y
# CONFIG_XEN_UNPRIVILEGED_GUEST is not set
CONFIG_XEN_PRIVCMD=y
CONFIG_XEN_XENBUS_DEV=y
CONFIG_XEN_NETDEV_ACCEL_SFC_UTIL=m
CONFIG_XEN_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=m
CONFIG_XEN_BLKDEV_TAP=m
CONFIG_XEN_NETDEV_BACKEND=m
# CONFIG_XEN_NETDEV_PIPELINED_TRANSMITTER is not set
CONFIG_XEN_NETDEV_LOOPBACK=m
CONFIG_XEN_PCIDEV_BACKEND=y
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
# CONFIG_XEN_PCIDEV_BE_DEBUG is not set
# CONFIG_XEN_TPMDEV_BACKEND is not set
CONFIG_XEN_SCSI_BACKEND=m
CONFIG_XEN_USB_BACKEND=m
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_XEN_NETDEV_ACCEL_SFC_FRONTEND=m
CONFIG_XEN_SCSI_FRONTEND=m
CONFIG_XEN_USB_FRONTEND=m
CONFIG_XEN_USB_FRONTEND_HCD_STATS=y
CONFIG_XEN_GRANT_DEV=y
CONFIG_XEN_FRAMEBUFFER=y
CONFIG_XEN_KEYBOARD=y
CONFIG_XEN_SCRUB_PAGES=y
# CONFIG_XEN_DISABLE_SERIAL is not set
CONFIG_XEN_SYSFS=y
CONFIG_XEN_COMPAT_030002_AND_LATER=y
# CONFIG_XEN_COMPAT_030004_AND_LATER is not set
# CONFIG_XEN_COMPAT_030100_AND_LATER is not set
# CONFIG_XEN_COMPAT_LATEST_ONLY is not set
CONFIG_XEN_COMPAT=0x030002
CONFIG_HAVE_IRQ_IGNORE_UNHANDLED=y
CONFIG_NO_IDLE_HZ=y
CONFIG_XEN_SMPBOOT=y
CONFIG_XEN_BALLOON=y
CONFIG_XEN_DEVMEM=y
#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_REED_SOLOMON=m
CONFIG_REED_SOLOMON_DEC16=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_PLIST=y
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: RE: xen-unstable pci passthrough
2009-09-03 15:07 ` djmagee
@ 2009-09-03 15:58 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 16:12 ` djmagee
2009-09-09 19:02 ` RE: xen-unstable gfx passthrough (was xen-unstable pci passthrough) djmagee
1 sibling, 1 reply; 39+ messages in thread
From: Mr. Teo En Ming (Zhang Enming) @ 2009-09-03 15:58 UTC (permalink / raw)
To: djmagee; +Cc: xen-devel, Han, Weidong
[-- Attachment #1.1: Type: text/plain, Size: 6495 bytes --]
Dear Magee,
Just to confirm, are you using Intel DQ45CB? As there are already too
many postings in this xen-devel mailing list, it is difficult to go back
to check.
So you are using PCI-e x16 as primary video controller? If you want to
try 2.6.18.8 non-pvops dom0 kernel, you can use my kernel config which I
have just posted earlier.
Do share with us the results.
Thank you!
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/03/2009 11:07 PM, djmagee@mageenet.net wrote:
>
> 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.
>
> *From:* Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
> *Sent:* Thursday, September 03, 2009 12:12 AM
> *To:* djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
> *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@hotmail.com
>
> ------------------------------------------------------------------------
>
> *From:* xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net
> *Sent:* Wednesday, September 02, 2009 6:59 PM
> *To:* Han, Weidong; xen-devel@lists.xensource.com
> *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@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Han, Weidong
> *Sent:* Tuesday, September 01, 2009 6:55 PM
> *To:* djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
> *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@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net
> *Sent:* 2009年9月2日 6:40
> *To:* xen-devel@lists.xensource.com
> *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@mageenet.net <mailto:djmagee@mageenet.net>
>
> 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
>
[-- Attachment #1.2: Type: text/html, Size: 19297 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-03 15:58 ` Mr. Teo En Ming (Zhang Enming)
@ 2009-09-03 16:12 ` djmagee
2009-09-03 16:16 ` Mr. Teo En Ming (Zhang Enming)
0 siblings, 1 reply; 39+ messages in thread
From: djmagee @ 2009-09-03 16:12 UTC (permalink / raw)
To: enming.teo; +Cc: xen-devel, Han, Weidong
[-- Attachment #1.1: Type: text/plain, Size: 6935 bytes --]
Yes, that’s the board I’m using (BIOS 0085, I know there’s a newer one, but the release notes made no mention of VT-d), along with an ATI HD4770. The 4770 is the primary controller.
I’ll try your kernel config later. I must have something misconfigured because it casues a kernel panic with the bridge-utils in fedora 9, and has similar (though less fatal) problems using the bridgeutils in centos 5.2, referring to some undefined symbol at module insertion.
From: Mr. Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
Sent: Thursday, September 03, 2009 11:59 AM
To: djmagee@mageenet.net
Cc: Han, Weidong; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] RE: xen-unstable pci passthrough
Dear Magee,
Just to confirm, are you using Intel DQ45CB? As there are already too many postings in this xen-devel mailing list, it is difficult to go back to check.
So you are using PCI-e x16 as primary video controller? If you want to try 2.6.18.8 non-pvops dom0 kernel, you can use my kernel config which I have just posted earlier.
Do share with us the results.
Thank you!
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/03/2009 11:07 PM, djmagee@mageenet.net wrote:
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.
From: Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
Sent: Thursday, September 03, 2009 12:12 AM
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
________________________________
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net
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
[-- Attachment #1.2: Type: text/html, Size: 21191 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: RE: xen-unstable pci passthrough
2009-09-03 16:12 ` djmagee
@ 2009-09-03 16:16 ` Mr. Teo En Ming (Zhang Enming)
0 siblings, 0 replies; 39+ messages in thread
From: Mr. Teo En Ming (Zhang Enming) @ 2009-09-03 16:16 UTC (permalink / raw)
To: djmagee; +Cc: xen-devel, Han, Weidong
[-- Attachment #1.1: Type: text/plain, Size: 8478 bytes --]
You can try flashing it to bios version 0093. It is the latest I think.
I downloaded the bios image ISO from Intel website.
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/04/2009 12:12 AM, djmagee@mageenet.net wrote:
>
> Yes, that’s the board I’m using (BIOS 0085, I know there’s a newer
> one, but the release notes made no mention of VT-d), along with an ATI
> HD4770. The 4770 is the primary controller.
>
> I’ll try your kernel config later. I must have something misconfigured
> because it casues a kernel panic with the bridge-utils in fedora 9,
> and has similar (though less fatal) problems using the bridgeutils in
> centos 5.2, referring to some undefined symbol at module insertion.
>
> *From:* Mr. Teo En Ming (Zhang Enming)
> [mailto:enming.teo@asiasoftsea.net]
> *Sent:* Thursday, September 03, 2009 11:59 AM
> *To:* djmagee@mageenet.net
> *Cc:* Han, Weidong; xen-devel@lists.xensource.com
> *Subject:* Re: [Xen-devel] RE: xen-unstable pci passthrough
>
> Dear Magee,
>
> Just to confirm, are you using Intel DQ45CB? As there are already too
> many postings in this xen-devel mailing list, it is difficult to go
> back to check.
>
> So you are using PCI-e x16 as primary video controller? If you want to
> try 2.6.18.8 non-pvops dom0 kernel, you can use my kernel config which
> I have just posted earlier.
>
> Do share with us the results.
>
> Thank you!
>
> --
> 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
> Company Website: http://www.asiasoft.sg/
> Mobile: +65-9648-9798
> MSN: teoenming@hotmail.com <mailto:teoenming@hotmail.com>
> Alma Maters: Singapore Polytechnic, National University of Singapore
>
>
>
> On 09/03/2009 11:07 PM, djmagee@mageenet.net
> <mailto:djmagee@mageenet.net> wrote:
>
> 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.
>
> *From:* Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
> *Sent:* Thursday, September 03, 2009 12:12 AM
> *To:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>; 'Han,
> Weidong'; xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
> *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@hotmail.com <mailto:teoenming@hotmail.com>
>
> ------------------------------------------------------------------------
>
> *From:* xen-devel-bounces@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net <mailto:djmagee@mageenet.net>
> *Sent:* Wednesday, September 02, 2009 6:59 PM
> *To:* Han, Weidong; xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
> *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@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Han, Weidong
> *Sent:* Tuesday, September 01, 2009 6:55 PM
> *To:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>;
> 'xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>'
> *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@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net <mailto:djmagee@mageenet.net>
> *Sent:* 2009年9月2日 6:40
> *To:* xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>
> *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@mageenet.net <mailto:djmagee@mageenet.net>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date:
> 09/01/09 20:03:00
>
[-- Attachment #1.2: Type: text/html, Size: 21649 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: xen-unstable pci passthrough
2009-09-03 9:42 ` Han, Weidong
2009-09-03 9:50 ` Teo En Ming (Zhang Enming)
@ 2009-09-03 19:07 ` Tim Moore
2009-09-03 20:29 ` Mr. Teo En Ming (Zhang Enming)
2009-09-04 0:03 ` Han, Weidong
2009-09-10 10:20 ` Tim Moore
2 siblings, 2 replies; 39+ messages in thread
From: Tim Moore @ 2009-09-03 19:07 UTC (permalink / raw)
To: 'Han, Weidong'; +Cc: 'xen-devel@lists.xensource.com'
[-- Attachment #1.1: Type: text/plain, Size: 7620 bytes --]
Hi Weidong,
Thanks for your replies...
I now have Windows XP DomU with Primary VGA , USB Keyboard + Mouse Passthrough. I am using 2.6.30-rc3 pvops with netbk vif.
Primary VGA is Nvidia Geforce GTX260
The DomU has hangs/locks with any graphics intensive operations, i.e. Opening Internet Explorer on the MSN homepage makes DomU freeze !!
I noticed in the attached qemu log that the some of the memory addresses are not the same as the lspci output:
pt_register_regions: IO region registered (size=0x01000000 base_addr=0xb6000000)
pt_register_regions: IO region registered (size=0x10000000 base_addr=0xe000000c)
pt_register_regions: IO region registered (size=0x02000000 base_addr=0xb4000004)
02:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce GTX 260] (rev a1) (prog-if 00 [VGA controller])
Subsystem: nVidia Corporation Device 068e
Flags: bus master, fast devsel, latency 0, IRQ 11
[virtual] Memory at b6000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at b4000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at 3000 [size=128]
Is this expected ?
Would you have any idea why this would be so unstable / crash ?
Also, the Mouse is passthrough using usbdevice=”host:##:##”, but has a really bad lag/delay on refresh .. can this be helped ?
Cheers,
Tim
From: Han, Weidong [mailto:weidong.han@intel.com]
Sent: 03 September 2009 10:43
To: Tim Moore
Cc: 'enming.teo@asiasoftsea.net'; 'djmagee@mageenet.net'; 'xen-devel@lists.xensource.com'
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
Tim,
See my comments belew.
________________________________
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: 2009年9月3日 17:03
To: Han, Weidong
Cc: 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net; xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
________________________________
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net<mailto:djmagee@mageenet.net>
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
[-- Attachment #1.2: Type: text/html, Size: 28915 bytes --]
[-- Attachment #2: qemu-dm-WinXP.log --]
[-- Type: application/octet-stream, Size: 3125 bytes --]
domid: 12
qemu: the number of cpus is 1
Discrete graphics card assignment
config qemu network with xen bridge for tap12.0 xenbr0
Watching /local/domain/0/device-model/12/logdirty/next-active
Watching /local/domain/0/device-model/12/command
char device redirected to /dev/pts/1
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 92eb6ba2-3797-375d-e2d1-b20b41ed66d1
Time offset set 0
Register xen platform.
Done register platform.
xs_read(/vm/92eb6ba2-3797-375d-e2d1-b20b41ed66d1/log-throttling): read error
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/12/xen_extended_power_mgmt): read error
husb: open device 5.3
husb: config #1 need -1
husb: 2 interfaces claimed for configuration 1
husb: grabbed usb device 5.3
xs_read(): vncpasswd get error. /vm/92eb6ba2-3797-375d-e2d1-b20b41ed66d1/vncpasswd.
medium change watch on `hdc' (index: 1):
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 02:00.0 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x2:0x0.0x0
pt_register_regions: IO region registered (size=0x01000000 base_addr=0xb6000000)
pt_register_regions: IO region registered (size=0x10000000 base_addr=0xe000000c)
pt_register_regions: IO region registered (size=0x02000000 base_addr=0xb4000004)
pt_register_regions: IO region registered (size=0x00000080 base_addr=0x00003001)
gfx_claim_vga_cycle: bridge for bus 7, previous bridge control is 0
gfx_claim_vga_cycle: bus=0x0, dev=0x1e, func=0x0
gfx_claim_vga_cycle: bridge for bus 7, updated bridge control is 0
gfx_claim_vga_cycle: bridge for bus 3, previous bridge control is 0
gfx_claim_vga_cycle: bus=0x0, dev=0x7, func=0x0
gfx_claim_vga_cycle: bridge for bus 3, updated bridge control is 0
gfx_claim_vga_cycle: bridge for bus 2, previous bridge control is 18
gfx_claim_vga_cycle: bus=0x0, dev=0x3, func=0x0
gfx_claim_vga_cycle: bridge for bus 2, updated bridge control is 18
gfx_claim_vga_cycle: bridge for bus 1, previous bridge control is 0
gfx_claim_vga_cycle: bus=0x0, dev=0x1, func=0x0
gfx_claim_vga_cycle: bridge for bus 1, updated bridge control is 0
gfx_claim_vga_cycle: previous igd control is d1
gfx_claim_vga_cycle: updated igd control is d3
pt_msi_setup: msi mapped with pirq 1f
register_real_device: Real physical device 02:00.0 registered successfuly!
IRQ type = MSI-INTx
pt_bar_reg_read: first read BARs of gfx
pt_iomem_map: e_phys=b6000000 maddr=b6000000 type=0 len=16777216 index=0 first_map=1
pt_bar_reg_read: first read BARs of gfx
pt_iomem_map: e_phys=e0000000 maddr=e0000000 type=8 len=268435456 index=1 first_map=1
pt_bar_reg_read: first read BARs of gfx
pt_bar_reg_read: first read BARs of gfx
pt_iomem_map: e_phys=b4000000 maddr=b4000000 type=0 len=33554432 index=3 first_map=1
pt_bar_reg_read: first read BARs of gfx
pt_bar_reg_read: first read BARs of gfx
pt_ioport_map: e_phys=3000 pio_base=3000 len=128 index=5 first_map=1
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: xen-unstable pci passthrough
2009-09-03 19:07 ` Tim Moore
@ 2009-09-03 20:29 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 20:34 ` Tim Moore
` (2 more replies)
2009-09-04 0:03 ` Han, Weidong
1 sibling, 3 replies; 39+ messages in thread
From: Mr. Teo En Ming (Zhang Enming) @ 2009-09-03 20:29 UTC (permalink / raw)
To: timothy.moore
Cc: 'xen-devel@lists.xensource.com', 'Han, Weidong'
[-- Attachment #1.1: Type: text/plain, Size: 10985 bytes --]
VGA Passthrough to Windows XP Home 32-bit HVM DomU SUCCESS!!!
A big thanks to Weidong and other engineers at Intel for the VGA
passthrough patches to xen 3.5-unstable, and other gurus here at
xen-devel mailing list for your kind assistance and help along the way.
I had abandoned the idea of booting up the onboard Intel GMA4500
graphics as the primary video adapter for dom0 and passing through the
secondary nVidia Geforce 8400 GS PCI-e x16 graphics to Win XP Home DomU.
I should have listened to Magee's advice earlier that both onboard and
pci-e graphics could not be operated simultaneously at the same time due
to lack of pci-e lanes on Intel DQ45CB.
After Timothy stressed on Magee's advice just now, I have totally
changed my approach. Now, I boot up the nVidia Geforce 8400 GS PCI-e x16
as the primary video adapter with-out any secondary video adapter.
I applied Weidong's xen-gfx-passthrough.patch,
qemu-gfx-passthrough.patch, xen-load-vbios-file.patch,
xen-vbar-pbar.patch, and qemu-vbar-pbar.patch to xen 3.5-unstable
changeset 20143 successfully. I skipped
qemu-claim-vga-cycle-secondary-gfx-passthrough.patch. Using this
approach, I am still loading the vga bios of nVidia Geforce 8400 GS from
firmware file. And I am using the Version 1 Intel gfx passthrough patches.
The pvops dom 0 kernel I am using is 2.6.31-rc6.
Before rebooting, I appended "blacklist nvidia" to
/etc/modprobe.d/blacklist.conf to prevent the nvidia driver from loading.
After rebooting, I hide nVidia Geforce 8400 GS from Dom 0 using Xen VT-d
wiki instructions. Then I started Windows XP Home 32-bit HVM Guest with
1 VCPU.
Windows XP Home HVM DomU successfully boots up!!! Emulated VGA is
disabled. Only nVidia Geforce 8400 GS shows up in Device Manager.
This time, instead of showing nVidia Geforce 8400 GS cannot start and no
resources, it shows there are NOT ENOUGH resources. There is still an
exclamation mark beside nvidia 8400 GS.
I tried to passthrough USB Keyboard and USB mouse using the following
config but with-out success:
usb = 1
usbdevice = [ 'host:vendorid:productid', 'host:vendorid:productid' ]
So I had to vnc into my Windows XP HVM domU.
Thank you Weidong and other engineers at Intel for the vga passthrough
patches!!!
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/04/2009 03:07 AM, Tim Moore wrote:
>
> Hi Weidong,
>
> Thanks for your replies...
>
> I now have Windows XP DomU with Primary VGA , USB Keyboard + Mouse
> Passthrough. I am using 2.6.30-rc3 pvops with netbk vif.
>
> Primary VGA is Nvidia Geforce GTX260
>
> The DomU has hangs/locks with any graphics intensive operations, i.e.
> Opening Internet Explorer on the MSN homepage makes DomU freeze !!
>
> I noticed in the attached qemu log that the some of the memory
> addresses are not the same as the lspci output:
>
> pt_register_regions: IO region registered (size=0x01000000
> base_addr=0xb6000000)
>
> pt_register_regions: IO region registered (size=0x10000000
> base_addr=*0xe000000c*)
>
> pt_register_regions: IO region registered (size=0x02000000
> base_addr=*0xb4000004*)
>
> 02:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce
> GTX 260] (rev a1) (prog-if 00 [VGA controller])
>
> Subsystem: nVidia Corporation Device 068e
>
> Flags: bus master, fast devsel, latency 0, IRQ 11
>
> [virtual] Memory at b6000000 (32-bit, non-prefetchable) [size=16M]
>
> Memory at *e0000000* (64-bit, prefetchable) [size=256M]
>
> Memory at *b4000000* (64-bit, non-prefetchable) [size=32M]
>
> I/O ports at 3000 [size=128]
>
> Is this expected ?
>
> Would you have any idea why this would be so unstable / crash ?
>
> Also, the Mouse is passthrough using usbdevice=”host:##:##”, but has a
> really bad lag/delay on refresh .. can this be helped ?
>
> Cheers,
> Tim
>
> *From:* Han, Weidong [mailto:weidong.han@intel.com]
> *Sent:* 03 September 2009 10:43
> *To:* Tim Moore
> *Cc:* 'enming.teo@asiasoftsea.net'; 'djmagee@mageenet.net';
> 'xen-devel@lists.xensource.com'
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> Tim,
>
> See my comments belew.
>
> ------------------------------------------------------------------------
>
> *From:* Tim Moore [mailto:timothy.moore@expidas.net]
> *Sent:* 2009年9月3日 17:03
> *To:* Han, Weidong
> *Cc:* 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net;
> xen-devel@lists.xensource.com
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> 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@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Teo En
> Ming (Zhang Enming)
> *Sent:* 03 September 2009 05:12
> *To:* djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
> *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@hotmail.com
>
> ------------------------------------------------------------------------
>
> *From:* xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net
> *Sent:* Wednesday, September 02, 2009 6:59 PM
> *To:* Han, Weidong; xen-devel@lists.xensource.com
> *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@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Han, Weidong
> *Sent:* Tuesday, September 01, 2009 6:55 PM
> *To:* djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
> *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@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net
> *Sent:* 2009年9月2日 6:40
> *To:* xen-devel@lists.xensource.com
> *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@mageenet.net <mailto:djmagee@mageenet.net>
>
> 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
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
[-- Attachment #1.2: Type: text/html, Size: 34443 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: xen-unstable pci passthrough
2009-09-03 20:29 ` Mr. Teo En Ming (Zhang Enming)
@ 2009-09-03 20:34 ` Tim Moore
2009-09-03 20:41 ` Mr. Teo En Ming (Zhang Enming)
[not found] ` <14D9C9E2ED61ED41BC3B37ACDF4E880002E0C4B8F66B@heavy-vm03.heavy.org.uk>
2009-09-03 20:35 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 23:58 ` Han, Weidong
2 siblings, 2 replies; 39+ messages in thread
From: Tim Moore @ 2009-09-03 20:34 UTC (permalink / raw)
To: 'enming.teo@asiasoftsea.net'
Cc: 'xen-devel@lists.xensource.com', 'Han, Weidong'
[-- Attachment #1.1: Type: text/plain, Size: 12217 bytes --]
HI Teo,
You need the qemu-claim-vga-cycle-secondary-gfx-passthrough.patch also that’s what you seem to be missing.
Also usb device syntax should be:
usbdevice = 'host:vendorid:productid' # mouse
usbdevice = 'host:vendorid:productid' # keyboard
I also had problems with this and disabled the keyboard to allow DomU to boot, I think there is a conflict with the qemu BIOS and Legacy keyboard support ..
Therefore once the DomU has booted with Passthrough mouse and vga, I used vncviewer to get to the qemu console and enter:
usb_add host:vendorid:productid
(no quotes)
Tim
From: Mr. Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
Sent: 03 September 2009 21:29
To: Tim Moore
Cc: 'Han, Weidong'; 'xen-devel@lists.xensource.com'
Subject: Re: [Xen-devel] xen-unstable pci passthrough
VGA Passthrough to Windows XP Home 32-bit HVM DomU SUCCESS!!!
A big thanks to Weidong and other engineers at Intel for the VGA passthrough patches to xen 3.5-unstable, and other gurus here at xen-devel mailing list for your kind assistance and help along the way.
I had abandoned the idea of booting up the onboard Intel GMA4500 graphics as the primary video adapter for dom0 and passing through the secondary nVidia Geforce 8400 GS PCI-e x16 graphics to Win XP Home DomU. I should have listened to Magee's advice earlier that both onboard and pci-e graphics could not be operated simultaneously at the same time due to lack of pci-e lanes on Intel DQ45CB.
After Timothy stressed on Magee's advice just now, I have totally changed my approach. Now, I boot up the nVidia Geforce 8400 GS PCI-e x16 as the primary video adapter with-out any secondary video adapter.
I applied Weidong's xen-gfx-passthrough.patch, qemu-gfx-passthrough.patch, xen-load-vbios-file.patch, xen-vbar-pbar.patch, and qemu-vbar-pbar.patch to xen 3.5-unstable changeset 20143 successfully. I skipped qemu-claim-vga-cycle-secondary-gfx-passthrough.patch. Using this approach, I am still loading the vga bios of nVidia Geforce 8400 GS from firmware file. And I am using the Version 1 Intel gfx passthrough patches.
The pvops dom 0 kernel I am using is 2.6.31-rc6.
Before rebooting, I appended "blacklist nvidia" to /etc/modprobe.d/blacklist.conf to prevent the nvidia driver from loading.
After rebooting, I hide nVidia Geforce 8400 GS from Dom 0 using Xen VT-d wiki instructions. Then I started Windows XP Home 32-bit HVM Guest with 1 VCPU.
Windows XP Home HVM DomU successfully boots up!!! Emulated VGA is disabled. Only nVidia Geforce 8400 GS shows up in Device Manager.
This time, instead of showing nVidia Geforce 8400 GS cannot start and no resources, it shows there are NOT ENOUGH resources. There is still an exclamation mark beside nvidia 8400 GS.
I tried to passthrough USB Keyboard and USB mouse using the following config but with-out success:
usb = 1
usbdevice = [ 'host:vendorid:productid', 'host:vendorid:productid' ]
So I had to vnc into my Windows XP HVM domU.
Thank you Weidong and other engineers at Intel for the vga passthrough patches!!!
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com<mailto:teoenming@hotmail.com>
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/04/2009 03:07 AM, Tim Moore wrote:
Hi Weidong,
Thanks for your replies...
I now have Windows XP DomU with Primary VGA , USB Keyboard + Mouse Passthrough. I am using 2.6.30-rc3 pvops with netbk vif.
Primary VGA is Nvidia Geforce GTX260
The DomU has hangs/locks with any graphics intensive operations, i.e. Opening Internet Explorer on the MSN homepage makes DomU freeze !!
I noticed in the attached qemu log that the some of the memory addresses are not the same as the lspci output:
pt_register_regions: IO region registered (size=0x01000000 base_addr=0xb6000000)
pt_register_regions: IO region registered (size=0x10000000 base_addr=0xe000000c)
pt_register_regions: IO region registered (size=0x02000000 base_addr=0xb4000004)
02:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce GTX 260] (rev a1) (prog-if 00 [VGA controller])
Subsystem: nVidia Corporation Device 068e
Flags: bus master, fast devsel, latency 0, IRQ 11
[virtual] Memory at b6000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at b4000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at 3000 [size=128]
Is this expected ?
Would you have any idea why this would be so unstable / crash ?
Also, the Mouse is passthrough using usbdevice=”host:##:##”, but has a really bad lag/delay on refresh .. can this be helped ?
Cheers,
Tim
From: Han, Weidong [mailto:weidong.han@intel.com]
Sent: 03 September 2009 10:43
To: Tim Moore
Cc: 'enming.teo@asiasoftsea.net<mailto:enming.teo@asiasoftsea.net>'; 'djmagee@mageenet.net<mailto:djmagee@mageenet.net>'; 'xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>'
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
Tim,
See my comments belew.
________________________________
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: 2009年9月3日 17:03
To: Han, Weidong
Cc: 'enming.teo@asiasoftsea.net<mailto:enming.teo@asiasoftsea.net>'; djmagee@mageenet.net<mailto:djmagee@mageenet.net>; xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net<mailto:djmagee@mageenet.net>; 'Han, Weidong'; xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
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@hotmail.com<mailto:teoenming@hotmail.com>
________________________________
From: xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net<mailto:djmagee@mageenet.net>
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
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@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net<mailto:djmagee@mageenet.net>; 'xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>'
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@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net<mailto:djmagee@mageenet.net>
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
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@mageenet.net<mailto:djmagee@mageenet.net>
No virus found in this incoming message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date: 09/01/09 20:03:00
________________________________
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 35434 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: xen-unstable pci passthrough
2009-09-03 20:29 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 20:34 ` Tim Moore
@ 2009-09-03 20:35 ` Mr. Teo En Ming (Zhang Enming)
2009-09-04 0:00 ` Han, Weidong
2009-09-03 23:58 ` Han, Weidong
2 siblings, 1 reply; 39+ messages in thread
From: Mr. Teo En Ming (Zhang Enming) @ 2009-09-03 20:35 UTC (permalink / raw)
To: enming.teo
Cc: 'Han, Weidong', 'xen-devel@lists.xensource.com',
timothy.moore
[-- Attachment #1.1: Type: text/plain, Size: 12501 bytes --]
Just to add:
I did try booting up onboard graphics as the primary video controller. I
did not try to pass though nvidia gf 8400 gs to Win XP Dom U. I tried to
passthrough onboard graphics to Win XP Dom U without success.
I had tried with pvops Dom 0 2.6.30-rc3 and 2.6.31-rc6. Every time I get
some iommu fault overflow condition and then Dom 0 died.
So next I tried nvidia geforce 8400 gs as the primary. And it works.
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/04/2009 04:29 AM, Mr. Teo En Ming (Zhang Enming) wrote:
> VGA Passthrough to Windows XP Home 32-bit HVM DomU SUCCESS!!!
>
> A big thanks to Weidong and other engineers at Intel for the VGA
> passthrough patches to xen 3.5-unstable, and other gurus here at
> xen-devel mailing list for your kind assistance and help along the way.
>
> I had abandoned the idea of booting up the onboard Intel GMA4500
> graphics as the primary video adapter for dom0 and passing through the
> secondary nVidia Geforce 8400 GS PCI-e x16 graphics to Win XP Home
> DomU. I should have listened to Magee's advice earlier that both
> onboard and pci-e graphics could not be operated simultaneously at the
> same time due to lack of pci-e lanes on Intel DQ45CB.
>
> After Timothy stressed on Magee's advice just now, I have totally
> changed my approach. Now, I boot up the nVidia Geforce 8400 GS PCI-e
> x16 as the primary video adapter with-out any secondary video adapter.
>
> I applied Weidong's xen-gfx-passthrough.patch,
> qemu-gfx-passthrough.patch, xen-load-vbios-file.patch,
> xen-vbar-pbar.patch, and qemu-vbar-pbar.patch to xen 3.5-unstable
> changeset 20143 successfully. I skipped
> qemu-claim-vga-cycle-secondary-gfx-passthrough.patch. Using this
> approach, I am still loading the vga bios of nVidia Geforce 8400 GS
> from firmware file. And I am using the Version 1 Intel gfx passthrough
> patches.
>
> The pvops dom 0 kernel I am using is 2.6.31-rc6.
>
> Before rebooting, I appended "blacklist nvidia" to
> /etc/modprobe.d/blacklist.conf to prevent the nvidia driver from loading.
>
> After rebooting, I hide nVidia Geforce 8400 GS from Dom 0 using Xen
> VT-d wiki instructions. Then I started Windows XP Home 32-bit HVM
> Guest with 1 VCPU.
>
> Windows XP Home HVM DomU successfully boots up!!! Emulated VGA is
> disabled. Only nVidia Geforce 8400 GS shows up in Device Manager.
>
> This time, instead of showing nVidia Geforce 8400 GS cannot start and
> no resources, it shows there are NOT ENOUGH resources. There is still
> an exclamation mark beside nvidia 8400 GS.
>
> I tried to passthrough USB Keyboard and USB mouse using the following
> config but with-out success:
>
> usb = 1
> usbdevice = [ 'host:vendorid:productid', 'host:vendorid:productid' ]
>
> So I had to vnc into my Windows XP HVM domU.
>
> Thank you Weidong and other engineers at Intel for the vga passthrough
> patches!!!
> --
> 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
> Company Website: http://www.asiasoft.sg/
> Mobile: +65-9648-9798
> MSN: teoenming@hotmail.com
> Alma Maters: Singapore Polytechnic, National University of Singapore
>
>
> On 09/04/2009 03:07 AM, Tim Moore wrote:
>>
>> Hi Weidong,
>>
>> Thanks for your replies...
>>
>> I now have Windows XP DomU with Primary VGA , USB Keyboard + Mouse
>> Passthrough. I am using 2.6.30-rc3 pvops with netbk vif.
>>
>> Primary VGA is Nvidia Geforce GTX260
>>
>> The DomU has hangs/locks with any graphics intensive operations, i.e.
>> Opening Internet Explorer on the MSN homepage makes DomU freeze !!
>>
>> I noticed in the attached qemu log that the some of the memory
>> addresses are not the same as the lspci output:
>>
>> pt_register_regions: IO region registered (size=0x01000000
>> base_addr=0xb6000000)
>>
>> pt_register_regions: IO region registered (size=0x10000000
>> base_addr=*0xe000000c*)
>>
>> pt_register_regions: IO region registered (size=0x02000000
>> base_addr=*0xb4000004*)
>>
>> 02:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce
>> GTX 260] (rev a1) (prog-if 00 [VGA controller])
>>
>> Subsystem: nVidia Corporation Device 068e
>>
>> Flags: bus master, fast devsel, latency 0, IRQ 11
>>
>> [virtual] Memory at b6000000 (32-bit, non-prefetchable) [size=16M]
>>
>> Memory at *e0000000* (64-bit, prefetchable) [size=256M]
>>
>> Memory at *b4000000* (64-bit, non-prefetchable) [size=32M]
>>
>> I/O ports at 3000 [size=128]
>>
>> Is this expected ?
>>
>> Would you have any idea why this would be so unstable / crash ?
>>
>> Also, the Mouse is passthrough using usbdevice=”host:##:##”, but has
>> a really bad lag/delay on refresh .. can this be helped ?
>>
>> Cheers,
>> Tim
>>
>> *From:* Han, Weidong [mailto:weidong.han@intel.com]
>> *Sent:* 03 September 2009 10:43
>> *To:* Tim Moore
>> *Cc:* 'enming.teo@asiasoftsea.net'; 'djmagee@mageenet.net';
>> 'xen-devel@lists.xensource.com'
>> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>>
>> Tim,
>>
>> See my comments belew.
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Tim Moore [mailto:timothy.moore@expidas.net]
>> *Sent:* 2009年9月3日 17:03
>> *To:* Han, Weidong
>> *Cc:* 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net;
>> xen-devel@lists.xensource.com
>> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>>
>> 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@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Teo En
>> Ming (Zhang Enming)
>> *Sent:* 03 September 2009 05:12
>> *To:* djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
>> *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@hotmail.com
>>
>> ------------------------------------------------------------------------
>>
>> *From:* xen-devel-bounces@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
>> *djmagee@mageenet.net
>> *Sent:* Wednesday, September 02, 2009 6:59 PM
>> *To:* Han, Weidong; xen-devel@lists.xensource.com
>> *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@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Han,
>> Weidong
>> *Sent:* Tuesday, September 01, 2009 6:55 PM
>> *To:* djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
>> *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@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
>> *djmagee@mageenet.net
>> *Sent:* 2009年9月2日 6:40
>> *To:* xen-devel@lists.xensource.com
>> *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@mageenet.net <mailto:djmagee@mageenet.net>
>>
>> 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
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
[-- Attachment #1.2: Type: text/html, Size: 37278 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: xen-unstable pci passthrough
2009-09-03 20:34 ` Tim Moore
@ 2009-09-03 20:41 ` Mr. Teo En Ming (Zhang Enming)
[not found] ` <14D9C9E2ED61ED41BC3B37ACDF4E880002E0C4B8F66B@heavy-vm03.heavy.org.uk>
1 sibling, 0 replies; 39+ messages in thread
From: Mr. Teo En Ming (Zhang Enming) @ 2009-09-03 20:41 UTC (permalink / raw)
To: timothy.moore
Cc: 'xen-devel@lists.xensource.com', 'Han, Weidong'
[-- Attachment #1.1: Type: text/plain, Size: 14218 bytes --]
Hi Timothy,
I had success without the
qemu-claim-vga-cycle-secondary-gfx-passthrough.patch because now I don't
have secondary video adapter.
For the usb passthrough, initially I also tried
usbdevice = [ 'host:vendorid:productid' ] # mouse
usbdevice = [ 'host:vendorid:productid' ] # keyboard
but it did not work out. So I combined the two into
usbdevice = [ 'host:vendorid:productid','host:vendorid:productid' ]
but it still did not work either.
So you actually got both usb mouse and keyboard to work by first passing
thru the usb mouse and later hot plugging the usb keyboard after winxp
domU has booted.
Thanks for the tip!!! I will try it later.
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com <mailto:teoenming@hotmail.com>
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/04/2009 04:34 AM, Tim Moore wrote:
>
> HI Teo,
>
> You need the qemu-claim-vga-cycle-secondary-gfx-passthrough.patch also
> that’s what you seem to be missing.
>
> Also usb device syntax should be:
>
> usbdevice = 'host:vendorid:productid' # mouse
>
> usbdevice = 'host:vendorid:productid' # keyboard
>
> I also had problems with this and disabled the keyboard to allow DomU
> to boot, I think there is a conflict with the qemu BIOS and Legacy
> keyboard support ..
>
> Therefore once the DomU has booted with Passthrough mouse and vga, I
> used vncviewer to get to the qemu console and enter:
>
> usb_add host:vendorid:productid
>
> (no quotes)
>
> Tim
>
> *From:* Mr. Teo En Ming (Zhang Enming)
> [mailto:enming.teo@asiasoftsea.net]
> *Sent:* 03 September 2009 21:29
> *To:* Tim Moore
> *Cc:* 'Han, Weidong'; 'xen-devel@lists.xensource.com'
> *Subject:* Re: [Xen-devel] xen-unstable pci passthrough
>
> VGA Passthrough to Windows XP Home 32-bit HVM DomU SUCCESS!!!
>
> A big thanks to Weidong and other engineers at Intel for the VGA
> passthrough patches to xen 3.5-unstable, and other gurus here at
> xen-devel mailing list for your kind assistance and help along the way.
>
> I had abandoned the idea of booting up the onboard Intel GMA4500
> graphics as the primary video adapter for dom0 and passing through the
> secondary nVidia Geforce 8400 GS PCI-e x16 graphics to Win XP Home
> DomU. I should have listened to Magee's advice earlier that both
> onboard and pci-e graphics could not be operated simultaneously at the
> same time due to lack of pci-e lanes on Intel DQ45CB.
>
> After Timothy stressed on Magee's advice just now, I have totally
> changed my approach. Now, I boot up the nVidia Geforce 8400 GS PCI-e
> x16 as the primary video adapter with-out any secondary video adapter.
>
> I applied Weidong's xen-gfx-passthrough.patch,
> qemu-gfx-passthrough.patch, xen-load-vbios-file.patch,
> xen-vbar-pbar.patch, and qemu-vbar-pbar.patch to xen 3.5-unstable
> changeset 20143 successfully. I skipped
> qemu-claim-vga-cycle-secondary-gfx-passthrough.patch. Using this
> approach, I am still loading the vga bios of nVidia Geforce 8400 GS
> from firmware file. And I am using the Version 1 Intel gfx passthrough
> patches.
>
> The pvops dom 0 kernel I am using is 2.6.31-rc6.
>
> Before rebooting, I appended "blacklist nvidia" to
> /etc/modprobe.d/blacklist.conf to prevent the nvidia driver from loading.
>
> After rebooting, I hide nVidia Geforce 8400 GS from Dom 0 using Xen
> VT-d wiki instructions. Then I started Windows XP Home 32-bit HVM
> Guest with 1 VCPU.
>
> Windows XP Home HVM DomU successfully boots up!!! Emulated VGA is
> disabled. Only nVidia Geforce 8400 GS shows up in Device Manager.
>
> This time, instead of showing nVidia Geforce 8400 GS cannot start and
> no resources, it shows there are NOT ENOUGH resources. There is still
> an exclamation mark beside nvidia 8400 GS.
>
> I tried to passthrough USB Keyboard and USB mouse using the following
> config but with-out success:
>
> usb = 1
> usbdevice = [ 'host:vendorid:productid', 'host:vendorid:productid' ]
>
> So I had to vnc into my Windows XP HVM domU.
>
> Thank you Weidong and other engineers at Intel for the vga passthrough
> patches!!!
>
> --
> 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
> Company Website: http://www.asiasoft.sg/
> Mobile: +65-9648-9798
> MSN: teoenming@hotmail.com <mailto:teoenming@hotmail.com>
> Alma Maters: Singapore Polytechnic, National University of Singapore
>
>
>
> On 09/04/2009 03:07 AM, Tim Moore wrote:
>
> Hi Weidong,
>
> Thanks for your replies...
>
> I now have Windows XP DomU with Primary VGA , USB Keyboard + Mouse
> Passthrough. I am using 2.6.30-rc3 pvops with netbk vif.
>
> Primary VGA is Nvidia Geforce GTX260
>
> The DomU has hangs/locks with any graphics intensive operations, i.e.
> Opening Internet Explorer on the MSN homepage makes DomU freeze !!
>
> I noticed in the attached qemu log that the some of the memory
> addresses are not the same as the lspci output:
>
> pt_register_regions: IO region registered (size=0x01000000
> base_addr=0xb6000000)
>
> pt_register_regions: IO region registered (size=0x10000000
> base_addr=*0xe000000c*)
>
> pt_register_regions: IO region registered (size=0x02000000
> base_addr=*0xb4000004*)
>
> 02:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce
> GTX 260] (rev a1) (prog-if 00 [VGA controller])
>
> Subsystem: nVidia Corporation Device 068e
>
> Flags: bus master, fast devsel, latency 0, IRQ 11
>
> [virtual] Memory at b6000000 (32-bit, non-prefetchable) [size=16M]
>
> Memory at *e0000000* (64-bit, prefetchable) [size=256M]
>
> Memory at *b4000000* (64-bit, non-prefetchable) [size=32M]
>
> I/O ports at 3000 [size=128]
>
> Is this expected ?
>
> Would you have any idea why this would be so unstable / crash ?
>
> Also, the Mouse is passthrough using usbdevice=”host:##:##”, but has a
> really bad lag/delay on refresh .. can this be helped ?
>
> Cheers,
> Tim
>
> *From:* Han, Weidong [mailto:weidong.han@intel.com]
> *Sent:* 03 September 2009 10:43
> *To:* Tim Moore
> *Cc:* 'enming.teo@asiasoftsea.net
> <mailto:enming.teo@asiasoftsea.net>'; 'djmagee@mageenet.net
> <mailto:djmagee@mageenet.net>'; 'xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>'
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> Tim,
>
> See my comments belew.
>
> ------------------------------------------------------------------------
>
> *From:* Tim Moore [mailto:timothy.moore@expidas.net]
> *Sent:* 2009年9月3日 17:03
> *To:* Han, Weidong
> *Cc:* 'enming.teo@asiasoftsea.net
> <mailto:enming.teo@asiasoftsea.net>'; djmagee@mageenet.net
> <mailto:djmagee@mageenet.net>; xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> 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@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Teo En
> Ming (Zhang Enming)
> *Sent:* 03 September 2009 05:12
> *To:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>; 'Han,
> Weidong'; xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
> *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@hotmail.com <mailto:teoenming@hotmail.com>
>
> ------------------------------------------------------------------------
>
> *From:* xen-devel-bounces@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net <mailto:djmagee@mageenet.net>
> *Sent:* Wednesday, September 02, 2009 6:59 PM
> *To:* Han, Weidong; xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
> *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@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Han, Weidong
> *Sent:* Tuesday, September 01, 2009 6:55 PM
> *To:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>;
> 'xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>'
> *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@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net <mailto:djmagee@mageenet.net>
> *Sent:* 2009年9月2日 6:40
> *To:* xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>
> *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@mageenet.net <mailto:djmagee@mageenet.net>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date:
> 09/01/09 20:03:00
>
>
> ------------------------------------------------------------------------
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com <mailto:Xen-devel@lists.xensource.com>
> http://lists.xensource.com/xen-devel
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
[-- Attachment #1.2: Type: text/html, Size: 38145 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: xen-unstable pci passthrough
[not found] ` <14D9C9E2ED61ED41BC3B37ACDF4E880002E0C4B8F66B@heavy-vm03.heavy.org.uk>
@ 2009-09-03 20:58 ` Mr. Teo En Ming (Zhang Enming)
0 siblings, 0 replies; 39+ messages in thread
From: Mr. Teo En Ming (Zhang Enming) @ 2009-09-03 20:58 UTC (permalink / raw)
To: timothy.moore, xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 14593 bytes --]
Hi Timothy,
My Intel DQ45CB cannot have secondary video card. It is a single PCI-e
x16 while you have two PCI-e x16 slots on your motherboard.
In my case, I blacklisted nvidia video driver first before rebooting
into text mode on Dom 0. nvidia video driver will not get loaded on dom
0 then. Then I hide nvidia pci-e x16 from dom 0 directly at the virtual
terminal. I didn't use ssh from another computer.
Then I start Win XP Dom U directly at the terminal also.
I saw Boch BIOS, then Booting from Harddisk....and then saw Windows XP
Home Dom U booting up.
But when I tried to shutdown Win XP Dom U from VNC, the display hangs at
"Shutting down..."
Then I need to do a hard reset of my computer.
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/04/2009 04:45 AM, Tim Moore wrote:
>
> Teo,
>
> When I say that it works for me, I also get full VGA output on my
> Primary display from the DomU - I usually start the DomU via ssh when
> Dom0 is only in textmode.
>
> I think you need the
> qemu-claim-vga-cycle-secondary-gfx-passthrough.patch also ..
>
> Tim
>
> *From:* xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Tim Moore
> *Sent:* 03 September 2009 21:34
> *To:* 'enming.teo@asiasoftsea.net'
> *Cc:* 'xen-devel@lists.xensource.com'; 'Han, Weidong'
> *Subject:* RE: [Xen-devel] xen-unstable pci passthrough
>
> HI Teo,
>
> You need the qemu-claim-vga-cycle-secondary-gfx-passthrough.patch also
> that’s what you seem to be missing.
>
> Also usb device syntax should be:
>
> usbdevice = 'host:vendorid:productid' # mouse
>
> usbdevice = 'host:vendorid:productid' # keyboard
>
> I also had problems with this and disabled the keyboard to allow DomU
> to boot, I think there is a conflict with the qemu BIOS and Legacy
> keyboard support ..
>
> Therefore once the DomU has booted with Passthrough mouse and vga, I
> used vncviewer to get to the qemu console and enter:
>
> usb_add host:vendorid:productid
>
> (no quotes)
>
> Tim
>
> *From:* Mr. Teo En Ming (Zhang Enming)
> [mailto:enming.teo@asiasoftsea.net]
> *Sent:* 03 September 2009 21:29
> *To:* Tim Moore
> *Cc:* 'Han, Weidong'; 'xen-devel@lists.xensource.com'
> *Subject:* Re: [Xen-devel] xen-unstable pci passthrough
>
> VGA Passthrough to Windows XP Home 32-bit HVM DomU SUCCESS!!!
>
> A big thanks to Weidong and other engineers at Intel for the VGA
> passthrough patches to xen 3.5-unstable, and other gurus here at
> xen-devel mailing list for your kind assistance and help along the way.
>
> I had abandoned the idea of booting up the onboard Intel GMA4500
> graphics as the primary video adapter for dom0 and passing through the
> secondary nVidia Geforce 8400 GS PCI-e x16 graphics to Win XP Home
> DomU. I should have listened to Magee's advice earlier that both
> onboard and pci-e graphics could not be operated simultaneously at the
> same time due to lack of pci-e lanes on Intel DQ45CB.
>
> After Timothy stressed on Magee's advice just now, I have totally
> changed my approach. Now, I boot up the nVidia Geforce 8400 GS PCI-e
> x16 as the primary video adapter with-out any secondary video adapter.
>
> I applied Weidong's xen-gfx-passthrough.patch,
> qemu-gfx-passthrough.patch, xen-load-vbios-file.patch,
> xen-vbar-pbar.patch, and qemu-vbar-pbar.patch to xen 3.5-unstable
> changeset 20143 successfully. I skipped
> qemu-claim-vga-cycle-secondary-gfx-passthrough.patch. Using this
> approach, I am still loading the vga bios of nVidia Geforce 8400 GS
> from firmware file. And I am using the Version 1 Intel gfx passthrough
> patches.
>
> The pvops dom 0 kernel I am using is 2.6.31-rc6.
>
> Before rebooting, I appended "blacklist nvidia" to
> /etc/modprobe.d/blacklist.conf to prevent the nvidia driver from loading.
>
> After rebooting, I hide nVidia Geforce 8400 GS from Dom 0 using Xen
> VT-d wiki instructions. Then I started Windows XP Home 32-bit HVM
> Guest with 1 VCPU.
>
> Windows XP Home HVM DomU successfully boots up!!! Emulated VGA is
> disabled. Only nVidia Geforce 8400 GS shows up in Device Manager.
>
> This time, instead of showing nVidia Geforce 8400 GS cannot start and
> no resources, it shows there are NOT ENOUGH resources. There is still
> an exclamation mark beside nvidia 8400 GS.
>
> I tried to passthrough USB Keyboard and USB mouse using the following
> config but with-out success:
>
> usb = 1
> usbdevice = [ 'host:vendorid:productid', 'host:vendorid:productid' ]
>
> So I had to vnc into my Windows XP HVM domU.
>
> Thank you Weidong and other engineers at Intel for the vga passthrough
> patches!!!
>
> --
> 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
> Company Website: http://www.asiasoft.sg/
> Mobile: +65-9648-9798
> MSN: teoenming@hotmail.com <mailto:teoenming@hotmail.com>
> Alma Maters: Singapore Polytechnic, National University of Singapore
>
>
>
> On 09/04/2009 03:07 AM, Tim Moore wrote:
>
> Hi Weidong,
>
> Thanks for your replies...
>
> I now have Windows XP DomU with Primary VGA , USB Keyboard + Mouse
> Passthrough. I am using 2.6.30-rc3 pvops with netbk vif.
>
> Primary VGA is Nvidia Geforce GTX260
>
> The DomU has hangs/locks with any graphics intensive operations, i.e.
> Opening Internet Explorer on the MSN homepage makes DomU freeze !!
>
> I noticed in the attached qemu log that the some of the memory
> addresses are not the same as the lspci output:
>
> pt_register_regions: IO region registered (size=0x01000000
> base_addr=0xb6000000)
>
> pt_register_regions: IO region registered (size=0x10000000
> base_addr=*0xe000000c*)
>
> pt_register_regions: IO region registered (size=0x02000000
> base_addr=*0xb4000004*)
>
> 02:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce
> GTX 260] (rev a1) (prog-if 00 [VGA controller])
>
> Subsystem: nVidia Corporation Device 068e
>
> Flags: bus master, fast devsel, latency 0, IRQ 11
>
> [virtual] Memory at b6000000 (32-bit, non-prefetchable) [size=16M]
>
> Memory at *e0000000* (64-bit, prefetchable) [size=256M]
>
> Memory at *b4000000* (64-bit, non-prefetchable) [size=32M]
>
> I/O ports at 3000 [size=128]
>
> Is this expected ?
>
> Would you have any idea why this would be so unstable / crash ?
>
> Also, the Mouse is passthrough using usbdevice=”host:##:##”, but has a
> really bad lag/delay on refresh .. can this be helped ?
>
> Cheers,
> Tim
>
> *From:* Han, Weidong [mailto:weidong.han@intel.com]
> *Sent:* 03 September 2009 10:43
> *To:* Tim Moore
> *Cc:* 'enming.teo@asiasoftsea.net
> <mailto:enming.teo@asiasoftsea.net>'; 'djmagee@mageenet.net
> <mailto:djmagee@mageenet.net>'; 'xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>'
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> Tim,
>
> See my comments belew.
>
> ------------------------------------------------------------------------
>
> *From:* Tim Moore [mailto:timothy.moore@expidas.net]
> *Sent:* 2009年9月3日 17:03
> *To:* Han, Weidong
> *Cc:* 'enming.teo@asiasoftsea.net
> <mailto:enming.teo@asiasoftsea.net>'; djmagee@mageenet.net
> <mailto:djmagee@mageenet.net>; xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
> *Subject:* RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> 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@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Teo En
> Ming (Zhang Enming)
> *Sent:* 03 September 2009 05:12
> *To:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>; 'Han,
> Weidong'; xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
> *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@hotmail.com <mailto:teoenming@hotmail.com>
>
> ------------------------------------------------------------------------
>
> *From:* xen-devel-bounces@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net <mailto:djmagee@mageenet.net>
> *Sent:* Wednesday, September 02, 2009 6:59 PM
> *To:* Han, Weidong; xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
> *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@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Han, Weidong
> *Sent:* Tuesday, September 01, 2009 6:55 PM
> *To:* djmagee@mageenet.net <mailto:djmagee@mageenet.net>;
> 'xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>'
> *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@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com>
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of
> *djmagee@mageenet.net <mailto:djmagee@mageenet.net>
> *Sent:* 2009年9月2日 6:40
> *To:* xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>
> *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@mageenet.net <mailto:djmagee@mageenet.net>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date:
> 09/01/09 20:03:00
>
>
>
>
> ------------------------------------------------------------------------
>
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com <mailto:Xen-devel@lists.xensource.com>
> http://lists.xensource.com/xen-devel
>
>
[-- Attachment #1.2: Type: text/html, Size: 40183 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: xen-unstable pci passthrough
2009-09-03 20:29 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 20:34 ` Tim Moore
2009-09-03 20:35 ` Mr. Teo En Ming (Zhang Enming)
@ 2009-09-03 23:58 ` Han, Weidong
2009-09-04 1:58 ` Teo En Ming (Zhang Enming)
2 siblings, 1 reply; 39+ messages in thread
From: Han, Weidong @ 2009-09-03 23:58 UTC (permalink / raw)
To: 'enming.teo@asiasoftsea.net',
'timothy.moore@expidas.net'
Cc: 'xen-devel@lists.xensource.com'
[-- Attachment #1.1: Type: text/plain, Size: 11646 bytes --]
It's good to hear that. Now keyboard/mouse is inconvenient in guest. I think it will be not a problem once Jean ports the patch which shares the host keyboard/mouse with multiple vms from XCI.
Regards,
Weidong
________________________________
From: Mr. Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
Sent: 2009年9月4日 4:29
To: timothy.moore@expidas.net
Cc: Han, Weidong; 'xen-devel@lists.xensource.com'
Subject: Re: [Xen-devel] xen-unstable pci passthrough
VGA Passthrough to Windows XP Home 32-bit HVM DomU SUCCESS!!!
A big thanks to Weidong and other engineers at Intel for the VGA passthrough patches to xen 3.5-unstable, and other gurus here at xen-devel mailing list for your kind assistance and help along the way.
I had abandoned the idea of booting up the onboard Intel GMA4500 graphics as the primary video adapter for dom0 and passing through the secondary nVidia Geforce 8400 GS PCI-e x16 graphics to Win XP Home DomU. I should have listened to Magee's advice earlier that both onboard and pci-e graphics could not be operated simultaneously at the same time due to lack of pci-e lanes on Intel DQ45CB.
After Timothy stressed on Magee's advice just now, I have totally changed my approach. Now, I boot up the nVidia Geforce 8400 GS PCI-e x16 as the primary video adapter with-out any secondary video adapter.
I applied Weidong's xen-gfx-passthrough.patch, qemu-gfx-passthrough.patch, xen-load-vbios-file.patch, xen-vbar-pbar.patch, and qemu-vbar-pbar.patch to xen 3.5-unstable changeset 20143 successfully. I skipped qemu-claim-vga-cycle-secondary-gfx-passthrough.patch. Using this approach, I am still loading the vga bios of nVidia Geforce 8400 GS from firmware file. And I am using the Version 1 Intel gfx passthrough patches.
The pvops dom 0 kernel I am using is 2.6.31-rc6.
Before rebooting, I appended "blacklist nvidia" to /etc/modprobe.d/blacklist.conf to prevent the nvidia driver from loading.
After rebooting, I hide nVidia Geforce 8400 GS from Dom 0 using Xen VT-d wiki instructions. Then I started Windows XP Home 32-bit HVM Guest with 1 VCPU.
Windows XP Home HVM DomU successfully boots up!!! Emulated VGA is disabled. Only nVidia Geforce 8400 GS shows up in Device Manager.
This time, instead of showing nVidia Geforce 8400 GS cannot start and no resources, it shows there are NOT ENOUGH resources. There is still an exclamation mark beside nvidia 8400 GS.
I tried to passthrough USB Keyboard and USB mouse using the following config but with-out success:
usb = 1
usbdevice = [ 'host:vendorid:productid', 'host:vendorid:productid' ]
So I had to vnc into my Windows XP HVM domU.
Thank you Weidong and other engineers at Intel for the vga passthrough patches!!!
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com<mailto:teoenming@hotmail.com>
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/04/2009 03:07 AM, Tim Moore wrote:
Hi Weidong,
Thanks for your replies...
I now have Windows XP DomU with Primary VGA , USB Keyboard + Mouse Passthrough. I am using 2.6.30-rc3 pvops with netbk vif.
Primary VGA is Nvidia Geforce GTX260
The DomU has hangs/locks with any graphics intensive operations, i.e. Opening Internet Explorer on the MSN homepage makes DomU freeze !!
I noticed in the attached qemu log that the some of the memory addresses are not the same as the lspci output:
pt_register_regions: IO region registered (size=0x01000000 base_addr=0xb6000000)
pt_register_regions: IO region registered (size=0x10000000 base_addr=0xe000000c)
pt_register_regions: IO region registered (size=0x02000000 base_addr=0xb4000004)
02:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce GTX 260] (rev a1) (prog-if 00 [VGA controller])
Subsystem: nVidia Corporation Device 068e
Flags: bus master, fast devsel, latency 0, IRQ 11
[virtual] Memory at b6000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at b4000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at 3000 [size=128]
Is this expected ?
Would you have any idea why this would be so unstable / crash ?
Also, the Mouse is passthrough using usbdevice=”host:##:##”, but has a really bad lag/delay on refresh .. can this be helped ?
Cheers,
Tim
From: Han, Weidong [mailto:weidong.han@intel.com]
Sent: 03 September 2009 10:43
To: Tim Moore
Cc: 'enming.teo@asiasoftsea.net<mailto:enming.teo@asiasoftsea.net>'; 'djmagee@mageenet.net<mailto:djmagee@mageenet.net>'; 'xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>'
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
Tim,
See my comments belew.
________________________________
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: 2009年9月3日 17:03
To: Han, Weidong
Cc: 'enming.teo@asiasoftsea.net<mailto:enming.teo@asiasoftsea.net>'; djmagee@mageenet.net<mailto:djmagee@mageenet.net>; xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net<mailto:djmagee@mageenet.net>; 'Han, Weidong'; xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
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@hotmail.com<mailto:teoenming@hotmail.com>
________________________________
From: xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net<mailto:djmagee@mageenet.net>
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
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@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net<mailto:djmagee@mageenet.net>; 'xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>'
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@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net<mailto:djmagee@mageenet.net>
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
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@mageenet.net<mailto:djmagee@mageenet.net>
No virus found in this incoming message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date: 09/01/09 20:03:00
________________________________
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 34040 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: xen-unstable pci passthrough
2009-09-03 20:35 ` Mr. Teo En Ming (Zhang Enming)
@ 2009-09-04 0:00 ` Han, Weidong
0 siblings, 0 replies; 39+ messages in thread
From: Han, Weidong @ 2009-09-04 0:00 UTC (permalink / raw)
To: 'enming.teo@asiasoftsea.net'
Cc: 'xen-devel@lists.xensource.com',
'timothy.moore@expidas.net'
[-- Attachment #1.1: Type: text/plain, Size: 12744 bytes --]
IGD (onboard graphics) passthrough needs some hacks. We are working on it.
Regards,
Weidong
________________________________
From: Mr. Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
Sent: 2009年9月4日 4:36
To: enming.teo@asiasoftsea.net
Cc: timothy.moore@expidas.net; 'xen-devel@lists.xensource.com'; Han, Weidong
Subject: Re: [Xen-devel] xen-unstable pci passthrough
Just to add:
I did try booting up onboard graphics as the primary video controller. I did not try to pass though nvidia gf 8400 gs to Win XP Dom U. I tried to passthrough onboard graphics to Win XP Dom U without success.
I had tried with pvops Dom 0 2.6.30-rc3 and 2.6.31-rc6. Every time I get some iommu fault overflow condition and then Dom 0 died.
So next I tried nvidia geforce 8400 gs as the primary. And it works.
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com<mailto:teoenming@hotmail.com>
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/04/2009 04:29 AM, Mr. Teo En Ming (Zhang Enming) wrote:
VGA Passthrough to Windows XP Home 32-bit HVM DomU SUCCESS!!!
A big thanks to Weidong and other engineers at Intel for the VGA passthrough patches to xen 3.5-unstable, and other gurus here at xen-devel mailing list for your kind assistance and help along the way.
I had abandoned the idea of booting up the onboard Intel GMA4500 graphics as the primary video adapter for dom0 and passing through the secondary nVidia Geforce 8400 GS PCI-e x16 graphics to Win XP Home DomU. I should have listened to Magee's advice earlier that both onboard and pci-e graphics could not be operated simultaneously at the same time due to lack of pci-e lanes on Intel DQ45CB.
After Timothy stressed on Magee's advice just now, I have totally changed my approach. Now, I boot up the nVidia Geforce 8400 GS PCI-e x16 as the primary video adapter with-out any secondary video adapter.
I applied Weidong's xen-gfx-passthrough.patch, qemu-gfx-passthrough.patch, xen-load-vbios-file.patch, xen-vbar-pbar.patch, and qemu-vbar-pbar.patch to xen 3.5-unstable changeset 20143 successfully. I skipped qemu-claim-vga-cycle-secondary-gfx-passthrough.patch. Using this approach, I am still loading the vga bios of nVidia Geforce 8400 GS from firmware file. And I am using the Version 1 Intel gfx passthrough patches.
The pvops dom 0 kernel I am using is 2.6.31-rc6.
Before rebooting, I appended "blacklist nvidia" to /etc/modprobe.d/blacklist.conf to prevent the nvidia driver from loading.
After rebooting, I hide nVidia Geforce 8400 GS from Dom 0 using Xen VT-d wiki instructions. Then I started Windows XP Home 32-bit HVM Guest with 1 VCPU.
Windows XP Home HVM DomU successfully boots up!!! Emulated VGA is disabled. Only nVidia Geforce 8400 GS shows up in Device Manager.
This time, instead of showing nVidia Geforce 8400 GS cannot start and no resources, it shows there are NOT ENOUGH resources. There is still an exclamation mark beside nvidia 8400 GS.
I tried to passthrough USB Keyboard and USB mouse using the following config but with-out success:
usb = 1
usbdevice = [ 'host:vendorid:productid', 'host:vendorid:productid' ]
So I had to vnc into my Windows XP HVM domU.
Thank you Weidong and other engineers at Intel for the vga passthrough patches!!!
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com<mailto:teoenming@hotmail.com>
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/04/2009 03:07 AM, Tim Moore wrote:
Hi Weidong,
Thanks for your replies...
I now have Windows XP DomU with Primary VGA , USB Keyboard + Mouse Passthrough. I am using 2.6.30-rc3 pvops with netbk vif.
Primary VGA is Nvidia Geforce GTX260
The DomU has hangs/locks with any graphics intensive operations, i.e. Opening Internet Explorer on the MSN homepage makes DomU freeze !!
I noticed in the attached qemu log that the some of the memory addresses are not the same as the lspci output:
pt_register_regions: IO region registered (size=0x01000000 base_addr=0xb6000000)
pt_register_regions: IO region registered (size=0x10000000 base_addr=0xe000000c)
pt_register_regions: IO region registered (size=0x02000000 base_addr=0xb4000004)
02:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce GTX 260] (rev a1) (prog-if 00 [VGA controller])
Subsystem: nVidia Corporation Device 068e
Flags: bus master, fast devsel, latency 0, IRQ 11
[virtual] Memory at b6000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at b4000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at 3000 [size=128]
Is this expected ?
Would you have any idea why this would be so unstable / crash ?
Also, the Mouse is passthrough using usbdevice=”host:##:##”, but has a really bad lag/delay on refresh .. can this be helped ?
Cheers,
Tim
From: Han, Weidong [mailto:weidong.han@intel.com]
Sent: 03 September 2009 10:43
To: Tim Moore
Cc: 'enming.teo@asiasoftsea.net<mailto:enming.teo@asiasoftsea.net>'; 'djmagee@mageenet.net<mailto:djmagee@mageenet.net>'; 'xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>'
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
Tim,
See my comments belew.
________________________________
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: 2009年9月3日 17:03
To: Han, Weidong
Cc: 'enming.teo@asiasoftsea.net<mailto:enming.teo@asiasoftsea.net>'; djmagee@mageenet.net<mailto:djmagee@mageenet.net>; xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net<mailto:djmagee@mageenet.net>; 'Han, Weidong'; xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
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@hotmail.com<mailto:teoenming@hotmail.com>
________________________________
From: xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net<mailto:djmagee@mageenet.net>
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
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@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net<mailto:djmagee@mageenet.net>; 'xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>'
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@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net<mailto:djmagee@mageenet.net>
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
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@mageenet.net<mailto:djmagee@mageenet.net>
No virus found in this incoming message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 8.5.409 / Virus Database: 270.13.75/2340 - Release Date: 09/01/09 20:03:00
________________________________
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
http://lists.xensource.com/xen-devel
________________________________
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 37294 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: xen-unstable pci passthrough
2009-09-03 19:07 ` Tim Moore
2009-09-03 20:29 ` Mr. Teo En Ming (Zhang Enming)
@ 2009-09-04 0:03 ` Han, Weidong
1 sibling, 0 replies; 39+ messages in thread
From: Han, Weidong @ 2009-09-04 0:03 UTC (permalink / raw)
To: 'Tim Moore'; +Cc: 'xen-devel@lists.xensource.com'
[-- Attachment #1.1: Type: text/plain, Size: 7935 bytes --]
The memory addresses are expected. The "c" and "4" are the flags of the addresses.
I didn't try Geforce GTX260 passthrough. No idea about the crash.
Regards,
Weidong
________________________________
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: 2009年9月4日 3:07
To: Han, Weidong
Cc: 'xen-devel@lists.xensource.com'
Subject: RE: [Xen-devel] xen-unstable pci passthrough
Hi Weidong,
Thanks for your replies...
I now have Windows XP DomU with Primary VGA , USB Keyboard + Mouse Passthrough. I am using 2.6.30-rc3 pvops with netbk vif.
Primary VGA is Nvidia Geforce GTX260
The DomU has hangs/locks with any graphics intensive operations, i.e. Opening Internet Explorer on the MSN homepage makes DomU freeze !!
I noticed in the attached qemu log that the some of the memory addresses are not the same as the lspci output:
pt_register_regions: IO region registered (size=0x01000000 base_addr=0xb6000000)
pt_register_regions: IO region registered (size=0x10000000 base_addr=0xe000000c)
pt_register_regions: IO region registered (size=0x02000000 base_addr=0xb4000004)
02:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce GTX 260] (rev a1) (prog-if 00 [VGA controller])
Subsystem: nVidia Corporation Device 068e
Flags: bus master, fast devsel, latency 0, IRQ 11
[virtual] Memory at b6000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at b4000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at 3000 [size=128]
Is this expected ?
Would you have any idea why this would be so unstable / crash ?
Also, the Mouse is passthrough using usbdevice=”host:##:##”, but has a really bad lag/delay on refresh .. can this be helped ?
Cheers,
Tim
From: Han, Weidong [mailto:weidong.han@intel.com]
Sent: 03 September 2009 10:43
To: Tim Moore
Cc: 'enming.teo@asiasoftsea.net'; 'djmagee@mageenet.net'; 'xen-devel@lists.xensource.com'
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
Tim,
See my comments belew.
________________________________
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: 2009年9月3日 17:03
To: Han, Weidong
Cc: 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net; xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
________________________________
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net<mailto:djmagee@mageenet.net>
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
[-- Attachment #1.2: Type: text/html, Size: 30483 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: xen-unstable pci passthrough
2009-09-03 23:58 ` Han, Weidong
@ 2009-09-04 1:58 ` Teo En Ming (Zhang Enming)
2009-09-04 3:10 ` Han, Weidong
0 siblings, 1 reply; 39+ messages in thread
From: Teo En Ming (Zhang Enming) @ 2009-09-04 1:58 UTC (permalink / raw)
To: weidong.han, timothy.moore; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 12361 bytes --]
Hi Weidong,
If I want to use the Version 2 patches, which changeset in xen 3.5-unstable
do I need to checkout?
But I understand that current xen-load-vbios-file.patch,
xen-vbar-pbar.patch, and qemu-change-vbar-pbar.patch are incompatible with
Version 2 patches and only works with Version 1 patches.
So to pass through primary nvidia geforce 8400 gs, I need to wait for
updates to the above mentioned xen-load-vbios-file.patch,
xen-vbar-pbar.patch, and qemu-change-vbar-pbar.patch before it can work with
Version 2 patches?
As for USB passthrough, think Timothy got the workaround.
I can also passthrough USB hubs??? Because my all-in-one printer cum scanner
uses a USB hub with individual devices (printer and scanner separately)
connected to the hub. So can I pass that through?
Thank you!!!!
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@hotmail.com
_____
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of Han, Weidong
Sent: Friday, September 04, 2009 7:59 AM
To: 'enming.teo@asiasoftsea.net'; 'timothy.moore@expidas.net'
Cc: 'xen-devel@lists.xensource.com'
Subject: RE: [Xen-devel] xen-unstable pci passthrough
It's good to hear that. Now keyboard/mouse is inconvenient in guest. I think
it will be not a problem once Jean ports the patch which shares the host
keyboard/mouse with multiple vms from XCI.
Regards,
Weidong
_____
From: Mr. Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
Sent: 2009年9月4日 4:29
To: timothy.moore@expidas.net
Cc: Han, Weidong; 'xen-devel@lists.xensource.com'
Subject: Re: [Xen-devel] xen-unstable pci passthrough
VGA Passthrough to Windows XP Home 32-bit HVM DomU SUCCESS!!!
A big thanks to Weidong and other engineers at Intel for the VGA passthrough
patches to xen 3.5-unstable, and other gurus here at xen-devel mailing list
for your kind assistance and help along the way.
I had abandoned the idea of booting up the onboard Intel GMA4500 graphics as
the primary video adapter for dom0 and passing through the secondary nVidia
Geforce 8400 GS PCI-e x16 graphics to Win XP Home DomU. I should have
listened to Magee's advice earlier that both onboard and pci-e graphics
could not be operated simultaneously at the same time due to lack of pci-e
lanes on Intel DQ45CB.
After Timothy stressed on Magee's advice just now, I have totally changed my
approach. Now, I boot up the nVidia Geforce 8400 GS PCI-e x16 as the primary
video adapter with-out any secondary video adapter.
I applied Weidong's xen-gfx-passthrough.patch, qemu-gfx-passthrough.patch,
xen-load-vbios-file.patch, xen-vbar-pbar.patch, and qemu-vbar-pbar.patch to
xen 3.5-unstable changeset 20143 successfully. I skipped
qemu-claim-vga-cycle-secondary-gfx-passthrough.patch. Using this approach, I
am still loading the vga bios of nVidia Geforce 8400 GS from firmware file.
And I am using the Version 1 Intel gfx passthrough patches.
The pvops dom 0 kernel I am using is 2.6.31-rc6.
Before rebooting, I appended "blacklist nvidia" to
/etc/modprobe.d/blacklist.conf to prevent the nvidia driver from loading.
After rebooting, I hide nVidia Geforce 8400 GS from Dom 0 using Xen VT-d
wiki instructions. Then I started Windows XP Home 32-bit HVM Guest with 1
VCPU.
Windows XP Home HVM DomU successfully boots up!!! Emulated VGA is disabled.
Only nVidia Geforce 8400 GS shows up in Device Manager.
This time, instead of showing nVidia Geforce 8400 GS cannot start and no
resources, it shows there are NOT ENOUGH resources. There is still an
exclamation mark beside nvidia 8400 GS.
I tried to passthrough USB Keyboard and USB mouse using the following config
but with-out success:
usb = 1
usbdevice = [ 'host:vendorid:productid', 'host:vendorid:productid' ]
So I had to vnc into my Windows XP HVM domU.
Thank you Weidong and other engineers at Intel for the vga passthrough
patches!!!
--
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
Company Website: http://www.asiasoft.sg/
Mobile: +65-9648-9798
MSN: teoenming@hotmail.com
Alma Maters: Singapore Polytechnic, National University of Singapore
On 09/04/2009 03:07 AM, Tim Moore wrote:
Hi Weidong,
Thanks for your replies...
I now have Windows XP DomU with Primary VGA , USB Keyboard + Mouse
Passthrough. I am using 2.6.30-rc3 pvops with netbk vif.
Primary VGA is Nvidia Geforce GTX260
The DomU has hangs/locks with any graphics intensive operations, i.e.
Opening Internet Explorer on the MSN homepage makes DomU freeze !!
I noticed in the attached qemu log that the some of the memory addresses are
not the same as the lspci output:
pt_register_regions: IO region registered (size=0x01000000
base_addr=0xb6000000)
pt_register_regions: IO region registered (size=0x10000000
base_addr=0xe000000c)
pt_register_regions: IO region registered (size=0x02000000
base_addr=0xb4000004)
02:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce GTX
260] (rev a1) (prog-if 00 [VGA controller])
Subsystem: nVidia Corporation Device 068e
Flags: bus master, fast devsel, latency 0, IRQ 11
[virtual] Memory at b6000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at b4000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at 3000 [size=128]
Is this expected ?
Would you have any idea why this would be so unstable / crash ?
Also, the Mouse is passthrough using usbdevice=”host:##:##”, but has a
really bad lag/delay on refresh .. can this be helped ?
Cheers,
Tim
From: Han, Weidong [mailto:weidong.han@intel.com]
Sent: 03 September 2009 10:43
To: Tim Moore
Cc: 'enming.teo@asiasoftsea.net'; 'djmagee@mageenet.net';
'xen-devel@lists.xensource.com'
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
Tim,
See my comments belew.
_____
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: 2009年9月3日 17:03
To: Han, Weidong
Cc: 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net;
xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
_____
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.
xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net
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
_____
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
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
[-- Attachment #1.2: Type: text/html, Size: 45166 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: xen-unstable pci passthrough
2009-09-04 1:58 ` Teo En Ming (Zhang Enming)
@ 2009-09-04 3:10 ` Han, Weidong
2009-09-04 10:27 ` Christian Tramnitz
0 siblings, 1 reply; 39+ messages in thread
From: Han, Weidong @ 2009-09-04 3:10 UTC (permalink / raw)
To: 'enming.teo@asiasoftsea.net',
'timothy.moore@expidas.net'
Cc: 'xen-devel@lists.xensource.com'
Let's use plain text format in mailing list, it's easy to discuss.
> If I want to use the Version 2 patches, which changeset in xen 3.5-unstable do I need to checkout?
The PATCH 1/2 was checked into Xen-unstable as changeset 20144, but the PATCH 2/2 is still not checked into QEMU tree. So if you checkout the changeset of xen-unstable is larger than 20144, you don't need to apply the PATCH 1/2, but you still need to apply PATCH 2/2 to QEMU.
> But I understand that current xen-load-vbios-file.patch, xen-vbar-pbar.patch, and qemu-change-vbar-pbar.patch are incompatible
> with Version 2 patches and only works with Version 1 >patches.
> So to pass through primary nvidia geforce 8400 gs, I need to wait for updates to the above mentioned xen-load-vbios-file.patch,
> xen-vbar-pbar.patch, and qemu-change-vbar-pbar.patch before it can work with Version 2 patches?
We are working on IGD passthrough now. We won't update these hacking patches immediately. I think it's not hard to rebase them on version 2 patches, you can do it by yourself if you need it immediately. Actually the 1:1 mapping patch is too tricky, we don't think it's suitable to be in upstream. The better way is the gfx vendors to remove this trick (maybe change their drivers) to make them virtualization friendly.
Regards,
Weidong
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: xen-unstable pci passthrough
2009-09-04 3:10 ` Han, Weidong
@ 2009-09-04 10:27 ` Christian Tramnitz
0 siblings, 0 replies; 39+ messages in thread
From: Christian Tramnitz @ 2009-09-04 10:27 UTC (permalink / raw)
To: xen-devel
Han, Weidong wrote:
> Actually the 1:1 mapping patch is too tricky, we don't think it's suitable to be in upstream. The better way is the gfx vendors to remove this trick (maybe change their drivers) to make them virtualization friendly.
I don't think that this is very likely. The userbase is to small (right
now), not to talk about existing bugs that affect a larger user group
that won't be fixed.
Also Nvidia wants to see some extra $ for their premium products
(capable of Multi OS), I don't think they will just change the drivers
to make that feature available for every card.
If anyhow possible we should try to get that "intelligence" into
Xen/xen-qemu and not rely on the vendors. If tricky/untested/unstable it
should be marked as such and its usage made optional, but I see a lot of
potential in that direction.
Best regards,
Christian
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable gfx passthrough (was xen-unstable pci passthrough)
2009-09-03 15:07 ` djmagee
2009-09-03 15:58 ` Mr. Teo En Ming (Zhang Enming)
@ 2009-09-09 19:02 ` djmagee
1 sibling, 0 replies; 39+ messages in thread
From: djmagee @ 2009-09-09 19:02 UTC (permalink / raw)
To: enming.teo, Han, Weidong, xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 10043 bytes --]
Ok, I’ve finally had some more time to work on this.
The hardware I’m using is a DQ45CB, a C2D E6600, and HIS ATI Radeon 4770.
The kernel I’m currently using is a pv_ops dom0 from Jeremy’s xen-tip/master branch, version 2.6.30-rc3. I will attach the config.
I built xen from xen-unstable c/s 20180. This includes Weidong’s gfx passthrough v2 patch. I applied the qemuv2 patch.
The interesting thing about this configuration is I’m having problems passing through devices that are sharing IRQs with devices that dom0 still has loaded. IR is not enabled, so that may be expected, but I’m certain I’ve managed to do this with other kernels (maybe it’s a difference between using pciback and pci-stub?)
Other than that this configuration was working just fine and perfectly stable for everything not gfx passthrough.
I passed my videocard through to the guest, without enabling gfx_passthru. I installed the driver for the device, and rebooted. The device was recognized properly, but device manager said “Could not start”, which I expected. I shut down and enabled gfx_passthru(=2) and started the guest again. Nothing happened on the screen and xm list was showing that the domu wasn’t using and cputime. Xm dmesg output stopped at HVM: Loading ROMBIOS, and there was no BIOS output as there usually is.
Next I applied a patch I made (well, in two pieces, also attached) adapted from Weidong’s v1 vBAR:pBAR patch and rebuilt tools. The guest started successfully, and I was able to read the bios messages and see the normal startup screens. The domU was perfectly stable; I logged on and looked through the event log and device manager using the keyboard and mouse attached to the usb controllers I passed through. Windows reverted to using the VgaSave (I guess roughly equivalent to X’s vesa driver?) driver, saying the 4770 could not get enough free resources.
I tried out a few basic tasks and everything was very stable. Strangely, even though the card had the same MAC address, Windows recognized the emulated network adapter as a different card and defaulted to using DHCP instead of using the static IP I’d assigned to that card. Perhaps windows remembers something else about the cards other than MAC (pci slot, io/mem region?) that changes when the graphics card is passed through, as it went back to recognizing the original adapter when I boot with gfx_passthru=0.
In device manager, if I select view->Resources by connection, and look at memory resources, I see my graphics device listed by itself, whereas I see all of the other PCI devices listed under a couple of PCI Bus entries.
Next I applied a patch to map the proper memory regions for my device (attached). I booted the guest, and watched the normal output during startup. When windows was about to start (switching from that Starting Windows screen that clearly uses BIOS vga capability, to the graphical shell with the login prompt), the screen shut off, and the dom0 froze completely. I rebooted and tried a couple more times, with the same result. The qemu log is attached.
I believe the memory regions are mapped properly (using that word loosely) and it tried to start the device, as it seems to have enabled MSI on the device, which it had never done before, according to the lines in the qemu log:
pt_msgctrl_reg_write: guest enabling MSI, disable MSI-INTx translation
pt_msi_update: Update msi with pirq 37 gvec b0 gflags 0
That IRQ corresponds with the one assigned to the graphics device earlier in the log. It’s almost immediately after this that the machine totally locks up.
I’d like to figure out why the BIOS never seems to execute without the vBAR=pBAR patch. Is it possible that the gpu’s BIOS has some values hardcoded that don’t let it operate with different i/o or memory regions? Or is it possible that xen is not properly assigning resources through it’s normal code path (which is skipped using the vBAR=pBAR patch)? When I get another minute, I will try again with an unpatched xen to see what resources are assigned to the device when I pass it through with gfx_passthru disabled.
Let me know if there’s anything I can do to help resolve this and test this functionality further.
Doug Magee
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Thursday, September 03, 2009 11:08 AM
To: enming.teo@asiasoftsea.net; Han, Weidong; xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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.
From: Teo En Ming (Zhang Enming) [mailto:enming.teo@asiasoftsea.net]
Sent: Thursday, September 03, 2009 12:12 AM
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
________________________________
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net
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
[-- Attachment #1.2: Type: text/html, Size: 25535 bytes --]
[-- Attachment #2: 00vBARpBAR.patch --]
[-- Type: application/octet-stream, Size: 895 bytes --]
diff -r 4f13590588e3 tools/firmware/hvmloader/hvmloader.c
--- a/tools/firmware/hvmloader/hvmloader.c Fri Aug 28 14:41:36 2009 +0800
+++ b/tools/firmware/hvmloader/hvmloader.c Mon Aug 31 12:41:21 2009 +0800
@@ -115,6 +115,9 @@ unsigned long pci_mem_end = PCI_MEM_END;
static enum { VGA_none, VGA_std, VGA_cirrus, VGA_pt } virtual_vga = VGA_none;
+/* virtual BDF of pass-throughed gfx */
+static uint8_t gfx_bdf;
+
static void init_hypercalls(void)
{
uint32_t eax, ebx, ecx, edx;
@@ -215,7 +218,10 @@ static void pci_setup(void)
else if ( (vendor_id == 0x1013) && (device_id == 0xb8) )
virtual_vga = VGA_cirrus;
else
+ {
virtual_vga = VGA_pt;
+ gfx_bdf = devfn;
+ }
break;
case 0x0680:
/* PIIX4 ACPI PM. Special device with special PCI config space. */
[-- Attachment #3: lspci-vvv.txt --]
[-- Type: text/plain, Size: 22102 bytes --]
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
Subsystem: Intel Corporation Unknown device 1003
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: 0
Capabilities: [e0] Vendor Specific Information <?>
00:01.0 PCI bridge: Intel Corporation 4 Series Chipset PCI Express Root Port (rev 03) (prog-if 00 [Normal decode])
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: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: c0000000-d00fffff
Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Intel Corporation Unknown device 0000
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Address: 00000000 Data: 0000
Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #2, Speed 5GT/s, Width x16, ASPM unknown, Latency L0 <256ns, L1 <4us
ClockPM- Suprise- 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+
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surpise-
Slot # 0, PowerLimit 0.000000; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
Changed: MRL- PresDet+ LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [100] Virtual Channel <?>
Capabilities: [140] Root Complex Link <?>
Kernel driver in use: pcieport-driver
Kernel modules: shpchp
00:03.0 Communication controller: Intel Corporation 4 Series Chipset HECI Controller (rev 03)
Subsystem: Intel Corporation Unknown device 1003
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: 0
Interrupt: pin A routed to IRQ 11
Region 0: Memory at d022a000 (64-bit, non-prefetchable) [size=16]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [8c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT IDER Controller (rev 03) (prog-if 85 [Master SecO PriO])
Subsystem: Intel Corporation Unknown device 1003
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-
Interrupt: pin C routed to IRQ 18
Region 0: I/O ports at d210 [size=8]
Region 1: I/O ports at d200 [size=4]
Region 2: I/O ports at d1f0 [size=8]
Region 3: I/O ports at d1e0 [size=4]
Region 4: I/O ports at d1d0 [size=16]
Capabilities: [c8] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Kernel modules: pata_acpi, ata_generic
00:03.3 Serial controller: Intel Corporation 4 Series Chipset Serial KT Controller (rev 03) (prog-if 02 [16550])
Subsystem: Intel Corporation Unknown device 1003
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: 0
Interrupt: pin B routed to IRQ 17
Region 0: I/O ports at d1c0 [size=8]
Region 1: Memory at d0229000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [c8] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Kernel driver in use: serial
00:19.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network Connection (rev 02)
Subsystem: Intel Corporation Unknown device 1003
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: 0
Interrupt: pin A routed to IRQ 20
Region 0: Memory at d0200000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at d0228000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at d100 [size=32]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [e0] Vendor Specific Information <?>
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corporation Unknown device 1003
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 4: I/O ports at d0e0 [size=32]
Capabilities: [50] Vendor Specific Information <?>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1a.1 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #5 (rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corporation Unknown device 1003
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 21
Region 4: I/O ports at d0c0 [size=32]
Capabilities: [50] Vendor Specific Information <?>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1a.2 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #6 (rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corporation Unknown device 1003
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 18
Region 4: I/O ports at d0a0 [size=32]
Capabilities: [50] Vendor Specific Information <?>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1a.7 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB2 EHCI Controller #2 (rev 02) (prog-if 20 [EHCI])
Subsystem: Intel Corporation Unknown device 1003
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 18
Region 0: Memory at d0227000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] Vendor Specific Information <?>
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:1b.0 Audio device: Intel Corporation 82801JD/DO (ICH10 Family) HD Audio Controller (rev 02)
Subsystem: Intel Corporation Unknown device 1003
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: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 22
Region 0: Memory at d0220000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag- RBE- FLReset+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0 <64ns, L1 <1us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Virtual Channel <?>
Capabilities: [130] Root Complex Link <?>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
00:1d.0 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corporation Unknown device 1003
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 23
Region 4: I/O ports at d080 [size=32]
Capabilities: [50] Vendor Specific Information <?>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1d.1 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corporation Unknown device 1003
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 19
Region 4: I/O ports at d060 [size=32]
Capabilities: [50] Vendor Specific Information <?>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1d.2 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corporation Unknown device 1003
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 18
Region 4: I/O ports at d040 [size=32]
Capabilities: [50] Vendor Specific Information <?>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1d.7 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB2 EHCI Controller #1 (rev 02) (prog-if 20 [EHCI])
Subsystem: Intel Corporation Unknown device 1003
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 23
Region 0: Memory at d0226000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] Vendor Specific Information <?>
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a2) (prog-if 01 [Subtractive decode])
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: 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: d0100000-d01fffff
Prefetchable memory behind bridge: 00000000d0300000-00000000d03fffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Subsystem: Gammagraphx, Inc. (or missing ID) Unknown device 0000
00:1f.0 ISA bridge: Intel Corporation 82801JDO (ICH10DO) LPC Interface Controller (rev 02)
Subsystem: Intel Corporation Unknown device 1003
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Capabilities: [e0] Vendor Specific Information <?>
00:1f.2 SATA controller: Intel Corporation 82801JD/DO (ICH10 Family) SATA AHCI Controller (rev 02) (prog-if 01 [AHCI 1.0])
Subsystem: Intel Corporation Unknown device 1003
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 19
Region 0: I/O ports at d1b0 [size=8]
Region 1: I/O ports at d1a0 [size=4]
Region 2: I/O ports at d190 [size=8]
Region 3: I/O ports at d180 [size=4]
Region 4: I/O ports at d020 [size=32]
Region 5: Memory at d0225000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/3 Enable-
Address: 00000000 Data: 0000
Capabilities: [70] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a8] SATA HBA <?>
Capabilities: [b0] Vendor Specific Information <?>
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation 82801JD/DO (ICH10 Family) SMBus Controller (rev 02)
Subsystem: Intel Corporation Unknown device 1003
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin C routed to IRQ 18
Region 0: Memory at d0224000 (64-bit, non-prefetchable) [size=256]
Region 4: I/O ports at d000 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c-i801
00:1f.5 IDE interface: Intel Corporation 82801JD/DO (ICH10 Family) 2-port SATA IDE Controller (rev 02) (prog-if 85 [Master SecO PriO])
Subsystem: Intel Corporation Unknown device 1003
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 19
Region 0: I/O ports at d170 [size=8]
Region 1: I/O ports at d160 [size=4]
Region 2: I/O ports at d150 [size=8]
Region 3: I/O ports at d140 [size=4]
Region 4: I/O ports at d130 [size=16]
Region 5: I/O ports at d120 [size=16]
Capabilities: [70] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [b0] Vendor Specific Information <?>
Kernel driver in use: ata_piix
Kernel modules: pata_acpi, ata_generic, ata_piix
01:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 94b3 (prog-if 00 [VGA controller])
Subsystem: ATI Technologies Inc Unknown device 0d00
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: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at c0000000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at d0020000 (64-bit, non-prefetchable) [size=64K]
Region 4: I/O ports at c000 [size=256]
Expansion ROM at d0000000 [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s L1, Latency L0 <64ns, L1 <1us
ClockPM- Suprise- 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: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [100] Vendor Specific Information <?>
Kernel driver in use: fglrx_pci
Kernel modules: fglrx
01:00.1 Audio device: ATI Technologies Inc RV730XT Audio device [Radeon HD 4670]
Subsystem: ATI Technologies Inc RV730XT Audio device [Radeon HD 4670]
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: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 17
Region 0: Memory at d0030000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s L1, Latency L0 <64ns, L1 <1us
ClockPM- Suprise- 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: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [100] Vendor Specific Information <?>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
02:00.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 64)
Subsystem: 3Com Corporation 3C905B Fast Etherlink XL 10/100
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (2500ns min, 2500ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 21
Region 0: I/O ports at b000 [size=128]
Region 1: Memory at d0122000 (32-bit, non-prefetchable) [size=128]
Expansion ROM at d0300000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: 3c59x
Kernel modules: 3c59x
02:01.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70) (prog-if 10 [OHCI])
Subsystem: Intel Corporation Unknown device 1003
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (3000ns min, 6000ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 22
Region 0: Memory at d0121000 (32-bit, non-prefetchable) [size=4K]
Region 1: Memory at d0120000 (32-bit, non-prefetchable) [size=256]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+
Kernel driver in use: firewire_ohci
Kernel modules: firewire-ohci
[-- Attachment #4: qemu-dm-win7domu.log.4 --]
[-- Type: application/octet-stream, Size: 9908 bytes --]
domid: 5
qemu: the number of cpus is 1
Discrete graphics card passthrough
config qemu network with xen bridge for tap5.0 vnetbr0
Watching /local/domain/0/device-model/5/logdirty/next-active
Watching /local/domain/0/device-model/5/command
char device redirected to /dev/pts/1
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 2cff25b6-cc4c-66d0-3df4-31283cdb197d
Time offset set 0
Register xen platform.
Done register platform.
xs_read(/vm/2cff25b6-cc4c-66d0-3df4-31283cdb197d/log-throttling): read error
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/5/xen_extended_power_mgmt): read error
medium change watch on `hdc' (index: 1): /rdata/iso/en_windows_7_ultimate_rc_x64_dvd_347803.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
(qemu) dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 01:00.0 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x1:0x0.0x0
pt_register_regions: IO region registered (size=0x10000000 base_addr=0xc000000c)
pt_register_regions: IO region registered (size=0x00010000 base_addr=0xd0020004)
pt_register_regions: IO region registered (size=0x00000100 base_addr=0x0000c001)
pt_register_regions: Expansion ROM registered (size=0x00020000 base_addr=0xd0000002)
pt_msi_setup: msi mapped with pirq 37
register_real_device: Real physical device 01:00.0 registered successfuly!
IRQ type = MSI-INTx
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 01:00.1 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x1:0x0.0x1
pt_register_regions: IO region registered (size=0x00004000 base_addr=0xd0030004)
pt_msi_setup: msi mapped with pirq 36
register_real_device: Real physical device 01:00.1 registered successfuly!
IRQ type = MSI-INTx
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 00:1a.0 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1a.0x0
pt_register_regions: IO region registered (size=0x00000020 base_addr=0x0000d0e1)
register_real_device: Real physical device 00:1a.0 registered successfuly!
IRQ type = INTx
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 00:1a.7 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1a.0x7
pt_register_regions: IO region registered (size=0x00000400 base_addr=0xd0227000)
pci_read_intx: intx=3
register_real_device: Real physical device 00:1a.7 registered successfuly!
IRQ type = INTx
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 00:1a.2 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1a.0x2
pt_register_regions: IO region registered (size=0x00000020 base_addr=0x0000d0a1)
pci_read_intx: intx=3
register_real_device: Real physical device 00:1a.2 registered successfuly!
IRQ type = INTx
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 00:1a.1 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1a.0x1
pt_register_regions: IO region registered (size=0x00000020 base_addr=0x0000d0c1)
pci_read_intx: intx=2
register_real_device: Real physical device 00:1a.1 registered successfuly!
IRQ type = INTx
pt_bar_reg_read: first read BARs of gfx
pt_iomem_map: e_phys=c0000000 maddr=c0000000 type=8 len=268435456 index=0 first_map=1
pt_bar_reg_read: first read BARs of gfx
pt_bar_reg_read: first read BARs of gfx
pt_iomem_map: e_phys=d0020000 maddr=d0020000 type=0 len=65536 index=2 first_map=1
pt_bar_reg_read: first read BARs of gfx
pt_bar_reg_read: first read BARs of gfx
pt_ioport_map: e_phys=c000 pio_base=c000 len=256 index=4 first_map=1
pt_iomem_map: e_phys=f1000000 maddr=d0030000 type=0 len=16384 index=0 first_map=1
pt_iomem_map: e_phys=f1004000 maddr=d0227000 type=0 len=4096 index=0 first_map=1
pt_ioport_map: e_phys=c220 pio_base=d0e0 len=32 index=4 first_map=1
pt_ioport_map: e_phys=c240 pio_base=d0c0 len=32 index=4 first_map=1
pt_ioport_map: e_phys=c260 pio_base=d0a0 len=32 index=4 first_map=1
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:04.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:04.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:04.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:04.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:04.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:04.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:04.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4]
pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4]
pt_iomem_map: e_phys=ffffffff maddr=c0000000 type=8 len=268435456 index=0 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=d0020000 type=0 len=65536 index=2 first_map=0
pt_ioport_map: e_phys=ffff pio_base=c000 len=256 index=4 first_map=0
pt_iomem_map: e_phys=c0000000 maddr=c0000000 type=8 len=268435456 index=0 first_map=0
pt_iomem_map: e_phys=d0020000 maddr=d0020000 type=0 len=65536 index=2 first_map=0
Overlapped to device[00:02.0][Region:0][Address:0000c000h][Size:00000100h]
pt_bar_mapping_one: Warning: ptdev[00:04.0][Region:4][Address:0000c000h][Size:00000100h] is overlapped.
pt_ioport_map: e_phys=c000 pio_base=c000 len=256 index=4 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=d0030000 type=0 len=16384 index=0 first_map=0
pt_iomem_map: e_phys=f1000000 maddr=d0030000 type=0 len=16384 index=0 first_map=0
pt_ioport_map: e_phys=ffff pio_base=d0e0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c220 pio_base=d0e0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=d0c0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c240 pio_base=d0c0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=d0a0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c260 pio_base=d0a0 len=32 index=4 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=d0227000 type=0 len=4096 index=0 first_map=0
pt_iomem_map: e_phys=f1004000 maddr=d0227000 type=0 len=4096 index=0 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=c0000000 type=8 len=268435456 index=0 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=d0020000 type=0 len=65536 index=2 first_map=0
pt_ioport_map: e_phys=ffff pio_base=c000 len=256 index=4 first_map=0
pt_iomem_map: e_phys=c0000000 maddr=c0000000 type=8 len=268435456 index=0 first_map=0
pt_iomem_map: e_phys=d0020000 maddr=d0020000 type=0 len=65536 index=2 first_map=0
pt_ioport_map: e_phys=ff00 pio_base=c000 len=256 index=4 first_map=0
pt_msgctrl_reg_write: guest enabling MSI, disable MSI-INTx translation
pt_msi_update: Update msi with pirq 37 gvec b0 gflags 0
pt_ioport_map: e_phys=ffff pio_base=d0e0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c220 pio_base=d0e0 len=32 index=4 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=d0030000 type=0 len=16384 index=0 first_map=0
pt_iomem_map: e_phys=f1000000 maddr=d0030000 type=0 len=16384 index=0 first_map=0
pt_ioport_map: e_phys=ffff pio_base=d0c0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c240 pio_base=d0c0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=ffff pio_base=d0a0 len=32 index=4 first_map=0
pt_ioport_map: e_phys=c260 pio_base=d0a0 len=32 index=4 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=d0227000 type=0 len=4096 index=0 first_map=0
pt_iomem_map: e_phys=f1004000 maddr=d0227000 type=0 len=4096 index=0 first_map=0
reset requested in cpu_handle_ioreq.
Issued domain 5 reboot
[-- Attachment #5: 02radeon4770MemRegions.patch --]
[-- Type: application/octet-stream, Size: 1210 bytes --]
--- xen-unstable-vgaptv2/tools/firmware/hvmloader/acpi/dsdt.asl 2009-09-08 17:45:33.000000000 -0400
+++ xen-unstable.hg/tools/firmware/hvmloader/acpi/dsdt.asl 2009-09-08 12:14:01.000000000 -0400
@@ -180,24 +180,6 @@ DefinitionBlock ("DSDT.aml", "DSDT", 2,
ResourceProducer, PosDecode, MinFixed, MaxFixed,
Cacheable, ReadWrite,
0x00000000,
- 0xC0000000,
- 0xCFFFFFFF,
- 0x00000000,
- 0x10000000)
-
- DWordMemory(
- ResourceProducer, PosDecode, MinFixed, MaxFixed,
- Cacheable, ReadWrite,
- 0x00000000,
- 0xD0020000,
- 0xD002FFFF,
- 0x00000000,
- 0x00010000)
-
- DWordMemory(
- ResourceProducer, PosDecode, MinFixed, MaxFixed,
- Cacheable, ReadWrite,
- 0x00000000,
0xF0000000,
0xF4FFFFFF,
0x00000000,
[-- Attachment #6: 01vBARpBAR.patch --]
[-- Type: application/octet-stream, Size: 1910 bytes --]
--- a/tools/firmware/hvmloader/hvmloader.c Mon Aug 31 13:14:47 2009 +0800
+++ b/tools/firmware/hvmloader/hvmloader.c Mon Aug 31 15:46:48 2009 +0800
@@ -221,6 +221,40 @@ static void pci_setup(void)
{
virtual_vga = VGA_pt;
gfx_bdf = devfn;
+
+ /* Make vBAR=pBAR */
+ printf("Make vBAR = pBAR of assigned gfx\n");
+ for ( bar = 0; bar < 7; bar++ )
+ {
+ bar_reg = PCI_BASE_ADDRESS_0 + 4*bar;
+ if ( bar == 6 )
+ bar_reg = PCI_ROM_ADDRESS;
+ /* When first time read, it will return physical address */
+ bar_data = pci_readl(devfn, bar_reg);
+ pci_writel(devfn, bar_reg, bar_data);
+
+ /* Now enable the memory or I/O mapping. */
+ cmd = pci_readw(devfn, PCI_COMMAND);
+ if ( (bar_reg == PCI_ROM_ADDRESS) ||
+ ((bar_data & PCI_BASE_ADDRESS_SPACE) ==
+ PCI_BASE_ADDRESS_SPACE_MEMORY) )
+ cmd |= PCI_COMMAND_MEMORY;
+ else
+ cmd |= PCI_COMMAND_IO;
+ cmd |= PCI_COMMAND_MASTER;
+ pci_writew(devfn, PCI_COMMAND, cmd);
+ }
+
+ /* Map the interrupt. */
+ pin = pci_readb(devfn, PCI_INTERRUPT_PIN);
+ if ( pin != 0 )
+ {
+ /* This is the barber's pole mapping used by Xen. */
+ link = ((pin - 1) + (devfn >> 3)) & 3;
+ isa_irq = pci_readb(PCI_ISA_DEVFN, 0x60 + link);
+ pci_writeb(devfn, PCI_INTERRUPT_LINE, isa_irq);
+ }
+ continue;
}
break;
case 0x0680:
[-- Attachment #7: 2.6.30-rc3-xen-tip.config --]
[-- Type: application/octet-stream, Size: 91936 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.30-rc3
# Tue Sep 8 03:36:42 2009
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_FAST_CMPXCHG_LOCAL=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_HAVE_DYNAMIC_PER_CPU_AREA=y
CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_TRAMPOLINE=y
# CONFIG_KTIME_SCALAR is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION="-xentip"
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_TREE=y
#
# RCU Subsystem
#
CONFIG_CLASSIC_RCU=y
# CONFIG_TREE_RCU is not set
# CONFIG_PREEMPT_RCU is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_PREEMPT_RCU_TRACE is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_GROUP_SCHED is not set
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_NS=y
# CONFIG_CGROUP_FREEZER is not set
CONFIG_CGROUP_DEVICE=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_RESOURCE_COUNTERS=y
# CONFIG_CGROUP_MEM_RES_CTLR is not set
# CONFIG_SYSFS_DEPRECATED_V2 is not set
CONFIG_RELAY=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
# CONFIG_NET_NS is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_EXTRA_PASS=y
# CONFIG_STRIP_ASM_SYMS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_HAVE_PERF_COUNTERS=y
#
# Performance Counters
#
CONFIG_PERF_COUNTERS=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
CONFIG_TRACEPOINTS=y
CONFIG_MARKERS=y
CONFIG_OPROFILE=m
# CONFIG_OPROFILE_IBS is not set
CONFIG_HAVE_OPROFILE=y
CONFIG_KPROBES=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_KRETPROBES=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_API_DEBUG=y
# CONFIG_SLOW_WORK is not set
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_INTEGRITY=y
CONFIG_BLOCK_COMPAT=y
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_FREEZER=y
#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
# CONFIG_SPARSE_IRQ is not set
CONFIG_X86_MPPARSE=y
CONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_VSMP is not set
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_PARAVIRT_GUEST=y
CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=32
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
CONFIG_XEN_DOM0_PCI=y
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_MICROCODE_XEN=y
CONFIG_KVM_CLOCK=y
CONFIG_KVM_GUEST=y
CONFIG_PARAVIRT=y
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_PARAVIRT_DEBUG is not set
# CONFIG_MEMTEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_CPU=y
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_INTERNODE_CACHE_BYTES=64
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
# CONFIG_X86_DS is not set
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
# CONFIG_AMD_IOMMU is not set
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
# CONFIG_IOMMU_API is not set
# CONFIG_MAXSMP is not set
CONFIG_NR_CPUS=64
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
CONFIG_X86_MCE_THRESHOLD=y
CONFIG_I8K=m
CONFIG_MICROCODE=m
CONFIG_MICROCODE_INTEL=y
# CONFIG_MICROCODE_AMD is not set
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
# CONFIG_X86_CPU_DEBUG is not set
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_DIRECT_GBPAGES=y
CONFIG_NUMA=y
CONFIG_K8_NUMA=y
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_NODES_SPAN_OTHER_NODES=y
# CONFIG_NUMA_EMU is not set
CONFIG_NODES_SHIFT=9
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
# CONFIG_DISCONTIGMEM_MANUAL is not set
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_NEED_MULTIPLE_NODES=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y
#
# Memory hotplug is currently incompatible with Software Suspend
#
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_MIGRATION=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_UNEVICTABLE_LRU=y
CONFIG_HAVE_MLOCK=y
CONFIG_HAVE_MLOCKED_PAGE_BIT=y
CONFIG_MMU_NOTIFIER=y
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
CONFIG_X86_RESERVE_LOW_64K=y
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
CONFIG_X86_PAT=y
CONFIG_EFI=y
CONFIG_SECCOMP=y
# CONFIG_CC_STACKPROTECTOR is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
# CONFIG_KEXEC_JUMP is not set
CONFIG_PHYSICAL_START=0x1000000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x200000
CONFIG_HOTPLUG_CPU=y
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
#
# Power management and ACPI options
#
CONFIG_ARCH_HIBERNATION_HEADER=y
CONFIG_PM=y
CONFIG_PM_DEBUG=y
# CONFIG_PM_VERBOSE is not set
CONFIG_CAN_PM_TRACE=y
CONFIG_PM_TRACE=y
CONFIG_PM_TRACE_RTC=y
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND=y
# CONFIG_PM_TEST_SUSPEND is not set
CONFIG_SUSPEND_FREEZER=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_NUMA=y
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_PCI_SLOT=m
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
CONFIG_ACPI_SBS=m
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=m
CONFIG_CPU_FREQ_DEBUG=y
CONFIG_CPU_FREQ_STAT=m
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_X86_POWERNOW_K8=m
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_P4_CLOCKMOD is not set
#
# shared options
#
# CONFIG_X86_SPEEDSTEP_LIB is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
#
# Memory power savings
#
# CONFIG_I7300_IDLE is not set
#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_XEN=y
CONFIG_PCI_DOMAINS=y
# CONFIG_DMAR is not set
# CONFIG_INTR_REMAP is not set
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=m
CONFIG_PCIEAER=y
CONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
CONFIG_PCI_STUB=m
CONFIG_HT_IRQ=y
# CONFIG_PCI_IOV is not set
CONFIG_ISA_DMA_API=y
CONFIG_K8_NB=y
CONFIG_PCCARD=y
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=y
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y
#
# PC-card bridges
#
CONFIG_YENTA=m
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_PD6729=m
CONFIG_I82092=m
CONFIG_PCCARD_NONSTATIC=m
CONFIG_HOTPLUG_PCI=y
CONFIG_HOTPLUG_PCI_FAKE=m
CONFIG_HOTPLUG_PCI_ACPI=y
CONFIG_HOTPLUG_PCI_ACPI_IBM=m
# CONFIG_HOTPLUG_PCI_CPCI is not set
CONFIG_HOTPLUG_PCI_SHPC=m
#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
# CONFIG_HAVE_AOUT is not set
CONFIG_BINFMT_MISC=y
CONFIG_IA32_EMULATION=y
# CONFIG_IA32_AOUT is not set
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
CONFIG_XFRM_SUB_POLICY=y
CONFIG_XFRM_MIGRATE=y
CONFIG_XFRM_STATISTICS=y
CONFIG_XFRM_IPCOMP=m
CONFIG_NET_KEY=m
CONFIG_NET_KEY_MIGRATE=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=m
CONFIG_TCP_CONG_CUBIC=y
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
CONFIG_TCP_CONG_SCALABLE=m
CONFIG_TCP_CONG_LP=m
CONFIG_TCP_CONG_VENO=m
CONFIG_TCP_CONG_YEAH=m
CONFIG_TCP_CONG_ILLINOIS=m
# CONFIG_DEFAULT_BIC is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_IPV6_OPTIMISTIC_DAD=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_IPV6_MIP6=m
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
CONFIG_IPV6_SIT=m
CONFIG_IPV6_NDISC_NODETYPE=y
CONFIG_IPV6_TUNNEL=m
CONFIG_IPV6_MULTIPLE_TABLES=y
CONFIG_IPV6_SUBTREES=y
CONFIG_IPV6_MROUTE=y
CONFIG_IPV6_PIMSM_V2=y
CONFIG_NETLABEL=y
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CT_ACCT=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CT_PROTO_DCCP=m
CONFIG_NF_CT_PROTO_GRE=m
CONFIG_NF_CT_PROTO_SCTP=m
CONFIG_NF_CT_PROTO_UDPLITE=m
CONFIG_NF_CONNTRACK_AMANDA=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_PPTP=m
CONFIG_NF_CONNTRACK_SANE=m
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
# CONFIG_NETFILTER_TPROXY is not set
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_HL=m
# CONFIG_NETFILTER_XT_TARGET_LED is not set
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_RATEEST=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m
# CONFIG_NETFILTER_XT_MATCH_CLUSTER is not set
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_HL=m
CONFIG_NETFILTER_XT_MATCH_IPRANGE=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_OWNER=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_RATEEST=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
# CONFIG_NETFILTER_XT_MATCH_RECENT is not set
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_TIME=m
CONFIG_NETFILTER_XT_MATCH_U32=m
CONFIG_IP_VS=m
# CONFIG_IP_VS_IPV6 is not set
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12
#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_AH_ESP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y
#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m
#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m
#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=m
CONFIG_NF_CONNTRACK_IPV4=m
# CONFIG_NF_CONNTRACK_PROC_COMPAT is not set
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_NF_NAT=m
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_NF_NAT_SNMP_BASIC=m
CONFIG_NF_NAT_PROTO_DCCP=m
CONFIG_NF_NAT_PROTO_GRE=m
CONFIG_NF_NAT_PROTO_UDPLITE=m
CONFIG_NF_NAT_PROTO_SCTP=m
CONFIG_NF_NAT_FTP=m
CONFIG_NF_NAT_IRC=m
CONFIG_NF_NAT_TFTP=m
CONFIG_NF_NAT_AMANDA=m
CONFIG_NF_NAT_PPTP=m
CONFIG_NF_NAT_H323=m
CONFIG_NF_NAT_SIP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_SECURITY=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
#
# IPv6: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV6=m
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_RAW=m
CONFIG_IP6_NF_SECURITY=m
#
# DECnet: Netfilter Configuration
#
# CONFIG_DECNET_NF_GRABULATOR is not set
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_IP6=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m
CONFIG_BRIDGE_EBT_NFLOG=m
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=y
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_CCID3_RTO=100
CONFIG_IP_DCCP_TFRC_LIB=y
#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
CONFIG_NET_DCCPPROBE=m
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
CONFIG_TIPC=m
# CONFIG_TIPC_ADVANCED is not set
# CONFIG_TIPC_DEBUG is not set
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set
CONFIG_ATM_LANE=m
# CONFIG_ATM_MPOA is not set
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_STP=m
CONFIG_GARP=m
CONFIG_BRIDGE=m
# CONFIG_NET_DSA is not set
CONFIG_VLAN_8021Q=m
CONFIG_VLAN_8021Q_GVRP=y
CONFIG_DECNET=m
CONFIG_DECNET_ROUTER=y
CONFIG_LLC=y
# CONFIG_LLC2 is not set
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
CONFIG_ATALK=m
CONFIG_DEV_APPLETALK=m
CONFIG_IPDDP=m
CONFIG_IPDDP_ENCAP=y
CONFIG_IPDDP_DECAP=y
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
CONFIG_WAN_ROUTER=m
# CONFIG_PHONET is not set
CONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=m
CONFIG_NET_SCH_PRIO=m
# CONFIG_NET_SCH_MULTIQ is not set
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
# CONFIG_NET_SCH_DRR is not set
CONFIG_NET_SCH_INGRESS=m
#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_FLOW=m
# CONFIG_NET_CLS_CGROUP is not set
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
CONFIG_NET_ACT_NAT=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
# CONFIG_NET_ACT_SKBEDIT is not set
CONFIG_NET_CLS_IND=y
CONFIG_NET_SCH_FIFO=y
# CONFIG_DCB is not set
#
# Network testing
#
CONFIG_NET_PKTGEN=m
# CONFIG_NET_TCPPROBE is not set
# CONFIG_NET_DROP_MONITOR is not set
CONFIG_HAMRADIO=y
#
# Packet Radio protocols
#
CONFIG_AX25=m
CONFIG_AX25_DAMA_SLAVE=y
CONFIG_NETROM=m
CONFIG_ROSE=m
#
# AX.25 network device drivers
#
CONFIG_MKISS=m
CONFIG_6PACK=m
CONFIG_BPQETHER=m
CONFIG_BAYCOM_SER_FDX=m
CONFIG_BAYCOM_SER_HDX=m
CONFIG_BAYCOM_PAR=m
CONFIG_YAM=m
CONFIG_CAN=m
CONFIG_CAN_RAW=m
CONFIG_CAN_BCM=m
#
# CAN Device Drivers
#
CONFIG_CAN_VCAN=m
# CONFIG_CAN_DEBUG_DEVICES is not set
CONFIG_IRDA=m
#
# IrDA protocols
#
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
# CONFIG_IRDA_ULTRA is not set
#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
# CONFIG_IRDA_DEBUG is not set
#
# Infrared-port device drivers
#
#
# SIR device drivers
#
CONFIG_IRTTY_SIR=m
#
# Dongle support
#
CONFIG_DONGLE=y
CONFIG_ESI_DONGLE=m
CONFIG_ACTISYS_DONGLE=m
CONFIG_TEKRAM_DONGLE=m
CONFIG_TOIM3232_DONGLE=m
CONFIG_LITELINK_DONGLE=m
CONFIG_MA600_DONGLE=m
CONFIG_GIRBIL_DONGLE=m
CONFIG_MCP2120_DONGLE=m
CONFIG_OLD_BELKIN_DONGLE=m
CONFIG_ACT200L_DONGLE=m
CONFIG_KINGSUN_DONGLE=m
CONFIG_KSDAZZLE_DONGLE=m
CONFIG_KS959_DONGLE=m
#
# FIR device drivers
#
CONFIG_USB_IRDA=m
CONFIG_SIGMATEL_FIR=m
CONFIG_NSC_FIR=m
CONFIG_WINBOND_FIR=m
CONFIG_SMC_IRCC_FIR=m
CONFIG_ALI_FIR=m
CONFIG_VLSI_FIR=m
CONFIG_VIA_FIR=m
CONFIG_MCS_FIR=m
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_CMTP=m
CONFIG_BT_HIDP=m
#
# Bluetooth device drivers
#
CONFIG_BT_HCIBTUSB=m
CONFIG_BT_HCIBTSDIO=m
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_LL=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_CFG80211=m
# CONFIG_CFG80211_REG_DEBUG is not set
# CONFIG_WIRELESS_OLD_REGULATORY is not set
CONFIG_WIRELESS_EXT=y
CONFIG_WIRELESS_EXT_SYSFS=y
CONFIG_LIB80211=m
CONFIG_LIB80211_CRYPT_WEP=m
CONFIG_LIB80211_CRYPT_CCMP=m
CONFIG_LIB80211_CRYPT_TKIP=m
# CONFIG_LIB80211_DEBUG is not set
CONFIG_MAC80211=m
#
# Rate control algorithm selection
#
CONFIG_MAC80211_RC_MINSTREL=y
# CONFIG_MAC80211_RC_DEFAULT_PID is not set
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel"
CONFIG_MAC80211_MESH=y
CONFIG_MAC80211_LEDS=y
CONFIG_MAC80211_DEBUGFS=y
# CONFIG_MAC80211_DEBUG_MENU is not set
# CONFIG_WIMAX is not set
CONFIG_RFKILL=m
CONFIG_RFKILL_INPUT=m
CONFIG_RFKILL_LEDS=y
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_FIRMWARE_IN_KERNEL is not set
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
CONFIG_DEBUG_DEVRES=y
CONFIG_SYS_HYPERVISOR=y
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_CONCAT=m
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_TESTS is not set
CONFIG_MTD_REDBOOT_PARTS=m
CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1
# CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set
# CONFIG_MTD_REDBOOT_PARTS_READONLY is not set
CONFIG_MTD_AR7_PARTS=m
#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=m
CONFIG_MTD_BLKDEVS=m
CONFIG_MTD_BLOCK=m
CONFIG_MTD_BLOCK_RO=m
CONFIG_FTL=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y
CONFIG_INFTL=m
CONFIG_RFD_FTL=m
CONFIG_SSFDC=m
CONFIG_MTD_OOPS=m
#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_GEN_PROBE=m
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_CFI_STAA=m
CONFIG_MTD_CFI_UTIL=m
CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=m
CONFIG_MTD_ABSENT=m
#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
# CONFIG_MTD_PHYSMAP is not set
CONFIG_MTD_SC520CDP=m
CONFIG_MTD_NETSC520=m
CONFIG_MTD_TS5500=m
# CONFIG_MTD_SBC_GXX is not set
# CONFIG_MTD_AMD76XROM is not set
# CONFIG_MTD_ICHXROM is not set
CONFIG_MTD_ESB2ROM=m
CONFIG_MTD_CK804XROM=m
CONFIG_MTD_SCB2_FLASH=m
# CONFIG_MTD_NETtel is not set
# CONFIG_MTD_DILNETPC is not set
# CONFIG_MTD_L440GX is not set
CONFIG_MTD_PCI=m
# CONFIG_MTD_INTEL_VR_NOR is not set
# CONFIG_MTD_PLATRAM is not set
#
# Self-contained MTD device drivers
#
CONFIG_MTD_PMC551=m
# CONFIG_MTD_PMC551_BUGFIX is not set
# CONFIG_MTD_PMC551_DEBUG is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
CONFIG_MTD_BLOCK2MTD=m
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
CONFIG_MTD_NAND=m
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
CONFIG_MTD_NAND_ECC_SMC=y
# CONFIG_MTD_NAND_MUSEUM_IDS is not set
CONFIG_MTD_NAND_IDS=m
CONFIG_MTD_NAND_DISKONCHIP=m
# CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
# CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set
# CONFIG_MTD_NAND_CAFE is not set
CONFIG_MTD_NAND_NANDSIM=m
# CONFIG_MTD_NAND_PLATFORM is not set
CONFIG_MTD_ALAUDA=m
# CONFIG_MTD_ONENAND is not set
#
# LPDDR flash memory drivers
#
# CONFIG_MTD_LPDDR is not set
#
# UBI - Unsorted block images
#
CONFIG_MTD_UBI=m
CONFIG_MTD_UBI_WL_THRESHOLD=4096
CONFIG_MTD_UBI_BEB_RESERVE=1
# CONFIG_MTD_UBI_GLUEBI is not set
#
# UBI debugging options
#
# CONFIG_MTD_UBI_DEBUG is not set
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
CONFIG_PARPORT_PC_PCMCIA=m
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
CONFIG_PARPORT_1284=y
CONFIG_PARPORT_NOT_PC=y
CONFIG_PNP=y
CONFIG_PNP_DEBUG_MESSAGES=y
#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=m
CONFIG_PARIDE=m
#
# Parallel IDE high-level drivers
#
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m
CONFIG_PARIDE_PG=m
#
# Parallel IDE protocol modules
#
CONFIG_PARIDE_ATEN=m
CONFIG_PARIDE_BPCK=m
CONFIG_PARIDE_COMM=m
CONFIG_PARIDE_DSTR=m
CONFIG_PARIDE_FIT2=m
CONFIG_PARIDE_FIT3=m
CONFIG_PARIDE_EPAT=m
CONFIG_PARIDE_EPATC8=y
CONFIG_PARIDE_EPIA=m
CONFIG_PARIDE_FRIQ=m
CONFIG_PARIDE_FRPW=m
CONFIG_PARIDE_KBIC=m
CONFIG_PARIDE_KTTI=m
CONFIG_PARIDE_ON20=m
CONFIG_PARIDE_ON26=m
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
CONFIG_CISS_SCSI_TAPE=y
CONFIG_BLK_DEV_DAC960=m
CONFIG_BLK_DEV_UMEM=m
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_SX8=m
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
# CONFIG_BLK_DEV_XIP is not set
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_ATA_OVER_ETH=m
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_VIRTIO_BLK=m
# CONFIG_BLK_DEV_HD is not set
CONFIG_MISC_DEVICES=y
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
CONFIG_SGI_IOC4=m
CONFIG_TIFM_CORE=m
CONFIG_TIFM_7XX1=m
# CONFIG_ICS932S401 is not set
CONFIG_ENCLOSURE_SERVICES=m
# CONFIG_HP_ILO is not set
# CONFIG_DELL_LAPTOP is not set
# CONFIG_ISL29003 is not set
# CONFIG_C2PORT is not set
#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_LEGACY is not set
CONFIG_EEPROM_93CX6=m
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=m
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=m
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
CONFIG_CHR_DEV_SCH=m
CONFIG_SCSI_ENCLOSURE=m
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_FC_TGT_ATTRS=y
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_SCSI_SAS_LIBSAS=m
CONFIG_SCSI_SAS_ATA=y
CONFIG_SCSI_SAS_HOST_SMP=y
# CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set
CONFIG_SCSI_SRP_ATTRS=m
CONFIG_SCSI_SRP_TGT_ATTRS=y
CONFIG_SCSI_LOWLEVEL=y
CONFIG_ISCSI_TCP=m
# CONFIG_SCSI_CXGB3_ISCSI is not set
CONFIG_BLK_DEV_3W_XXXX_RAID=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=4
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
# CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set
CONFIG_SCSI_AIC7XXX_OLD=m
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=4
CONFIG_AIC79XX_RESET_DELAY_MS=15000
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
CONFIG_SCSI_AIC94XX=m
# CONFIG_AIC94XX_DEBUG is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
CONFIG_SCSI_ARCMSR=m
CONFIG_SCSI_ARCMSR_AER=y
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
CONFIG_MEGARAID_LEGACY=m
CONFIG_MEGARAID_SAS=m
# CONFIG_SCSI_MPT2SAS is not set
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_LIBFC is not set
# CONFIG_LIBFCOE is not set
# CONFIG_FCOE is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
CONFIG_SCSI_GDTH=m
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
CONFIG_SCSI_INIA100=m
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
CONFIG_SCSI_MVSAS=m
CONFIG_SCSI_STEX=m
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
# CONFIG_SCSI_IPR is not set
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA_FC=m
CONFIG_SCSI_QLA_ISCSI=m
CONFIG_SCSI_LPFC=m
# CONFIG_SCSI_LPFC_DEBUG_FS is not set
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_SRP=m
CONFIG_SCSI_LOWLEVEL_PCMCIA=y
# CONFIG_PCMCIA_FDOMAIN is not set
CONFIG_PCMCIA_QLOGIC=m
CONFIG_PCMCIA_SYM53C500=m
CONFIG_SCSI_DH=m
CONFIG_SCSI_DH_RDAC=m
CONFIG_SCSI_DH_HP_SW=m
CONFIG_SCSI_DH_EMC=m
CONFIG_SCSI_DH_ALUA=m
# CONFIG_SCSI_OSD_INITIATOR is not set
CONFIG_ATA=m
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
CONFIG_SATA_AHCI=m
CONFIG_SATA_SIL24=m
CONFIG_ATA_SFF=y
CONFIG_SATA_SVW=m
CONFIG_ATA_PIIX=m
CONFIG_SATA_MV=m
CONFIG_SATA_NV=m
CONFIG_PDC_ADMA=m
CONFIG_SATA_QSTOR=m
CONFIG_SATA_PROMISE=m
CONFIG_SATA_SX4=m
CONFIG_SATA_SIL=m
CONFIG_SATA_SIS=m
CONFIG_SATA_ULI=m
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=m
CONFIG_SATA_INIC162X=m
CONFIG_PATA_ACPI=m
CONFIG_PATA_ALI=m
CONFIG_PATA_AMD=m
CONFIG_PATA_ARTOP=m
CONFIG_PATA_ATIIXP=m
CONFIG_PATA_CMD640_PCI=m
CONFIG_PATA_CMD64X=m
CONFIG_PATA_CS5520=m
CONFIG_PATA_CS5530=m
CONFIG_PATA_CYPRESS=m
CONFIG_PATA_EFAR=m
CONFIG_ATA_GENERIC=m
CONFIG_PATA_HPT366=m
CONFIG_PATA_HPT37X=m
CONFIG_PATA_HPT3X2N=m
CONFIG_PATA_HPT3X3=m
# CONFIG_PATA_HPT3X3_DMA is not set
CONFIG_PATA_IT821X=m
CONFIG_PATA_IT8213=m
CONFIG_PATA_JMICRON=m
CONFIG_PATA_TRIFLEX=m
CONFIG_PATA_MARVELL=m
CONFIG_PATA_MPIIX=m
CONFIG_PATA_OLDPIIX=m
CONFIG_PATA_NETCELL=m
CONFIG_PATA_NINJA32=m
CONFIG_PATA_NS87410=m
CONFIG_PATA_NS87415=m
CONFIG_PATA_OPTI=m
CONFIG_PATA_OPTIDMA=m
CONFIG_PATA_PCMCIA=m
CONFIG_PATA_PDC_OLD=m
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
CONFIG_PATA_SERVERWORKS=m
CONFIG_PATA_PDC2027X=m
CONFIG_PATA_SIL680=m
CONFIG_PATA_SIS=m
CONFIG_PATA_VIA=m
CONFIG_PATA_WINBOND=m
CONFIG_PATA_SCH=m
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
CONFIG_MD_RAID6_PQ=m
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=m
CONFIG_DM_DEBUG=y
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
# CONFIG_DM_DELAY is not set
CONFIG_DM_UEVENT=y
CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=40
CONFIG_FUSION_CTL=m
CONFIG_FUSION_LAN=m
CONFIG_FUSION_LOGGING=y
#
# IEEE 1394 (FireWire) support
#
#
# Enable only one of the two stacks, unless you know what you are doing
#
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
CONFIG_FIREWIRE_OHCI_DEBUG=y
CONFIG_FIREWIRE_SBP2=m
# CONFIG_IEEE1394 is not set
CONFIG_I2O=m
# CONFIG_I2O_LCT_NOTIFY_ON_CHANGES is not set
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_EXT_ADAPTEC_DMA64=y
CONFIG_I2O_BUS=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m
CONFIG_MACINTOSH_DRIVERS=y
CONFIG_MAC_EMUMOUSEBTN=y
CONFIG_NETDEVICES=y
CONFIG_COMPAT_NET_DEV_OPS=y
CONFIG_IFB=m
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_MACVLAN=m
CONFIG_EQUALIZER=m
CONFIG_TUN=m
CONFIG_VETH=m
CONFIG_NET_SB1000=m
# CONFIG_ARCNET is not set
CONFIG_PHYLIB=m
#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=m
CONFIG_DAVICOM_PHY=m
CONFIG_QSEMI_PHY=m
CONFIG_LXT_PHY=m
CONFIG_CICADA_PHY=m
CONFIG_VITESSE_PHY=m
CONFIG_SMSC_PHY=m
CONFIG_BROADCOM_PHY=m
CONFIG_ICPLUS_PHY=m
CONFIG_REALTEK_PHY=m
# CONFIG_NATIONAL_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_LSI_ET1011C_PHY is not set
CONFIG_MDIO_BITBANG=m
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_CASSINI=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
# CONFIG_ETHOC is not set
# CONFIG_DNET is not set
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
CONFIG_TULIP_MMIO=y
# CONFIG_TULIP_NAPI is not set
CONFIG_DE4X5=m
CONFIG_WINBOND_840=m
CONFIG_DM9102=m
CONFIG_ULI526X=m
CONFIG_PCMCIA_XIRCOM=m
# CONFIG_HP100 is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
CONFIG_NET_PCI=y
CONFIG_PCNET32=m
CONFIG_AMD8111_ETH=m
CONFIG_ADAPTEC_STARFIRE=m
CONFIG_B44=m
CONFIG_B44_PCI_AUTOSELECT=y
CONFIG_B44_PCICORE_AUTOSELECT=y
CONFIG_B44_PCI=y
CONFIG_FORCEDETH=m
CONFIG_FORCEDETH_NAPI=y
CONFIG_E100=m
CONFIG_FEALNX=m
CONFIG_NATSEMI=m
CONFIG_NE2K_PCI=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_R6040=m
CONFIG_SIS900=m
CONFIG_EPIC100=m
# CONFIG_SMSC9420 is not set
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
CONFIG_TLAN=m
CONFIG_VIA_RHINE=m
CONFIG_VIA_RHINE_MMIO=y
CONFIG_SC92031=m
CONFIG_NET_POCKET=y
CONFIG_ATP=m
CONFIG_DE600=m
CONFIG_DE620=m
CONFIG_ATL2=m
CONFIG_NETDEV_1000=y
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I is not set
CONFIG_DL2K=m
CONFIG_E1000=m
CONFIG_E1000E=m
CONFIG_IP1000=m
CONFIG_IGB=m
CONFIG_IGB_DCA=y
# CONFIG_IGBVF is not set
CONFIG_NS83820=m
CONFIG_HAMACHI=m
CONFIG_YELLOWFIN=m
CONFIG_R8169=m
CONFIG_R8169_VLAN=y
CONFIG_SIS190=m
CONFIG_SKGE=m
# CONFIG_SKGE_DEBUG is not set
CONFIG_SKY2=m
# CONFIG_SKY2_DEBUG is not set
CONFIG_VIA_VELOCITY=m
CONFIG_TIGON3=m
CONFIG_BNX2=m
CONFIG_QLA3XXX=m
CONFIG_ATL1=m
CONFIG_ATL1E=m
# CONFIG_ATL1C is not set
# CONFIG_JME is not set
CONFIG_NETDEV_10000=y
CONFIG_CHELSIO_T1=m
CONFIG_CHELSIO_T1_1G=y
CONFIG_CHELSIO_T3_DEPENDS=y
CONFIG_CHELSIO_T3=m
# CONFIG_ENIC is not set
CONFIG_IXGBE=m
CONFIG_IXGBE_DCA=y
CONFIG_IXGB=m
CONFIG_S2IO=m
CONFIG_MYRI10GE=m
CONFIG_MYRI10GE_DCA=y
CONFIG_NIU=m
# CONFIG_MLX4_EN is not set
# CONFIG_MLX4_CORE is not set
CONFIG_TEHUTI=m
CONFIG_BNX2X=m
# CONFIG_QLGE is not set
# CONFIG_SFC is not set
# CONFIG_BE2NET is not set
CONFIG_TR=y
CONFIG_IBMOL=m
CONFIG_3C359=m
# CONFIG_TMS380TR is not set
#
# Wireless LAN
#
CONFIG_WLAN_PRE80211=y
# CONFIG_STRIP is not set
CONFIG_PCMCIA_WAVELAN=m
CONFIG_PCMCIA_NETWAVE=m
CONFIG_WLAN_80211=y
# CONFIG_PCMCIA_RAYCS is not set
CONFIG_LIBERTAS=m
CONFIG_LIBERTAS_USB=m
CONFIG_LIBERTAS_CS=m
CONFIG_LIBERTAS_SDIO=m
CONFIG_LIBERTAS_DEBUG=y
# CONFIG_LIBERTAS_THINFIRM is not set
CONFIG_AIRO=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m
CONFIG_PCMCIA_ATMEL=m
# CONFIG_AT76C50X_USB is not set
CONFIG_AIRO_CS=m
CONFIG_PCMCIA_WL3501=m
CONFIG_PRISM54=m
CONFIG_USB_ZD1201=m
CONFIG_USB_NET_RNDIS_WLAN=m
CONFIG_RTL8180=m
CONFIG_RTL8187=m
CONFIG_ADM8211=m
CONFIG_MAC80211_HWSIM=m
# CONFIG_MWL8K is not set
CONFIG_P54_COMMON=m
CONFIG_P54_USB=m
CONFIG_P54_PCI=m
CONFIG_P54_LEDS=y
CONFIG_ATH5K=m
CONFIG_ATH5K_DEBUG=y
CONFIG_ATH9K=m
# CONFIG_ATH9K_DEBUG is not set
# CONFIG_AR9170_USB is not set
CONFIG_IPW2100=m
CONFIG_IPW2100_MONITOR=y
# CONFIG_IPW2100_DEBUG is not set
CONFIG_IPW2200=m
CONFIG_IPW2200_MONITOR=y
CONFIG_IPW2200_RADIOTAP=y
CONFIG_IPW2200_PROMISCUOUS=y
CONFIG_IPW2200_QOS=y
# CONFIG_IPW2200_DEBUG is not set
CONFIG_LIBIPW=m
# CONFIG_LIBIPW_DEBUG is not set
CONFIG_IWLWIFI=m
CONFIG_IWLWIFI_LEDS=y
CONFIG_IWLWIFI_RFKILL=y
# CONFIG_IWLWIFI_SPECTRUM_MEASUREMENT is not set
CONFIG_IWLWIFI_DEBUG=y
CONFIG_IWLWIFI_DEBUGFS=y
CONFIG_IWLAGN=m
CONFIG_IWL4965=y
CONFIG_IWL5000=y
CONFIG_IWL3945=m
CONFIG_IWL3945_SPECTRUM_MEASUREMENT=y
CONFIG_HOSTAP=m
CONFIG_HOSTAP_FIRMWARE=y
CONFIG_HOSTAP_FIRMWARE_NVRAM=y
CONFIG_HOSTAP_PLX=m
CONFIG_HOSTAP_PCI=m
CONFIG_HOSTAP_CS=m
CONFIG_B43=m
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
CONFIG_B43_PCMCIA=y
CONFIG_B43_PIO=y
CONFIG_B43_LEDS=y
CONFIG_B43_RFKILL=y
CONFIG_B43_DEBUG=y
# CONFIG_B43_FORCE_PIO is not set
CONFIG_B43LEGACY=m
CONFIG_B43LEGACY_PCI_AUTOSELECT=y
CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
CONFIG_B43LEGACY_LEDS=y
CONFIG_B43LEGACY_RFKILL=y
CONFIG_B43LEGACY_DEBUG=y
CONFIG_B43LEGACY_DMA=y
CONFIG_B43LEGACY_PIO=y
CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
# CONFIG_B43LEGACY_DMA_MODE is not set
# CONFIG_B43LEGACY_PIO_MODE is not set
CONFIG_ZD1211RW=m
# CONFIG_ZD1211RW_DEBUG is not set
CONFIG_HERMES=m
CONFIG_HERMES_CACHE_FW_ON_INIT=y
CONFIG_PLX_HERMES=m
CONFIG_TMD_HERMES=m
CONFIG_NORTEL_HERMES=m
CONFIG_PCI_HERMES=m
CONFIG_PCMCIA_HERMES=m
CONFIG_PCMCIA_SPECTRUM=m
#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#
#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
CONFIG_USB_NET_DM9601=m
# CONFIG_USB_NET_SMSC95XX is not set
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
CONFIG_USB_NET_MCS7830=m
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_KC2190=y
CONFIG_USB_NET_ZAURUS=m
CONFIG_USB_HSO=m
CONFIG_NET_PCMCIA=y
CONFIG_PCMCIA_3C589=m
CONFIG_PCMCIA_3C574=m
CONFIG_PCMCIA_FMVJ18X=m
CONFIG_PCMCIA_PCNET=m
CONFIG_PCMCIA_NMCLAN=m
CONFIG_PCMCIA_SMC91C92=m
CONFIG_PCMCIA_XIRC2PS=m
CONFIG_PCMCIA_AXNET=m
# CONFIG_PCMCIA_IBMTR is not set
# CONFIG_WAN is not set
CONFIG_ATM_DRIVERS=y
# CONFIG_ATM_DUMMY is not set
CONFIG_ATM_TCP=m
CONFIG_ATM_LANAI=m
CONFIG_ATM_ENI=m
# CONFIG_ATM_ENI_DEBUG is not set
# CONFIG_ATM_ENI_TUNE_BURST is not set
CONFIG_ATM_FIRESTREAM=m
# CONFIG_ATM_ZATM is not set
CONFIG_ATM_IDT77252=m
# CONFIG_ATM_IDT77252_DEBUG is not set
# CONFIG_ATM_IDT77252_RCV_ALL is not set
CONFIG_ATM_IDT77252_USE_SUNI=y
CONFIG_ATM_AMBASSADOR=m
# CONFIG_ATM_AMBASSADOR_DEBUG is not set
CONFIG_ATM_HORIZON=m
# CONFIG_ATM_HORIZON_DEBUG is not set
# CONFIG_ATM_IA is not set
CONFIG_ATM_FORE200E=m
# CONFIG_ATM_FORE200E_USE_TASKLET is not set
CONFIG_ATM_FORE200E_TX_RETRY=16
CONFIG_ATM_FORE200E_DEBUG=0
CONFIG_ATM_HE=m
# CONFIG_ATM_HE_USE_SUNI is not set
# CONFIG_ATM_SOLOS is not set
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_FDDI=y
# CONFIG_DEFXX is not set
CONFIG_SKFP=m
# CONFIG_HIPPI is not set
CONFIG_PLIP=m
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
# CONFIG_PPP_BSDCOMP is not set
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
CONFIG_PPPOL2TP=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLHC=m
CONFIG_SLIP_SMART=y
# CONFIG_SLIP_MODE_SLIP6 is not set
CONFIG_NET_FC=y
CONFIG_NETCONSOLE=m
CONFIG_NETCONSOLE_DYNAMIC=y
CONFIG_NETPOLL=y
CONFIG_NETPOLL_TRAP=y
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_VIRTIO_NET=m
CONFIG_ISDN=y
CONFIG_ISDN_I4L=m
CONFIG_ISDN_PPP=y
CONFIG_ISDN_PPP_VJ=y
CONFIG_ISDN_MPP=y
CONFIG_IPPP_FILTER=y
# CONFIG_ISDN_PPP_BSDCOMP is not set
CONFIG_ISDN_AUDIO=y
CONFIG_ISDN_TTY_FAX=y
#
# ISDN feature submodules
#
CONFIG_ISDN_DIVERSION=m
#
# ISDN4Linux hardware drivers
#
#
# Passive cards
#
CONFIG_ISDN_DRV_HISAX=m
#
# D-channel protocol features
#
CONFIG_HISAX_EURO=y
CONFIG_DE_AOC=y
CONFIG_HISAX_NO_SENDCOMPLETE=y
CONFIG_HISAX_NO_LLC=y
CONFIG_HISAX_NO_KEYPAD=y
CONFIG_HISAX_1TR6=y
CONFIG_HISAX_NI1=y
CONFIG_HISAX_MAX_CARDS=8
#
# HiSax supported cards
#
CONFIG_HISAX_16_3=y
CONFIG_HISAX_TELESPCI=y
CONFIG_HISAX_S0BOX=y
CONFIG_HISAX_FRITZPCI=y
CONFIG_HISAX_AVM_A1_PCMCIA=y
CONFIG_HISAX_ELSA=y
CONFIG_HISAX_DIEHLDIVA=y
CONFIG_HISAX_SEDLBAUER=y
CONFIG_HISAX_NETJET=y
CONFIG_HISAX_NETJET_U=y
CONFIG_HISAX_NICCY=y
CONFIG_HISAX_BKM_A4T=y
CONFIG_HISAX_SCT_QUADRO=y
CONFIG_HISAX_GAZEL=y
CONFIG_HISAX_HFC_PCI=y
CONFIG_HISAX_W6692=y
CONFIG_HISAX_HFC_SX=y
CONFIG_HISAX_ENTERNOW_PCI=y
# CONFIG_HISAX_DEBUG is not set
#
# HiSax PCMCIA card service modules
#
CONFIG_HISAX_SEDLBAUER_CS=m
CONFIG_HISAX_ELSA_CS=m
CONFIG_HISAX_AVM_A1_CS=m
CONFIG_HISAX_TELES_CS=m
#
# HiSax sub driver modules
#
CONFIG_HISAX_ST5481=m
# CONFIG_HISAX_HFCUSB is not set
CONFIG_HISAX_HFC4S8S=m
CONFIG_HISAX_FRITZ_PCIPNP=m
CONFIG_HISAX_HDLC=y
#
# Active cards
#
CONFIG_HYSDN=m
CONFIG_HYSDN_CAPI=y
CONFIG_ISDN_DRV_GIGASET=m
CONFIG_GIGASET_BASE=m
CONFIG_GIGASET_M105=m
CONFIG_GIGASET_M101=m
# CONFIG_GIGASET_DEBUG is not set
# CONFIG_GIGASET_UNDOCREQ is not set
CONFIG_ISDN_CAPI=m
CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON=y
# CONFIG_CAPI_TRACE is not set
CONFIG_ISDN_CAPI_MIDDLEWARE=y
CONFIG_ISDN_CAPI_CAPI20=m
CONFIG_ISDN_CAPI_CAPIFS_BOOL=y
CONFIG_ISDN_CAPI_CAPIFS=m
CONFIG_ISDN_CAPI_CAPIDRV=m
#
# CAPI hardware drivers
#
CONFIG_CAPI_AVM=y
CONFIG_ISDN_DRV_AVMB1_B1PCI=m
CONFIG_ISDN_DRV_AVMB1_B1PCIV4=y
CONFIG_ISDN_DRV_AVMB1_B1PCMCIA=m
CONFIG_ISDN_DRV_AVMB1_AVM_CS=m
CONFIG_ISDN_DRV_AVMB1_T1PCI=m
CONFIG_ISDN_DRV_AVMB1_C4=m
# CONFIG_CAPI_EICON is not set
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=y
CONFIG_INPUT_POLLDEV=m
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
CONFIG_XEN_KBDDEV_FRONTEND=m
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_APPLETOUCH=m
CONFIG_MOUSE_BCM5974=m
CONFIG_MOUSE_VSXXXAA=m
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
CONFIG_JOYSTICK_A3D=m
CONFIG_JOYSTICK_ADI=m
CONFIG_JOYSTICK_COBRA=m
CONFIG_JOYSTICK_GF2K=m
CONFIG_JOYSTICK_GRIP=m
CONFIG_JOYSTICK_GRIP_MP=m
CONFIG_JOYSTICK_GUILLEMOT=m
CONFIG_JOYSTICK_INTERACT=m
CONFIG_JOYSTICK_SIDEWINDER=m
CONFIG_JOYSTICK_TMDC=m
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_USB=y
CONFIG_JOYSTICK_IFORCE_232=y
CONFIG_JOYSTICK_WARRIOR=m
CONFIG_JOYSTICK_MAGELLAN=m
CONFIG_JOYSTICK_SPACEORB=m
CONFIG_JOYSTICK_SPACEBALL=m
CONFIG_JOYSTICK_STINGER=m
CONFIG_JOYSTICK_TWIDJOY=m
CONFIG_JOYSTICK_ZHENHUA=m
CONFIG_JOYSTICK_DB9=m
CONFIG_JOYSTICK_GAMECON=m
CONFIG_JOYSTICK_TURBOGRAFX=m
CONFIG_JOYSTICK_JOYDUMP=m
CONFIG_JOYSTICK_XPAD=m
CONFIG_JOYSTICK_XPAD_FF=y
CONFIG_JOYSTICK_XPAD_LEDS=y
# CONFIG_JOYSTICK_WALKERA0701 is not set
CONFIG_INPUT_TABLET=y
CONFIG_TABLET_USB_ACECAD=m
CONFIG_TABLET_USB_AIPTEK=m
CONFIG_TABLET_USB_GTCO=m
CONFIG_TABLET_USB_KBTAB=m
CONFIG_TABLET_USB_WACOM=m
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_AD7879_I2C is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
CONFIG_TOUCHSCREEN_FUJITSU=m
CONFIG_TOUCHSCREEN_GUNZE=m
CONFIG_TOUCHSCREEN_ELO=m
# CONFIG_TOUCHSCREEN_WACOM_W8001 is not set
CONFIG_TOUCHSCREEN_MTOUCH=m
CONFIG_TOUCHSCREEN_INEXIO=m
CONFIG_TOUCHSCREEN_MK712=m
CONFIG_TOUCHSCREEN_PENMOUNT=m
CONFIG_TOUCHSCREEN_TOUCHRIGHT=m
CONFIG_TOUCHSCREEN_TOUCHWIN=m
# CONFIG_TOUCHSCREEN_WM97XX is not set
CONFIG_TOUCHSCREEN_USB_COMPOSITE=m
CONFIG_TOUCHSCREEN_USB_EGALAX=y
CONFIG_TOUCHSCREEN_USB_PANJIT=y
CONFIG_TOUCHSCREEN_USB_3M=y
CONFIG_TOUCHSCREEN_USB_ITM=y
CONFIG_TOUCHSCREEN_USB_ETURBO=y
CONFIG_TOUCHSCREEN_USB_GUNZE=y
CONFIG_TOUCHSCREEN_USB_DMC_TSC10=y
CONFIG_TOUCHSCREEN_USB_IRTOUCH=y
CONFIG_TOUCHSCREEN_USB_IDEALTEK=y
CONFIG_TOUCHSCREEN_USB_GENERAL_TOUCH=y
CONFIG_TOUCHSCREEN_USB_GOTOP=y
CONFIG_TOUCHSCREEN_TOUCHIT213=m
# CONFIG_TOUCHSCREEN_TSC2007 is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_APANEL=m
CONFIG_INPUT_ATLAS_BTNS=m
CONFIG_INPUT_ATI_REMOTE=m
CONFIG_INPUT_ATI_REMOTE2=m
CONFIG_INPUT_KEYSPAN_REMOTE=m
CONFIG_INPUT_POWERMATE=m
CONFIG_INPUT_YEALINK=m
# CONFIG_INPUT_CM109 is not set
CONFIG_INPUT_UINPUT=m
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
CONFIG_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
CONFIG_GAMEPORT_L4=m
CONFIG_GAMEPORT_EMU10K1=m
CONFIG_GAMEPORT_FM801=m
#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
# CONFIG_DEVKMEM is not set
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
CONFIG_ROCKETPORT=m
CONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
CONFIG_SYNCLINK=m
CONFIG_SYNCLINKMP=m
CONFIG_SYNCLINK_GT=m
CONFIG_N_HDLC=m
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
# CONFIG_STALDRV is not set
CONFIG_NOZOMI=m
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_CONSOLE_POLL=y
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
# CONFIG_LEGACY_PTYS is not set
CONFIG_PRINTER=m
CONFIG_LP_CONSOLE=y
CONFIG_PPDEV=m
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_XEN=y
CONFIG_VIRTIO_CONSOLE=m
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
CONFIG_HW_RANDOM_VIRTIO=m
CONFIG_NVRAM=y
CONFIG_R3964=m
# CONFIG_APPLICOM is not set
#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
CONFIG_CARDMAN_4000=m
CONFIG_CARDMAN_4040=m
CONFIG_IPWIRELESS=m
CONFIG_MWAVE=m
# CONFIG_PC8736x_GPIO is not set
CONFIG_RAW_DRIVER=y
CONFIG_MAX_RAW_DEVS=8192
CONFIG_HPET=y
# CONFIG_HPET_MMAP is not set
CONFIG_HANGCHECK_TIMER=m
CONFIG_TCG_TPM=m
CONFIG_TCG_TIS=m
CONFIG_TCG_NSC=m
CONFIG_TCG_ATMEL=m
CONFIG_TCG_INFINEON=m
CONFIG_TELCLOCK=m
CONFIG_DEVPORT=y
CONFIG_I2C=m
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=m
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCA=m
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_I801=m
CONFIG_I2C_ISCH=m
CONFIG_I2C_PIIX4=m
CONFIG_I2C_NFORCE2=m
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
CONFIG_I2C_SIS96X=m
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_OCORES is not set
CONFIG_I2C_SIMTEC=m
#
# External I2C/SMBus adapter drivers
#
CONFIG_I2C_PARPORT=m
CONFIG_I2C_PARPORT_LIGHT=m
# CONFIG_I2C_TAOS_EVM is not set
CONFIG_I2C_TINY_USB=m
#
# Graphics adapter I2C/DDC channel drivers
#
CONFIG_I2C_VOODOO3=m
#
# Other I2C/SMBus bus drivers
#
CONFIG_I2C_PCA_PLATFORM=m
CONFIG_I2C_STUB=m
#
# Miscellaneous I2C Chip support
#
# CONFIG_DS1682 is not set
CONFIG_SENSORS_PCF8574=m
CONFIG_PCF8575=m
CONFIG_SENSORS_PCA9539=m
CONFIG_SENSORS_MAX6875=m
CONFIG_SENSORS_TSL2550=m
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
# CONFIG_SPI is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
CONFIG_W1=m
CONFIG_W1_CON=y
#
# 1-wire Bus Masters
#
# CONFIG_W1_MASTER_MATROX is not set
CONFIG_W1_MASTER_DS2490=m
CONFIG_W1_MASTER_DS2482=m
#
# 1-wire Slaves
#
CONFIG_W1_SLAVE_THERM=m
CONFIG_W1_SLAVE_SMEM=m
# CONFIG_W1_SLAVE_DS2431 is not set
CONFIG_W1_SLAVE_DS2433=m
CONFIG_W1_SLAVE_DS2433_CRC=y
CONFIG_W1_SLAVE_DS2760=m
# CONFIG_W1_SLAVE_BQ27000 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
# CONFIG_BATTERY_BQ27x00 is not set
CONFIG_HWMON=m
CONFIG_HWMON_VID=m
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ABITUGURU3=m
CONFIG_SENSORS_AD7414=m
CONFIG_SENSORS_AD7418=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
# CONFIG_SENSORS_ADT7462 is not set
CONFIG_SENSORS_ADT7470=m
CONFIG_SENSORS_ADT7473=m
# CONFIG_SENSORS_ADT7475 is not set
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_ASB100=m
# CONFIG_SENSORS_ATK0110 is not set
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FSCHER=m
CONFIG_SENSORS_FSCPOS=m
CONFIG_SENSORS_FSCHMD=m
# CONFIG_SENSORS_G760A is not set
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_CORETEMP=m
CONFIG_SENSORS_IBMAEM=m
CONFIG_SENSORS_IBMPEX=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_LM93=m
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LM95241 is not set
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX6650=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_DME1737=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_ADS7828=m
CONFIG_SENSORS_THMC50=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83L786NG=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
CONFIG_SENSORS_HDAPS=m
# CONFIG_SENSORS_LIS3LV02D is not set
CONFIG_SENSORS_APPLESMC=m
# CONFIG_HWMON_DEBUG_CHIP is not set
CONFIG_THERMAL=y
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
CONFIG_ALIM1535_WDT=m
CONFIG_ALIM7101_WDT=m
# CONFIG_SC520_WDT is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
CONFIG_IBMASR=m
# CONFIG_WAFER_WDT is not set
CONFIG_I6300ESB_WDT=m
CONFIG_ITCO_WDT=m
CONFIG_ITCO_VENDOR_SUPPORT=y
CONFIG_IT8712F_WDT=m
# CONFIG_IT87_WDT is not set
CONFIG_HP_WATCHDOG=m
# CONFIG_SC1200_WDT is not set
# CONFIG_PC87413_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SBC8360_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_SMSC_SCH311X_WDT is not set
# CONFIG_SMSC37B787_WDT is not set
CONFIG_W83627HF_WDT=m
CONFIG_W83697HF_WDT=m
# CONFIG_W83697UG_WDT is not set
CONFIG_W83877F_WDT=m
CONFIG_W83977F_WDT=m
CONFIG_MACHZ_WDT=m
# CONFIG_SBC_EPX_C3_WATCHDOG is not set
#
# PCI-based Watchdog Cards
#
CONFIG_PCIPCWATCHDOG=m
CONFIG_WDTPCI=m
CONFIG_WDT_501_PCI=y
#
# USB-based Watchdog Cards
#
CONFIG_USBPCWATCHDOG=m
CONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
CONFIG_SSB=m
CONFIG_SSB_SPROM=y
CONFIG_SSB_BLOCKIO=y
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
CONFIG_SSB_B43_PCI_BRIDGE=y
CONFIG_SSB_PCMCIAHOST_POSSIBLE=y
CONFIG_SSB_PCMCIAHOST=y
# CONFIG_SSB_DEBUG is not set
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y
#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
CONFIG_MFD_SM501=m
# CONFIG_HTC_PASIC3 is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_REGULATOR is not set
#
# Multimedia devices
#
#
# Multimedia core support
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L2_COMMON=m
CONFIG_VIDEO_ALLOW_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_DVB_CORE=m
CONFIG_VIDEO_MEDIA=m
#
# Multimedia drivers
#
CONFIG_VIDEO_SAA7146=m
CONFIG_VIDEO_SAA7146_VV=m
CONFIG_MEDIA_ATTACH=y
CONFIG_MEDIA_TUNER=m
# CONFIG_MEDIA_TUNER_CUSTOMISE is not set
CONFIG_MEDIA_TUNER_SIMPLE=m
CONFIG_MEDIA_TUNER_TDA8290=m
CONFIG_MEDIA_TUNER_TDA827X=m
CONFIG_MEDIA_TUNER_TDA18271=m
CONFIG_MEDIA_TUNER_TDA9887=m
CONFIG_MEDIA_TUNER_TEA5761=m
CONFIG_MEDIA_TUNER_TEA5767=m
CONFIG_MEDIA_TUNER_MT20XX=m
CONFIG_MEDIA_TUNER_MT2060=m
CONFIG_MEDIA_TUNER_MT2266=m
CONFIG_MEDIA_TUNER_MT2131=m
CONFIG_MEDIA_TUNER_QT1010=m
CONFIG_MEDIA_TUNER_XC2028=m
CONFIG_MEDIA_TUNER_XC5000=m
CONFIG_MEDIA_TUNER_MXL5005S=m
CONFIG_MEDIA_TUNER_MXL5007T=m
CONFIG_MEDIA_TUNER_MC44S803=m
CONFIG_VIDEO_V4L2=m
CONFIG_VIDEO_V4L1=m
CONFIG_VIDEOBUF_GEN=m
CONFIG_VIDEOBUF_DMA_SG=m
CONFIG_VIDEOBUF_VMALLOC=m
CONFIG_VIDEOBUF_DVB=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_IR=m
CONFIG_VIDEO_TVEEPROM=m
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
# CONFIG_VIDEO_HELPER_CHIPS_AUTO is not set
CONFIG_VIDEO_IR_I2C=m
#
# Encoders/decoders and other helper chips
#
#
# Audio decoders
#
CONFIG_VIDEO_TVAUDIO=m
CONFIG_VIDEO_TDA7432=m
CONFIG_VIDEO_TDA9840=m
CONFIG_VIDEO_TDA9875=m
CONFIG_VIDEO_TEA6415C=m
CONFIG_VIDEO_TEA6420=m
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_CS5345=m
CONFIG_VIDEO_CS53L32A=m
CONFIG_VIDEO_M52790=m
CONFIG_VIDEO_TLV320AIC23B=m
CONFIG_VIDEO_WM8775=m
CONFIG_VIDEO_WM8739=m
CONFIG_VIDEO_VP27SMPX=m
#
# RDS decoders
#
CONFIG_VIDEO_SAA6588=m
#
# Video decoders
#
CONFIG_VIDEO_BT819=m
CONFIG_VIDEO_BT856=m
CONFIG_VIDEO_BT866=m
CONFIG_VIDEO_KS0127=m
CONFIG_VIDEO_OV7670=m
CONFIG_VIDEO_TCM825X=m
CONFIG_VIDEO_SAA7110=m
CONFIG_VIDEO_SAA711X=m
CONFIG_VIDEO_SAA717X=m
CONFIG_VIDEO_SAA7191=m
# CONFIG_VIDEO_TVP514X is not set
CONFIG_VIDEO_TVP5150=m
CONFIG_VIDEO_VPX3220=m
#
# Video and audio decoders
#
CONFIG_VIDEO_CX25840=m
#
# MPEG video encoders
#
CONFIG_VIDEO_CX2341X=m
#
# Video encoders
#
CONFIG_VIDEO_SAA7127=m
CONFIG_VIDEO_SAA7185=m
CONFIG_VIDEO_ADV7170=m
CONFIG_VIDEO_ADV7175=m
#
# Video improvement chips
#
CONFIG_VIDEO_UPD64031A=m
CONFIG_VIDEO_UPD64083=m
# CONFIG_VIDEO_VIVI is not set
CONFIG_VIDEO_BT848=m
CONFIG_VIDEO_BT848_DVB=y
CONFIG_VIDEO_BWQCAM=m
CONFIG_VIDEO_CQCAM=m
CONFIG_VIDEO_W9966=m
CONFIG_VIDEO_CPIA=m
CONFIG_VIDEO_CPIA_PP=m
CONFIG_VIDEO_CPIA_USB=m
CONFIG_VIDEO_CPIA2=m
CONFIG_VIDEO_SAA5246A=m
CONFIG_VIDEO_SAA5249=m
CONFIG_VIDEO_STRADIS=m
CONFIG_VIDEO_ZORAN=m
CONFIG_VIDEO_ZORAN_DC30=m
CONFIG_VIDEO_ZORAN_ZR36060=m
CONFIG_VIDEO_ZORAN_BUZ=m
CONFIG_VIDEO_ZORAN_DC10=m
CONFIG_VIDEO_ZORAN_LML33=m
CONFIG_VIDEO_ZORAN_LML33R10=m
CONFIG_VIDEO_ZORAN_AVS6EYES=m
CONFIG_VIDEO_MEYE=m
CONFIG_VIDEO_SAA7134=m
CONFIG_VIDEO_SAA7134_ALSA=m
CONFIG_VIDEO_SAA7134_DVB=m
CONFIG_VIDEO_MXB=m
CONFIG_VIDEO_HEXIUM_ORION=m
CONFIG_VIDEO_HEXIUM_GEMINI=m
CONFIG_VIDEO_CX23885=m
CONFIG_VIDEO_IVTV=m
CONFIG_VIDEO_FB_IVTV=m
CONFIG_VIDEO_CX18=m
# CONFIG_VIDEO_CAFE_CCIC is not set
CONFIG_SOC_CAMERA=m
CONFIG_SOC_CAMERA_MT9M001=m
# CONFIG_SOC_CAMERA_MT9M111 is not set
# CONFIG_SOC_CAMERA_MT9T031 is not set
CONFIG_SOC_CAMERA_MT9V022=m
# CONFIG_SOC_CAMERA_TW9910 is not set
CONFIG_SOC_CAMERA_PLATFORM=m
# CONFIG_SOC_CAMERA_OV772X is not set
CONFIG_V4L_USB_DRIVERS=y
CONFIG_USB_VIDEO_CLASS=m
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_USB_GSPCA=m
# CONFIG_USB_M5602 is not set
# CONFIG_USB_STV06XX is not set
# CONFIG_USB_GSPCA_CONEX is not set
# CONFIG_USB_GSPCA_ETOMS is not set
# CONFIG_USB_GSPCA_FINEPIX is not set
# CONFIG_USB_GSPCA_MARS is not set
# CONFIG_USB_GSPCA_MR97310A is not set
# CONFIG_USB_GSPCA_OV519 is not set
# CONFIG_USB_GSPCA_OV534 is not set
# CONFIG_USB_GSPCA_PAC207 is not set
# CONFIG_USB_GSPCA_PAC7311 is not set
# CONFIG_USB_GSPCA_SONIXB is not set
# CONFIG_USB_GSPCA_SONIXJ is not set
# CONFIG_USB_GSPCA_SPCA500 is not set
# CONFIG_USB_GSPCA_SPCA501 is not set
# CONFIG_USB_GSPCA_SPCA505 is not set
# CONFIG_USB_GSPCA_SPCA506 is not set
# CONFIG_USB_GSPCA_SPCA508 is not set
# CONFIG_USB_GSPCA_SPCA561 is not set
# CONFIG_USB_GSPCA_SQ905 is not set
# CONFIG_USB_GSPCA_SQ905C is not set
# CONFIG_USB_GSPCA_STK014 is not set
# CONFIG_USB_GSPCA_SUNPLUS is not set
# CONFIG_USB_GSPCA_T613 is not set
# CONFIG_USB_GSPCA_TV8532 is not set
# CONFIG_USB_GSPCA_VC032X is not set
# CONFIG_USB_GSPCA_ZC3XX is not set
CONFIG_VIDEO_PVRUSB2=m
CONFIG_VIDEO_PVRUSB2_SYSFS=y
CONFIG_VIDEO_PVRUSB2_DVB=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set
CONFIG_VIDEO_HDPVR=m
CONFIG_VIDEO_EM28XX=m
CONFIG_VIDEO_EM28XX_ALSA=m
CONFIG_VIDEO_EM28XX_DVB=m
CONFIG_VIDEO_USBVISION=m
CONFIG_VIDEO_USBVIDEO=m
CONFIG_USB_VICAM=m
CONFIG_USB_IBMCAM=m
CONFIG_USB_KONICAWC=m
CONFIG_USB_QUICKCAM_MESSENGER=m
CONFIG_USB_ET61X251=m
CONFIG_VIDEO_OVCAMCHIP=m
CONFIG_USB_W9968CF=m
CONFIG_USB_OV511=m
CONFIG_USB_SE401=m
CONFIG_USB_SN9C102=m
CONFIG_USB_STV680=m
# CONFIG_USB_ZC0301 is not set
CONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not set
CONFIG_USB_PWC_INPUT_EVDEV=y
CONFIG_USB_ZR364XX=m
CONFIG_USB_STKWEBCAM=m
CONFIG_USB_S2255=m
CONFIG_RADIO_ADAPTERS=y
CONFIG_RADIO_GEMTEK_PCI=m
CONFIG_RADIO_MAXIRADIO=m
CONFIG_RADIO_MAESTRO=m
CONFIG_USB_DSBR=m
CONFIG_USB_SI470X=m
# CONFIG_USB_MR800 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_DVB_DYNAMIC_MINORS is not set
CONFIG_DVB_CAPTURE_DRIVERS=y
#
# Supported SAA7146 based PCI Adapters
#
CONFIG_TTPCI_EEPROM=m
CONFIG_DVB_AV7110=m
CONFIG_DVB_AV7110_OSD=y
CONFIG_DVB_BUDGET_CORE=m
CONFIG_DVB_BUDGET=m
CONFIG_DVB_BUDGET_CI=m
CONFIG_DVB_BUDGET_AV=m
CONFIG_DVB_BUDGET_PATCH=m
#
# Supported USB Adapters
#
CONFIG_DVB_USB=m
# CONFIG_DVB_USB_DEBUG is not set
CONFIG_DVB_USB_A800=m
CONFIG_DVB_USB_DIBUSB_MB=m
# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set
CONFIG_DVB_USB_DIBUSB_MC=m
CONFIG_DVB_USB_DIB0700=m
CONFIG_DVB_USB_UMT_010=m
CONFIG_DVB_USB_CXUSB=m
CONFIG_DVB_USB_M920X=m
CONFIG_DVB_USB_GL861=m
CONFIG_DVB_USB_AU6610=m
CONFIG_DVB_USB_DIGITV=m
CONFIG_DVB_USB_VP7045=m
CONFIG_DVB_USB_VP702X=m
CONFIG_DVB_USB_GP8PSK=m
CONFIG_DVB_USB_NOVA_T_USB2=m
CONFIG_DVB_USB_TTUSB2=m
CONFIG_DVB_USB_DTT200U=m
CONFIG_DVB_USB_OPERA1=m
CONFIG_DVB_USB_DW2102=m
# CONFIG_DVB_USB_CINERGY_T2 is not set
CONFIG_DVB_USB_ANYSEE=m
# CONFIG_DVB_USB_DTV5100 is not set
# CONFIG_DVB_USB_AF9015 is not set
# CONFIG_DVB_USB_CE6230 is not set
CONFIG_DVB_TTUSB_BUDGET=m
CONFIG_DVB_TTUSB_DEC=m
CONFIG_DVB_SIANO_SMS1XXX=m
CONFIG_DVB_SIANO_SMS1XXX_SMS_IDS=y
#
# Supported FlexCopII (B2C2) Adapters
#
CONFIG_DVB_B2C2_FLEXCOP=m
CONFIG_DVB_B2C2_FLEXCOP_PCI=m
CONFIG_DVB_B2C2_FLEXCOP_USB=m
# CONFIG_DVB_B2C2_FLEXCOP_DEBUG is not set
#
# Supported BT878 Adapters
#
CONFIG_DVB_BT8XX=m
#
# Supported Pluto2 Adapters
#
CONFIG_DVB_PLUTO2=m
#
# Supported SDMC DM1105 Adapters
#
# CONFIG_DVB_DM1105 is not set
#
# Supported DVB Frontends
#
# CONFIG_DVB_FE_CUSTOMISE is not set
CONFIG_DVB_STB0899=m
CONFIG_DVB_STB6100=m
CONFIG_DVB_CX24110=m
CONFIG_DVB_CX24123=m
CONFIG_DVB_MT312=m
CONFIG_DVB_ZL10036=m
CONFIG_DVB_S5H1420=m
CONFIG_DVB_STV0288=m
CONFIG_DVB_STB6000=m
CONFIG_DVB_STV0299=m
CONFIG_DVB_STV6110=m
CONFIG_DVB_STV0900=m
CONFIG_DVB_TDA8083=m
CONFIG_DVB_TDA10086=m
CONFIG_DVB_TDA8261=m
CONFIG_DVB_VES1X93=m
CONFIG_DVB_TUNER_ITD1000=m
CONFIG_DVB_TUNER_CX24113=m
CONFIG_DVB_TDA826X=m
CONFIG_DVB_TUA6100=m
CONFIG_DVB_CX24116=m
CONFIG_DVB_SI21XX=m
CONFIG_DVB_SP8870=m
CONFIG_DVB_SP887X=m
CONFIG_DVB_CX22700=m
CONFIG_DVB_CX22702=m
CONFIG_DVB_L64781=m
CONFIG_DVB_TDA1004X=m
CONFIG_DVB_NXT6000=m
CONFIG_DVB_MT352=m
CONFIG_DVB_ZL10353=m
CONFIG_DVB_DIB3000MB=m
CONFIG_DVB_DIB3000MC=m
CONFIG_DVB_DIB7000M=m
CONFIG_DVB_DIB7000P=m
CONFIG_DVB_TDA10048=m
CONFIG_DVB_VES1820=m
CONFIG_DVB_TDA10021=m
CONFIG_DVB_TDA10023=m
CONFIG_DVB_STV0297=m
CONFIG_DVB_NXT200X=m
CONFIG_DVB_OR51211=m
CONFIG_DVB_BCM3510=m
CONFIG_DVB_LGDT330X=m
CONFIG_DVB_LGDT3305=m
CONFIG_DVB_S5H1409=m
CONFIG_DVB_S5H1411=m
CONFIG_DVB_PLL=m
CONFIG_DVB_TUNER_DIB0070=m
CONFIG_DVB_LNBP21=m
CONFIG_DVB_ISL6405=m
CONFIG_DVB_ISL6421=m
CONFIG_DVB_LGS8GL5=m
CONFIG_DAB=y
CONFIG_USB_DABUSB=m
#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
CONFIG_AGP_SIS=y
CONFIG_AGP_VIA=y
CONFIG_DRM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
# CONFIG_DRM_I915_KMS is not set
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
CONFIG_DRM_VIA=m
CONFIG_DRM_SAVAGE=m
CONFIG_VGASTATE=m
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
CONFIG_FB_DDC=m
CONFIG_FB_BOOT_VESA_SUPPORT=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
CONFIG_FB_SYS_FILLRECT=m
CONFIG_FB_SYS_COPYAREA=m
CONFIG_FB_SYS_IMAGEBLIT=m
# CONFIG_FB_FOREIGN_ENDIAN is not set
CONFIG_FB_SYS_FOPS=m
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_SVGALIB=m
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
CONFIG_FB_CIRRUS=m
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=m
# CONFIG_FB_UVESA is not set
CONFIG_FB_VESA=y
CONFIG_FB_EFI=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
CONFIG_FB_NVIDIA=m
CONFIG_FB_NVIDIA_I2C=y
# CONFIG_FB_NVIDIA_DEBUG is not set
CONFIG_FB_NVIDIA_BACKLIGHT=y
CONFIG_FB_RIVA=m
# CONFIG_FB_RIVA_I2C is not set
# CONFIG_FB_RIVA_DEBUG is not set
CONFIG_FB_RIVA_BACKLIGHT=y
# CONFIG_FB_LE80578 is not set
CONFIG_FB_INTEL=m
# CONFIG_FB_INTEL_DEBUG is not set
CONFIG_FB_INTEL_I2C=y
CONFIG_FB_MATROX=m
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MAVEN=m
CONFIG_FB_MATROX_MULTIHEAD=y
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=m
CONFIG_FB_ATY128_BACKLIGHT=y
CONFIG_FB_ATY=m
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_ATY_BACKLIGHT=y
CONFIG_FB_S3=m
CONFIG_FB_SAVAGE=m
CONFIG_FB_SAVAGE_I2C=y
CONFIG_FB_SAVAGE_ACCEL=y
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
CONFIG_FB_NEOMAGIC=m
CONFIG_FB_KYRO=m
CONFIG_FB_3DFX=m
CONFIG_FB_3DFX_ACCEL=y
CONFIG_FB_3DFX_I2C=y
CONFIG_FB_VOODOO1=m
# CONFIG_FB_VT8623 is not set
CONFIG_FB_TRIDENT=m
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_GEODE is not set
CONFIG_FB_SM501=m
# CONFIG_FB_VIRTUAL is not set
CONFIG_XEN_FBDEV_FRONTEND=m
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_BROADSHEET is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_LCD_CLASS_DEVICE=m
# CONFIG_LCD_ILI9320 is not set
CONFIG_LCD_PLATFORM=m
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_GENERIC=y
CONFIG_BACKLIGHT_PROGEAR=m
CONFIG_BACKLIGHT_MBP_NVIDIA=m
# CONFIG_BACKLIGHT_SAHARA is not set
#
# Display device support
#
CONFIG_DISPLAY_SUPPORT=m
#
# Display hardware drivers
#
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_SOUND=m
CONFIG_SOUND_OSS_CORE=y
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_JACK=y
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_HRTIMER is not set
CONFIG_SND_DYNAMIC_MINORS=y
# CONFIG_SND_SUPPORT_OLD_API is not set
CONFIG_SND_VERBOSE_PROCFS=y
CONFIG_SND_VERBOSE_PRINTK=y
CONFIG_SND_DEBUG=y
# CONFIG_SND_DEBUG_VERBOSE is not set
CONFIG_SND_PCM_XRUN_DEBUG=y
CONFIG_SND_VMASTER=y
CONFIG_SND_MPU401_UART=m
CONFIG_SND_OPL3_LIB=m
CONFIG_SND_VX_LIB=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_DRIVERS=y
# CONFIG_SND_PCSP is not set
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTS64=m
CONFIG_SND_SERIAL_U16550=m
CONFIG_SND_MPU401=m
CONFIG_SND_PORTMAN2X4=m
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0
CONFIG_SND_SB_COMMON=m
CONFIG_SND_SB16_DSP=m
CONFIG_SND_PCI=y
CONFIG_SND_AD1889=m
CONFIG_SND_ALS300=m
CONFIG_SND_ALS4000=m
CONFIG_SND_ALI5451=m
CONFIG_SND_ATIIXP=m
CONFIG_SND_ATIIXP_MODEM=m
CONFIG_SND_AU8810=m
CONFIG_SND_AU8820=m
CONFIG_SND_AU8830=m
# CONFIG_SND_AW2 is not set
CONFIG_SND_AZT3328=m
CONFIG_SND_BT87X=m
# CONFIG_SND_BT87X_OVERCLOCK is not set
CONFIG_SND_CA0106=m
CONFIG_SND_CMIPCI=m
CONFIG_SND_OXYGEN_LIB=m
CONFIG_SND_OXYGEN=m
CONFIG_SND_CS4281=m
CONFIG_SND_CS46XX=m
CONFIG_SND_CS46XX_NEW_DSP=y
CONFIG_SND_CS5530=m
CONFIG_SND_DARLA20=m
CONFIG_SND_GINA20=m
CONFIG_SND_LAYLA20=m
CONFIG_SND_DARLA24=m
CONFIG_SND_GINA24=m
CONFIG_SND_LAYLA24=m
CONFIG_SND_MONA=m
CONFIG_SND_MIA=m
CONFIG_SND_ECHO3G=m
CONFIG_SND_INDIGO=m
CONFIG_SND_INDIGOIO=m
CONFIG_SND_INDIGODJ=m
# CONFIG_SND_INDIGOIOX is not set
# CONFIG_SND_INDIGODJX is not set
CONFIG_SND_EMU10K1=m
CONFIG_SND_EMU10K1X=m
CONFIG_SND_ENS1370=m
CONFIG_SND_ENS1371=m
CONFIG_SND_ES1938=m
CONFIG_SND_ES1968=m
CONFIG_SND_FM801=m
CONFIG_SND_FM801_TEA575X_BOOL=y
CONFIG_SND_FM801_TEA575X=m
CONFIG_SND_HDA_INTEL=m
CONFIG_SND_HDA_HWDEP=y
# CONFIG_SND_HDA_RECONFIG is not set
# CONFIG_SND_HDA_INPUT_BEEP is not set
CONFIG_SND_HDA_CODEC_REALTEK=y
CONFIG_SND_HDA_CODEC_ANALOG=y
CONFIG_SND_HDA_CODEC_SIGMATEL=y
CONFIG_SND_HDA_CODEC_VIA=y
CONFIG_SND_HDA_CODEC_ATIHDMI=y
CONFIG_SND_HDA_CODEC_NVHDMI=y
CONFIG_SND_HDA_CODEC_INTELHDMI=y
CONFIG_SND_HDA_ELD=y
CONFIG_SND_HDA_CODEC_CONEXANT=y
CONFIG_SND_HDA_CODEC_CMEDIA=y
CONFIG_SND_HDA_CODEC_SI3054=y
CONFIG_SND_HDA_GENERIC=y
CONFIG_SND_HDA_POWER_SAVE=y
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
CONFIG_SND_HDSP=m
CONFIG_SND_HDSPM=m
CONFIG_SND_HIFIER=m
CONFIG_SND_ICE1712=m
CONFIG_SND_ICE1724=m
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
CONFIG_SND_KORG1212=m
CONFIG_SND_MAESTRO3=m
CONFIG_SND_MIXART=m
CONFIG_SND_NM256=m
CONFIG_SND_PCXHR=m
CONFIG_SND_RIPTIDE=m
CONFIG_SND_RME32=m
CONFIG_SND_RME96=m
CONFIG_SND_RME9652=m
CONFIG_SND_SONICVIBES=m
CONFIG_SND_TRIDENT=m
CONFIG_SND_VIA82XX=m
CONFIG_SND_VIA82XX_MODEM=m
CONFIG_SND_VIRTUOSO=m
CONFIG_SND_VX222=m
CONFIG_SND_YMFPCI=m
CONFIG_SND_USB=y
CONFIG_SND_USB_AUDIO=m
CONFIG_SND_USB_USX2Y=m
CONFIG_SND_USB_CAIAQ=m
CONFIG_SND_USB_CAIAQ_INPUT=y
# CONFIG_SND_USB_US122L is not set
# CONFIG_SND_PCMCIA is not set
# CONFIG_SND_SOC is not set
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=m
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
CONFIG_HID_DEBUG=y
CONFIG_HIDRAW=y
#
# USB Input Devices
#
CONFIG_USB_HID=y
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y
#
# Special HID drivers
#
CONFIG_HID_A4TECH=y
CONFIG_HID_APPLE=y
CONFIG_HID_BELKIN=y
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
CONFIG_HID_CYPRESS=y
# CONFIG_DRAGONRISE_FF is not set
CONFIG_HID_EZKEY=y
CONFIG_HID_KYE=y
CONFIG_HID_GYRATION=y
CONFIG_HID_KENSINGTON=y
CONFIG_HID_LOGITECH=y
CONFIG_LOGITECH_FF=y
CONFIG_LOGIRUMBLEPAD2_FF=y
CONFIG_HID_MICROSOFT=y
CONFIG_HID_MONTEREY=y
CONFIG_HID_NTRIG=y
CONFIG_HID_PANTHERLORD=y
CONFIG_PANTHERLORD_FF=y
CONFIG_HID_PETALYNX=y
CONFIG_HID_SAMSUNG=y
CONFIG_HID_SONY=y
CONFIG_HID_SUNPLUS=y
# CONFIG_GREENASIA_FF is not set
CONFIG_HID_TOPSEED=y
CONFIG_THRUSTMASTER_FF=y
CONFIG_ZEROPLUS_FF=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set
CONFIG_USB_MON=y
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_HCD_SSB is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_U132_HCD=m
CONFIG_USB_SL811_HCD=m
# CONFIG_USB_SL811_CS is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HWA_HCD is not set
#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
CONFIG_USB_WDM=m
# CONFIG_USB_TMC is not set
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=m
CONFIG_USB_STORAGE_FREECOM=m
CONFIG_USB_STORAGE_ISD200=m
CONFIG_USB_STORAGE_USBAT=m
CONFIG_USB_STORAGE_SDDR09=m
CONFIG_USB_STORAGE_SDDR55=m
CONFIG_USB_STORAGE_JUMPSHOT=m
CONFIG_USB_STORAGE_ALAUDA=m
CONFIG_USB_STORAGE_ONETOUCH=m
CONFIG_USB_STORAGE_KARMA=m
CONFIG_USB_STORAGE_CYPRESS_ATACB=m
# CONFIG_USB_LIBUSUAL is not set
#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m
#
# USB port drivers
#
CONFIG_USB_USS720=m
CONFIG_USB_SERIAL=m
CONFIG_USB_EZUSB=y
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_AIRCABLE=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_CH341=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
# CONFIG_USB_SERIAL_CP210X is not set
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_FUNSOFT=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
# CONFIG_USB_SERIAL_GARMIN is not set
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_IUU=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_MOS7720=m
CONFIG_USB_SERIAL_MOS7840=m
CONFIG_USB_SERIAL_MOTOROLA=m
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_OTI6858=m
# CONFIG_USB_SERIAL_QUALCOMM is not set
CONFIG_USB_SERIAL_SPCP8X5=m
CONFIG_USB_SERIAL_HP4X=m
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
# CONFIG_USB_SERIAL_SIEMENS_MPI is not set
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
# CONFIG_USB_SERIAL_SYMBOL is not set
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
# CONFIG_USB_SERIAL_OPTICON is not set
CONFIG_USB_SERIAL_DEBUG=m
#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_ADUTUX=m
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
CONFIG_USB_BERRY_CHARGE=m
CONFIG_USB_LED=m
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
CONFIG_USB_IDMOUSE=m
CONFIG_USB_FTDI_ELAN=m
CONFIG_USB_APPLEDISPLAY=m
CONFIG_USB_SISUSBVGA=m
CONFIG_USB_SISUSBVGA_CON=y
CONFIG_USB_LD=m
CONFIG_USB_TRANCEVIBRATOR=m
CONFIG_USB_IOWARRIOR=m
# CONFIG_USB_TEST is not set
CONFIG_USB_ISIGHTFW=m
# CONFIG_USB_VST is not set
CONFIG_USB_ATM=m
CONFIG_USB_SPEEDTOUCH=m
CONFIG_USB_CXACRU=m
CONFIG_USB_UEAGLEATM=m
CONFIG_USB_XUSBATM=m
#
# OTG and related infrastructure
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_UWB is not set
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set
#
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_BOUNCE=y
CONFIG_SDIO_UART=m
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
CONFIG_MMC_SDHCI_PCI=m
CONFIG_MMC_RICOH_MMC=m
CONFIG_MMC_WBSD=m
CONFIG_MMC_TIFM_SD=m
CONFIG_MMC_SDRICOH_CS=m
CONFIG_MEMSTICK=m
# CONFIG_MEMSTICK_DEBUG is not set
#
# MemoryStick drivers
#
# CONFIG_MEMSTICK_UNSAFE_RESUME is not set
CONFIG_MSPRO_BLOCK=m
#
# MemoryStick Host Controller Drivers
#
CONFIG_MEMSTICK_TIFM_MS=m
CONFIG_MEMSTICK_JMICRON_38X=m
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
#
# LED drivers
#
# CONFIG_LEDS_ALIX2 is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_LP5521 is not set
CONFIG_LEDS_CLEVO_MAIL=m
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_BD2802 is not set
#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_HEARTBEAT=m
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
CONFIG_LEDS_TRIGGER_DEFAULT_ON=m
#
# iptables trigger is under Netfilter config (LED target)
#
CONFIG_ACCESSIBILITY=y
CONFIG_A11Y_BRAILLE_CONSOLE=y
CONFIG_EDAC=y
#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_MM_EDAC=m
CONFIG_EDAC_E752X=m
CONFIG_EDAC_I82975X=m
CONFIG_EDAC_I3000=m
# CONFIG_EDAC_X38 is not set
# CONFIG_EDAC_I5400 is not set
CONFIG_EDAC_I5000=m
CONFIG_EDAC_I5100=m
# CONFIG_EDAC_AMD8131 is not set
# CONFIG_EDAC_AMD8111 is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
# CONFIG_RTC_HCTOSYS is not set
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1374=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_MAX6900=m
CONFIG_RTC_DRV_RS5C372=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_PCF8563=m
CONFIG_RTC_DRV_PCF8583=m
CONFIG_RTC_DRV_M41T80=m
CONFIG_RTC_DRV_M41T80_WDT=y
# CONFIG_RTC_DRV_S35390A is not set
CONFIG_RTC_DRV_FM3130=m
# CONFIG_RTC_DRV_RX8581 is not set
#
# SPI RTC drivers
#
#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
# CONFIG_RTC_DRV_DS1286 is not set
CONFIG_RTC_DRV_DS1511=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_STK17TA8=m
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
CONFIG_RTC_DRV_M48T59=m
# CONFIG_RTC_DRV_BQ4802 is not set
CONFIG_RTC_DRV_V3020=m
#
# on-CPU RTC drivers
#
CONFIG_DMADEVICES=y
#
# DMA Devices
#
CONFIG_INTEL_IOATDMA=m
CONFIG_DMA_ENGINE=y
#
# DMA Clients
#
CONFIG_NET_DMA=y
# CONFIG_ASYNC_TX_DMA is not set
# CONFIG_DMATEST is not set
CONFIG_DCA=m
CONFIG_AUXDISPLAY=y
CONFIG_KS0108=m
CONFIG_KS0108_PORT=0x378
CONFIG_KS0108_DELAY=2
CONFIG_CFAG12864B=m
CONFIG_CFAG12864B_RATE=20
CONFIG_UIO=m
CONFIG_UIO_CIF=m
CONFIG_UIO_PDRV=m
CONFIG_UIO_PDRV_GENIRQ=m
CONFIG_UIO_SMX=m
# CONFIG_UIO_AEC is not set
# CONFIG_UIO_SERCOS3 is not set
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=y
CONFIG_XEN_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_NETDEV_BACKEND=y
CONFIG_XENFS=y
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_XENBUS_FRONTEND=m
CONFIG_XEN_GNTDEV=y
# CONFIG_STAGING is not set
CONFIG_X86_PLATFORM_DEVICES=y
CONFIG_ACER_WMI=m
CONFIG_ASUS_LAPTOP=m
# CONFIG_DELL_WMI is not set
CONFIG_FUJITSU_LAPTOP=m
# CONFIG_FUJITSU_LAPTOP_DEBUG is not set
CONFIG_HP_WMI=m
CONFIG_MSI_LAPTOP=m
# CONFIG_PANASONIC_LAPTOP is not set
CONFIG_COMPAL_LAPTOP=m
CONFIG_SONY_LAPTOP=m
CONFIG_SONYPI_COMPAT=y
CONFIG_THINKPAD_ACPI=m
# CONFIG_THINKPAD_ACPI_DEBUGFACILITIES is not set
# CONFIG_THINKPAD_ACPI_DEBUG is not set
# CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not set
CONFIG_THINKPAD_ACPI_BAY=y
CONFIG_THINKPAD_ACPI_VIDEO=y
CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y
# CONFIG_INTEL_MENLOW is not set
# CONFIG_EEEPC_LAPTOP is not set
CONFIG_ACPI_WMI=m
# CONFIG_ACPI_ASUS is not set
CONFIG_ACPI_TOSHIBA=m
#
# Firmware Drivers
#
CONFIG_EDD=m
# CONFIG_EDD_OFF is not set
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_EFI_VARS=y
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
CONFIG_DMIID=y
CONFIG_ISCSI_IBFT_FIND=y
CONFIG_ISCSI_IBFT=m
#
# File systems
#
CONFIG_EXT2_FS=m
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT2_FS_XIP=y
CONFIG_EXT3_FS=m
# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=m
CONFIG_EXT4DEV_COMPAT=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
CONFIG_FS_XIP=y
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=m
CONFIG_JBD2_DEBUG=y
CONFIG_FS_MBCACHE=m
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_FILE_LOCKING=y
CONFIG_XFS_FS=m
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
# CONFIG_XFS_RT is not set
# CONFIG_XFS_DEBUG is not set
CONFIG_GFS2_FS=m
# CONFIG_GFS2_FS_LOCKING_DLM is not set
CONFIG_OCFS2_FS=m
CONFIG_OCFS2_FS_O2CB=m
CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m
# CONFIG_OCFS2_FS_STATS is not set
# CONFIG_OCFS2_DEBUG_MASKLOG is not set
# CONFIG_OCFS2_DEBUG_FS is not set
# CONFIG_OCFS2_FS_POSIX_ACL is not set
# CONFIG_BTRFS_FS is not set
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
# CONFIG_PRINT_QUOTA_WARNING is not set
CONFIG_QUOTA_TREE=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m
CONFIG_GENERIC_ACL=y
#
# Caches
#
# CONFIG_FSCACHE is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="ascii"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_CONFIGFS_FS=m
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
CONFIG_AFFS_FS=m
CONFIG_ECRYPT_FS=m
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_BEFS_FS=m
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=m
CONFIG_EFS_FS=m
CONFIG_JFFS2_FS=m
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
CONFIG_JFFS2_SUMMARY=y
CONFIG_JFFS2_FS_XATTR=y
CONFIG_JFFS2_FS_POSIX_ACL=y
CONFIG_JFFS2_FS_SECURITY=y
# CONFIG_JFFS2_COMPRESSION_OPTIONS is not set
CONFIG_JFFS2_ZLIB=y
# CONFIG_JFFS2_LZO is not set
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
CONFIG_UBIFS_FS=m
CONFIG_UBIFS_FS_XATTR=y
# CONFIG_UBIFS_FS_ADVANCED_COMPR is not set
CONFIG_UBIFS_FS_LZO=y
CONFIG_UBIFS_FS_ZLIB=y
# CONFIG_UBIFS_FS_DEBUG is not set
CONFIG_CRAMFS=m
CONFIG_SQUASHFS=m
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
CONFIG_VXFS_FS=m
CONFIG_MINIX_FS=m
CONFIG_OMFS_FS=m
# CONFIG_HPFS_FS is not set
CONFIG_QNX4FS_FS=m
CONFIG_ROMFS_FS=m
CONFIG_ROMFS_BACKED_BY_BLOCK=y
# CONFIG_ROMFS_BACKED_BY_MTD is not set
# CONFIG_ROMFS_BACKED_BY_BOTH is not set
CONFIG_ROMFS_ON_BLOCK=y
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_UFS_DEBUG is not set
# CONFIG_NILFS2_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_RPCSEC_GSS_SPKM3=m
# CONFIG_SMB_FS is not set
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
CONFIG_CIFS_WEAK_PW_HASH=y
CONFIG_CIFS_UPCALL=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
CONFIG_CIFS_DFS_UPCALL=y
CONFIG_CIFS_EXPERIMENTAL=y
CONFIG_NCP_FS=m
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
CONFIG_NCPFS_SMALLDOS=y
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
CONFIG_CODA_FS=m
# CONFIG_AFS_FS is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
CONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not set
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m
CONFIG_DLM=m
CONFIG_DLM_DEBUG=y
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ALLOW_WARNINGS=y
# CONFIG_ENABLE_WARN_DEPRECATED is not set
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=2048
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
CONFIG_HEADERS_CHECK=y
# CONFIG_DEBUG_SECTION_MISMATCH is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_SHIRQ=y
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
CONFIG_DETECT_HUNG_TASK=y
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
CONFIG_SCHED_DEBUG=y
CONFIG_SCHEDSTATS=y
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
CONFIG_DEBUG_LIST=y
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y
CONFIG_BOOT_PRINTK_DELAY=y
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_KPROBES_SANITY_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_LKDTM is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_LATENCYTOP=y
# CONFIG_SYSCTL_SYSCALL_CHECK is not set
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_NOP_TRACER=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_FTRACE_SYSCALLS=y
CONFIG_RING_BUFFER=y
CONFIG_EVENT_TRACING=y
CONFIG_TRACING=y
CONFIG_TRACING_SUPPORT=y
# CONFIG_FTRACE is not set
CONFIG_PROVIDE_OHCI1394_DMA_INIT=y
# CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set
CONFIG_BUILD_DOCSRC=y
# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
CONFIG_KGDB=y
CONFIG_KGDB_SERIAL_CONSOLE=y
CONFIG_KGDB_TESTS=y
# CONFIG_KGDB_TESTS_ON_BOOT is not set
CONFIG_HAVE_ARCH_KMEMCHECK=y
CONFIG_STRICT_DEVMEM=y
# CONFIG_X86_VERBOSE_BOOTUP is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_EARLY_PRINTK_DBGP is not set
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_X86_PTDUMP is not set
CONFIG_DEBUG_RODATA=y
# CONFIG_DEBUG_RODATA_TEST is not set
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_IOMMU_DEBUG is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
CONFIG_DEBUG_BOOT_PARAMS=y
# CONFIG_CPA_DEBUG is not set
CONFIG_OPTIMIZE_INLINING=y
#
# Security options
#
CONFIG_KEYS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y
CONFIG_SECURITY=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=y
# CONFIG_SECURITY_PATH is not set
CONFIG_SECURITY_FILE_CAPABILITIES=y
# CONFIG_SECURITY_ROOTPLUG is not set
CONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR=65536
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
# CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_IMA is not set
CONFIG_XOR_BLOCKS=m
CONFIG_ASYNC_CORE=m
CONFIG_ASYNC_MEMCPY=m
CONFIG_ASYNC_XOR=m
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
# CONFIG_CRYPTO_FIPS is not set
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=m
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_WORKQUEUE=y
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=m
CONFIG_CRYPTO_TEST=m
#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=m
CONFIG_CRYPTO_GCM=m
CONFIG_CRYPTO_SEQIV=m
#
# Block modes
#
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_CTR=m
CONFIG_CRYPTO_CTS=m
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_LRW=m
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_XTS=m
#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=m
#
# Digest
#
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_CRC32C_INTEL is not set
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_RMD128=m
CONFIG_CRYPTO_RMD160=m
CONFIG_CRYPTO_RMD256=m
CONFIG_CRYPTO_RMD320=m
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_WP512=m
#
# Ciphers
#
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_X86_64=m
# CONFIG_CRYPTO_AES_NI_INTEL is not set
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_CAMELLIA=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_FCRYPT=m
CONFIG_CRYPTO_KHAZAD=m
# CONFIG_CRYPTO_SALSA20 is not set
CONFIG_CRYPTO_SALSA20_X86_64=m
CONFIG_CRYPTO_SEED=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_TEA=m
# CONFIG_CRYPTO_TWOFISH is not set
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_X86_64=m
#
# Compression
#
CONFIG_CRYPTO_DEFLATE=m
# CONFIG_CRYPTO_ZLIB is not set
CONFIG_CRYPTO_LZO=m
#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_HIFN_795X=m
CONFIG_CRYPTO_DEV_HIFN_795X_RNG=y
CONFIG_HAVE_KVM=y
CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=m
CONFIG_KVM_INTEL=m
CONFIG_KVM_AMD=m
CONFIG_KVM_TRACE=y
CONFIG_VIRTIO=m
CONFIG_VIRTIO_RING=m
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIO_BALLOON=m
CONFIG_BINARY_PRINTF=y
#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_FIND_LAST_BIT=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC_T10DIF=m
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_LZO_COMPRESS=m
CONFIG_LZO_DECOMPRESS=m
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_REED_SOLOMON=m
CONFIG_REED_SOLOMON_DEC16=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_CHECK_SIGNATURE=y
CONFIG_NLATTR=y
[-- Attachment #8: win7domu.cfg --]
[-- Type: application/octet-stream, Size: 617 bytes --]
import os, re
arch_libdir = 'lib'
arch = os.uname()[4]
if os.uname()[0] == 'Linux' and re.search('64', arch):
arch_libdir = 'lib64'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 2048
shadow_memory = 8
name = "win7domu"
vcpus=1
pae=1
acpi=1
apic=1
vif = [ 'type=ioemu, bridge=vnetbr0, mac=00:16:3e:00:3f:48' ]
disk = [ 'phy:/dev/VolGroup01/win7domu,hda,w','file:/rdata/iso/en_windows_7_ultimate_rc_x64_dvd_347803.iso,hdc:cdrom,r' ]
device_model = 'qemu-dm'
boot="cd"
sdl=0
vnc=0
vncdisplay=2
stdvga=0
serial='pty'
usb=1
usbdevice='tablet'
pci=[ '0000:01:00.*','0000:00:1a.*' ]
gfx_passthru=2
[-- Attachment #9: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-03 9:42 ` Han, Weidong
2009-09-03 9:50 ` Teo En Ming (Zhang Enming)
2009-09-03 19:07 ` Tim Moore
@ 2009-09-10 10:20 ` Tim Moore
2009-09-10 10:56 ` Han, Weidong
2 siblings, 1 reply; 39+ messages in thread
From: Tim Moore @ 2009-09-10 10:20 UTC (permalink / raw)
To: 'Han, Weidong'; +Cc: 'xen-devel@lists.xensource.com'
[-- Attachment #1.1: Type: text/plain, Size: 6444 bytes --]
hi Weidong,
Below, you mention the FLR code is in xen-unstable already - please could you point out where?
I thought that this code was in pciback and now transferred to pci-stub, but I can`t seem to find it anywhere ...
Cheers,
Tim
From: Han, Weidong [mailto:weidong.han@intel.com]
Sent: 03 September 2009 10:43
To: Tim Moore
Cc: 'enming.teo@asiasoftsea.net'; 'djmagee@mageenet.net'; 'xen-devel@lists.xensource.com'
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
Tim,
See my comments belew.
________________________________
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: 2009年9月3日 17:03
To: Han, Weidong
Cc: 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net; xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
________________________________
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net<mailto:djmagee@mageenet.net>
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
[-- Attachment #1.2: Type: text/html, Size: 25352 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-10 10:20 ` Tim Moore
@ 2009-09-10 10:56 ` Han, Weidong
2009-09-10 11:24 ` Ian Pratt
0 siblings, 1 reply; 39+ messages in thread
From: Han, Weidong @ 2009-09-10 10:56 UTC (permalink / raw)
To: 'Tim Moore'; +Cc: 'xen-devel@lists.xensource.com'
[-- Attachment #1.1: Type: text/plain, Size: 6689 bytes --]
Tim,
the FLR code is in xend (tools/python/xen/util/pci.py).
Regards,
Weidong
________________________________
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: 2009年9月10日 18:21
To: Han, Weidong
Cc: 'xen-devel@lists.xensource.com'
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
hi Weidong,
Below, you mention the FLR code is in xen-unstable already - please could you point out where?
I thought that this code was in pciback and now transferred to pci-stub, but I can`t seem to find it anywhere ...
Cheers,
Tim
From: Han, Weidong [mailto:weidong.han@intel.com]
Sent: 03 September 2009 10:43
To: Tim Moore
Cc: 'enming.teo@asiasoftsea.net'; 'djmagee@mageenet.net'; 'xen-devel@lists.xensource.com'
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
Tim,
See my comments belew.
________________________________
From: Tim Moore [mailto:timothy.moore@expidas.net]
Sent: 2009年9月3日 17:03
To: Han, Weidong
Cc: 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net; xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
Sent: 03 September 2009 05:12
To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
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@hotmail.com
________________________________
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: Wednesday, September 02, 2009 6:59 PM
To: Han, Weidong; xen-devel@lists.xensource.com
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Han, Weidong
Sent: Tuesday, September 01, 2009 6:55 PM
To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
Sent: 2009年9月2日 6:40
To: xen-devel@lists.xensource.com
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@mageenet.net<mailto:djmagee@mageenet.net>
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
[-- Attachment #1.2: Type: text/html, Size: 27042 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-10 10:56 ` Han, Weidong
@ 2009-09-10 11:24 ` Ian Pratt
2009-09-10 11:36 ` Han, Weidong
0 siblings, 1 reply; 39+ messages in thread
From: Ian Pratt @ 2009-09-10 11:24 UTC (permalink / raw)
To: Han, Weidong, 'Tim Moore'
Cc: Ian, Pratt, 'xen-devel@lists.xensource.com'
> Tim,
>
> the FLR code is in xend (tools/python/xen/util/pci.py).
IMO, it should live in pciback -- see the code in the XCI tree.
It would be good to get this cleaned up and upstream.
Ian
>
> Regards,
> Weidong
>
> ________________________________
>
> From: Tim Moore [mailto:timothy.moore@expidas.net]
> Sent: 2009年9月10日 18:21
> To: Han, Weidong
> Cc: 'xen-devel@lists.xensource.com'
> Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
>
>
>
> hi Weidong,
>
>
>
> Below, you mention the FLR code is in xen-unstable already - please could
> you point out where?
>
>
>
> I thought that this code was in pciback and now transferred to pci-stub,
> but I can`t seem to find it anywhere ...
>
>
>
> Cheers,
>
> Tim
>
>
>
> From: Han, Weidong [mailto:weidong.han@intel.com]
> Sent: 03 September 2009 10:43
> To: Tim Moore
> Cc: 'enming.teo@asiasoftsea.net'; 'djmagee@mageenet.net'; 'xen-
> devel@lists.xensource.com'
> Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
>
>
>
> Tim,
>
>
>
> See my comments belew.
>
>
>
>
>
> ________________________________
>
> From: Tim Moore [mailto:timothy.moore@expidas.net]
> Sent: 2009年9月3日 17:03
> To: Han, Weidong
> Cc: 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net; xen-
> devel@lists.xensource.com
> Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> 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@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
> Sent: 03 September 2009 05:12
> To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
> 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@hotmail.com
>
> ________________________________
>
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
> Sent: Wednesday, September 02, 2009 6:59 PM
> To: Han, Weidong; xen-devel@lists.xensource.com
> 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@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Han, Weidong
> Sent: Tuesday, September 01, 2009 6:55 PM
> To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
> 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@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
> Sent: 2009年9月2日 6:40
> To: xen-devel@lists.xensource.com
> 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@mageenet.net
>
>
>
> 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
^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: RE: xen-unstable pci passthrough
2009-09-10 11:24 ` Ian Pratt
@ 2009-09-10 11:36 ` Han, Weidong
0 siblings, 0 replies; 39+ messages in thread
From: Han, Weidong @ 2009-09-10 11:36 UTC (permalink / raw)
To: 'Ian Pratt', 'Tim Moore'
Cc: 'xen-devel@lists.xensource.com'
[-- Attachment #1: Type: text/plain, Size: 8083 bytes --]
Agree. It's cleaner in pciback. Community discussed it a long time ago. But no one did it for xen-unstable. Now it also needs to implement it in pci-stub for pv-ops dom0.
Regards,
Weidong
-----Original Message-----
From: Ian Pratt [mailto:Ian.Pratt@eu.citrix.com]
Sent: 2009年9月10日 19:24
To: Han, Weidong; 'Tim Moore'
Cc: 'xen-devel@lists.xensource.com'; Ian Pratt
Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
> Tim,
>
> the FLR code is in xend (tools/python/xen/util/pci.py).
IMO, it should live in pciback -- see the code in the XCI tree.
It would be good to get this cleaned up and upstream.
Ian
>
> Regards,
> Weidong
>
> ________________________________
>
> From: Tim Moore [mailto:timothy.moore@expidas.net]
> Sent: 2009年9月10日 18:21
> To: Han, Weidong
> Cc: 'xen-devel@lists.xensource.com'
> Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
>
>
>
> hi Weidong,
>
>
>
> Below, you mention the FLR code is in xen-unstable already - please could
> you point out where?
>
>
>
> I thought that this code was in pciback and now transferred to pci-stub,
> but I can`t seem to find it anywhere ...
>
>
>
> Cheers,
>
> Tim
>
>
>
> From: Han, Weidong [mailto:weidong.han@intel.com]
> Sent: 03 September 2009 10:43
> To: Tim Moore
> Cc: 'enming.teo@asiasoftsea.net'; 'djmagee@mageenet.net'; 'xen-
> devel@lists.xensource.com'
> Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
>
>
>
> Tim,
>
>
>
> See my comments belew.
>
>
>
>
>
> ________________________________
>
> From: Tim Moore [mailto:timothy.moore@expidas.net]
> Sent: 2009年9月3日 17:03
> To: Han, Weidong
> Cc: 'enming.teo@asiasoftsea.net'; djmagee@mageenet.net; xen-
> devel@lists.xensource.com
> Subject: RE: [Xen-devel] RE: xen-unstable pci passthrough
>
> 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@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Teo En Ming (Zhang Enming)
> Sent: 03 September 2009 05:12
> To: djmagee@mageenet.net; 'Han, Weidong'; xen-devel@lists.xensource.com
> 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@hotmail.com
>
> ________________________________
>
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
> Sent: Wednesday, September 02, 2009 6:59 PM
> To: Han, Weidong; xen-devel@lists.xensource.com
> 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@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Han, Weidong
> Sent: Tuesday, September 01, 2009 6:55 PM
> To: djmagee@mageenet.net; 'xen-devel@lists.xensource.com'
> 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@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of djmagee@mageenet.net
> Sent: 2009年9月2日 6:40
> To: xen-devel@lists.xensource.com
> 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@mageenet.net
>
>
>
> 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
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 39+ messages in thread
end of thread, other threads:[~2009-09-10 11:36 UTC | newest]
Thread overview: 39+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-09-01 22:40 xen-unstable pci passthrough djmagee
2009-09-01 22:55 ` Han, Weidong
2009-09-02 0:30 ` Mr. Teo En Ming (Zhang Enming)
2009-09-02 3:31 ` Teo En Ming (Zhang Enming)
2009-09-02 10:58 ` djmagee
2009-09-03 4:12 ` Teo En Ming (Zhang Enming)
2009-09-03 9:03 ` Tim Moore
2009-09-03 9:14 ` Teo En Ming (Zhang Enming)
2009-09-03 9:18 ` Teo En Ming (Zhang Enming)
2009-09-03 14:18 ` Tim Moore
2009-09-03 14:24 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 9:42 ` Han, Weidong
2009-09-03 9:50 ` Teo En Ming (Zhang Enming)
2009-09-03 13:40 ` Tim Moore
2009-09-03 14:11 ` Mr. Teo En Ming (Zhang Enming)
[not found] ` <14D9C9E2ED61ED41BC3B37ACDF4E880002E0C4B8F667@heavy-vm03.heavy.org.uk>
2009-09-03 14:28 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 15:33 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 15:39 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 19:07 ` Tim Moore
2009-09-03 20:29 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 20:34 ` Tim Moore
2009-09-03 20:41 ` Mr. Teo En Ming (Zhang Enming)
[not found] ` <14D9C9E2ED61ED41BC3B37ACDF4E880002E0C4B8F66B@heavy-vm03.heavy.org.uk>
2009-09-03 20:58 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 20:35 ` Mr. Teo En Ming (Zhang Enming)
2009-09-04 0:00 ` Han, Weidong
2009-09-03 23:58 ` Han, Weidong
2009-09-04 1:58 ` Teo En Ming (Zhang Enming)
2009-09-04 3:10 ` Han, Weidong
2009-09-04 10:27 ` Christian Tramnitz
2009-09-04 0:03 ` Han, Weidong
2009-09-10 10:20 ` Tim Moore
2009-09-10 10:56 ` Han, Weidong
2009-09-10 11:24 ` Ian Pratt
2009-09-10 11:36 ` Han, Weidong
2009-09-03 15:07 ` djmagee
2009-09-03 15:58 ` Mr. Teo En Ming (Zhang Enming)
2009-09-03 16:12 ` djmagee
2009-09-03 16:16 ` Mr. Teo En Ming (Zhang Enming)
2009-09-09 19:02 ` RE: xen-unstable gfx passthrough (was xen-unstable pci passthrough) djmagee
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.