Error when starting a VM in Hyper-V 2012

Quick post!
Got an error after I’ve upgraded my servers from 2008 R2 to 2012 and I wanted to boot my VM’s.
In the event viewer I got this error message Hypervisor launch failed; Secure Mode Extensions have been enabled by the BIOS. Please disable Secure Mode Extensions in the BIOS to launch Hyper-V.
I the hyper-v manager I got the message:

Virtual machine ‘VM_Name’ could not be started because the hypervisor is not running (Virtual machine ID <Virtual_Machine_ID>). The following actions may help you resolve the problem:

1. Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.
2. Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer. (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on. Resetting the physical computer is not sufficient.)
3. If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.

This was a bit odd since it was working for 2008 R2, so I tried the basics.

First I ran systeminfo and saw under Hyper-V requirements to see that it was fully supported.

Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes

I ran the command bcdedit /set hypervisorlaunchtype auto
Since it stated that the Hypervisor was not running.

Tried a reboot, but still nothing happened.
In my case it was because I had an old BIOS driver on my server so when I updated my BIOS everything started working again , so remember to check that you have the latest BIOS driver, that is always a good best practice

#hyper-v-2012, #windows-server-2012

Windows Server 2012 Hyper-V and Vsphere 5.1

A lot of fuzz is going on regarding virtualization these days, and the primary topic is Hyper-V vs VMware vSphere.
And of course there going to be some arguments regarding which one is better, and which of them has the more features and who is the most enterprise ready so on and so forth.
Just last week VMware released version 5.1 of vSphere which included some new functionality and improvements in  scalability, and Windows Server 2012 was released the 4th of September. So therefore like many before me I’m going to compare the two of them. I have read many blogs lately where people claim that one of the products are better then the other, and a lot of them compare features in the wrong way (For instance if Product 1 has feature 1 and Product 2 has feature 2 even thou they do the same the use different names and therefore aren’t compared). I’m not here to write down a conclusion of which one is better, I’m just going to lay down the facts so you can decide what you think is the better option.  And I’m not going to debate vCenter and System Center comparison, because that is another different story

Windows and virtualization:
Microsoft first came out with its hyper-v virtualization platform in 2008 (With Windows Server 2008) Before that Microsoft has a product which was named Virtual Server, many people claim that Microsoft is pretty fresh in the server virtualization marked but actually Microsoft has been in the marked since 2004 (When the first release of Virtual Server was released) But was again later superseded by Hyper-V. Now the latest version of Hyper is called V 3.0 comes with Windows Server 2012.
You also have the free version of Hyper-V which is called Hyper-V server 2012. http://www.microsoft.com/en-us/server-cloud/hyper-v-server/ (This product only contains the hypervisor, Windows Server driver model, virtualization capabilities, and supporting components such as failover clustering but does not contain the rest of the features and roles in Windows Server. Therefore you get a small footprint on the host. But other then that the versions of Server 2012 that contains Hyper-V is Windows Server 2012 Standard and Windows Server 2012 Datacenter.
The difference licensing between the two is the following.

Standard edition = allows you to run 2 virtual machines $882 for a 2 physical CPU server
Datacenter edition = allows you to run unlimited virtual machines $4,809 for a 2 physical CPU server

Some examples;
1 server: 2 CPU and 4 virtual machines = You could either have 2 standard edition licenses or 1 datacenter edition license
1 server: 6 CPU and 8 virtual machines= You could either have 4 standard edition licensers or 3 datacenter edition licenses.
And in both scenarios you wouldn’t need a license for the VM because the license is for physical hosts!

In Windows Server 2012 Hyper-V 3.0 Windows has the following workloads and the following features.

Host max
Logical processors on hardware 320
Physical memory  4 TB
Virtual processors per host 2,048

Virtual machine max
Virtual processors per virtual machine 64
Memory per virtual machine  1 TB
Active virtual machines per server 1,024

Cluster max
Nodes 32
Virtual machines 4,000

Network
Quality of Service (QoS)
SR-IOV
Network Virtualization (Using GRE or IP rewrite) Link to the IEEE draft = http://tools.ietf.org/html/draft-sridharan-virtualization-nvgre-00
PVLAN support
Dynamic Virtual Machine Queue (D-VMQ) (allows the host’s network adapter to pass DMA packets directly into individual virtual machine memory stacks)
Receive Side Scaling (RSS spreads monitoring interrupts over multiple processors, so a single processor isn’t required to handle all I/O interrupts,)
Receive Segment Coalescing (RSC improves the scalability of the servers by reducing the overhead for processing a large amount of network I/O traffic.)
DHCP Guard (DHCP guard drops server messages from unauthorized virtual machines that are acting as DHCP servers.)
Router Guard (Router guard drops router advertisement and redirection messages from unauthorized virtual machines that are acting as routers.)
Port mirroring (not promiscuous mode, does a forward of all the packet to a VM to another destination)
Virtual Port ACLs
Trunk mode using 802.1q
IPsec Task offload
Integrated Network Adapter Teaming
Hyper-V Extensible Switch
Data Center Bridging (DCB)
Resource metering (Measure usage of CPU, Memory, Network and disk for a virtual machine)
NIC Teaming (Allows for LACP in the native OS, before this needed to be done by a third party product like Broadcom)

Management
PowerShell
SCVMM 2012 SP1 (You can use CTP release for Windows Server 2012 but official support comes with Service Pack 1 which is in Beta now)
Server Manager
Cluster Manager
Hyper-V Manager
Cluster Aware updating
IPAM

Storage
New Virtual Disk format (VHDX supports up to 64 TB Virtual Disks)
Offloaded Data Transfer – ODX (Is a feature of a SAN, allows the file transfer/copying between hosts on the SAN to be done by the SAN instead of the regular network transfer)
Live merging of VHDs and Snapshots
RDMA (IS a direct memory access from the memory of one computer into another without involving either’s OS.
SMB 3.0 (Allows to use regular network fileservers instead of expensive SAN solution)
Native 4 KB sector disks support (But for compability sake it allows for an 512-byte emulation called 512e )
Data De-duplication
Virtual Fibre Channel inside the Virtual Machines
VM boot from SAN
Storage Spaces (Software like RAID solution)
New File system ReFS (Luckily most of the system filters which a written for NTFS will work for ReFS, and it has improvements to resilience, reliability)
Bitlocker on CSV (Allows you to encrypt an CSV volume)
SMI-S (Is a storage standard by the SNIA which allows for management functions via HTTP)
Encrypt VHD files with Bitlocker Network Boot(Gives you an ability to encrypt an VHD file, so if it reboot it will contact a wds server and get the decryption keys and continue to boot)

Migration
Improved Live Migration
Unlimited Simultaneous live migrations
Live Storage Migration
Shared-Nothing Live Migration
Hyper-V Replica
Failover Prioritization

VMware and virtualization:
VMware started its life with VMware workstation which was released in 1999 (Yes its really that old!) And has since then been living on virtualization technology, the first release of vSphere came in 2001. They have also created an VDI product called VMware View, and in 2010 they acquired the open-source groupware solution Zimbra from Yahoo.  So they are expanding their horizon when relating to software products but their primary focus has always been virtualization. Now last week (
VMware released their newest version of vSphere, version 5.1 http://www.vmware.com/files/pdf/products/vsphere/vmware-what-is-new-vsphere51.pdf and VMware has also just recently killed of the vRAM memory tax, in order to compete with Windows.

VMware pricing and editions:

VMware vSphere 5.1 is licensed on a per- physical processor basis

Standard edition = $1144 (Is a bit more stripped version of the hypervisor)
Enterprise edition = $3308 (Is also a bit stripped version of the full version)
Enterprise plus edition = $4024 (Contains all of the features and has the full workload)
NOTE:These prices are fetched from VMware’s site which is usually listed as EURO not US$

Some examples;
1 Server = 1 CPU 4 Virtual Machines (IF you want all the features you need 1 Enterprise plus licenses)
1 Server = 2 CPU 4 Virtual Machines (IF you want all the features you need 2 Enterprise plus licenses)
So in both cases you would need a WS2012 Datacenter License in addition to the Vmware license (IF you wish to use Windows Server 2012 VM’s on that host)

VMware and vSphere 5.1 has the following workloads and the following features.(Enterprice plus edition)

Host max
Logical processors on hardware 256
Physical memory  2TB
Virtual CPU per host 2,048

Virtual machine max
Virtual processors per virtual machine 64
Memory per virtual machine  1 TB
Active virtual machines per server 1,024

Network
Netflow 10 (IPFIX)
Port Mirroring (RSPAN and ERSPAN)
LLDP
QOS (Network I/O)
SRV-IO
VXLAN
PVLAN
DCB (Data Center Bridging) refers to a set of enhancements to Ethernet local area networks for use in data center environments.
Receive Side Scaling (RSS spreads monitoring interrupts over multiple processors, so a single processor isn’t required to handle all I/O interrupts,)
TCP Segment Offload
Distributed Virtual Switch
LACP (Link Aggregation Control Protocol)

Management
vSphere webclient
Powershell via PowerCLI
vCenter
vCloud
SCVMM (Eventually will come with support, with SP1 you have support for up to vSphere 5.0)

Storage
vMotion enchancements ( similar to shared-nothing live migration)
Boot from Software FCoE
16Gb HBA Support
iSCSI jumbo frames
SSD Monitoring
VMFS-5 enchancements

So there is  a lot happening in both camps nowadays.
For higher workloads Windows seems to be the good option ,and you don’t think that anyone is actually going to max out those numbers? I’ve actually spoken to a service provider in the US which was a bit annoyed with the max VM per cluster since each server can hold 1,024 virtual machines and in a cluster with 32 nodes you can “only” have 4,000 virtual machines.  But another question, how is the performance ? There is no use having a 150HK engine if another car with 110HK can go right past you.
VMware actually has a performance document stating that each VM was performing about 18,9% on VMware 5. (This document is 2008R2 Hyper-v vs. VMware) http://www.vmware.com/files/pdf/products/vsphere/VMware-vSphere-vs-Hyper-V.pdf
Again this is for the old version, it is going to be interesting too see how the performance is going to impact with WS2012.

Microsoft is working hard these days with SP1 for System Center, since for enterprise deployment you are going to need SCVMM (Since full support for Server 2012 comes with SP1). VMware already has the management solution for its new hypervisor available so Microsoft better hurry up
And Microsoft is also working with Service Provider foundation. For hosters that wish to deliver IaaS this is going to be big news! V1 of this is going to be avaliable with SP1 for System Center, if you don’t want to use this
Citrix has a Control Panel solution which integrates to SCVMM to deliver IaaS, Paas & SaaS called Cloudportal Services Manager (which does not use the Service Provieder Foundation API)
ExtendASP which also is a control panel solution for hosters have full support for Windows Server 2012, so it allows for hosters to easy deploy solutions for their customers.
VMware already has their IaaS solution in place with vCloud director so its going to be interesting to see how they compete in functionality and features.

Links:
(VMware comparison set of Hyper-V VS VMware) http://www.vmware.com/files/pdf/getthefacts/vmw-vSphere-5-vs-Hyper-V-3-Beta.pdf
(Microsoft comparison set of Hyper-V VS VMware)http://download.microsoft.com/download/5/A/0/5A0AAE2E-EB20-4E20-829D-131A768717D2/Competitive%20Advantages%20of%20Windows%20Server%202012%20RC%20Hyper-V%20over%20VMware%20vSphere%205%200%20V1%200.pdf
Vmware vSphere 5.1 http://www.vmware.com/pdf/vsphere5/r51/vsphere-51-configuration-maximums.pdf 
What’s new in vSphere 5.1 Networking http://blogs.vmware.com/vsphere/2012/09/whats-new-in-vsphere-5-1-networking.html
What’s new in vsPhere 5.1 Storage http://www.vmware.com/files/pdf/techpaper/Whats-New-VMware-vSphere-51-Storage-Technical-Whitepaper.pdf
http://www.vmware.com/files/pdf/techpaper/Whats-New-VMware-vSphere-51-Performance-Technical-Whitepaper.pdf

#hyper-v-2012, #vmware, #vsphere-5-1, #windows-server-2012

Hyper-V 2012 and BSOD with WLAN

 

Hyper-v 2012 and BSOD with WLAN
so lately I have had some strange issues with my Hyper-V Server (Running Server 2012) and this server is connected to my intranet using WLAN. Why you ask? Because in 2012 WLAN is supported and it is the only way I can connect my server to the network without using EoP.
I am using the wireless adapter as a bridge adapter to my virtual interfaces. So all my virtual machines connect to the internet using the wireless adapter.

So at random times my server got a BSOD.
With the regular DRIVER_IRQL_NOT_LESS_OR_EQUAL error message. (Not like the picture shown above)
I started looking at the normal places, is something wrong with a driver? I haven’t installed anything recently and it has been working fine for a couple of months so I couldn’t be that. Could It be that Windows update has updated a driver and didn’t notify me? According to the event log of the drivers that was a no to.
Next I checked my memory modules they also have a tendency to create BSOD. No faults there either, and the BSOD was happening at random times. So troubleshooting 101, what did you change before the first BSOD? I added my WLAN as a connection to the virtual switch, so I removed the wireless adapter from the server and no BSOD. So now I am one step closer and I found out what was creating the BSOD, I tried updating the drivers for the wireless adapter but there were no new drivers available.
So therefore I needed to resort to debugging the memory dump using WinDbg. (You can find the memory dump from c:\windows\memory.dmp

First I added the symbol path from Microsoft online,
SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
(if you do this after you open the memory dump do a .reload )

Looks like the sinner here is bridge.sys, but what is that?
Hyper-v creates a bridge between your virtual interface (virtual switch) and your physical interface when you choose “Allow management operating system to share this network adapter” and this bridge (You can see it under network adapters) is the source of the problems.
So by choosing this option the parent host can still be online using the same physical interface as the virtual hosts use.
I know there are a lot of features which are not supported using a wireless connection, but since Microsoft says WLAN are supported in 2012 it better work in time for the RTM.
FYI: The only way I found out so far to fix this was to remove the “Allow management Operating system to share this network adapter” This disables the bridge and I haven’t had any BSOD after that.

#hyper-v-2012, #wlan-bridge