After mounting the floppy, and pointing to it after asking XP to update its SCSI driver, then restarting the guest, I still get the message about needing a BusLogic driver, and the guest is really slow.
Can someone please tell me what SCSI type I should be using for Windows XP Pro? No matter what SCSI controller I use, VSphere provides an error telling me that Win XP does not support the driver VMWare ESX uses for virtual SCSI devices - but it works fine.
Esxi Xp Scsi Driver
I understanding that BusLogic is the only SCSI controller type I should use for Win XP Pro, correct? The doc says the driver is not needed for LSI controller types, but those types also provide the same error.
I matched the driver I was using to the one you recommend. The ONLY way I do not receive this error is if I use virtual IDE hard drives. ANY virtual SCSI drive regardless of the driver I use seems to create this error, except the words BusLogic will be exchanged with LSI Logic, LSI SAS, etc.... I do not have to click OK, continue, or cancel as the error indicates.
I recently installed ESXi on a Dell Precision 670 (Thanks to the members on this forum for helping me with my nocheckCPUIDLimit issue). I now have an issue trying to install Win XP Pro 32bit. I mount it to the .ISO and everything seems to run fine, but Windows fails to see my SATA controller. I tried making a .flp file with the SATA drivers from Dell and mount that but it doesn't see the hard drive. Is there a trick to this or is my SATA controller not supported?
The XP cd doesn't have the SCSI drivers on it to recognize either the Buslogic or LSI logic SCSC controllers that ESX uses in its VMs. If you created your VM with a SCSI adapter type of buslogic, you'll need to download a drivers floppy image from the below link.
ESXi abstracts the physical hardware and creates a layer between it and your virtual machine. The virtual machine can't see that physical hardware, it only sees the virtual hardware that ESXi presents to it. When you setup the virtual machine, you chose either Buslogic or LSI disk controller for the system. With Windows XP, neither of those drivers are included on the install disk and so you must download the linked .flp, mount it on the system and press F6 at the start of the Windows install to add SCSI or RAID drivers.
There is at last one virtual SCSI device installed on this Windows XP virtual machine. Windows XP does not include drivers for the BusLogic SCSI adapter that VMware ESX uses for virtual SCSI devices. To use these virtual SCSI devices, install the VMware driver in the virtual machine.
There us at least one virtual SCSI device installed on this Windows XP virtual machine. Windows XP does not include drivers for the LSILogic SCSI adapter that VMware ESX uses for virtual SCSI devices. To use these virtual SCSI device, download the LSI Logic drivers separately.
When you build an XP guest VM, chances are you use the IDE driver to get up and running right away. The IDE driver works OK for locally stored VMs, but performance will degrade significantly when accessing disk files over the network. Below are (rough) steps to switching to the Red Hat virtio drivers in a Windows XP guest.
By default, ESX will use the LSI Logic driver when deploying a new Windows XP virtual machine. The LSI Logic driver is not found on the CD-ROM media, so Windows XP will not continue with the installation if this driver is not found.
NOTE: when using the BusLogic driver instead, you can download & use a preconfigured .flp file from the VMware site: -1.2.0.4.flp. Follow the same procedure as described above. The driver should be name VMware SCSI Controller in Windows XP.
Make sure you download the SCSI LSI Logic driver. Restart the setup; run F6 and load the SCSI drivers. With the lastest versions of VMWare ESX/ESXi you will be able to add IDE devices and perform usual installation without the SCSI driver.
There are numerous articles covering this, but no apparent consensus on what exactly should be done to solve it. Many of the googled answers point to XP's flaky SCSI support and recommend the installation of SCSI drivers through the mounting of a floppy image ( -1.2.0.4.flp). This didn't work for me, despite getting Windows xp to recognise the image. Upon getting a confirmation of the install and an installation welcome screen, the exact same hard-disk error displayed, preventing any further progress.
Pre ESX 4.1 the PVSCSI adapter had only been recommended for VMDK's backed by fast (2,000+ IOPS) storage. Why? The PVSCSI driver only coalesces OIOs (Outstanding IOs) and not throughput (IOPS). What this means is; when the VM is requesting a lot of IO and the storage cannot deliver it, the PVSCSI driver is coalescing interrupts. Without the steady steam of IOs from the storage, there are no interrupts to coalesce. This can cause extra latency on low throughput environments.
However! In ESX 4.1 this issue explained above has been fixed. This means that the PVSCSI could perform as well as the LSI Logic driver with low throughput. I have yet to see any official performance test results. If you have already used PVSCSI adapters and are not seeing any performance problems, I wouldn't worry too much about making the change to LSI.
The ESXi-Customizer-PS PowerShell script ( -front.de/p/esxi-customizer-ps.html) can be used to integrate drivers and updates into the ESXi 5.x, 6.x, and 7.0 installation images. To use this script, you must have VMware PowerCLI installed on your computer.
If you receive: An unexpected error occured: Could not find trusted signer while exporting the image, disable driver signature verification with the -nsc (-noSignatureCheck) option. Also, try this option if an error occurs:
Save ESXi-Customizer.cmd file and run it. In the next window, specify the path to the source ESXi ISO image, the driver file (VIB file or TGZ archive with drivers), and the folder, to which the resulting image with the integrated driver must be saved. Uncheck the automatic update option.
I finally got annoyed. I have 2x esxi production hosts and 2x proxmox hosts that are my homelab testing hosts. The only reason tehy dont have esxi on them is the fact my dell optiplex mciro sff 7080s dont recongize nic and sata drivers. WEll that is now fixedI also moved my production esxi hots from 6..5 to 6.7 and vcenter to 6.7 as wellThanks for this guide!
Install XP to a VM and, once installed, install the VMware Tools. There should be an option for that if you right-click on your VM. One of the folders I mentioned should give you SCSI driver and a few others. VMware, Inc. Mouse vmmouse.inf 12.4.0.5VMware, Inc. SCSIAdapter vmscsi.inf 1.2.1.0VMware, Inc. Display vmx_svga.inf 11.06.00.0031ThinPrint Printer OEMPRINT.INF 7.15.0.6ThinPrint Printer OEMPRINT.inf 1.0.0.12VMware, Inc. System vmci.inf 7.2.30.0VMware, Inc. Net vmware-nic.inf 2.0.3.6VMware, Inc. Net vmxnet.inf 2.0.3.6VMware, Inc. Net vmxnet3ndis5.inf 1.0.0.11The link I provided is the floppy you need if you are installing XP from source files and using SCSI.
Now that you are done slipstreaming the service pack using the command line. You should now skip to the section detailing how to slipstream your SATA hard drive drivers. If you are not using a SATA drive you can skip ahead to learn how to burn the DVD.
If you have not already installed nLite, you will need to download and install the program first. Next, you will need to download your SATA drivers from your motherboard or computer manufacture's web site. In our example, I will be using VIA raid drivers from Biostar. Once the SATA drivers have been downloaded, you should extract them to a folder on your hard drive. In our example, we have extracted the drivers into the C:\SATA Driver folder.
After selecting Drivers, you should click on the Next button. You will now be at the Drivers screen. You should now click on the Insert button and then select the Multiple driver folder option so you can include all of the drivers for your specific operating system.
You will now be prompted for the folder where your extracted drivers are. You now want to browse to this folder, and when there, locate the correct folder for your Operating system. In our case it is the x86 directory since I am using 32bit Windows XP Pro.
You should now select the folder, and then press the OK button. nLite will now automatically install the drivers contained in both subdirectories. You will now see a screen showing the available drivers found in these folders. You should click the All button to select all drivers for your system and then press the OK button.
NOTE: If there are drivers for other versions of windows, for example Vista or 64 bit drivers, do not install them as it will cause file load errors. If you do select them, nLite will notify you of the problem.
If multiple are listed in the Textmode integration options box, select the appropriate driver for your operating system. The OK button will now become available and you should click on it. Do this same routine for for each and every driver that you are installing.
After selecting Textmode Driver you will be at a page listing all the drivers that will be installed. You should click on the Next button and then click on the OK button when it asks if you want to start the process. Your SATA drivers will now be integrated into your Windows files folder. When the process has finished, click on the Next button and then the Finish button.
A driver is a program that is able to control a device that is connected to your computer. These drivers are used by the operating system to enable it to communicate with the particular device the driver was made for. Devices that you connect to your computer are often very specialized which makes it so Windows can not communicate directly with the device without a program telling it how to. This ... 2ff7e9595c
Comments