win-pvdrivers

view doc/INSTALLING.old.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
children
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\<arch>\xenhide.inf
10 Xen\<arch>\xenpci.inf
11 Xen\<arch>\xenvbd.inf
12 Xen\<arch>\i386\xenaddresource.sys Xen\<arch>\i386\xenhide.sys
13 Xen\<arch>\i386\xenpci.sys
14 Xen\<arch>\i386\xenvbd.sys
15 Xen\<arch>\i386\WdfCoInstaller01005.dll
16 (If you have compiled yourself, you'll need to copy
17 WdfCoInstaller01005.dll from the redist folder in the DDK) (<arch> is
18 winxp for XP, or winnet for 2K3)
20 2. Go to the device manager (Right click on My Computer, then select the
21 Hardware tab, then click Device Manager)
23 3. Find the 'PCI Device' under 'Other Devices' - it should have an
24 exclamation mark against it. Right click on it and select 'Update
25 Driver...'
27 4. Select 'No, not this time' in answer to 'Can Windows connect to
28 Windows Update...' and click Next
30 5. Select 'Install from a list of specific location (Advanced)' and
31 click Next
33 6. Untick 'Search removable media...' and tick 'Include this
34 location...'. Enter the name of the directory where you put the .inf
35 files, then click Next
37 7. Windows should find the XenPCI driver as a candidate, and will
38 complain that it hasn't been signed. Just accept the warning.
40 8. Windows should load the XenPCI driver, and then give you 4 more
41 'Other Devices' - console, vfb, vif, and vbd.
43 9. Repeat steps 3-7 for the vbd and vif devices. Windows should then
44 load the XenVBD driver.
46 10. The next bit is a bit tricker. In Device Manager, drill down on
47 System devices and right click on PCI Bus and select Update Driver.
49 11. Select 'No, not this time' in answer to 'Can Windows connect to
50 Windows Update...' and click Next
52 12. Select 'Install from a list or specific location (Advanced)' and
53 click Next
55 13. This time, select 'Don't search. I will choose the driver to
56 install' and click Next
58 14. Click 'Have Disk' and go to the locaton where you put the .inf
59 files.
61 15. Select the 'Xen PCI Device Hider Driver' (I know, it's a stupid
62 name) and install it, again accepting the unsigned driver warning.
64 16. edit your boot.ini to look something like this:
66 " [boot loader] timeout=30
67 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems]
68 multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003,
69 Enterprise" /noexecute=optout /fastdetect
70 multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003,
71 Enterprise, GPLPV" /noexecute=optout /fastdetect /gplpv "
73 17. The main thing in the above step is that you have a line with /gplpv
74 on the end. This tells the PV device (vbd, vif) drivers to activate,
75 otherwise they will pretty much sit silent.
77 18. Reboot and select the /gplpv entry. If it doesn't work then email me
78 (james.harper@bendigoit.com.au) with some details and i'll see what I can
79 do.
81 Without the /gplpv option specified, the xenvbd driver will only pick up
82 on devices you have added since boot, so you can still test it without
83 specifying /gplpv and doing something like the following in Dom0:
85 " xm block-attach mywindowsdomain phy:/dev/someblockdevice /dev/hdc w "
87 You need to specify the 'phy:' in your xen config file and in the
88 block-attach line otherwise the backend doesn't seem to publish the block
89 and sector sizes correctly.
91 If you do the block-attach, then your block device should show up under
92 windows, and you can partition it etc.
94 19. If you have built ShutdownMon, run "ShutdownMon -i" which will
95 install it as a service. You will need to change the service to
96 'Automatic' and start it (or reboot). 'xm shutdown' and 'xm reboot'
97 should then do the right thing.