vmware workstation failed to lock the file

I installed VMware Workstation 8 instead of ESXi 5 and managed to get a nested Hyper-VM working. Undeterred, I decided to try something different. No matter what additional information I gave, it just would not work. What I found from the blogs posted above was there were some great pointers, but when I followed either post’s instructions, all I got was a blank Black Screen like a few other people were reporting. Through Twitter, someone sent me a link to a few blogs that helped me start my quest:īy the time I’d gotten a chance to give it a whirl, ESXi had gone GA. I also managed to build a lab with the same architecture that I plan to use on the road for events. So firstly, I went about making sure that when I was due for a new laptop, I would have this Intel architecture, or equivalent AMD, in my system. I’d also heard that ESXi 5 running on Intel Nehalem or Intel Core i7 was going to allow nested hypervisors to also contain running, nested 64bit virtual machines. This post will function as a how-to guide and provide a step-by-step process to run Hyper-V virtual machines on either VMware Workstation 8 or ESXi 5.įor a long time, I was told it was impossible, and a few months ago, I heard a passing rumour that it would be possible when ESXi 5 came out. We would often have a nested ESX server, vCenter, DC and Veeam apps running on a single laptop and I wanted to know if Hyper-V could be thrown into the mix. Veeam has been very successful in presenting its solutions through the use of portable labs running for example on laptops nested under VMware Workstation.

I wanted to know if it could be virtualized running inside a VMware virtual machine of some sorts. As Veeam moves forward and starts to become focused two virtualization platforms, I thought to myself now is the time to work out how I’m going to introduce Microsoft Hyper-V in my lab environment.

Vmware workstation failed to lock the file