Windows XP VM Showing Blank in Console

[SheldonEden]

We are running ESXi 4.4.0 (bare metal) on a Dell PowerEdge R410 server with a PERC H700 RAID controller. Currently hosting several Server 2003 development VMs with no issues.

I am trying to create/deploy a Windows XP VM to this server, but due to lack of budget and poor planning on the part of the person who ordered the hardware, I cannot create the VM directly on the host: there are no XP-level drivers for the RAID controller. Okay, I'll just install XP on a physical PC and convert it to a VM, upload it to the data store, and I'm good to go. Using vCenter Converter Standalone 4.0.1 I converted the system, uploading it to the datastore without issue or error. I also set the reserved video memory at 32MB.

However, whenever I start the VM inside my vSphere client, all I am getting is a blank screen, with a cursor in the upper right-hand corner, like this:

I have also tried creating a VM of the same system using VMWare Server as well as Workstation, writing it to an external disk, and then uploading it to the datastore, but I am getting the same result every time I launch the VM.

Is there something that I am missing? Is there another way that I can create the VM to successfully run on this setup? Please help!

[MentholMoose]

You can configure a VM with virtual IDE disks and XP will install with no problem. Also you can use virtual SCSI disks with the BusLogic controller, and use the F6 floppy during setup to add the drivers needed to install:

Using the VMware SCSI Disk Driver for Windows Guest Operating Systems

EDIT: Note that the lack of SCSI drivers when installing an XP VM has nothing to do with the physical hardware, since the VMs do not see the physical hardware (XP just doesn't include drivers for the virtual SCSI controllers).

---

Kirk Kosinski

VCP 4, MCITP: EA/VA/EDA7

[Troy_Clavell]

couple things. Is the VM in question using an IDE drive? If so, this is probably the issue. I would do the conversion again and in step 3 change the controller type to SCSI (LSI or BusLogic. I prefer LSI)

As for the correct drivers. It an XP CD issue, the SCSI drivers are not present. you can create a new custom VM, choose LSI for controller and then during the install of XP hit F6 and mount the floppy image attached. (although a little old, still works well)

[SheldonEden]

That seemed to do the trick; I was able to get the OS installed and running. Now, I can't seem to get my network connection functioning.

Getting the usual "Limited or no connectivity" error. Device Manager is showing an AMD PCNET Family PCI Ethernet Controller as the primary NIC. Physically, the host system has a BroadCom NetXtreme 100/1000 NIC, set at 100MB/Full. Currently, nothing is configured for Passthrough.

[MentholMoose]

Edit the VM Properties and verify that the network adapter is connected to a valid network. It sounds like the VM is configured to use DHCP so there will have to be a DHCP server on that network. If you're not using DHCP on the network then configure the VM with a static IP.

Did you configure any networks or vSwitches? For a standalone host, these are configured on the host on the Configuration tab under Networking.

---

Kirk Kosinski

VCP 4, MCITP: EA/VA/EDA7

[SheldonEden]

Looks like changing over from DHCP to a static IP did the trick. What could cause this? I'm planning on keeping all my VMs static, so this is purely for my knowledge...

Thanks for your help!

[MentholMoose]

For DHCP to work, a DHCP server needs to be on the same subnet as the VMs. Or, if the DHCP server is on another subnet, there needs to be a DHCP relay (e.g. ip helper-address on Cisco switches).

---

Kirk Kosinski

VCP 4, MCITP: EA/VA/EDA7

[Troy_Clavell]

If you edit settings of the guest, there is a check box next to connected for the network adapter?