win-pvdrivers

view INSTALLING.txt @ 7:078654ce6a13

Fixed the XenHide inf file so that we don't need to bother with the regedit step anymore on install
author James Harper <james.harper@bendigoit.com.au>
date Mon Nov 12 23:04:56 2007 +1100 (2007-11-12)
parents 0cd078f41eed
children d25a6f733a8e
line source
1 Please follow the steps here exactly. If you don't, you may be left with an unbootable machine (although 'Last known good configuration' should make it bootable again).
3 1. Copy the driver files that you built by following the BUILDING.txt steps, so that on your testing machine the tree looks like this:
5 Xen\xenhide.inf
6 Xen\xenpci.inf
7 Xen\xenvbd.inf
8 Xen\i386\xenhide.sys
9 Xen\i386\xenpci.sys
10 Xen\i386\xenvbd.sys
11 Xen\i386\WdfCoInstaller01005.dll
12 (you'll need to copy WdfCoInstaller01005.dll from the redist folder in the DDK)
14 2. Go to the device manager (Right click on My Computer, then select the Hardware tab, then click Device Manager)
16 3. Find the 'PCI Device' under 'Other Devices' - it should have an exclamation mark against it. Right click on it and select 'Update Driver...'
18 4. Select 'No, not this time' in answer to 'Can Windows connect to Windows Update...' and click Next
20 5. Select 'Install from a list of specific location (Advanced)' and click Next
22 6. Untick 'Search removable media...' and tick 'Include this location...'. Enter the name of the directory where you put the .inf files, then click Next
24 7. Windows should find the XenPCI driver as a candidate, and will complain that it hasn't been signed. Just accept the warning.
26 8. Windows should load the XenPCI driver, and then give you 4 more 'Other Devices' - console, vfb, vif, and vbd.
28 9. Repeat steps 3-7 for the vbd device. Windows should then load the XenVBD driver.
30 10. The next bit is a bit tricker. In Device Manager, drill down on System devices and right click on PCI Bus and select Update Driver.
32 11. Select 'No, not this time' in answer to 'Can Windows connect to Windows Update...' and click Next
34 12. Select 'Install from a list or specific location (Advanced)' and click Next
36 13. This time, select 'Don't search. I will choose the driver to install' and click Next
38 14. Click 'Have Disk' and go to the locaton where you put the .inf files.
40 15. Select the 'Xen PCI Device Hider Driver' (I know, it's a stupid name) and install it, again accepting the unsigned driver warning.
42 16. *** Shouldn't need to do this step anymore *** Open the registry editor (Start -> Run, then type 'regedit')
44 17. *** Shouldn't need to do this step anymore *** In the registry editor, open the key 'HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ServiceGroupOrder' and modify the List value so that WdfLoadGroup is before Boot Bus Extender.
46 18. edit your boot.ini to look something like this:
48 "
49 [boot loader]
50 timeout=30
51 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
52 [operating systems]
53 multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect
54 multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise, PV" /noexecute=optout /fastdetect /gplpv
55 "
57 19. The main thing in the above step is that you have a line with /gplpv on the end. This tells the PV drivers to activate, otherwise they will pretty much sit silent.
59 20. Reboot and select the /gplpv entry. If it doesn't work then email me with some details and i'll see what I can do.
63 Without the /gplpv option specified, the xenvbd driver will only pick up on devices you have added since boot, so you can still test it without specifying /gplpv and doing something like the following in Dom0:
65 "
66 xm block-attach mywindowsdomain phy:/dev/someblockdevice /dev/hdc w
67 "
69 I'm pretty sure that you need to specify the 'phy:' otherwise the backend doesn't seem to publish the block and sector sizes correctly.
71 If you do the block-attach, then your block device should show up under windows, and you can partition it etc.