view doc/INSTALLING.txt @ 190:8242c5efce07

Added a note about upgrading and xenhide.
author James Harper <>
date Mon Feb 18 22:32:41 2008 +1100 (2008-02-18)
parents eeeeb6924803
children 99985a5aa1dc
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 0. If you are installing over a previous version where you installed the xenhide
6 driver over the top of the windows PCI driver, make sure you install the system
7 PCI driver back again. doing an Update Driver on xenhide and just clicking next
8 should do this. It's probably a good idea to also uninstall all the xen drivers
9 too before upgrading... ymmv.
11 1. Copy the driver files that you built by following the BUILDING.txt
12 steps (or that you got from a binary dist), so that on your testing
13 machine the tree looks like this:
15 Xen\install.bat
16 Xen\ShutdownMon.exe
17 Xen\<os>\xenhide.inf
18 Xen\<os>\xenpci.inf
19 Xen\<os>\xenvbd.inf
20 Xen\<os>\DPInst.exe
21 Xen\<os>\<arch>\xenaddresource.sys
22 Xen\<os>\<arch>\xenhide.sys
23 Xen\<os>\<arch>\xenpci.sys
24 Xen\<os>\<arch>\xenvbd.sys
25 Xen\<os>\<arch>\WdfCoInstaller01005.dll
26 (If you have compiled yourself, you'll need to copy
27 WdfCoInstaller01007.dll and DPInst.exe from the redist folder in the DDK) (<os> is
28 winxp for XP, or winnet for 2K3. <arch> is i386 or amd64)
30 2. run 'install.bat' in the Xen directory
32 3. Click Next and Ok when prompted. The drivers are unsigned so be prepared to do
33 this more than once.
35 4. Reboot when prompted to ensure that your computer still boots without any
36 issues. You'll now have two ethernet interfaces, which may or may not cause
37 problems.
39 5. edit your boot.ini to look something like this:
41 "
42 [boot loader]
43 timeout=30
44 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
46 [operating systems]
47 multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect
48 multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise, GPLPV" /noexecute=optout /fastdetect /gplpv
49 "
51 17. The main thing in the above step is that you have a line with /gplpv
52 on the end. This tells the PV device (vbd, vif) drivers to activate,
53 otherwise they will pretty much sit silent. At the moment, vif always
54 activates.
56 18. Reboot and select the /gplpv entry. If it doesn't work then email me
57 ( with some details and i'll see what I can
58 do.
60 Without the /gplpv option specified, the xenvbd driver will only pick up
61 on devices you have added since boot, so you can still test it without
62 specifying /gplpv and doing something like the following in Dom0:
64 "
65 xm block-attach mywindowsdomain phy:/dev/someblockdevice /dev/hdc w
66 "
68 You need to specify the 'phy:' in your xen config file and in the
69 block-attach line otherwise the backend doesn't seem to publish the block
70 and sector sizes correctly.
72 If you do the block-attach, then your block device should show up under
73 windows, and you can partition it etc.