WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re : Re : Re : Re : [Xen-devel] Re: Patches for VGA-Passthrough XEN 4.2

To: komkon555 <komkon555@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re : Re : Re : Re : [Xen-devel] Re: Patches for VGA-Passthrough XEN 4.2 unstable
From: David TECHER <davidtecher@xxxxxxxx>
Date: Fri, 9 Sep 2011 20:56:50 +0100 (BST)
Cc:
Delivery-date: Fri, 09 Sep 2011 12:58:06 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.fr; s=s1024; t=1315598210; bh=ZaDNL2i2gvq1YyQorSFxCvlut/PmbcGgsZajB8YmQYY=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=IrF4bMYrHhil0A4h8z9p8UxjH75jCowUsoJki8Sd1Lj15/eblu85SEgpZ83/KPxRwWdaRKay5F7KBx2l1vRdGIXbXsmt5KqGl9ytdXapCbBOk9RzFetiNJWlo6aB8cvWAG2TJqLbi35LvfUb1iIdDyztln3zrTeu2Fz/iNtwAnQ=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=AJIa1zJJbmwKMhV/Sw2sa0iu6YNyPxLV3qDCCPe9PemiXA+3NPrTOaiE4KWM3jIv04n9LhlB/t2pcrpItdQRBxeNcsdn/Wuts1qihsKRxHBVKus/U3F2380sj+eZmfLXic/zjuV/udr/5QF8kITHX/RnMx6p0BrEz+MbLFQVklo=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1315554847212-4785386.post@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1315310225039-4774097.post@xxxxxxxxxxxxx> <1315343879.61837.YahooMailNeo@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <1315382742268-4777689.post@xxxxxxxxxxxxx> <1315389138.56652.YahooMailNeo@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <1315398360680-4778339.post@xxxxxxxxxxxxx> <1315401901083-4778494.post@xxxxxxxxxxxxx> <1315403644525-4778586.post@xxxxxxxxxxxxx> <1315405372.87224.YahooMailNeo@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <1315405921936-4778727.post@xxxxxxxxxxxxx> <1315408931610-4778925.post@xxxxxxxxxxxxx> <1315554847212-4785386.post@xxxxxxxxxxxxx>
Reply-to: David TECHER <davidtecher@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Please have a look on http://wiki.xensource.com/xenwiki/VTdHowTo.

I've just applied what it is recommended on the wiki. It works  like a charm.



For VGA,
========
you can use PCI_STUB, I do not use it as module

root@mercury:~# grep pci_stub -i /boot/config-2.6.39.3
CONFIG_PCI_STUB=y

root@mercury:~# lspci |grep VGA
01:00.0 VGA compatible controller: nVidia Corporation Device 0de0 (rev a1)



root@mercury:~# lspci -s 01:00.0 -n
01:00.0 0300: 10de:0de0 (rev a1)

Create a script with the following content

root@mercury:~# grep -vE '^(#|$)' start_windows.sh
echo "10de 0de0" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:01:00.0" > /sys/bus/pci/devices/0000:01:00.0/driver/unbind
echo "0000:01:00.0" > /sys/bus/pci/drivers/pci-stub/bind
xl  create /etc/xen/machines/mercury-xen03.cfg

For KeyBoard and Mouse
===================

Use passthrough.

root@mercury:~# grep CONFIG_XEN_PCIDEV_BACKEND=  /boot/config-2.6.39.3
CONFIG_XEN_PCIDEV_BACKEND=y

I've got two USB controllers (1: mouse + keyboard, 2: for sound Logitech USB Speaker)

root@mercury:~# lspci |grep USB
00:1a.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #2 (rev 05)
00:1d.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #1 (rev 05)

Put it on grub so that dom0 will not use it

root@mercury:~# grep permissive /boot/grub/grub.cfg
        module  /boot/vmlinuz-2.6.39.3 placeholder root=UUID=1cd457ae-85f4-4626-8f94-1f444fcf6d5c ro nomodeset xen-pciback.permissive xen-pciback.hide=(00:1a.0)(00:1d.0) quiet

In my  domU configuration file
======================
root@mercury:~# grep ^pci /etc/xen/machines/mercury-xen03.cfg
pci  = [ '01:00.0','00:1a.0','00:1d.0' ]





De : komkon555 <komkon555@xxxxxxxxxx>
À : xen-devel@xxxxxxxxxxxxxxxxxxx
Envoyé le : Vendredi 9 Septembre 2011 9h54
Objet : Re: Re : Re : Re : [Xen-devel] Re: Patches for VGA-Passthrough XEN 4.2 unstable

          Hi. There is the promised report to JavMV: with fixes on dsd are
your patches also functional. Windows XP starts and GTX260 works perfect
with driver version 275.33.
          Some news more: The best results I got with this configuration:
xen 4.1-unstable changeset 21668 (patched clearly with these
http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00441.html
patches , dsd fixed according to David TECHER) + jeremi xen kernel 2.6.32.45
(xenfs static). This configuration works excellent both: with primary and
secondary vga-adapter (GTX260). There are two Problem with all
configurations:
1. DomU can be started only once. Being  correctly shouted  down, starts
DomU no more.
2. Physical usb- keyboard and mouse can not be assigned to DomU (regular usb
assignment has no effect, PVUSB crashes)

Best regards
Kom.


--
View this message in context: http://xen.1045712.n5.nabble.com/Patches-for-VGA-Passthrough-XEN-4-2-unstable-tp4406265p4785386.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

_______________________________________________
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
<Prev in Thread] Current Thread [Next in Thread>