Blue screen after converting from free VMware server to ESX server

Find this post interesting? Do you like interesting things? Maybe you would like my invention, a connectible candle called a WickBrick!

Get one here


I was getting a blue screen after a V2V conversion with inaccessible boot device. So I read all over that you can fix this using the console of the windows xp cd. So I use a copy of undisker and convert a slipstreamed sp2 xp disc into an .iso. Then I try to sftp the .iso over to the ESX server where it runs into a problem during the rename process. I find on the internet that if you use SCP it will work, so I copy it with SCP. Next I had to figure out how to get a VM to boot off of the CD. If you right click on the properties there is a check box to go into the bios on next boot, in the BIOS you can set the boot order. Finally it boots to the recovery console and I’m informed that it can’t find the OS… grr I wonder if I need to F6 and load some driver.. anyways so after all this in order to get it working I just uninstalled the vmware tools first before running the V2V and then it converts, joy. Actually it still failed if I tried to change the disk image size. If I leave the disk image size alone then it works. Who knows, I’m just happy it boots now.


How to screw up an ESX server

In my monday foggy brain state I kept on doing strangely stupid things to test our VMware ESX 3.5 server.  It allowed me to do things that I don’t think it should for example set ip addresses to the same value on different nics, or set the vmotion ipaddress to the same on two ESX servers. A quick check of Ipaddresses across the entire system might be a useful fail safe.