annotate doc/INSTALLING.old.txt @ 1041:4016afe45e7b

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