New VM converted from physical machine hangs after power up

I have just converted an XP Professional PC using Converter Standalone Client in local mode to my ESXi server.

When powering up the new VM using vSphere Client, all I see via the console is a cursor. Nothing else happens at all. I then have to force a power off.

How should I look at fixing this?

Am using ESXi V4.
logicalcAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

vmwarun - ArunCommented:
This problem occurs when you select the wrong SCSI Controller type when converting the VM,
What type of disk (IDE, SATA) is the Windows XP Pro running on ?
0
bbnp2006Commented:
Have you got VMWare tools installed on your XP virtual machine? Is this the first time you boot it up after the P2V conversion? In the virtual machine settings configuration, double check if you are using LSIlogic or Buslogic for your SCSI controller.  Make sure you are using LSI logic. Better yet, if you can post a screenshot of your Hardware configuration settings for your XP VM, it would be easier to point you to the right direction.
0
coolsport00Commented:
This is a somewhat often post on EE. Check out these 2 somewhat recent posts for suggestions:
http://www.experts-exchange.com/Software/VMWare/Q_25105961.html?sfQueryTermInfo=1+black+convers+fail+screen
http://www.experts-exchange.com/Software/VMWare/Q_25019886.html

Hope this helps.

Regards,
~coolsport00
0
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

Vijay kumar MohanrajCloud ArchitechCommented:
Agent Installation Location
Locally: Install Converter and agent directly on source machine if converting directly into ESX Server
Remotely: Connect to source machine over network to install agent

Agent Installation

Use local administrator account
Avoid domain accounts that have restrictive policies
Allow reboot for Windows NT 4.0 and 2000 sources

Machine Preparation
Do not deactivate the following services or harden security
Workstation service
Server service
TCP/IP NetBIOS Helper service
Volume Shadow Copy service (Windows 2003 or XP)
Ensure sufficient free disk space (at least 200MB)
Mirrored or striped volumes across multiple disks should be broken
Dynamic disks with utility partitions should use cold cloning
Disable Windows Simple File Sharing (Windows XP only)
Disable anti-virus software
Defrag hard disks
Shutdown any un-needed Windows Services
Clean-up any temporary files and un-needed data
Run chkdsk
Keep users off if possible
Power off VM if not using hot cloning
VCB VM exports need editing prior to import
Edit virtual disk filenames inside .vmx
Rename filenames for .vmdk files to match those listed in .vmx
Edit index .vmdk file to change references to span files

Network Preparation
Open TCP/UDP ports 139, 445, and 902 (Converter 3.0.0) or 443 (Converter 3.0.1)
Open network ports between source and destination, alternative is to create a VM visible to source, copy VM files to location visible to destination, and import VM
Use FQDN to connect to both source and VI3

Clean-Up After Power On

Detect hardware
VMware Tools installation may hang if hardware not detected
Allow reboots to occur
Detect hardware and VMware Tools installation
Verify HAL and change if necessary
Remove non-present old hardware
CMD prompt type set DEVMGR_SHOW_NONPRESENT_DEVICES=1
Next type DEVMGMT.MSC and select Show Hidden Devices
Delete any old grayed out non-present hardware

Guest Troubleshooting
Blue screen after powering on
Start Windows in Safe Mode and uninstall hardware-specific applications or services
Attach VM to “Helper VM” to remove hardware-specific drivers or to correct the boot.ini
No keyboard/mouse
Select Workstation/Server VM instead of ESX Server, then import VM to ESX Server
Use PS/2 keyboard/mouse on source
Display problems
Uninstall PC Anywhere prior to installing VMware Tools
0
Vijay kumar MohanrajCloud ArchitechCommented:
HI is that my information is useful please vote me.
0
logicalcAuthor Commented:
Many thanks mail2vijay1982, this certainly looks like what I need to try.

When I started, I thought this would be easy! (wrong move!). Since then I just have not had time to try. Will try again in the next few days.

unfortunately the PC I am trying to convert is slow and old. The conversion last time took 6 hours, so I want to avoid many tries.
0
vmwarun - ArunCommented:
Another alternative is to use Acronis True Image, StorageCraft Shadow Protect or Norton Ghost to take an image of the physical machine and use VMware vConverter to  convert it into a Virtual Machine.

Acronis - http://www.acronis.com.sg/backup-recovery/advanced-server/

Norton Ghost - http://www.symantec.com/norton/ghost

StorageCraft - http://www.storagecraft.com/shadow_protect_SBS.php
0
logicalcAuthor Commented:
No success yet.

Arunraju, for Acronis True Image, are you suggesting using VMware vCenter Converter Standalone 4 or  VMware Converter 3?

The former supports only "Acronis True Image Echo 9.1, 9.5, and Acronis True Image 10, 11 (Home product)". How can I use Acronis True Image 2010?

Does VMware Converter 3 support Acronis True Image 2010? And also with ESXi V4?
0
vmwarun - ArunCommented:
Acronis True Image 10 or 11 can be used ,logicalc and the TIB Image can be used with vCenter Standalone Converter v4.0 to be converted into a VM.
I apologize for replying late.
0
coolsport00Commented:
What is the SCSI Controller set to? Change it to LSI Logic, if it's set to BUS Logic and see if that works.

Regards,
~coolsport00
0
logicalcAuthor Commented:
coolsport00, am using SATA hard disk. Is SCSI controller setting relevant?
0
Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:
Hi

Let me copy here a list that i post in another question

Use this to have a more successful P2V for Windows Servers

I use scripts for most of this tasks and other pre and post P2V tasks

1º Create some txt files with all the Network settings in save on the physical server for future use
2º Use msconfig to stop all non windows services
3º Never power up the VM after the P2V and dont use the power on, on the NICs to migrate
4º Before any changes on the new VM create a Snapshot for the Initial State for possible rollback
5º Before start the VM clean all usb, serial port, disk drives etc
6º Remove also any adapters created by the P2V. Create new ones(vmxnet for 3.x or vmxnet3 for 4.x)
7º Start your VM for the first time in safe mode
8º In safe mode, remove all phantom hardware(i have a script for this), and uninstall all Software for Hardware Management(like RAID, Storage agents etc)
9º Use the txt files to config your Network settings according to the old server(do not connect the adepter yet)
10º After this changes reboot the server in normal mode(dont change msconfig yet)
11º After new boot check all the software and services.If you see no issues, or and phantom hardware, then msconfig and choose normal boot. Reboot the server
12º After rebooting the server, check if all services are running, and after all is running, then shutdown the physical server(or disconnect the cable) and connect to the network the VM
13º Reboot on more time the server will all runing(services and network) and test all the network connection and use a domain account

This are some of the tasks that we need to create to have a good P2V sucess

Hope this can help you

Jail
0
coolsport00Commented:
Yes...SCSI is relevant. Try changing to LSI Logic if it's not already.

~coolsport00
0
logicalcAuthor Commented:
Am a relative newbie to this.

Coolsport00 - Where do I change from SCSI (if set!) to LSI Logic?

Betstway - how do I:
- clean all usb, serial port, disk drives etc
- Remove adapters created by the P2V. Create new ones
    - how do I get vmxnet3? Is it free?
- Start my VM for the first time in safe mode?

Am using ESXi V4 as stated earlier.
0
coolsport00Commented:
Right-click on VM -> Edit Settings. Click on SCSI Controller and select LSI Logic on the right. VM must be powered down.

~coolsport00
0
logicalcAuthor Commented:
coolsport00, No SCSI controller is available, as I have a SATA hard disk
0
Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:
Hi

- clean all usb, serial port, disk drives etc

Just delete this hardware from the VM. Right-click on VM -> Edit Settings. and delete this

- Remove adapters created by the P2V. Create new ones

The same way that the above, remove and create new ones

- how do I get vmxnet3? Is it free?

This is from ESX 4.x so if you have this version, when you create a new Adapter you can choose vmxnet3

- Start my VM for the first time in safe mode?

Just star the VM as normal Windows( this is Windows safe mode not VMware) on the boot F8 and choose safe mode

For the type of questions(many are simple and very basic) I think you are very newbie on this, so try to read some VMware documentation before go further with VMware technology

This is my opinion

Hope this can help

Jail
0
coolsport00Commented:
If you have no SCSI Controller associated with your VM, that is your problem as to why it can't/won't boot up. Retry the conversion, or try an alternative method -> Acronis True Image, for example to make an image of your box, then use Converter to convert the image to VMware.

~coolsport00
0
Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:
Hi

@coolsport00

Did not understand that. I have migrate many servers, with IDE, or just SATA controllers, and I have found no issues in the VM boot

Jail
0
coolsport00Commented:
I have too :) Sometimes...for whatever reason, during a P2V, the SCSI Controller doesn't get added to the converted machine (VM). If that happens, the VM can be powered on, but will only show a black screen with a blinking cursor. There have been other posts the past several months that this has happened to that I've assisted with. I like vCenter Converter, but it can be 'buggy' in my opinion sometimes.

~coolsport00
0
Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:
Hi

OK thank you for he information, I never had that issue

If you do a cold migration, this issue I think will never happen. This why i like cold migration :)

Jail
0
coolsport00Commented:
Yeah...I have yet to see any issues with that migration, but for most of us, that is a 'last resort' option since it takes down the source host and is kind of a bit more drawn out process. But yes...works pretty consistently. :)

Regards,
~coolsport00
0
logicalcAuthor Commented:
Unfortunately I could not get any VM from the old PC to run properly. Am instead creating a new VM from scratch, loading a fresh copy of Windows.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.