win-pvdrivers

view doc/INSTALLING.txt @ 189:eeeeb6924803

updates preparing for next release
author James Harper <james.harper@bendigoit.com.au>
date Mon Feb 18 22:16:03 2008 +1100 (2008-02-18)
parents 21a7b050e472
children 8242c5efce07
line source
1 Please follow the steps here exactly. If you don't, you may be left with
2 an unbootable machine (although 'Last known good configuration' should
3 make it bootable again).
5 1. Copy the driver files that you built by following the BUILDING.txt
6 steps (or that you got from a binary dist), so that on your testing
7 machine the tree looks like this:
9 Xen\install.bat
10 Xen\ShutdownMon.exe
11 Xen\<os>\xenhide.inf
12 Xen\<os>\xenpci.inf
13 Xen\<os>\xenvbd.inf
14 Xen\<os>\DPInst.exe
15 Xen\<os>\<arch>\xenaddresource.sys
16 Xen\<os>\<arch>\xenhide.sys
17 Xen\<os>\<arch>\xenpci.sys
18 Xen\<os>\<arch>\xenvbd.sys
19 Xen\<os>\<arch>\WdfCoInstaller01005.dll
20 (If you have compiled yourself, you'll need to copy
21 WdfCoInstaller01007.dll and DPInst.exe from the redist folder in the DDK) (<os> is
22 winxp for XP, or winnet for 2K3. <arch> is i386 or amd64)
24 2. run 'install.bat' in the Xen directory
26 3. Click Next and Ok when prompted. The drivers are unsigned so be prepared to do
27 this more than once.
29 4. Reboot when prompted to ensure that your computer still boots without any
30 issues. You'll now have two ethernet interfaces, which may or may not cause
31 problems.
33 5. edit your boot.ini to look something like this:
35 "
36 [boot loader]
37 timeout=30
38 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
40 [operating systems]
41 multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect
42 multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise, GPLPV" /noexecute=optout /fastdetect /gplpv
43 "
45 17. The main thing in the above step is that you have a line with /gplpv
46 on the end. This tells the PV device (vbd, vif) drivers to activate,
47 otherwise they will pretty much sit silent. At the moment, vif always
48 activates.
50 18. Reboot and select the /gplpv entry. If it doesn't work then email me
51 (james.harper@bendigoit.com.au) with some details and i'll see what I can
52 do.
54 Without the /gplpv option specified, the xenvbd driver will only pick up
55 on devices you have added since boot, so you can still test it without
56 specifying /gplpv and doing something like the following in Dom0:
58 "
59 xm block-attach mywindowsdomain phy:/dev/someblockdevice /dev/hdc w
60 "
62 You need to specify the 'phy:' in your xen config file and in the
63 block-attach line otherwise the backend doesn't seem to publish the block
64 and sector sizes correctly.
66 If you do the block-attach, then your block device should show up under
67 windows, and you can partition it etc.