My Fried Tech! - Virtual Server

Clustered Hyper-V showing 'Saved-Critical' and failing to restore virtual machine state

papabear — Tue, 30 Mar 2010 15:46:33 GMT

I rebooted my clustered Hyper-V server. When I logged back on a test Virtual Server was showing a 'Saved-Critical' state. Attempting to start it resulted in the error message 'failed to restore virtual machine state'.

The issue? I had not made the VM clustered, so it was trying to launch the server without having access to the drive where the VM was stored. DOH!!!

Roll it back and start it, no problemo....

Hyper-V, Windows 2008 R2, and 'MyVM' could not initialize error

papabear — Thu, 29 Oct 2009 15:18:14 GMT

There appears to be an issue with w08r2 when it comes to using Hyper-V. When attempting to launch your VM you might encounter the error: The application encountered an error while attempting to change the state of %yourVM%.

The solution seems very simple (thanks to this post) which is that you need to give 'Authenticated Users' the 'List folder / read data' permission at the root of the drive that contains the Virtual Machines (and you ONLY need to do it at that level, not the ones below).

Why this solves the problem I do not know, but here are the steps (with some pictures) to walk you through the process:

1 - Open up the root of the drive's properties and choose the Security tab. Click on the Advanced button

2. Click on 'Change Permissions'

3. Click on 'Add', Type in 'Authenticated Users' and hit the OK button, you should see the screen below. Change the "Apply to:" to be "This folder only" and put a check in to the "List folder / read data" check box. Click 'OK'

4. Make sure NOT to check the 'Replace all child objects...' checkbox. Check your settings, and click OK. Click OK to close the Properties screen for the drive and you should be good to go.

The Web Proxy filter failed to bind its socket to .... or why you can't have Virtual Server & ISA 2006 on the same box

papabear — Sun, 26 Apr 2009 19:29:53 GMT

I installed ISA 2006 on a new firewall box. Or rather reinstalled, since I had stuck the trial version on because I NEEDED IT UP NOW!!!!!!!!!!!!!!

Of course I had stuck on the trial version and then let it expire so our website was suddenly unavailable. My cohort Patrick spent many frurstrating hours trying to get SOMEONE at MSoft to give us a license key so we could reactivate it.

Meanwhile....

I downloaded the MSoft Virtual Server for Windows 2003 R2, whipped it on the box, installed the trial version of ISA 2006 (AGAIN), and got it up and running.

Don't try this at home. I mean you, Lee.

Anyway, that was dandy and finally, much later, Patrick finally got ahold of someone who let him know that the license key was already in the product that we download via EA.

Ahhhhh

So today I decide to install ISA 2006 for real, and shut down the Virtual Server. I do so, and discover that I no longer have a site. My web server is groovy, but my firewall is throwing hissy fits. Egads, horror in the land.

So I restart the Virtual server, shutting down the ISA 2006, and now IT does not work. Shut down the Virtual Server and try again with the real thing.

hmmm

A wee bit o troubleshooting later I figure out that the network cable is bad (although it DID appear to work on the screen, it just couldn't GET anywhere).

Problem one solved.

Now I reboot it (why not) and see the error above. Thank the heavens for Google - turns out that ISA 2006 refuses to run if you have IIS installed. Virtual Server (for administration) requires IIS to be installed. Hence the bloody battle.

Deinstall Virtual Server. Deinstall IIS.

*boom*

it is working and I am going home!