Posts Tagged ‘Windows’

VMWare ESX – Creating a Windows XP VM and getting error: "Setup did not find any hard disk drives installed in your computer."

VMware

Trying to install Windows XP within VMWare ESX and getting the following error message?

"Setup did not find any hard disk drives installed in your computer."

ESX,XP,Drivers

If so not to worry – all that the Windows XP installation process is telling you, as the error message explains, is that it can’t see any available hard disks on which to install XP.

The reason for this is that the necessary hard disk controller drivers have not been installed.

Within ESX there are two types of SCSI controller types available.  These are ‘BusLogic’ or ‘LSI Logic’.

ESX XP Driver

When installing Windows XP the ESX VM will assign the ‘BusLogic’ SCSI controller type as the default.  The Windows XP installation media doesn’t contain the drivers for either of these controllers so unless they are provided via floppy disk at the start of the installation process then XP will not know about any of the disks attached to the controller (which it doesn’t have drivers for).

Using an LSI Logic SCSI controller type has been shown to provide faster performance over that of a BusLogic controller type.

Although only relating to ESX v2.1.1 and Windows Server 2000/2003 this article highlights the performance difference with running a Windows Server OS using a LSI Logic controller under the VM as opposed to BUSLogic.  Ok, I know it doesn’t mention XP but apparently XP also benefits with increased performance (as with W2K3) when using the LSI Logic controller type.

To provide Windows XP with the correct drivers during the installation process following the steps outlined below.

All you have to do to resolve this issue is:

- Download the flp (floppy disk) image for either LSI Logic or BUSLogic from the links below:

*Update Note (March 09): A few people have reported that the newer LSI Logic XP driver doesn’t work.  I would recommend trying the older version first and failing that try the newer version. Thanks to ‘cubeconn’ in pointing out a useful VMware Forum post around this.

LSI Logic XP Driver (Older Version)

LSI Logic XP Driver (Newer Version)

Bus Logic XP Driver

- Upload the flp file(s) to your data/ISO store used by your ESX server.

- From within the XP installations Virtual Machine settings, edit the floppy disk settings and select the flp file containing the SCSI Controller driver you wish to use during the installation process.  Though don’t tick/check the ‘Connect at power on’ box.  Otherwise XP when you go to start the installation will try to boot from the floppy disk and will fail. 
 ESX XP Driver

- Start the installation of the guest OS, in this case Windows XP after creating the VM.

- When prompted to add ‘Additional SCSI Drivers’, press F6 (Function 6 button).

- Connect your floppy disk ISO (flp file) of the SCSI controller driver you wish to use.

- Then press the ‘S’ key to specify an additional device.  The XP installation process should now read this ISO file and will detect the controller drivers.  Press the ‘Enter’ key to continue.

ESX XP Driver

- The XP installation should now detect the disk created for this guess OS and proceed as normal.

- Install VMTools!

Good Luck!

Technorati Tags: ,,,,,,,,,,,

Cool Blogging Tool

General

Looking for a cool blogging tool?

If so, check out ‘Ecto’. It is available for both the Windows and MacOS platforms. You can download a 20 day trial or purchase a copy for US$17.95. I’m currently using it both on my MacBook and PC.

If your looking for some good Mac based blogging tools head over to ‘ProBlogger’ and read their list of 5 “essential” tools.

Differences between the various Windows Server 2003 Versions

 

Here is a breakdown of the differences between the various Windows Server 2003 editions.  This information is from the Parameg site – I decided to include it due to it’s nice clear explanations.


Windows Server 2003 Web Edition
Windows Server 2003, Web Edition is mainly for building and hosting Web applications, Web pages, and XML Web Services. It is designed to be used primarily as an IIS 6.0 Web server and provides a platform for rapidly developing and deploying XML Web services and applications that use ASP.NET technology, a key part of the .NET Framework. This edition does not require Client Access Licenses and Terminal Server mode is not included on Web Edition. However, Remote Desktop for Administration is available on Windows Server 2003, Web Edition. Only 10 concurrent file-sharing connections are allowed at any moment. It is not possible to install Microsoft SQL Server and Microsoft Exchange software on this version of Windows, although MSDE and SQL Server 2005 Express are fully supported after service pack 1 is installed. The most important limitation of Web edition is a maximum memory of 2 GB RAM. Additionally, Windows Server 2003, Web Edition cannot act as a domain controller. See Compare the Editions of Windows Server 2003.

Windows Server 2003 Standard Edition
Windows Server 2003, Standard Edition is aimed towards small to medium sized businesses. Flexible yet versatile, Standard Edition supports file and printer sharing, offers secure Internet connectivity, and allows centralized desktop application deployment. This edition of Windows will run on up to 4 processors with up to 4 GB RAM. 64-bit versions are also available for the AMD x86-64 architecture and the Intel clone of that same architecture, EM64T. The 64-bit version of Windows Server 2003, Standard Edition is capable of addressing up to 32 GB of RAM and it also supports Non-Uniform Memory Access (NUMA), something the 32-bit version does not.

Windows Server 2003 Enterprise Edition
Windows Server 2003, Enterprise Edition is aimed towards medium to large businesses. It is a full-function server operating system that supports up to eight processors and provides enterprise-class features such as eight-node clustering using Microsoft Cluster Server (MSCS) software and support for up to 32 GB of memory. Enterprise Edition also comes in a 64-bit edition for Intel. 64-bit versions are also available for the AMD x86-64 architecture and the Intel clone of that same architecture, EM64T. The 64-bit version of Windows Server 2003, Enterprise Edition is capable of addressing up to 1 TB of RAM. Both 32-bit and 64-bit versions support Non-Uniform Memory Access (NUMA).

Windows Server 2003 Datacenter Edition
Windows Server 2003, Datacenter Edition is the flagship of the Windows Server line and designed for immense infrastructures demanding high security and reliability. Datacenter supports up to 64 processors. It also supports Non-Uniform Memory Access (NUMA).

Windows Server 2003 Compute Cluster Edition
Windows Server 2003, Compute Cluster Edition is designed for working with the most difficult computing problems that would require high performance computing clusters. Compute Cluster edition deploys in clusters of multiple servers to form large supercomputers. Microsoft intends to release this edition in 2006.

Windows Server 2003 Storage Server
Windows Storage Server 2003 is optimised to provide dedicated file and print sharing services. It is only available through OEMs when purchased pre-configured with network attached storage devices, which are available in a wide variety of sizes from a couple hundred gigabytes to a few terabytes. One significant difference, when compared with the other Windows Server 2003 editions that provide file and print services, is that Storage Server does not require client access licenses.

Also, here is a good Microsoft TechNet library article that clearly outlines the differences between the versions of Windows Server 2003.

This Microsoft article also offers similar information.


  

Trilead
VMware vSphere Recommended Reads
TrainSignal - vSphere Pro
Veeam #1
StarWind Software
TechHead Needs You - Top 25 Blog Sites
AppAssure