Solved

Blue screen of death on Virtual Machine after Upgrading VMware Tools

Posted on 2014-09-22
16
1,762 Views
Last Modified: 2014-11-06
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...
0
Comment
Question by:sglee
16 Comments
 

Author Comment

by:sglee
Comment Utility
I do have NAKIVO backup and I can restore this entire VM from the backup.
Can I restore a file or files to current VM folder to make it work instead of restoring the entire VM into Recovery VM?
0
 
LVL 61

Accepted Solution

by:
gheist earned 300 total points
Comment Utility
Better so.

For restored machines
Snapshot
UnInstall tools
poweroff
Snapshot
poweron
Install tools
?
0
 

Author Comment

by:sglee
Comment Utility
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?
0
 
LVL 9

Assisted Solution

by:Zacharia Kurian
Zacharia Kurian earned 100 total points
Comment Utility
could you check if you are using VMXNET 3 (network) for your VMs? Sometime back we had an issue with one of our clients and changing the net work to VMXNET 3 before updating the VMware tools, solved the issue.

By the way, the OS was windows 2008 R2.
0
 

Author Comment

by:sglee
Comment Utility
Zach,

  Under Network Connection, it has "VM Network". Other VMs are also using the same "VM Network".
0
 

Author Comment

by:sglee
Comment Utility
On blue screen, it says "STOP0x0000007B (0xF78A6A98, 0xC0000034, 0x0000000, 0x00000000)
0
 
LVL 61

Expert Comment

by:gheist
Comment Utility
Stop 0x...7B means "boot device inaccessible"
0
 
LVL 117

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE)
Andrew Hancock (VMware vExpert / EE MVE) earned 100 total points
Comment Utility
I would restore your Backup you made before installing VMware Tools.

VMware Tools is not strictly required after an upgrade!
0
Free Gift Card with Acronis Backup Purchase!

Backup any data in any location: local and remote systems, physical and virtual servers, private and public clouds, Macs and PCs, tablets and mobile devices, & more! For limited time only, buy any Acronis backup products and get a FREE Amazon/Best Buy gift card worth up to $200!

 
LVL 61

Assisted Solution

by:gheist
gheist earned 300 total points
Comment Utility
I would speculate it installed some sinister mix of old and new vmware tools. So would be nice to go through uninstall and reinstall checking if machine functions at every step and keeping snapshot for safety (one machine per evening is a good pace)
0
 

Author Comment

by:sglee
Comment Utility
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?
0
 
LVL 61

Assisted Solution

by:gheist
gheist earned 300 total points
Comment Utility
Power off snapshot
Uninstall vm tools
Power off snapshot
Install vm tools
reboot to check
0
 

Author Comment

by:sglee
Comment Utility
Since I could not fix the original VM with "Blue screen of death", I have decided to use "Restored" VM.
0
 
LVL 61

Expert Comment

by:gheist
Comment Utility
Just walk carefully through upgrading VM tools..
0
 

Author Comment

by:sglee
Comment Utility
I will not mess with VM tools anymore unless VM does not function correctly.
0
 
LVL 61

Expert Comment

by:gheist
Comment Utility
There is no mess... You need vmware tools to roughly match host to benefit from DRS aka automated vmotion.
0
 

Author Comment

by:sglee
Comment Utility
I ended up restoring the VM from the backup instead of trying to fix the corrupted VM.
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

When we have a dead host and we lose all connections to the ESXi, and we need to find a way to move all VMs from that dead ESXi host.
Veeam Backup & Replication has added a new integration – Veeam Backup for Microsoft Office 365.  In this blog, we will discuss how you can benefit from Office 365 email backup with the Veeam’s new product and try to shed some light on the needs and …
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
This Micro Tutorial walks you through using a remote console to access a server and install ESXi 5.1. This example is showing remote access and installation using a Dell server. The hypervisor is the very first component of your virtual infrastructu…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now