But my dilemma didn’t stop there. I obviously don’t want to access the internet via the Windows Server 2008 platform. That’s what my Windows XP virtual machine is for. So what I did was to add an Internal virtual network using Hyper-V’s Virtual Network Manager. This will create another network adapter on the host operating system – in this case, Windows Server 2008. I’ve renamed this WiFi-Guest-Bridge. Next, I’ve added a network adapter on the Hyper-V guest and mapped it to this virtual network. Once, I’ve done both of these, I’ve bridged the wireless network adapter and the WiFi-Guest-Bridge network adapter, thereby, providing wireless connectivity to my Hyper-V guest.

Keith Combs provided a step-by-step procedure (with screenshots) on how to configure wireless networking with Hyper-V guests in his blog

It is very important to name your network adapters accordingly as Windows does a real good job of using a generic naming convention (i.e. Local Area Network x) which adds confusion especially if you are dealing with a ton of virtual networks from within a single Hyper-V (or other virtualization) platform

Status: 0x800713de The quorum disk could not be located by the cluster service.

This occurs even if you have created shared disks on a node you wanted to add in a cluster but created it on the same SCSI bus as the disk that holds the operating system. Windows does not allow you to do that since if you are going to failover to the other node, the shared disk should be flexible enough to move. This is a common mistake when trying to create a cluster in a virtualized environment, assigning shared disks on the same SCSI bus as that of the disk that holds the operating system. Check out this blog entry on creating clustered VMs in VMWare Workstation 6. It doesn’t matter whether you are using VMWare, Microsoft Virtual Server or Hyper-V; if you don’t take note of this, you’ll end up spending a lot of time troubleshooting a very simple configuration issue