(Clearify why I think this might be outdated)
m (VirtioWindowsDrivers moved to WindowsGuestDrivers/kvmnet/installer: This page doesn't describe the driver but the installer.)
Latest revision as of 13:14, 12 April 2010
The information below might be outdated (or not) as it links to different drivers than WindowsGuestDrivers/Download_Drivers.
Drivers can be found at: https://sourceforge.net/project/showfiles.php?group_id=180599&package_id=267944
Note that there are 2 pointers to it. The "kvm-guest-drivers-windows" is older version.
This is a general installer, it's not Windows standard and it won't handle all sort of possibilities (like if you have 3 virtio devices, two of them with older virtio drivers, disabled). It does handle 95% of the cases. Anyway, enjoy, installation instructions below.
Installer for NetKVM drivers
1. During installation on there are system pop-ups related to installation of unsigned drivers. These pop-ups can not be suppressed and the installation must be confirmed manually.
2. During installation there are pop-ups of drivers search etc - they usually are closed automatically and should be ignored.
3. Sometimes pop-up (1) may be not visible under pop-up (2) - the installation will wait until the pop-up (1) confirmed.
4. Expected placement of installer is in the root of driver's tree. If the placement is different, command-line should include the actual driver's root path, relative or absolute.
5. Since we did not (yet) sign the drivers you need to install a certificate workaround manually. This is required for Windows Vista/2008 64-bit. There are several things to do:
a. Disable UAC
b. Install certificate using installcertificate.bat
c. Run "bcdedit /set testsigning on" and reboot
Please contact me for any questions/comments regarding the installer
ReadMe files (included below): tools\NetKVM-Installer\ReadMe.txt tools\Package\ReadMe.txt
Readme of tools\NetKVM-Installer
This project creates installer application for NetKVM drivers. 32-bit and 64-bit installers are built using suitable configurations in the VS solution.
By design, both 32 and 64 bit executables are packed into single 32-bit installer application, which extracts them according to exact system architecture into temporary file and runs, passing command line arguments as was passed to the application. See "Package" project for details.
Relative location of drivers and list of PnPID to install are currently hard-coded inside installer, exactly as they are created by the build procedure of NetKVM drivers.
NOTE: The installer doesn't automates the Driver certifications required by Windows 64-bit. This step must be done manually.
Command-line options: OS-Specific-Installer [path] [options]
path - (optional) absolute or relative path to the root directory of drivers tree
OS-dependent drivers are expected to be placed under it as: +---2K ¦ L---x86 +---Vista ¦ +---amd64 ¦ L---x86 L---XP +---amd64 L---x86
options: -u uninstall drivers only, do not install -ni non-interactive install (only for signed drivers)
If no parameters passed: path=. (current directory where the installer runs) action - uninstall existing drivers, then install current ones.
Readme of tools\Package
This project is Installer package - 32-bit application, including as resources 2 applications:
- 32-bit installer - 64-bit installer
It contains also 32 and 64 bits DLL of DIFX API, which currently is not in use.
When run, the actual per-architecture installer is unpacked into temporary directory and runs without changing the current directory and passes to the actual installer the command line of container application.
Debugging NetKVM drivers
1. Enable logging by setting the NIC's Advanced settings -> Logging Enable, then -> Logging Level -> 2
2. In order to collect the log of installation - run DebugView and enable Win32 logging capture.
3. The system diagnostic, related to installation, on 2008 is in %windir%\inf\setupapi.dev.log