view INSTALLING.txt @ 73:f74723639713

Corrected merge of dpc patches.
author James Harper <>
date Thu Dec 20 13:07:44 2007 +1100 (2007-12-20)
parents d25a6f733a8e
children 9dbe0f19c27e
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 (or that you got from a binary dist), so that on your testing machine the tree looks like this:
5 Xen\<arch>\xenhide.inf
6 Xen\<arch>\xenpci.inf
7 Xen\<arch>\xenvbd.inf
8 Xen\<arch>\i386\xenaddresource.sys
9 Xen\<arch>\i386\xenhide.sys
10 Xen\<arch>\i386\xenpci.sys
11 Xen\<arch>\i386\xenvbd.sys
12 Xen\<arch>\i386\WdfCoInstaller01005.dll
13 (you'll need to copy WdfCoInstaller01005.dll from the redist folder in the DDK)
14 (<arch> is winxp for XP, or winnet for 2K3)
16 2. Go to the device manager (Right click on My Computer, then select the Hardware tab, then click Device Manager)
18 3. Find the 'PCI Device' under 'Other Devices' - it should have an exclamation mark against it. Right click on it and select 'Update Driver...'
20 4. Select 'No, not this time' in answer to 'Can Windows connect to Windows Update...' and click Next
22 5. Select 'Install from a list of specific location (Advanced)' and click Next
24 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
26 7. Windows should find the XenPCI driver as a candidate, and will complain that it hasn't been signed. Just accept the warning.
28 8. Windows should load the XenPCI driver, and then give you 4 more 'Other Devices' - console, vfb, vif, and vbd.
30 9. Repeat steps 3-7 for the vbd device. Windows should then load the XenVBD driver.
32 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.
34 11. Select 'No, not this time' in answer to 'Can Windows connect to Windows Update...' and click Next
36 12. Select 'Install from a list or specific location (Advanced)' and click Next
38 13. This time, select 'Don't search. I will choose the driver to install' and click Next
40 14. Click 'Have Disk' and go to the locaton where you put the .inf files.
42 15. Select the 'Xen PCI Device Hider Driver' (I know, it's a stupid name) and install it, again accepting the unsigned driver warning.
44 16. edit your boot.ini to look something like this:
46 "
47 [boot loader]
48 timeout=30
49 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
50 [operating systems]
51 multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect
52 multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise, GPLPV" /noexecute=optout /fastdetect /gplpv
53 "
55 17. 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.
57 18. 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.
59 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:
61 "
62 xm block-attach mywindowsdomain phy:/dev/someblockdevice /dev/hdc w
63 "
65 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.
67 If you do the block-attach, then your block device should show up under windows, and you can partition it etc.
69 19. If you have built ShutdownMon, run "ShutdownMon -i" which will install it as a service. You will need to change the service to 'Automatic' and start it (or reboot). 'xm shutdown' and 'xm reboot' should then do the right thing.