Hi,

according to the official documentation of Microsoft, Hyper-V does not block Sleep and Hibernate on Windows Server 2012 and Windows Server 2012 R2.

From powercfg I get the following output:

The following sleep states are not available on this system:
    Standby (S1)
        The system firmware does not support this standby state.
        An internal system component has disabled this standby state.
                Hypervisor

    Standby (S2)
        The system firmware does not support this standby state.
        An internal system component has disabled this standby state.
                Hypervisor

    Standby (S3)
        An internal system component has disabled this standby state.
                Hypervisor

    Hibernate
        An internal system component has disabled hibernation.
                Hypervisor

    Standby (Connected)
        The hypervisor does not support this standby state.
        The system firmware does not support this standby state.

    Hybrid Sleep
        Standby (S3) is not available.
        Hibernation is not available.
        The hypervisor does not support this standby state.

    Fast Startup
        Hibernation is not available.
I already installed a graphics device driver to prevent the graphics device from blocking Sleep and Hyper-V. So this should not be an issue. 
What can I do to enable Sleep and Hibernate?
Regards,
Daniel

If anyone could assist with this issues I would greatly appreciate it!

The role in the title does not show up under my remote desktop options and therefore I cannot use remoteFX.

User the Remote Desktop Services I only see Broker, Gateway, Licensing, Session Host and Web Access roles

System:

Server 2012r2 Essentials

i7 5820k

GTX780 DX11

Thanks!

Configuring what's surely a common setup...

* server 2012 R2 (host) and DC (root), 192.168.1.2

* hyper-v, server 2012 R2 for SQL Server (probably with AD (could DC failover that way), 192.168.1.3

Should I virtualise the network environment?  The PC has two adapters, just using one for now, we'll look at NiC teaming perhaps later (or for the 2nd virtual server???)

I'm no expert on Hyper-V!

Normally, for separate servers, I could use DHCP on the primary DC and reserve IP's for other servers (as well as other devices (printers etc)).  That's the way I'd like to configure this virtual setup, use reservations in the DHCP server.

If anyone can help on how best to setup the NiC in the Hyper-V instance, it'd be appreciated.  I assume I can create a virtual NiC and then cancel that if it's not best.

Is there a good guide around for this (surely very common) setup scencario?

Cheers,   Duncan.

Hello.

I am trying to troubleshoot some performance issues with an application that utilizes sql server, which runs in a Hyper-V Guest.

I have found that the ram, cpu, disk i/o all appear to be within normal range.
Before troubleshooting the sql end of things, I wanted to make make sure the vm isn't waiting for cpu time.

In Vmware, the metric for this is " CPU Ready". From what I can tell, the equivilant to this for Hyper-V on server 2012 is:

Hyper-V Hypervisor Virtual processor\CPU Wait time per dispatch.

I have fired this up and been monitoring it and found that the average is around 22,000, maximum 41,000.

The problem is, I have no idea if this is a normal or acceptable range. I can't seem to find any further information on actually interpreting this data, as to what is acceptable and what will cause performance issues etc..

Can anyone help enlighten me further on this?

Thanks

Hi guys, 

Server OS: Windows Server 2012 R2

I have a VM Gen2 with following settings: 

I can boot fine from the same .iso from a Gen1 VM so the .iso is bootable. 

I know that the Gen2 VM uses SCSI instead of IDE, but I have no clue regarding how to boot from the .iso..

Any ideas?

Thanks in advance!

Best regards,

Kenny

Enabled                    : True
OperationalStatus          : {NonRecoverableError, ProtocolMismatch}
PrimaryOperationalStatus   : NonRecoverableError
SecondaryOperationalStatus : ProtocolMismatch
StatusDescription          : {Non-Recoverable Error, The protocol version of the component installed in the virtual
                             machine does not match the version expected by the hosting system}
PrimaryStatusDescription   : Non-Recoverable Error
SecondaryStatusDescription : The protocol version of the component installed in the virtual machine does not match the
                             version expected by the hosting system
ComputerName               : SERVER
Name                       : VSS
Id                         : Microsoft:4FE1D1C4-A0F9-48C7-B599-B48D74525AF5\5CED1297-4598-4915-A5FC-AD21BB4D02A4
IsDeleted                  : False
VMId                       : 4fe1d1c4-a0f9-48c7-b599-b48d74525af5
VMName                     : Windows 10 x64 - VM
VMSnapshotId               : 00000000-0000-0000-0000-000000000000
VMSnapshotName             :
Key                        :

Additional detail here: Technet Post

Hello all,

I've searched around looking for an answer to my question, but the only examples I can find online of a VM automatically going into a saved state are cases in which there is a backup program causing the VM to enter that saved state.

My VM seems to be entering a State of Saving randomly in the afternoon while no backups are happening.

Has anyone else experienced this? This is a critical problem as we run IIS and host files and an internal webpage on the VM. The VM does not host Exchange or Active Directory.

I should say, I have Windows Backup running on the Guest OS, which I know is not the best way to back up, and I'm changing my solution to VEEAM, but my backups happen at 3AM.

Any ideas would be greatly appreciated!
I'm running Version 6.1.7601.1754 and only one VM that has Server 2008 R2 on it.

Recently I purchased a new tablet with Windows 10 Pro. I have installed HyperV and deployed my Linux machine as a VM.

I created a virtual switch, "Internal", assigning the following addresses: 192.168.255.1 (for host machine vEthernet), 192.168.255.2 (for the VM). I also set up 192.168.255.1 as a default gateway on VM, and set up NAT using the command:

Net-NetNat -Name LinuxNet -InternalIPInterfaceAddressPrefix 192.168.255.0/24

DNS server for the VM is 8.8.8.8

I have internet from my WiFi as well as LTE card in the tablet.

When I use WiFi connection or Ethernet connection through a dock, everything is fine, VM accesses internet, no problems.

When I use LTE connection, traffic does not go through. Interesting and weird: if I download large files (make LTE broadband device heavily used by a host system), ICMP packets go through and VM receives ICMP replies (with a big packet loss).

Any ideas?

Hello Team,

Hyper-V VM's are performing too slow which are hosted on Brand new HP Server (HPE ProLiant ML350 Gen9 Server) with OS Windows server 2012 R2 Data Center edition.

Below are the Host server and Hyper-V VM configuration details:-
Host Server:- 
HP Server - Windows Server 2012 R2 Data Center Edi - 64 GB RAM, 2.8 TB HDD.
Hyper-V VM:- Two VM's created. 
First VM - Server 2012 Std Edi. with 4GB RAM and 127 GB HDD. 
Second VM - Windows 10 Enterprise N - 4 GB RAM and 127 GB HDD.

We tried trouble shooting like installing latest windows updates and Ethernet driver updates but no luck. Please advice if there any other way to increase VM's performance.

Regards,

Vishal Suryan

Hi,

I have tried so many different topics and nothing seems to work.
I have a Windows Server 2012 running Hyper-V with currently one desktop only that is essential because we have our shipping program on it (E-Commerce).

When I start the desktop I have a great internet speed with 90/100Mbits but after just a few minutes it drops down to 10/1Mbits and we this causes problem because we can't access our shipping program and print out package labels.

When I first started everything worked fine, I had internet problems at first but solved it by disabling the VMQ and everything was running smooth in 3 months. Until this week...

I tried to adjust the "Jumbo Mtu", Disable "Large Send Offload", Disable "TCP Checksum Offload" and Enabling VMQ and adding a regkey to adjust it.
Nothing seem to work.

I really dont understand why I have great internet response the first 5-10 minutes after I restart the Virtual Desktop either.

Hello All

I need to pick you're brains.  I've recently built a two host 2012 r2 failover cluster.  I get green ticks across the board when running the validation checks.  The plan is to move away from our current fail over cluster and into the newly created one.

Please bear with me, I want to make sure I get all of the details down to help you understand what's going on.

Old fail over cluster 2012.

3x server 2012 r2 remote desktop servers static IP addresses assigned.  Only virtual switch applied against these VM's is the production LAN.

Hyper-v virtual switches setup for production LAN, iSCSI and DMZ.

New fail over cluster 2012 r2

Hyper-v virtual switches setup for production LAN, iSCSI and DMZ.

My process to move the VM's from old to new is as follows:

OLD fail over cluster manager:

Shut down all three VM's.

Offline the disk within fail over cluster manager.

Remove the disk from cluster shared storage.

Remove the disk completely from fail over cluster manager.

New fail over cluster manager:

Connect iSCSI to the san disk, and the necessary steps within disk management to make the disk available.

Attach the disk in fail over cluster.

Bring into cluster shared storage.

Bring the disk online.

Open hyper-v on the host.

Create the VM and point it at the disk with the same name.

Modify the settings for the hardware.

Connect and power on the VM.

This is where things start to happen:

Domain server not connecting to the domain.  I have to log in as local admin.

Network connection is unidentified and set to DHCP.

Set to original static IP it had on old fail over cluster.

Server 1 connects fine and sees the domain network

Server 2 connects fine and sees the domain network.

Server 3 even with its original static IP it doesn't connect to the domain network and keeps displaying unidentified network.

If I move the 3rd VM to the 2nd new host it works.  The domain network connects as normal.  If I fail over the other two VM's which worked on host 1 to host 2 I loose network on vm 3.  If I fail vm's 1 and 2 back to host 1 all 3 vm's have domain network connections again.

Can someone please help me with this as its driving me made.  I cannot see any errors within failover cluster.  I've tried this with both DHCP and static IPs assigned and I get the same symptoms on both attempts.

Have I missed some setting which only allows a set number of VM's on a virtual switch within hyper-v?

Cheers
Dave 

Hello,

We have two 2 node clusters. One in our main office and one in our CoLo office. We are using ArcServe UDP to back up our virtual machines. All the machines in the CoLo office backup fine. However the VM's in our main office will not backup. Whenever we backup the VMs here the VSS writers will fail. We get a timed out error. We have tried many different things and hoping someone here can point us in the right direction.

Our HP 2040 SAN is split across both sites but it is backing in the main office.

Hi,

We have Windows server 2012R2 Data center edition installed on our hyper-v host server. I was under the impression I could install VM using the same disc onto the host server but it's quering the serial number? I thought the license allowed unlimited vm on the host up to basically what the server can host?

Is this correct or am I thinking wrong about the licensing?

If someone can explain be appreciated.

Thanks

Brenden

I have an old checkpoint on a VM, and when trying to remove it, I receive the following error:

Cannot delete checkpoint: Catastrophic failure (0x8000FFFF).

It looks like the .avhdx file is missing for this as it was from quite a while back.  From my understanding of reading some similar stories and technet articles, I should be able to:

Create a new checkpoint, right click it then select Export.  This would create a new single VHDX file.  Would this eliminate this lingering old checkpoint even though the avhdx file no longer exists?

While restoring VMs I receive the following error in event logs:

The chain of virtual hard disks is inaccessible. The process has not been granted access rights to the parent virtual hard disk for the differencing disk.

I am the admin. The machines are messed up. Of course they had checkpoints and of course it was a bad idea (from today's perspective). Now when restoring them I feel like catching all Pokemons from the MSDN error codes list. Please advise how to proceed with this particular one.

Hi,

When I try to start emulator the start task fails, with message like below.

10.08.2015 14:06:01: [Critical] Unable to add user to the Hyper-V Administrators group. Exit code 2220.

I was using it on Windows 8.1 where it worked well on the same PC. This proves that my PC meets all requirements and it is properly configured. After clean install of Windows 10 emulator doesn't work. 

Hyper-V on my PC is running well. I can create and run 32 and 64 bit vm's. There is problem with creating android vm's by vs emulator. There is no group "Hyper-V Administrators" and it can't be created.

Tried these solutions:
http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/09/28/creating-a-hyper-v-administrators-local-group-through-powershell.aspx

http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/01/17/allowing-non-administrators-to-control-hyper-v.aspx

also i tried to recreate InitialStore.xml for Hyper-V with needed group and operations but without success. It seems that hyper-v bundled with windows 10 doesn't require any special group to run, create, manage and remove vm's, switches, etc. Emulator thinks different and it can't assign me to group which does not exists. 

Trying to access Hyper-V running on Server 2012 R2 from Windows 10 LTSB 2016 and I only get an error:

The Hyper-V Management Tools could not access an expected WMI class on computer....

Same server accessed from Windows 8.1 H-V Management Tools is working fine.

Anybody any idea?

According to this it should be no issue

Seb

Recently we've set up a two Windows Server 2012 Datacenter as Hyper-V nodes in a cluster.
The nodes have dual Intel E5-2620 CPU's at 2.00GHz for a totall of 24 logical processors.
Each node has 16 DIMMs of 8GB for a totall of 128GByte RAM. Low voltage DDR3 modules.

Both nodes have a dual port QLogic 3242 convergered ethernet adapters.
The ports are set up using NPAR to each have four virtual NICs, of which both last two are set to a max bandwidth of 9Gbit/s.
There are four teams created over the four vNICs. Management, Virtual Switch for Hyper-V, Live Migration, and iSCSI.
All are set up as Failsafe Teams, meaning only one port is used actively.

iSCSI teams are set up to use a Max Ethernet Frame Size of 9614, and pings to the Netapp SAN respond to a 8000 packet size ping.

The nodes are all very fast and responsive. It is the VM's that I find too slow in several ways.

On of the main things I've bee noticing with Hyper-V so far, and we still have a 2008 R2 cluster from which I am migrating to the new 2012 cluster, is the relative slow performance of the VM's. Sometimes they are slow to respond to a RDP connection, slow response with starting programs.

The most odd thing I have witnessed so far is Quick formatting a virtual hard drive inside a Windows Server 2012 Standard VM.
A 40GByte drive (GPT, NTFS with Default sector size) takes about 5 minutes. Never had that problem on 2008 R2.
Both clusters connect to the same SAN using the same NIC configuration.

It sounds to me like a I/O problem, but I can't figure out why.
For example: When I migrate VM's from the 2008 R2 cluster to the new 2012 cluster (manually, since the Failover Cluster wizard cannot handle VM's created in SCVMM 2008 R2), and then Convert-VHD them to another drive to a VHDX file, it's runs at 1 to 1.4Gbps in both ways. Oddly enough the Move-Item back to the Original location does it in half the speed (which I assume is a bug in Move-Item).

This makes me believe the I/O is just fine for the host, so why is it so damn slow in the VM?
Although when I copy a file from the local hard drive of the host to a hard drive inside the VM, from within the VM, it shows a 1 to 1.6Gbps speed. Totally fine.

Is it just some weird bugs that exist in Hyper-V 2012, and will those be fixed in R2 or is it something else that I am missing?

Hi,

Host: Windows 2012 R2
VM:   Windows 2012 R2
Storage: Direct Attached (Dell PowerVault MD3400)

I have a VM that is used as a productionFile Server.  This has a number of vhdx's (C: OS, D: Data Y: Pagefile and a 10TB Shares disk that is mounted to a folder in D:).

Recently a backup (Altaro) has created a recovery checkpoint and failed (31st August). Consequently the checkpoint file never got deleted and therefore I have a number of avhdx's.  In Hyper-V Manager there is no option to to Delete or Delete the Subtree.  Also there have been no backups since this date as another (inconsequential) VM suffered the same fate and backups just kept creating new recovery checkpoints.

Running Get-VMSnapshot -VMName hstv.artemis gives this.

VMName       Name                                            SnapshotType CreationTime        ParentSnapshotName
------       ----                                            ------------ ------------        ------------------
hstv.artemis hstv.artemis - Backup - (31/08/2016 - 16:39:31) Recovery     31/08/2016 16:41:33

Trying Get-VMSnapshot -VMName hstv.artemis | Remove-VMSnapshot fails with (Cannot delete checkpoint: Catastrophic failure (0x8000FFFF).

My research indicates my only option is to do an offline manual merge (on copies) of the disks to get them all back into single vhdx's.

1. Is this my only option?
2. What would happen to the VM Snapshot files?

Thanks
Tony