win-pvdrivers

changeset 143:21a7b050e472 0.6.0.0

Final changes and documentation updates for 0.6.0.0 release
author James Harper <james.harper@bendigoit.com.au>
date Tue Jan 22 20:01:56 2008 +1100 (2008-01-22)
parents 8d3f39a47293
children af3f6972fe54
files BUILDING.txt INSTALLING.txt README.txt TODO.txt doc/BUILDING.txt doc/INSTALLING.txt doc/README.txt doc/TODO.txt exclude.txt makedist.bat xenaddresource/sources xenenum/sources xenhide/sources xennet/sources xenpci/sources xenvbd/sources
line diff
     1.1 --- a/BUILDING.txt	Tue Jan 22 16:30:53 2008 +1100
     1.2 +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.3 @@ -1,31 +0,0 @@
     1.4 -1. Download and install the Windows Driver Framework SDK (6000, not 6001 
     1.5 -which is Longhorn only) from Microsoft. You have to jump through a few 
     1.6 -hoops to get it, but it is free (as in beer of course. Microsoft don't 
     1.7 -do the 'as in speech' variety of free). It's also huge. 
     1.8 -http://www.microsoft.com/whdc/driver/wdf/default.mspx is a good place to 
     1.9 -start. http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx is 
    1.10 -probably a better place to start. 
    1.11 -
    1.12 -2. Start the WDF Build Environment that best suits your needs. I've only 
    1.13 -ever used 2003 32 Bit Checked. 
    1.14 -
    1.15 -3. Use Mercurial (get it from 
    1.16 -http://www.selenic.com/mercurial/wiki/index.cgi/BinaryPackages) to get 
    1.17 -the latest sources from 
    1.18 -http://xenbits.xensource.com/ext/win-pvdrivers.hg. 
    1.19 -
    1.20 -4. From the top directory, type 'BLD'. 
    1.21 -
    1.22 -5. Assuming all went well, your drivers should be in target/<sys>/i386 
    1.23 -directory. (<sys> is winnet or winxp, depending on your DDK compilation 
    1.24 -environment.) 
    1.25 -
    1.26 -I've probably omitted some vitally important step from the above, so 
    1.27 -please let me know if you need any assistance compiling. 
    1.28 -
    1.29 -See the INSTALLING.txt file for information on how to install. 
    1.30 -
    1.31 -There is also a simple C# app which will enable 'graceful' shutdown (eg 
    1.32 -'xm shutdown' and 'xm reboot' will do the right thing). Open Xen.sln in 
    1.33 -Visual Studio to build it. 
    1.34 -
     2.1 --- a/INSTALLING.txt	Tue Jan 22 16:30:53 2008 +1100
     2.2 +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     2.3 @@ -1,92 +0,0 @@
     2.4 -Please follow the steps here exactly. If you don't, you may be left with 
     2.5 -an unbootable machine (although 'Last known good configuration' should 
     2.6 -make it bootable again). 
     2.7 -
     2.8 -1. Copy the driver files that you built by following the BUILDING.txt 
     2.9 -steps (or that you got from a binary dist), so that on your testing 
    2.10 -machine the tree looks like this: 
    2.11 -
    2.12 -Xen\<arch>\xenhide.inf Xen\<arch>\xenpci.inf Xen\<arch>\xenvbd.inf 
    2.13 -Xen\<arch>\i386\xenaddresource.sys Xen\<arch>\i386\xenhide.sys 
    2.14 -Xen\<arch>\i386\xenpci.sys Xen\<arch>\i386\xenvbd.sys 
    2.15 -Xen\<arch>\i386\WdfCoInstaller01005.dll (you'll need to copy 
    2.16 -WdfCoInstaller01005.dll from the redist folder in the DDK) (<arch> is 
    2.17 -winxp for XP, or winnet for 2K3) 
    2.18 -
    2.19 -2. Go to the device manager (Right click on My Computer, then select the 
    2.20 -Hardware tab, then click Device Manager) 
    2.21 -
    2.22 -3. Find the 'PCI Device' under 'Other Devices' - it should have an 
    2.23 -exclamation mark against it. Right click on it and select 'Update 
    2.24 -Driver...' 
    2.25 -
    2.26 -4. Select 'No, not this time' in answer to 'Can Windows connect to 
    2.27 -Windows Update...' and click Next 
    2.28 -
    2.29 -5. Select 'Install from a list of specific location (Advanced)' and 
    2.30 -click Next 
    2.31 -
    2.32 -6. Untick 'Search removable media...' and tick 'Include this 
    2.33 -location...'. Enter the name of the directory where you put the .inf 
    2.34 -files, then click Next 
    2.35 -
    2.36 -7. Windows should find the XenPCI driver as a candidate, and will 
    2.37 -complain that it hasn't been signed. Just accept the warning. 
    2.38 -
    2.39 -8. Windows should load the XenPCI driver, and then give you 4 more 
    2.40 -'Other Devices' - console, vfb, vif, and vbd. 
    2.41 -
    2.42 -9. Repeat steps 3-7 for the vbd device. Windows should then load the 
    2.43 -XenVBD driver. 
    2.44 -
    2.45 -10. The next bit is a bit tricker. In Device Manager, drill down on 
    2.46 -System devices and right click on PCI Bus and select Update Driver. 
    2.47 -
    2.48 -11. Select 'No, not this time' in answer to 'Can Windows connect to 
    2.49 -Windows Update...' and click Next 
    2.50 -
    2.51 -12. Select 'Install from a list or specific location (Advanced)' and 
    2.52 -click Next 
    2.53 -
    2.54 -13. This time, select 'Don't search. I will choose the driver to 
    2.55 -install' and click Next 
    2.56 -
    2.57 -14. Click 'Have Disk' and go to the locaton where you put the .inf 
    2.58 -files. 
    2.59 -
    2.60 -15. Select the 'Xen PCI Device Hider Driver' (I know, it's a stupid 
    2.61 -name) and install it, again accepting the unsigned driver warning. 
    2.62 -
    2.63 -16. edit your boot.ini to look something like this: 
    2.64 -
    2.65 -" [boot loader] timeout=30 
    2.66 -default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] 
    2.67 -multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, 
    2.68 -Enterprise" /noexecute=optout /fastdetect 
    2.69 -multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, 
    2.70 -Enterprise, GPLPV" /noexecute=optout /fastdetect /gplpv " 
    2.71 -
    2.72 -17. The main thing in the above step is that you have a line with /gplpv 
    2.73 -on the end. This tells the PV drivers to activate, otherwise they will 
    2.74 -pretty much sit silent. 
    2.75 -
    2.76 -18. Reboot and select the /gplpv entry. If it doesn't work then email me 
    2.77 -with some details and i'll see what I can do. 
    2.78 -
    2.79 -Without the /gplpv option specified, the xenvbd driver will only pick up 
    2.80 -on devices you have added since boot, so you can still test it without 
    2.81 -specifying /gplpv and doing something like the following in Dom0: 
    2.82 -
    2.83 -" xm block-attach mywindowsdomain phy:/dev/someblockdevice /dev/hdc w " 
    2.84 -
    2.85 -I'm pretty sure that you need to specify the 'phy:' otherwise the 
    2.86 -backend doesn't seem to publish the block and sector sizes correctly. 
    2.87 -
    2.88 -If you do the block-attach, then your block device should show up under 
    2.89 -windows, and you can partition it etc. 
    2.90 -
    2.91 -19. If you have built ShutdownMon, run "ShutdownMon -i" which will 
    2.92 -install it as a service. You will need to change the service to 
    2.93 -'Automatic' and start it (or reboot). 'xm shutdown' and 'xm reboot' 
    2.94 -should then do the right thing. 
    2.95 -
     3.1 --- a/README.txt	Tue Jan 22 16:30:53 2008 +1100
     3.2 +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     3.3 @@ -1,26 +0,0 @@
     3.4 -This is my GPL'd Xen HVM PV drivers for Windows. You can contact me at 
     3.5 -james.harper@bendigoit.com.au, or on the xen-devel mailing list. 
     3.6 -
     3.7 -Only block device drivers are supported so far. Also it's probably only 
     3.8 -really useful to anyone who knows something about windows driver 
     3.9 -development. 
    3.10 -
    3.11 -My test environment is Xen 3.1.1 (64 bit Hypervisor) and Windows 2003 
    3.12 -sp2 (32 bit PAE). YMMV. 
    3.13 -
    3.14 -You can get the source using Mercurial at 
    3.15 -http://xenbits.xensource.com/ext/win-pvdrivers.hg. 
    3.16 -
    3.17 -Please do not in any way consider it ready for production use. 
    3.18 -Definitely do not use them on a production DomU. While I have never seen 
    3.19 -them cause a problem with the hypervisor or Dom0, I would also be very 
    3.20 -wary of using them on a production physical machine too. It now seems 
    3.21 -fairly sane in use, I haven't had a crash for a while, but I haven't 
    3.22 -done nearly enough testing yet. 
    3.23 -
    3.24 -See BUILDING.txt for instructions on building the drivers. 
    3.25 -
    3.26 -See INSTALLING.txt for instructions on installing the drivers. 
    3.27 -
    3.28 -See TODO.txt for known problems and future plans. 
    3.29 -
     4.1 --- a/TODO.txt	Tue Jan 22 16:30:53 2008 +1100
     4.2 +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     4.3 @@ -1,21 +0,0 @@
     4.4 -The source code still needs a tidy up. The Windows DDK stuff has it's 
     4.5 -own coding style which I've imitated in places, and then xen has it's 
     4.6 -own too, so this code is mostly one, the other, both, or neither. I'll 
     4.7 -get to that as soon as I figure out what coding style to use and where. 
     4.8 -
     4.9 -Known problems or things that need doing to make it properly useful:
    4.10 -. Test under environments other than 32-bit PAE Windows 2003. Almost certainly
    4.11 -  won't work under 64 bit
    4.12 -. No power management
    4.13 -. Almost certainly won't support migration or suspend/resume.
    4.14 -. Reports of problems on Intel systems
    4.15 -. Lockups under SMP
    4.16 -. Probably lots of other things too.
    4.17 -
    4.18 -TODO:
    4.19 -. Do some performance testing
    4.20 -. virtual scsi (eg a front end for the scsi passthrough stuff)
    4.21 -. balloon drivers (this should actually be pretty easy)
    4.22 -. Write an installer for the above binaries to automate everything
    4.23 -. Fix crash dump under vbd (currently just hangs)
    4.24 -. Correctly handle CD changes
     5.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     5.2 +++ b/doc/BUILDING.txt	Tue Jan 22 20:01:56 2008 +1100
     5.3 @@ -0,0 +1,33 @@
     5.4 +1. Download and install the Windows Driver Framework SDK (6000, although
     5.5 +there are some reports that 6001 works too) from Microsoft. You have to
     5.6 +jump through a few hoops to get it, but it is free (as in beer of
     5.7 +course. Microsoft don't do the 'as in speech' variety of free). It's
     5.8 +also huge. http://www.microsoft.com/whdc/driver/wdf/default.mspx is a
     5.9 +good place to start.
    5.10 +http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx is probably a
    5.11 +better place to start. 
    5.12 +
    5.13 +2. Start the WDF Build Environment that best suits your needs. 32 bit
    5.14 +W2K3 and XP checked and free should all work. 64 bit builds but doesn't
    5.15 +run.
    5.16 +
    5.17 +3. Use Mercurial (get it from 
    5.18 +http://www.selenic.com/mercurial/wiki/index.cgi/BinaryPackages) to get 
    5.19 +the latest sources from 
    5.20 +http://xenbits.xensource.com/ext/win-pvdrivers.hg. 
    5.21 +
    5.22 +4. From the top directory, type 'BLD'. 
    5.23 +
    5.24 +5. Assuming all went well, your drivers should be in target/<sys>/i386 
    5.25 +directory. (<sys> is winnet or winxp, depending on your DDK compilation 
    5.26 +environment.) 
    5.27 +
    5.28 +I've probably omitted some vitally important step from the above, so 
    5.29 +please let me know if you need any assistance compiling. 
    5.30 +
    5.31 +See the INSTALLING.txt file for information on how to install. 
    5.32 +
    5.33 +There is also a simple C# app which will enable 'graceful' shutdown (eg 
    5.34 +'xm shutdown' and 'xm reboot' will do the right thing). Open Xen.sln in 
    5.35 +Visual Studio to build it. 
    5.36 +
     6.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     6.2 +++ b/doc/INSTALLING.txt	Tue Jan 22 20:01:56 2008 +1100
     6.3 @@ -0,0 +1,97 @@
     6.4 +Please follow the steps here exactly. If you don't, you may be left with 
     6.5 +an unbootable machine (although 'Last known good configuration' should 
     6.6 +make it bootable again). 
     6.7 +
     6.8 +1. Copy the driver files that you built by following the BUILDING.txt 
     6.9 +steps (or that you got from a binary dist), so that on your testing 
    6.10 +machine the tree looks like this: 
    6.11 +
    6.12 +Xen\<arch>\xenhide.inf
    6.13 +Xen\<arch>\xenpci.inf
    6.14 +Xen\<arch>\xenvbd.inf 
    6.15 +Xen\<arch>\i386\xenaddresource.sys Xen\<arch>\i386\xenhide.sys 
    6.16 +Xen\<arch>\i386\xenpci.sys
    6.17 +Xen\<arch>\i386\xenvbd.sys 
    6.18 +Xen\<arch>\i386\WdfCoInstaller01005.dll
    6.19 +(If you have compiled yourself, you'll need to copy
    6.20 +WdfCoInstaller01005.dll from the redist folder in the DDK) (<arch> is
    6.21 +winxp for XP, or winnet for 2K3)
    6.22 +
    6.23 +2. Go to the device manager (Right click on My Computer, then select the 
    6.24 +Hardware tab, then click Device Manager) 
    6.25 +
    6.26 +3. Find the 'PCI Device' under 'Other Devices' - it should have an 
    6.27 +exclamation mark against it. Right click on it and select 'Update 
    6.28 +Driver...' 
    6.29 +
    6.30 +4. Select 'No, not this time' in answer to 'Can Windows connect to 
    6.31 +Windows Update...' and click Next 
    6.32 +
    6.33 +5. Select 'Install from a list of specific location (Advanced)' and 
    6.34 +click Next 
    6.35 +
    6.36 +6. Untick 'Search removable media...' and tick 'Include this 
    6.37 +location...'. Enter the name of the directory where you put the .inf 
    6.38 +files, then click Next 
    6.39 +
    6.40 +7. Windows should find the XenPCI driver as a candidate, and will 
    6.41 +complain that it hasn't been signed. Just accept the warning. 
    6.42 +
    6.43 +8. Windows should load the XenPCI driver, and then give you 4 more 
    6.44 +'Other Devices' - console, vfb, vif, and vbd. 
    6.45 +
    6.46 +9. Repeat steps 3-7 for the vbd and vif devices. Windows should then
    6.47 +load the XenVBD driver. 
    6.48 +
    6.49 +10. The next bit is a bit tricker. In Device Manager, drill down on 
    6.50 +System devices and right click on PCI Bus and select Update Driver. 
    6.51 +
    6.52 +11. Select 'No, not this time' in answer to 'Can Windows connect to 
    6.53 +Windows Update...' and click Next 
    6.54 +
    6.55 +12. Select 'Install from a list or specific location (Advanced)' and 
    6.56 +click Next 
    6.57 +
    6.58 +13. This time, select 'Don't search. I will choose the driver to 
    6.59 +install' and click Next 
    6.60 +
    6.61 +14. Click 'Have Disk' and go to the locaton where you put the .inf 
    6.62 +files. 
    6.63 +
    6.64 +15. Select the 'Xen PCI Device Hider Driver' (I know, it's a stupid 
    6.65 +name) and install it, again accepting the unsigned driver warning. 
    6.66 +
    6.67 +16. edit your boot.ini to look something like this: 
    6.68 +
    6.69 +" [boot loader] timeout=30 
    6.70 +default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] 
    6.71 +multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, 
    6.72 +Enterprise" /noexecute=optout /fastdetect 
    6.73 +multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, 
    6.74 +Enterprise, GPLPV" /noexecute=optout /fastdetect /gplpv " 
    6.75 +
    6.76 +17. The main thing in the above step is that you have a line with /gplpv 
    6.77 +on the end. This tells the PV device (vbd, vif) drivers to activate,
    6.78 +otherwise they will pretty much sit silent.
    6.79 +
    6.80 +18. Reboot and select the /gplpv entry. If it doesn't work then email me 
    6.81 +(james.harper@bendigoit.com.au) with some details and i'll see what I can
    6.82 +do. 
    6.83 +
    6.84 +Without the /gplpv option specified, the xenvbd driver will only pick up 
    6.85 +on devices you have added since boot, so you can still test it without 
    6.86 +specifying /gplpv and doing something like the following in Dom0: 
    6.87 +
    6.88 +" xm block-attach mywindowsdomain phy:/dev/someblockdevice /dev/hdc w " 
    6.89 +
    6.90 +You need to specify the 'phy:' in your xen config file and in the
    6.91 +block-attach line otherwise the backend doesn't seem to publish the block
    6.92 +and sector sizes correctly. 
    6.93 +
    6.94 +If you do the block-attach, then your block device should show up under 
    6.95 +windows, and you can partition it etc. 
    6.96 +
    6.97 +19. If you have built ShutdownMon, run "ShutdownMon -i" which will 
    6.98 +install it as a service. You will need to change the service to 
    6.99 +'Automatic' and start it (or reboot). 'xm shutdown' and 'xm reboot' 
   6.100 +should then do the right thing. 
     7.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     7.2 +++ b/doc/README.txt	Tue Jan 22 20:01:56 2008 +1100
     7.3 @@ -0,0 +1,27 @@
     7.4 +This is my GPL'd Xen HVM PV drivers for Windows. You can contact me at 
     7.5 +james.harper@bendigoit.com.au, or on the xen-devel mailing list. 
     7.6 +
     7.7 +Block and Network drivers are supported, and a service is supplied which
     7.8 +will respond to 'xm shutdown' and 'xm reboot' commands.
     7.9 +
    7.10 +My test environment is Xen 3.1.1 (64 bit Hypervisor) and Windows 2003 
    7.11 +sp2 (32 bit PAE). YMMV. There have definitely been problems reported on
    7.12 +Intel architectures.
    7.13 +
    7.14 +You can get the source using Mercurial at 
    7.15 +http://xenbits.xensource.com/ext/win-pvdrivers.hg. 
    7.16 +
    7.17 +Please do not in any way consider it ready for production use. 
    7.18 +Definitely do not use them on a production DomU. While I have never seen 
    7.19 +them cause a problem with the hypervisor or Dom0, I would also be very 
    7.20 +wary of using them on a production physical machine too.
    7.21 +
    7.22 +It now seems fairly sane, I'm using it on a few low-risk production
    7.23 +machines without any problems.
    7.24 +
    7.25 +See BUILDING.txt for instructions on building the drivers. 
    7.26 +
    7.27 +See INSTALLING.txt for instructions on installing the drivers. 
    7.28 +
    7.29 +See TODO.txt for known problems and future plans. 
    7.30 +
     8.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     8.2 +++ b/doc/TODO.txt	Tue Jan 22 20:01:56 2008 +1100
     8.3 @@ -0,0 +1,21 @@
     8.4 +The source code still needs a tidy up. The Windows DDK stuff has it's 
     8.5 +own coding style which I've imitated in places, and then xen has it's 
     8.6 +own too, so this code is mostly one, the other, both, or neither. I'll 
     8.7 +get to that as soon as I figure out what coding style to use and where.
     8.8 +
     8.9 +Known problems or things that need doing to make it properly useful:
    8.10 +. Test under environments other than 32-bit PAE Windows 2003.
    8.11 +. No power management
    8.12 +. Almost certainly won't support migration or suspend/resume.
    8.13 +. Reports of problems on Intel systems
    8.14 +. Not enough testing under SMP.
    8.15 +. Probably lots of other things too.
    8.16 +
    8.17 +TODO:
    8.18 +. Do some performance testing
    8.19 +. virtual scsi (eg a front end for the scsi passthrough stuff)
    8.20 +. balloon drivers (this should actually be pretty easy)
    8.21 +. Write an installer for the above binaries to automate everything
    8.22 +. Fix BSoD crash dump under vbd (currently just hangs without writing
    8.23 +  a dump file)
    8.24 +. Correctly handle CD changes
     9.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     9.2 +++ b/exclude.txt	Tue Jan 22 20:01:56 2008 +1100
     9.3 @@ -0,0 +1,2 @@
     9.4 +.pdb
     9.5 +.vshost.exe
     9.6 \ No newline at end of file
    10.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    10.2 +++ b/makedist.bat	Tue Jan 22 20:01:56 2008 +1100
    10.3 @@ -0,0 +1,3 @@
    10.4 +@echo off
    10.5 +xcopy target\* dist /E /EXCLUDE:exclude.txt /D /Y
    10.6 +copy doc\*.txt dist
    11.1 --- a/xenaddresource/sources	Tue Jan 22 16:30:53 2008 +1100
    11.2 +++ b/xenaddresource/sources	Tue Jan 22 20:01:56 2008 +1100
    11.3 @@ -1,7 +1,7 @@
    11.4  TARGETNAME=XENADDRESOURCE
    11.5  TARGETTYPE=DRIVER
    11.6  TARGETPATH=..\Target\$(DDK_TARGET_OS)
    11.7 -VERSION=0.5.0.1
    11.8 +VERSION=0.6.0.0
    11.9  KMDF_VERSION=1
   11.10  MSC_WARNING_LEVEL=/W4
   11.11  #INF_NAME=xenaddresource
    12.1 --- a/xenenum/sources	Tue Jan 22 16:30:53 2008 +1100
    12.2 +++ b/xenenum/sources	Tue Jan 22 20:01:56 2008 +1100
    12.3 @@ -1,7 +1,7 @@
    12.4  TARGETNAME=xenenum
    12.5  TARGETTYPE=DRIVER
    12.6  TARGETPATH=..\Target\$(DDK_TARGET_OS)
    12.7 -VERSION=0.5.0.21
    12.8 +VERSION=0.6.0.0
    12.9  KMDF_VERSION=1
   12.10  MSC_WARNING_LEVEL=/W4
   12.11  INF_NAME=xenenum
    13.1 --- a/xenhide/sources	Tue Jan 22 16:30:53 2008 +1100
    13.2 +++ b/xenhide/sources	Tue Jan 22 20:01:56 2008 +1100
    13.3 @@ -1,7 +1,7 @@
    13.4  TARGETNAME=XENHIDE
    13.5  TARGETTYPE=DRIVER
    13.6  TARGETPATH=..\Target\$(DDK_TARGET_OS)
    13.7 -VERSION=0.5.0.9
    13.8 +VERSION=0.6.0.0
    13.9  KMDF_VERSION=1
   13.10  MSC_WARNING_LEVEL=/W4
   13.11  INF_NAME=xenhide
    14.1 --- a/xennet/sources	Tue Jan 22 16:30:53 2008 +1100
    14.2 +++ b/xennet/sources	Tue Jan 22 20:01:56 2008 +1100
    14.3 @@ -1,7 +1,7 @@
    14.4  TARGETNAME=XENNET
    14.5  TARGETTYPE=DRIVER
    14.6  TARGETPATH=..\Target\$(DDK_TARGET_OS)
    14.7 -VERSION=0.5.0.191
    14.8 +VERSION=0.6.0.0
    14.9  KMDF_VERSION=1
   14.10  MSC_WARNING_LEVEL=/W4
   14.11  INF_NAME=xennet
    15.1 --- a/xenpci/sources	Tue Jan 22 16:30:53 2008 +1100
    15.2 +++ b/xenpci/sources	Tue Jan 22 20:01:56 2008 +1100
    15.3 @@ -1,7 +1,7 @@
    15.4  TARGETNAME=XENPCI
    15.5  TARGETTYPE=DRIVER
    15.6  TARGETPATH=..\Target\$(DDK_TARGET_OS)
    15.7 -VERSION=0.5.0.43
    15.8 +VERSION=0.6.0.0
    15.9  KMDF_VERSION=1
   15.10  MSC_WARNING_LEVEL=/W4
   15.11  INF_NAME=xenpci
    16.1 --- a/xenvbd/sources	Tue Jan 22 16:30:53 2008 +1100
    16.2 +++ b/xenvbd/sources	Tue Jan 22 20:01:56 2008 +1100
    16.3 @@ -1,7 +1,7 @@
    16.4  TARGETNAME=XENVBD
    16.5  TARGETTYPE=DRIVER
    16.6  TARGETPATH=..\Target\$(DDK_TARGET_OS)
    16.7 -VERSION=0.5.0.17
    16.8 +VERSION=0.6.0.0
    16.9  KMDF_VERSION=1
   16.10  MSC_WARNING_LEVEL=/W4
   16.11  INF_NAME=xenvbd