Archive for the ‘Hyper-V 3’ Category

BSOD STOP0x000000d1 bridge.sys Windows 8 Hyper-V

July 23, 2013

I’m running Windows 8 with the Hyper-V Role enabled on my LAB-top.
To connect my VMs to the outside world, i have created two Hyper-V Virtual Switches; one connected to my WiFi adapter, and one connected to the Onboard NIC.
Both connections are bridged, using the “Allow Management operating system to share this network adapter” setting, allowing the Host OS (Windows 8) to also use these interfaces.
This worked fine for me the last couple of months, but today i got a BSOD. ūüė¶
After starting the Crash Analyzer tool, which is part of DaRT (Diagnostics and Recovery Toolset), the cause of the BSOD appeared to be the bridge.sys driver.


This is the driver that provides the functionality for the network bridging that is done when you enable the “Allow the management OS to share this network adapter” in hyper-v.
It seems I’m not the only one that experienced this issue; Marius Sandbu and Henk hoogendoorn also encountered this, and have provided some workarounds (disable bridging on the WiFi nic)

For now, i will continue using the bridging, unless i get more BSODs…

For what it’s worth; i have been running this setup for 3 months now, and i have used the bridging over WiFi and the onboard NIC quite extensively, but have never had any problems with it.

So my question is; why did this start now? Updates? Patches?


Built-in Windows Server Backup of Server 2012 Hyper-V does NOT backup VMs on CSV

April 15, 2013

This was not entirely clear to me, to say the least.
It seemed that the native Windows Server Backup feature in Windows Server 2012 had added support to backup Hyper-V VMs running on the local machine. But alas, this is not the case when these VMs are stored on a CSV volume.
See this table on the article about Windows Server Backup in Server 2012 on technet:

Support for backup of Cluster Shared Volumes (CSVs) :
Limited support for backing up CSVs as follows:

  1. Virtual machines hosted on CSV’s cannot be added as part of backup configuration
  2. – Windows Server Backup has to be configured on all nodes to ensure that backup and recovery will be available in the event of a failure on one of
    the nodes in the cluster.
  3.  РVolumes recovery not supported
  4. – Security access control lists are not applicable on CSV file service root. Therefore, file recovery to the root of CSV volume is not supported

And indeed, when trying to backup a VM running on a CSV on my Windows Server 2012 machine, i got these errors:

Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: 67FF0C4A-E91B-442D-840A-65257B465E45
Caption     : Backup Using Child Partition Snapshot\vm-dc01
Logical Path:
Error           : 80780175
Error Message   : Component was skipped from volume shadow copy.

Detailed Error  : 80780189
Detailed Error Message : Windows Backup cannot backup an application with files on a CSV volume.

So, no dice



So, no dice…

“Shared-Nothing” migration in Server 2012 Beta. The Logon attempt failed (0x8009030C)

May 4, 2012

Virtual Machine Live Migration in Server 8 Beta has been enhanced with some nice features, one of them being the so-called “Shared Nothing Live migration

Basically this means that the datafiles of the VM you want to Migrate, no longer neeed to reside on shared storage.

Also, the Hyper-V hosts you want to move the VM between, do not have to be in the same cluster.

Beware though, that the Hype-V Hosts DO have to be in the same Active Directory domain. This will NOT work in a workgroup scenario!

I am NOT going to show you how to do this, there are enough nice blogposts about this already (1 and2 )

I got a nice error today i want to share with you, because i couldn’t find anything about it.

When trying to kickoff a LiveMigration from one Server 8 Beta host to another i (sometimes) got the following error:

The Virtual Machine Service faield to authenticate the connection for a Virtual Machine migration at the source host: The Logon attempt failed (0x8009030C)

So, first question; did i set up the authentication correcly then?

Nothing special here, using Kerberos for authentication, and of course configured the Hyper-V hosts in AD for Constrained Delegation


Both Hyper-V hosts were able to properly reach the Domain Controller, and eachother.

Weird thing is, sometimes it WOULD work. By the way, changing to CredSSP didn’t help either.



After some testing it turned out that the problem only occured when i start a Live Migration on another host then the one i am running the Hyper-V Management console on.

Wait, whut?

– On Host 1, i log on locally and start the Hyper-V Management Console.

– I select a VM running on the local host and am able to properly move this to Host 2.

The VM is now running on Host 2.

– Then, in the Hyper-V Management Console, i add Host 2 to the console. (still running on Host 1)

– I then try to migrate the VM back to Host 1. This fails, with the error about logon.


So, when trying to move a VM to another Server 8 Beta host, execute this action on the Local Hyper-V Host.

As we already read here, it is also not a good plan at this time to start a live migration from your workstation. For now, just use the local server.

Server App-V 2012 – a (very short) testdrive on Server 2012 Beta.

April 23, 2012

With the System Center 2012 “Cloud-based” approach, focusing on easily deploying multiple VM’s (both Servers and Workstations), a new feature has been added that makes it even easier to get an ApplicationServer quickly up-and-running.
Server Application Virtualization, or Server App-V , or SAV.
The latter not to be confused with Symantec Anti Virus ūüôā
So in my testlab based on Server 2012 Beta, Hyper-V, and System Center 2012 SP1 CTP, I was ready to go and build me some packages.
First, we have to install the App-V Sequencing Agent on a clean server, to start packaging.
Of course, I did this on a freshly deployed Windows Server 2012 Beta VM.
Only to get this message:

Okay, I know that the prereqs page states that only Windows Server 2003, 2008, 2008 R2 are supported, but I was hoping that this was outdated, with the CTP of SP1 for SC2012.
So, no dice.
Ah well, lets fire up a good ol’ Server 2008 R2 VM then. :p

What is NOT supported in the SCVMM 2012 SP1 CTP version?

April 16, 2012

After reading this 65-page documentation for the CTP of SP1 for SC2012 i was a little disappointed.

A lot of things are not supported in this release, amongst them:
– installing the VMM Selfservice Portal
Yep. I tried it, but got a LOT of funky errors. Mainly to do with IIS not liking some multiple configuration settings in the web.config.

VMM user roles, anything except the Administrator role is not supported

Perimeter network based hosts. All computers must be in the same AD.

Hmm, but this seemed to work quite well. Just remember that when you¬†install the VMM agent software on the Hyper-V host,¬†you should¬†choose for the SCVMM server to contact the Hyper-V host BY NAME, and not by IP Address. Otherwise you’ll get nasty certificate based errors when you want to connect to a VM on it.

Apparantly the choice for hostname- or ip based connection is written to the Securityfile.txt which is then used to import the host into SCVMM.

When you select IP based, the certificate used to connect to the console of the VM won’t match with the issuer. Bummer. When re-installing the SCVMM agent and choosing the hostname option, all works fine.

– ALL servers, need to run Windows Server 8 Beta.

All? Well, the hyper-v host, the guest VMs, the vmm library server, the vmm management server, even the VMM console must run on it. Only exception is the vmm database server, this can be a 2008 r2 server.  No, Windows 8 Consumer Preview is also not supported.

Well, this makes this CTP really a ” Windows Server 8- only” ¬†release.

To be continued.. ūüôā

Setting up a Server 8 ‚Äď System Center 2012 testenvironment‚Ķ on a laptop ‚Äď Part 3: Hyper-V

April 16, 2012

Now that we have WiFi working, let’s get our Hyper-V on ūüôā

After making sure that Intel-VT is enabled on the BIOS, install the Hyper-V role.

Go to Server Manager, Manage, Add Roles and Features, and select the Hyper-V Role.

Do not choose any adapters to bind to while installing this Role, we’ll do that later.

After rebooting the Role is installed and we can start configuring it.

Now the goal here is to have multiple Virtual Switches, binding to different networks.

I want to be able to easily switch to another network in a running VM, without having to add or remove Network Adapters.

Also, I want to be able to share the WiFi connection of my parent OS (Windows 8 Server Beta) with the VM’s.

As we can read in this article¬†, it was a little tricky for the Server 8 / Hyper-V team to get this stuff working. But they managed, by using the ol’ trusted Network Bridging technique, which people were using already to get WiFi connected to their Server 2008 R2 Hyper-V environments.

So, these are the networks and their Hyper-V virtual Switches I use:

– External Switch – Wifi

Connected to the Intel 6300 WiFi adapter. Provides internet access to the VMs.

– External Switch – Wired

Connected to the Intel 82579LM Gigabit wired adapter. Provides internet access to VMs.

– Internal Switch – SC2012 Demo

No external connections, just for internal InterVM communication.

Basically, all VM’s in this environment will only be attached to the SC2012-Demo switch. This is an Internal Switch, allowing connecting to/between VMs and the host.

I created this ‘vSwitch with the checkbox on for ” Allow management OS to use this Connection”, and after that I assigned the newly created NIC in the parent OS with an IP address in the range i’m using for this environment.

This way I can include the parent OS of the laptop into the SC2012 environment. Hey, I need a Hyper-V host to manage, right?

So this is how it looks in Switch Manager in Hyper-V:

and this is how it looks in Networking Center in the parent OS:

As you can see a Network Bridge has been created that links the WiFi adapter to the Virtual Switch called External Virtual Switch – Wifi.

This will allow my VMs to access the internet when needed.

Setting up a Server 8 ‚Äď System Center 2012 testenvironment‚Ķ on a laptop ‚Äď Part 2- Configuring Server 8

April 16, 2012

Now for running Server 8 Beta on the laptop.

WiFi on Server 8 Beta

Firstly, as this is a mobile workstation, i want to be able to use WiFi in the testenvironment.

Luckily the drivers for the Intel Centrino Ultimate-N 6300 AGN WiFi NIC are already included in Server 8 Beta.

If it would not be included, i’d have a go for a Windows 7 x64 driver to see it that would work. This is what i did for the display driver and it turned out fine.

This is however not enough to use WiFi connections. Being a Server, the WiFi services are not enabled by default. Makes sense right? So, lets enable this first.

So, go to Server Manager, Click Manage, and choose Add Roles and Features

Select “Role-based or Feature-based installation”, Select the local server and click Next.

We’re not going to install a Role now, so click Next to get to the Features list.

Scroll down to the “Wireless LAN Service” and select it.

Click Next and wait for the installation to finish.

This installs the Wireless Autoconfig Service, allowing connecting to WiFi networks.

Now i can connect to the internet, and start with running Windows Update to get available updates for Server 8 Beta, and see if there are some drivers available for the hardware.

Display drivers

Next thing to do is install a display driver for the built-in Intel HD display, so i can get some more features like using an external display for presentation mode. For this i use the Windows 7 X64 driver for Intel GMA HD provided by Dell (Click)

The installer for these drivers requires .NET Framework , and it doesn’t accept the built-in 4.5 version of .NET FW that comes in Server 8.

So I installed the .NET FW 3.5 Feature, which also includes .NET FW 2.0.

Easy, just click the feature, let it install and done. Right?


.NET Hell

As it turns out the source files for this feature are not installed in the local sxs folder,  and it downloads its source files from Windows Update rather then from the local installation files..

So , when it cannot access the Windows Update site, for example when you do not yet have a working internet connection or are behind a corporate firewall, the installation of the feature fails!

That sucks, especially because you don’t get any feedback that an internet connection is required here….

So, off to DISM.exe then:

type “Dism /online /enable-feature /featurename:NetFx3 /All /Source:x:\sources\sxs /LimitAccess”

where x: maps to your Windows Server 8 Beta ISO/DVD and LimitAccess is for telling the installer that there is no internet connection available, so it shouldn’t even try it.

Oh yeah, on my first installation this situation f*cked up the installer store, so this dism.exe method wouldn’t even work anymore. So I reinstalled Server 8 completely . Yes that sucked. ūüė¶

Also, I want to use the Snipping Tool to do some screenshots now and then. For this we have to enable the Desktop Experience feature.

Its a little hidden, within the “User Interfaces and Infrastructures ” item so check this out: