Thursday, February 4, 2010

VMWare and Windows 7

Trials and tribulations of a software developer. It's somewhat difficult to get your tasks done when you are interrupted by the evil BSOD [Blue Screen Of Death].

A few days ago, out of the blue (no pun intended), the BSOD turned it's ugly head to my new Windows 7 machine, and said to my machine, "I eat PCs like you for breakfast." Omm nomm nomm. So the machine restarts and I go on with life as if nothing happened. So about a week later, the BSOD appeared again. So, as before I just let the machine come back up and I was able to go on with my work. Well yesterday, after I got back from lunch, it happened again...not just once, not just twice; but, THREE times! I talked with one of the IT guys and they modified a setting on my Windows 7 host machine, in which it would put the computer to sleep after 30 minutes of inactivity. So finally at the end of the day (after the last BSOD, mind you) I decided to call it quits and start fresh tomorrow.

Today is the day, I'm going to start up my machine, I'm going to get my virtual machines running and BAM! I'm gonna get that BSOD and we're gonna call Dell and get this PC issue fixed. Hell no! BSOD didn't want to come out and play. This morning was somewhat productive. I was able to reproduce an odd bug from yesterday morning and got a solution figured out. But, I realized that "it's noon, it's time for lunch!" I lock my computer with my VMs running as I always do and I go to lunch. About an hour later I come back and I noticed that my Windows 7 VM decided to go into standby mode and now I need to resume my VM state. I get it up and running, and get an IM from another co-worker with a link. So, I figure while I have a minute, I'll check out this link; and then, BAM! that BSOD does want to play!

By this point I'm just done, I've had enough. I get the IT guy to ever so kindly listen to my ramblings of why this is jacked up and I explained my steps to reproduce the issue. In my event viewer, I'm getting this error at the point of the BSOD in which I get a critical error from "Microsoft Windows Kernel Power". The IT dude thought that maybe it's the outlet I'm in because we have such freak power incidents; so, I shut down my machine and we plug into an outlet that's on a different wall. I start that puppy up, resume my VM and that annoying blue with the hideous white font stares me straight in the face.

It turns out that my Windows 7 VM was going into "sleep" mode, and the act of resuming that VM state, was causing all of the issues. So we updated the Windows 7 power settings in the VM to "Never" put the machine to sleep. So far, *knock on wood* I have not run into any issues.