sglee
asked on
Blue screen of death on Virtual Machine after Upgrading VMware Tools
Hi,
I upgraded ESXi V4 to V5.1 successfully on Saturday. All virtual machines were running fine except the warning about needing to upgrade VMware tools.
So I ran VMware tools on all VMs (5 Virtual machines) and one of 5 VMs is constantly restarting itself after "blue screen of death". It changes so quick that I can't even read what it says.
I powered it down and tried to restart in SAFE / SAFE with Networking / Last Know Good .. , but to no avail.
Is there any other option to try to salvage this VM?
I hope I can hear from Andrew Hancock...
I upgraded ESXi V4 to V5.1 successfully on Saturday. All virtual machines were running fine except the warning about needing to upgrade VMware tools.
So I ran VMware tools on all VMs (5 Virtual machines) and one of 5 VMs is constantly restarting itself after "blue screen of death". It changes so quick that I can't even read what it says.
I powered it down and tried to restart in SAFE / SAFE with Networking / Last Know Good .. , but to no avail.
Is there any other option to try to salvage this VM?
I hope I can hear from Andrew Hancock...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am currently restoring the virtual machine as of 6pm and that is before I tried to run Vmware tool update.
First, in there a chance that I can get this corrupted vm fixed?
First, in there a chance that I can get this corrupted vm fixed?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Zach,
Under Network Connection, it has "VM Network". Other VMs are also using the same "VM Network".
Under Network Connection, it has "VM Network". Other VMs are also using the same "VM Network".
ASKER
On blue screen, it says "STOP0x0000007B (0xF78A6A98, 0xC0000034, 0x0000000, 0x00000000)
Stop 0x...7B means "boot device inaccessible"
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It just completed "RESTORE", the virtual machine was booted automatically and I logged on to the VM successfully.
It appears that everything is there as of around 9PM last night - Files, and folders, Static TCP/IP Information, Computer NetBIOS name ... etc.
Is there anything that I need to do follow as far as "POST RESTORE" goes?
It appears that everything is there as of around 9PM last night - Files, and folders, Static TCP/IP Information, Computer NetBIOS name ... etc.
Is there anything that I need to do follow as far as "POST RESTORE" goes?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Since I could not fix the original VM with "Blue screen of death", I have decided to use "Restored" VM.
Just walk carefully through upgrading VM tools..
ASKER
I will not mess with VM tools anymore unless VM does not function correctly.
There is no mess... You need vmware tools to roughly match host to benefit from DRS aka automated vmotion.
ASKER
I ended up restoring the VM from the backup instead of trying to fix the corrupted VM.
ASKER
Can I restore a file or files to current VM folder to make it work instead of restoring the entire VM into Recovery VM?