How to fix hyper-v cannot be installed a hypervisor is already running

Enable-WindowsOptionalFeature –Online -FeatureName Microsoft-Hyper-V –All -NoRestart The above command installs only the hypervisor but does not install the administration tools, if you want to manage the Hyper-V within the virtual machine you must install RSAT for Hyper-V to do this run the following command: Install-WindowsFeature RSAT-Hyper-V-Tools -IncludeAllSubFeature you want to create a cluster then you need to install the Cluster service, run: Install-WindowsFeature RSAT-Clustering -IncludeAllSubFeature you can install Multipath I/O to enable multiple paths to the storage, if this is your case follow: Install-WindowsFeature Multipath-IO Restart to finalize the virtual machine with the command: Restart-Computer

VMware Workstation and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Workstation.

 VMware Workstation and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Workstation.

This is because the Hyper-V role is installed and this conflicts with VMware Workstation. To disable



Hyper-V from starting the following command can be used:

bcdedit /set hypervisorlaunchtype off

A reboot of of the Windows OS is necessary.



To enable the Hyper-V role again use the following command:

bcdedit /set hypervisorlaunchtype auto

A reboot of of the Windows OS is necessary.

Installing a server role on a server running a Server Core installation

Dism /online /enable-feature /featurename:Microsoft-Hyper-V
Dism /online /enable-feature /featurename:Microsoft-Hyper-V-Management-Clients /all

http://technet.microsoft.com/en-us/library/ee441260(v=ws.10).aspx

Hyper-V Installation Network Settings Reset

Cause

=======
This issue occurred because of the SR-IOV feature enabled in the server's BIOS.

With certain HP hardware/drivers, this causes re-enumeration of the PCI devices when Hyper-V Role is installed.

Solution

========

To resolve the issue, the following steps can be performed:

A. Disable SR-IOV from HP's BIOS:

To disable SR-IOV in the UEFI ROM, complete the following steps:

1. During system boot, press F9 to run the System Utility.

2. Select System Configuration, and then press Enter.

3. Select BIOS/Platform Configuration (RBSU), and then press Enter.

4. Select Advanced Options, and then press Enter.

5. Select Advanced System ROM Options, and then press Enter.

6. Select SR-IOV, and then press Enter.

7. Select Disable, and then press Enter.

8. Press F10 to save.

B. Configure the NIC teaming and all other relevant configuration as required.

C. Install Hyper-V role and reboot.

Following information which might be relate:
DL 380 Gen8 with Windows Server 2012 R2 Hyper-V Role NICS change
http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-DL-SL/DL-380-Gen8-with-Windows-Server-2012-R2-Hyper-V-Role-NICS-change/td-p/6656826#.VYAoyeQw-Uk

Windows Svr 2012,VM failed to be started due to the corruption of the VHD

HP 3PAR StoreServ Storage - HP 3PAR OS 3.1.2 can Improperly Zero Blocks Beyond the Requested Range When Using Windows Server 2012 ODX Commands
http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04236215

Workaround
===========
Disable ODX on the Windows 2012 or Windows 2012 R2 hosts. To disable ODX, type the following:

Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem -Name "FilterSupportedFeaturesMode" -Value 1

A server reboot is required for all servers in which the registry value is modified.

How to get dump of a VM on Hyper-V

How to create a Complete Memory Dump of a running or hanging Virtual Machine (VM) on Windows Server 2012 R2 Hyper-V

http://blogs.msdn.com/b/scstr/archive/2015/01/11/how-to-create-a-complete-memory-dump-of-a-running-or-hanging-virtual-machine-vm-on-windows-server-2012-r2-hyper-v.aspx

Get a kernel dump of a 2012 R2 Hyper-V server with Powershell

http://blogs.msdn.com/b/winsdk/archive/2014/04/17/10442746.aspx

Hyper-v,Linux Integration Services issue

Edit the file /etc/initramfs-tools/modules
and add the line allow us to load the rest of the required modules:
hv_vmbus
hv_storvsc
hv_blkvsc
hv_netvsc
hv_utils

Save the file and run the command:
$ Sudo update-initramfs-u

Put this in /etc/network/interfaces your new synthetic network interface seth0.
If you have used an outdated network interface Legacy, it would be called eth0.
For a static address:
Auto seth0
iface seth0 inet static
address xxxx
netmask xxxx
Gateway xxxx
To get the address for DHCP:
Auto seth0
iface seth0 inet dhcp
I tested both methods of network addressing, they work.
Reboot and see now in the process of such reports that the device associated with vmbus found.

Hyper-V Virtual Machine cannot be displayed or showed as “saved-critical” in Hyper-V Manager.

Problem
========
Hyper-V Virtual Machine cannot be displayed or showed as “saved-critical” in Hyper-V Manager.

Solution
========
1. Delete the DC virtual machine manually as it cannot be shutdown/start from hyper-v manager;
2. Create two virtual machine with original VHD disk for DC and Exchange VM;
3. Boot up the DC and Exchange VM, configure the network adapter with correct IP settings.
4. Verify the exchange service and we can receive/send email normally.

SCOM 2012 agent shows warning for Hyper-v 2012 host for 26004

Symptom

=========

SCOM 2012 agent shows warning for Hyper-v 2012 host 

Cause

=======

Monitors in the Hyper-V 2008 MP Trying to access the event log which doesn't exist in Windows Server 2012

Solution

===========
 Remoove Hyper-V 2008 MP

Or

If you have deployed the Hyper-V 2008 management pack and have a mixture of Hyper-V 2008 and Hyper-V 2012 hosts in your environment, this is a false alarm.

1.In the SCOM Management console navigate to Authoring > Management Pack Objects > Monitors

   

2.Click Scope button at the top of the console, enter ‘Hyper-V’ > View All Targets > Select All > OK

3.In the Look for field enter ‘Connectivity’ > Find

4.For both ‘Port Connectivity’ and ‘Port Disconnectivity’ right click the Monitor > Overrides > Disable the monitor > For a specific object of class

5.You should see your Agent managed Hyper-V hosts, tick the 2012 Hyper-V Hosts > OK

  

6.Back to the Look for field enter ‘mounted drive’ > Find

7.Find the ‘Mounted Drive Read-Only’ monitor > Right click > Overrides > Disable the monitor > For a specific object of class

8.Select your 2012 Hyper-V hosts > OK

Disabled the following monitors for Windows Server 2012 Hyper-V servers

Port Connectivity  Microsoft.Windows.HyperV.2008.VirtualNetwork.PortConnectionMonitor

Port Disconnectivity  Microsoft.Windows.HyperV.2008.VirtualNetwork.PortDisconnectionMonitor

Static MAC Address Microsoft.Windows.HyperV.2008.VirtualNetworkAdapter.InvalidStaticAddressMonitor

Dynamic MAC Address Microsoft.Windows.HyperV.2008.VirtualNetworkAdapter.InvalidDynamicAddressMonitor

Mac Address Microsoft.Windows.HyperV.2008.VirtualNetworkAdapter.MacAddressAvailabilityMonitor