P2V i,ssue - black screen on boot

Hi Guys

I've P2V'd about 15 servers with no issues in our enviroment but have hit one with an old desktop that has been running as a server.

The desktop is a dv2000MT, 2gb ram, 80gb HDD running Windows Server 2003 Standard 32 bit.

I'm using VCenter Converter Standalone v4.0 (I think this is the version)

The enviroment i'm putting this is ESXi 4.0.

The server seemingly converts without issue, however when I attempt to boot it goes past the VMWare bios and hits a black screen with a hash in the top left.

I've had a look around the VM communities for similar issues and people have had them, however the solutions providing do not seem to work in my case, i've tried;

  • Making sure the disk controller is SCSI LSI Logic (have also tried SCSI Bus Logic)
  • Removing all unecessary components (e.g. USB, CD etc)
  • Reconfiguring the Virtual Machine using VCenter Converter (this is successful but same result)
  • Deleting the actual VM but retaining the disks, then creating a fresh new VM within VSphere and attaching the disks
  • Have checked the boot.ini by using a helper VM and it is fine
  • Converted to a seperate ESXi Server

I've not tried converting the server offline as downtime can only be had on sunday evenings so would have to wait until then if this was a worthwhile suggestion.

Worth trying a different P2V tool?

Any similar issues anyone else has had?

As a last resort we will have to rebuild the server from scratch, however really is a last ditch because it's fairly 'bespoke' as you can imagine from having a desktop run critical services ;) ps. I've inherited this before I get grief.

Thanks
 
If you don't mind paying for it Platespin is a great P2V tool.

Is there anything running on the server with special permissions that the migration tool might be having problems with?
 
Shouldn't be - will check tommorow - just standard domain stuff I think but worth a check!

I'll have a scan if Platespin do a trial, would be nice for the one server ;)
 
Resolved - I converted for a fourth time (using the VCenter Converter) but edited the conversion options to include;

  • Changing disk controller during conversion to LSI Logic
  • Removed the NIC
  • Installed VMWare tools during conversion
  • Reduced the disk size to the minimum (will expand volume once complete)

And it boots into Windows :)

Wooohooo!
 
Did you find the conversion was quicker when you made changes to the disk size? I have found this greatly reduces the time it takes to convert any machine, it's a bit weird :s
 
It was actually (I kicked it off again overnight so have only just checked the time)

This was a 76GB disk reduced to 32GB.

Original retaining disk sizes took 1 hour 46 minutes. The one changing the disk size took 1 hour 4 minutes.

Fairly strange given that you'd expect the 'emtpy space' on the original server to be a fairly quick 'conversion'.
 
jam pie said:
Fairly strange given that you'd expect the 'emtpy space' on the original server to be a fairly quick 'conversion'.
Click to expand...

When you migrate and change the disk size it does a file level copy, if you retain the original size it does a block level copy. At block level it has no idea what is used space and what isn't. Incidentally, when you do a file level copy you get the added bonus of a free 'defrag' as it writes to the disk sequentially.
 
You must log in or register to reply here.
Back
Top Bottom