upgraded vmware player osx wont boot anymore

I'm confused because all of these VM's were deployed from the same template and are running the same patches, software, etc, and they have the exact same VM settings and configurations. When I power it down and move it back to Cluster 1, it boots up fine. I tried powering off and moving the VM to all other hosts in Cluster 2, but it continues to have the same issues. It gets passed the BIOS (and I can boot to BIOS fine), then the console screen just freezes on a black screen with a cursor. It powers on without errors, but the OS never boots. Task: Cold migrate 6 x RHEL 5.7 VM's from Cluster 1 to Cluster 2. Of course I will provide the answer everywhere if I find one.īREAKTHROUGH: I got the system to boot with with the resized HD.Cluster 1: 5 x ESXi 5.0 - Update 2 hosts, HP BL685c G7's (AMD Gen 3 - EVC enabled AMD Gen 3 No 3DNOW)Ĭluster 2: 5 x ESXi 5.1 - Update 1 hosts, HP BL685c G7's (AMD Gen 4 EVC enabled AMD Gen 3 No 3DNOW) The weird thing is: When I boot the system with Debian Live afterwards, and check the partition with gparted, I see that the NTFS partition fills the whole 500GB, even though I didn't increase it yet with a partition manager.Īny ideas what I could do differently to increase the partition 'safely'?ĭisclaimer: I posted this question in the vmware Forum and serverfault as well. When I resize the disk I just set the value to 500 in the window shown below: I tried fixmbr, fixboot and boogcfg /rebuild in the recovery console, but nothing works. However when I do so, the machine doesn't boot anymore ('Error loading operating system'). I want to increase the size of the disk from 275GB to 500GB.

The problem is, that the legacy application on that machine is running out of disk space.

The image used to be a VMWare Player instance, but I converted it to a vmdk. I have a Windows 2003 R2 legacy installation on a ESXi 6.5 VM.

Upgraded vmware player osx wont boot anymore