Xen project Mailing List

I think I understand what's wrong now :)

Init build

======

wget http://bits.xensource.com/oss-xen/release/4.1.2/xen-4.1.2.tar.gz
tar xzf xen-4.1.2.tar.gz
cd xen-4.1.2/
cd tools/
make
make clean
cd ..

Download patches

=============

wget -q http://old-list-archives.xen.org/archives/html/xen-devel/2010-05/txtIj4stRFbPo.txt -O 01_pass-through.patch
wget -q http://old-list-archives.xen.org/archives/html/xen-devel/2010-05/txt06YdYEsi3S.txt -O 02_makefile.patch
wget -q http://old-list-archives.xen.org/archives/html/xen-devel/2010-05/txtS2w8cPgsnS.txt -O 03_dsdt.patch
wget -q http://old-list-archives.xen.org/archives/html/xen-devel/2010-05/txt2am6wEpoR5.txt -O 04_hvmloader.patch
wget -q http://old-list-archives.xen.org/archives/html/xen-devel/2010-05/txtiSIyxOHBZ8.txt -O 05_sound-makefile.patch

Modify the first patch

================

Replace the path for the good path in the first patch 01_pass-through.patch

sed -i "s:tools/ioemu-remote/hw/:tools/ioemu-qemu-xen/hw/:g" 01_pass-through.patch

Apply patches

==========

root@mercury:/opt/tmp/xen-4.1.2# for file in $(ls 0*patch);do echo "######## PATCH = $file ############";patch -p0 < $file;done
######## PATCH = 01_pass-through.patch ############
patching file tools/ioemu-qemu-xen/hw/pass-through.c
Hunk #1 succeeded at 22 with fuzz 2 (offset -1843 lines).
Hunk #2 succeeded at 3312 (offset -55 lines).
Hunk #3 succeeded at 3336 (offset -55 lines).
Hunk #4 succeeded at 4335 with fuzz 2 (offset -144 lines).
######## PATCH = 02_makefile.patch ############
patching file tools/firmware/hvmloader/Makefile
######## PATCH = 03_dsdt.patch ############
patching file tools/firmware/hvmloader/acpi/dsdt.asl
######## PATCH = 04_hvmloader.patch ############
patching file tools/firmware/hvmloader/hvmloader.c
Hunk #1 succeeded at 116 (offset 1 line).
Hunk #2 succeeded at 221 (offset 1 line).
Hunk #3 succeeded at 789 (offset 60 lines).
######## PATCH = 05_sound-makefile.patch ############
patching file tools/ioemu-remote/xen-setup
Hunk #1 FAILED at 16

I will go on my tests and will let you know

Thanks

David

De : David TECHER <davidtecher@xxxxxxxx>
À : -+= Lta =+- <lta@xxxxxx>
Cc : "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Envoyé le : Samedi 7 Janvier 2012 13h04
Objet : [Xen-devel] Re : Re : Secondary VGA Passthrough, nvidia, win7: success report.

I tested xen 4.1.2 too. Tobias patches are the patches I've tested. I am not very lucky.

Since you used Tobias patches as me, my question is - to be more precise - could you sent Tobias patches that you have modified in order to checking

I did not forget something as you.

My idea is that since I already have xen 4.2 installed, installing xen 4.1.2 over this , something wrong happens

My screen stays like a black screen and nothing happens. no "gfx message" in the log.

With Xen 4.2 I tried aero desktop too but my domU crashes when I tried to activate aero.

De : -+= Lta =+- <lta@xxxxxx>
À : David TECHER <davidtecher@xxxxxxxx>
Cc : xen-devel@xxxxxxxxxxxxxxxxxxx
Envoyé le : Samedi 7 Janvier 2012 3h17
Objet : Re: Re : [Xen-devel] Secondary VGA Passthrough, nvidia, win7: success report.

Hi,

On Fri, Jan 6, 2012 at 11:23 PM, David TECHER <davidtecher@xxxxxxxx> wrote:

Could you tell me what version of Xen? 4.1.0? 4.1.2?

As it is stated before this is a 4.1.2 version with debian patches

By the way could you send your patches attached to a mail so I could try?

- There's also a link to tobias patche's on the first post.

Test on Xen 4.2 failed (desktop stays to lag...)

Have u tried to force windows to activate the aero desktop ?

With installing xen 4.1.0/4.2.0 over my xen 4.2, domU boot but nothing appears on screen.

I also followed tobias (same as yours) instructions to dump and build vgabios-pt.bin into xen, did u do it also ?

Strange.

De : -+= Lta =+- <lta@xxxxxx>

À : xen-devel@xxxxxxxxxxxxxxxxxxx
Envoyé le : Vendredi 6 Janvier 2012 17h48
Objet : [Xen-devel] Secondary VGA Passthrough, nvidia, win7: success report.

Hello xen-devel,

This is my first post on this list and as such i might be breaking some explicit/implicit rules and i apologize if it's the case. Maybe this list isn't the exact right kind of place where to post this kind of stuff, but i know lots of us are browsing this list as the primary source of documentation for xen.

I've read many times windows 7 isn't the right os to run on top of xen. Most of the guy's who are running vga passthru are recommanding to use windows xp, and i've never seen any success report of vga passthru on windows 7 so i thought it was important to post mine.

Anyway, here's my hardware setup :
- Gigabyte GA-990X-UD3
- AMD Phenom II X6 1075T Processor
- MSI Cyclone NVIDIA Geforce GTX 460

On the software side i'm using :

- Debian testing as Dom0
- Xen-4.1 (debian version 4.1.2-2) with what's now referred to as "Tobias Geiger patches" (http://old-list-archives.xen.org/archives/html/xen-devel/2010-05/msg00441.html) (You have to edit the patches, changing the path to some qemu source files for them to apply)

- debian's kernel 3.1.5, compiled to include the pciback driver. Here's the output of `cat /boot/my3.1.5config | grep -i xen`
CONFIG_XEN=y
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_PVHVM=y

CONFIG_XEN_MAX_DOMAIN_MEMORY=128
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set

# CONFIG_XEN_DEBUG is not set
CONFIG_PCI_XEN=y
CONFIG_XEN_PCIDEV_FRONTEND=m

CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_XEN_BLKDEV_BACKEND=m
CONFIG_NETXEN_NIC=m

CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_XEN_NETDEV_BACKEND=m
CONFIG_INPUT_XEN_KBDDEV_FRONTEND=y

CONFIG_HVC_XEN=y
CONFIG_XEN_WDT=m
CONFIG_XEN_FBDEV_FRONTEND=y

# Xen driver support
CONFIG_XEN_BALLOON=y
# CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is not set

CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m
CONFIG_XEN_BACKEND=y

CONFIG_XENFS=m
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y

CONFIG_XEN_XENBUS_FRONTEND=y
CONFIG_XEN_GNTDEV=m
CONFIG_XEN_GRANT_DEV_ALLOC=m

CONFIG_XEN_PLATFORM_PCI=m
CONFIG_SWIOTLB_XEN=y
CONFIG_XEN_PCIDEV_BACKEND=y

The kernel boot options are 'nomodeset xen-pciback.passthrough=1 xen-pciback.hide=(01:00.0)(01:00.1)'

- Here's my win7 domU config file :

kernel = "/usr/lib/xen-4.1/boot/hvmloader"
builder='hvm'
memory = 3072

name = "w7"
vif = [ 'type=netfront,bridge=xenbr0, mac=00:16:3e:35:49:62']
disk = [ 'phy:/dev/w7-xen/system,hda,w', 'phy:/dev/w7-xen/appz,hdb,w']

device_model = '/usr/lib/xen-4.1/bin/qemu-dm'
boot="dc"

pci=['01:00.0','01:00.1']
gfx_passthru=1

vcpus=6
acpi=1
sdl=0
vnc=1

vncconsole=1
vncpasswd=''
serial='pty'

usbdevice='tablet'
pae=1
pci_msitranslate=0

pci_power_mgmt=0
acpi_s3 = 1
acpi_s4 = 1

on_reboot = 'restart'
on_crash = 'restart'
xen_platform_pci=1

hpet = 1
viridian=1
monitor=1
xen_extended_power_mgmt=2

hpet=1

What's important here for the Nvidia drivers to work and not give a nice nvlddmkm.sys BSOD is:
pci_msitranslate=0

pci_power_mgmt=0

- Windows 7 32bits
- Nvidia drivers 275.33
- You have to manually run aero speed test or force aero to start by using registry entries for the desktop not to be laggy

The windows 7 domU is running fine with no performance decrease noticeable, although i've not yet played intensive gpu video game, i'm still pretty confident they'll run fine.

Anyway. i've still some problems i shall report in separate posts :
- The PCI bus topology isn't preserved, and the gfx card, which is plugged on 01:00 becomes 05:00 on domU.
- I'm passing through an RME Hdsp / hammerfall pci sound card to the domU and while it is working fine on his own, there's a strange interaction between it and the GPLPV network driver. When i start playing sound, the network instantly cease working. It starts back as soon as i stop playing audio.

That's all folks,

Cheers,
Lta

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

[Xen-devel] Re : Re : Re : Secondary VGA Passthrough, nvidia, win7: success report.