Hi all,

I've got a Generation 2 VM running Windows 2012R2 though SCVMM/Hyper-V 2012R2 (update roll-up 6).

The VM has two disks (C: and D: drive) on separate SCSI controllers, but with both VHDX's in the same folder on the same SMB3 share.

When I run DiskSPD on the C: drive, I get around 10K IOPS and 100MB/s throughput, when I run the same test on the D: drive I get 100K IOPS and 6Gbps throughput. Nothing else is using the SMB3 share to affect the results, and the tests have been run many times with the same result..

Any suggestions as to why that might be?

Many Thanks,

David

hello. i have two hyper-v hosts which are configured identically and from time to time have to move vm's from one to the other (shared nothing live migrations). this works flawlessly except for the fact that the migrations seem to only use 1Gbps of network bandwidth although both hosts have a team of four 1Gbps nic's configured (LACP with Hyper-V Port). On the switch side the teamed ports are also set using LACP. Both servers run Server 2012 R2.

What can be causing this?

I used to have a virtual switch that was bound to my wireless adapter. It was at one point removed, but now I want to re-create it.

But, now Hyper-V throws this error any time I try to bind a virtual switch to my wireless adapter:

Error applying Virtual Switch Properties changes

Failed while adding virtual Ethernet switch connections.

Ethernet port '{Guid}' bind failed: The system cannot find the file specified. (0x80070002).

I've tried uninstalling/re-installing my network adapter. My efforts have had no effect.

We have two Hyper-V clusters in two separate datacenters. These datacenters are connected with a 100 Mbit/s redundant connection. Redundancies is achieved with spanning tree and the two sites share the same private IP range. In both datacenters are two domain controllers in the same domain. We use Hyper-V replica to replicate about 50 VM's to the secondary datacenter. We use the primary datacenter as our production environment and the secondary datacenter as our failover location, backup location and test environment. When everything was working and all the servers were being replicated the bandwidth that was used over the WAN connection was about 10 - 15 Mbit/s. We use http for replication.

After a failure, which was caused by a rebooting Hyper-V host (wrong configured automated update settings) several VM's stopped with their replication. After that incident I could not get the replication working properly. I get timeouts errors and other error messages indicating that there is no connection at that moment. The replication works but not all the time. Replication status are going to warning when more than 20% of the replication cycles are missed. Eventually we even see a status of critical on several VM's. After that we have to resume the replication manually.

I have the feeling that this is caused by the limited amount of bandwidth that is available. I had to do a complete new initial replication for some servers because these servers would no longer resume replication after a manual resume command. Even the resynchronization command did not work, so I had to stop the replication and start again. The problem is that the initial replication uses all the available bandwidth and I have the feeling that there is not enough bandwidth left for the regular replication of the other VM's and that this is causing the timeouts. I am however not sure about this theory. Is it possible that initial replications drain so much bandwidth that regular replications are getting timeouts or is there a mechanism that prevents this. Are there possible other causes of these problems?

below you see the error messages that I frequently get. I get these errors on VM's with a normal replication status as well as VM's with a warning status or a critical status.

Hyper-V could not replicate changes for virtual machine 'XXXXX' because the Replica server refused the connection. This may be because there is a pending replication operation in the Replica server for the same virtual machine which is taking longer than expected or has an existing connection. (Virtual machine ID 33F83E0A-843A-4E83-9CD2-92EC7D3E3FEA)

ID: 32552

Hyper-V suspended replication for virtual machine 'VADC01' due to a non-recoverable failure. (Virtual Machine ID 33F83E0A-843A-4E83-9CD2-92EC7D3E3FEA). Resume replication after correcting the failure.

ID: 32086

Hyper-V could not replicate changes for virtual machine 'XXXXX': The device does not recognize the command. (0x80070016). (Virtual Machine ID 33F83E0A-843A-4E83-9CD2-92EC7D3E3FEA)

ID: 32022

Could not replicate changes for virtual machine 'XXXXX' as the Replica server 'cc-hv11.cc.lan' on port '80' is not reachable. The operation timed out (0x00002EE2). (Virtual Machine ID 308792FF-E1E8-4C15-930B-15506C4BF85D)

ID: 29292

Connection to the Replica server 'computer.domain.lan' timed out while waiting to receive a response for virtual machine XXXXX: The operation timed out(0x00002EE2). The total size of replication data being transferred is 65639 KByte(s). (Virtual Machine ID 5A99E295-7E42-4D9E-8814-9469151C7400)

ID: 29312

Hello, I just upgraded my machine to Windows 10 and now my Hyper-V Manager cannot connect to and manage our Server 2012R2 Hyper-V Hosts. I get the following error.

"An error occurred while attempting to connect to server xxxxx. Check that the Virtual Machine Management service is running and that you are authorized to connect to the server."

I've read in multiple places that Hyper-V Manager in Windows 10 and Server 10 will support managing Server 2012 and 2012R2 hosts. I'm not sure why it's not working though.

Any help would be appreciated.

When I try to restore the 6.4gb recovery image "windows recovery" doesn't recognize it, but it does recognize the recovery location which is in my case is a sd card attached to my "archos 80 cesium" tablet ,and all external drives are recognized

"backup or restor" at control panel can open that same image and extract any files and folders but it doesn't show the "windows directory and its subfolders",

when try to mount that image a massage box popup says "this disk image file is corrupted" . Is there any solution to get it work or at least extract the drivers folder from it,

any help will be greatly appreciated

Scenario

I have a 3 Windows 2012 R2 Hyper-V hosts which is participating in a cluster, all of the virtual machines are hosted on CSV's. We also use Dynamic Memory for most of the servers

We do regular reboots every week for our virtual machines, but we've found that sometimes, a virtual guest will suddenly stop requesting additional memory.  At the time of writing, I have identified 10 machines - on different hosts, and even different clusters which are exhibiting this behaviour.  They're also running OS's ranging from Windows 7 to Windows 2008 R2 and Windows 2012.

I have selected one to demonstrate below.

Here, you can see the virtual machine is configured to use Dynamic Memory

and here, you can see that it's not actually demanding more than the start memory, despite the fact that I've overloaded the servers virtual memory by using MSPAINT.

Workaround

Rebooting the virtual machine does not resolve the issue, but live migrating the virtual machine from the host it is on to another host suddenly allows it to demand more memory.  One can then live-migrate it back to the original host and the problem is no longer there.

Troubleshooting

We have performed the following troubleshooting steps:

• Verified that the Integration Services are up-to-date (currently running 6.3.9600.16384)
• Verified that the virtual server has up-to-date Windows Updates
• Checked the Hyper-V-Worker\Admin event log on the current host - no errors pertaining to this VM.
• Verified that the Hyper-V host has sufficient RAM (currently only using 542 out of 768 GB)
• Checked the System event log on the virtual machine - nothing out of the ordinary to report.
• Verified that all services which start with the word "Hyper-V" on the guest machine is running.

Using the following command, I can easily identify which machines are affected (this command applies to SCVMM only):

Get-SCVirtualMachine | where {$_.DynamicMemoryEnabled -eq $true -and $_.DynamicMemoryDemandMB -eq $_.Memory} | ft Name,HostName,OperatingSystem,Memory,DynamicMemoryDemandMB,DynamicMemoryMinimumMB,DynamicMemoryMaximumMB

I do not know any diagnostic program which can give me more information regarding the memory status of a server - specifically one which can tell me more information about Memory demand, and why it's not working. 

Considering that the problem is resolved when I live migrate the affected machine, it would suggest that the issue is with the host, but as live migrating it back no longer exhibits the issue - that seems to negate that theory.  Additionally, the other 103 virtual machines which run on this host seem to not show this issue.

It's almost as if the machine is being ran with static memory, and Hyper-V doesn't realise it's dynamic, but the moment it's live migrated, it suddenly realises this and enables dynamic memory.

Any thoughts?

This is my first time using the forums and I like to thank you for your help.

First of all I am new to Hyper-V and to PowerShell. I do have an IT background.

I wanted to learn more about both topic and when I found Hyper-V core was free and I did not need to pay for the windows server with Hyper-V, I had to jump in.

Now I am at a standstill.

I have been able to make a VM using PowerShell and set all the parameters that I can understand but I don’t have any way to get into the OS that I am installing on to the VM.

To manage the server I have only windows 7 that seems to not work with Hyper-V R2 or I have windows 10 and this seems to not have any documentation at all. I am not on a domain and am unable connected to the server using the Hyper-V Management tools.  

I have read several articles that I can setup remote management in a workgroup environment with some extra configuring but those instruction are for windows 8 and seem to not work for windows 10.

If you can help me configure windows 10 to allow me to remote into the Hyper-V server and finish installing the OS, I can continues with my little learning project.  

Hello,

I've been struggling with a strange problem. Out client runs an environment with Windows Server 2008R2 running Hyper-V. There are four guests all running Windows 2008. He claimed about poor performance lately. The outcome of checking speed with Iperf from one VM to the other is that the speed is about 500-600 MBit/sec, but it often drops to 2.62 Mbit/sec (quite a jump) for some time. It kind of alternates between the high and low speed with practically no middle ground.

I tried a different NIC (original Broadcom, new Intel) with no difference. I tested with disabled/physically disconnected network. No change. The only difference is when there are people logged in and working, the drops occur more often. Anybody has any idea what could it be/what to check ?

Dear reader,

We sometimes have a problem where our windows 2012 r2 RDS virtual servers, that reside on windows 2012r2 hyper-v hosts, loose their dynamic memory and only have their startup memory left to work with. Users start complaining that things are very slow etc.

If I check several screens (RDS Broker load balancing, hyper-v manager, cluster manager and the vm's task manager) it's clear that the vm only has its startup memory allocated. I'm not sure if this happens instantly or immidiatly after the nightly reboot. To resolve the problem we have to call all users on the vm where it happens and ask them to logoff (if they are even able to), and then we reboot the machine.

I have checked the logs from the machine where the VM resides on and the logs from the vm itself. But I cannot find anything. We also have alot of windows 2008r2 vm's with dynamivc memory, but none of those have ever had this problem.

Searched the internet, but so far it seems we are only.

Can anyone give me a lead to troubleshoot this?

Best regards,

Ruud Boersma

MCITP Enterprise administrator

Hello,

Just wondering how backups should work with a failover cluster running on 2012R2. From what I have read Direct I/O should be used in 2012R2 when running a virtual machine backups instead of redirected access in 2008. I am expecting that when a backup is taken that the VM backed up will access the data from its local ISCSI connection no matter which node the CSV is owned by.

What I am seeing is that if the VM and CSV are on different nodes the disk access is run over the management network connection from the CSV iSCSI owner to the VM owner and then sent to the backup server. This causes a reduced backup speed. The CSV stays in online mode and running Get-ClusterSharedVolumeState shows all volumes in direct access still. We have no 3^rd party hardware VSS providers and this is happening on 2 separate clusters.

What I am trying to figure out is this how it is supposed to work or not? Is anyone able to help me with this? I have spoken to Symantec who now say it is a Microsoft issue but have not confirm this is expected or not.

I apologize in advanced for the upcoming wall of text. I have been working on this issue for almost a week now so I have collected a fair bit of information.

The Situation: I have two Hyper-V servers, both in the same Active Directory domain. There is no clustering or SCVMM, it’s a fairly simple straightforward setup. One of the servers runs all of our VM’s, the other is just a replica destination. Currently there are 9 Virtual Machines on the primary host, of which 7 are currently replicating over to the replica host without an issue.

The Problem: While the existing 7 Virtual Machines are currently replicating without any problem at all, I cannot initiate replication on the other two, or on any newly created virtual machine.

The Errors: Attempting to initiate replication on any VM comes up with the following errors (Only one error per attempt, the last error repeats indefinitely for further attempts):

First Attempt: Hyper-V failed to enable replication for virtual machine ‘Main’: An unexpected error occurred. (0x800300FD). (Virtual Machine ID F12E84F3-A789-4AEA-AAA8-81D64109CD66).

Second Attempt: Hyper-V failed to enable replication for virtual machine ‘Main’: Cannot create a file when that file already exists. (0x800700B7). (Virtual Machine ID F12E84F3-A789-4AEA-AAA8-81D64109CD66).

Subsequent Attempts: Hyper-V failed to enable replication for virtual machine ‘Main’: Operation aborted (0x80004004). (Virtual Machine ID F12E84F3-A789-4AEA-AAA8-81D64109CD66). ‘Main’ failed to perform the operation. The virtual machine is not in a valid state to perform this operation.

If you look on the replica server, you will find that the XML was successfully copied over and directories were made for the Virtual Disks, but no virtual disk files are present. Deleting all the directories and XML files from the failed replication, restarting the hyper-v management service on the replica server and trying again will bring you back to the original Unexpected Error message and the sequence begins again. I suspect it is the Unexpected Error (the first message) that is the root of this problem. The other two messages are ones I have seen before when a piece of a VM already exists on the replica (which it does after the first failed attempt) so those are more or less expected.

I get this sequence of errors attempting to replicate either of the two currently un-replicated VM’s or on any newly created virgin VM. Other than the failure to initiate replication I have had no other problems. I can create new VM’s on either host with no problem, I can Live Migrate VM’s both storage and configuration from one host to the other and back. I have tried both Kerberos and Certificate authentication. And all the currently replicating VM’s are still replicating without an issue.

I have scoured the event logs, however the events listed don’t tell me even so much as a single word more than the error messages themselves, on either the primary or the replica. Any help or direction would be greatly appreciated, thanks in advance.

can you bitlocker a guest? I remember in a recent talk that windows 10 allowed this but I cant find anything on it?

-Nex6

Im having some issues and Supermicro customer support is not being very helpful. Anyone have any thoughts on this.

 Please see below:

Hi

Using Cluster Managements mmc I can see for example VM's operating system type: Windows XP, windows 7. How can I get this information using powershell.

Kind Regards Tomasz

VeasnaYim

I am trying to wrap my head around the configuration of SMB Multichannel on a Hyper-V cluster that is NOT using a SOFS cluster - so, using SMB Multichannel for Live Migration and CSV I/O redirection only.

I am seeing a lot of guidance online that says the possible NICs for SMB Multichannel should be restricted.  On the cluster, I would expect the restriction to only allow the Cluster/CSV and Live Migration networks for SMB Multichannel.  How is this achieved?  Everything that I see on setting a constraint with New-SmbMultichannelConstraint is setting the constraint against an SMB file server.  I do not have one to specify.

Additionally, I am using a converged network configuration, with teamed physical interfaces, a Hyper-V virtual switch, and virtual adapters off of that switch for management, cluster/CSV, and live migration networks.  Are these constraints only set on physical NICs?

Strange, when I run Get-SmbMultichannelConnection on any of my hosts, on the client IP it shows connections coming from the management network (10.1.80.x/24), connecting over to the cluster network (10.1.81.x/24) on other hosts.  The Live Migration network (10.1.82.x/24) appears to be functioning as expected.

Server Name    Selected       Client IP      Server IP
-----------    --------       ---------      ---------
fe80::ecad:... True           10.1.82.15     10.1.82.16
fe80::ecad:... True           10.1.80.15     10.1.81.16

Am I overthinking this?  I just don't want an I/O redirection to occur, with the redirection happening on a management interface that impedes our access to the system.

Media is currently locked by guest - RedHat 7.1 on Windows Server 2012R2 Hyper-V 

About the error, i found an article talinkg about it:

https://bugs.launchpad.net/ubuntu/+bug/1177148

=========================================================================

Tested on the Windows Server 2016 Technical Preview 2 with a Ubuntu 14.10 VM.
The change to Hyper-V worked - the media was successfully removed.

Note: The current udev rules leave the media mounted in the VM, even though the media has been removed.
As a test, modifying the udev DISK_EJECT_REQUEST to:
    ENV{DISK_EJECT_REQUEST}=="?*", RUN+="/usr/bin/eject $devnode", GOTO="cdrom_end"
resulted in the media being unmounted when the .iso is removed from the Hyper-V side.

=========================================================================

Besides that one, provided by the article, any other solution?

Where the hell we can type this information?

in the udev.conf ? there´s only one one file insde the directory, not related...

We are in the process off moving our 2008R2 VM's from the 2008R2 HyperV servers to new Server 2012R2 Hosts.

We shut down the VM's copy the files and VHD's to the new CSV's en import the VM in the Hyperv Manager. Then we make them high available in the Failover Cluster Manager (Configure role - Virtual machine). We mount the integration tools and update the VM to version 6.3.9600.16384

For a specific type of VM (mostly RDS Host servers) we always had Dynamic Memory configured (when they were hosted on de 2008R2 platform), so we are using the same settings on the 2012r2 platform. The memory settings were;

Startup memory: 1024 MB

Minimum memory: 1024 MB

Maximum memory: 12288 MB

These VM's reboot every morning, this is done for specific reasons. But now once in a while (once per week/2 weeks) we notice that the VM's are not using more memory then 1024 MB while the demand is much higher. Rebooting the server helps most of the times, live migrating to another host also helps. In the VM we see that memory usage in the taskmanager is 99-100%, and after the move it immediately starts using more than the minimum configured amount.

Until the failover the memory usage was 1024 MB and it did not get any higher.

This happened several times. Last week we changed the Memory configuration to:

Startup memory : 2048 MB

Minimum memory: 2048 MB

Maximum memory: 12288 MB

But this morning we had a call about the performance of one of the VM's, We saw that it was only using 2 GB memory while the demand was much higher. After live migrating it to another host it started using more memory immediately.

The 2012R2 hosts are not overcommited, there is a lot of memory still available for the VM's. Those VM's never had this problem on the 2008R2 Hyperv platform.

Any idea why this happens?

Peter Camps