PS C:\> Set-VMProcessor -VMName hvm -ExposeVirtualizationExtensions $true

PS C:\> Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart

PS C:\> Get-NetVirtualizationProviderAddress
ProviderAddress  : 192.168.1.2
InterfaceIndex   : 5
PrefixLength     : 24
VlanID           : 0
AddressState     : Preferred
MACAddress       : XXXXXXXXXXXX
ManagedByCluster : False

PS C:\> Get-NetVirtualizationProviderRoute
InterfaceIndex    : 5
DestinationPrefix : 0.0.0.0/0
NextHop           : 192.168.1.1
Metric            : 0

PS C:\> Get-NetVirtualizationCustomerRoute
RoutingDomainID   : {9CC4A292-A1C6-41DF-A4ED-4C78F850E682}
VirtualSubnetID   : 4101
DestinationPrefix : 192.168.46.0/24
NextHop           : 0.0.0.0
Metric            : 255

PS C:\> Get-NetVirtualizationLookupRecord
CustomerAddress : 192.168.46.2
VirtualSubnetID : 4101
MACAddress      : 00155d5d2a02
ProviderAddress : 192.168.1.2
Rule            : TranslationMethodEncap
VMName          :
UseVmMACAddress : False
Type            : Dynamic

CustomerAddress : 0.0.0.0
VirtualSubnetID : 4101
MACAddress      : 00155d5d2a02
ProviderAddress : 192.168.1.2
Rule            : TranslationMethodEncap
VMName          : vm01
UseVmMACAddress : False
Type            : L2Only

CustomerAddress : 0.0.0.0
VirtualSubnetID : 4101
MACAddress      : 00155d5d2a03
ProviderAddress : 192.168.1.2
Rule            : TranslationMethodEncap
VMName          : vm02
UseVmMACAddress : False
Type            : L2Only

VMName SwitchName VirtualSubnetId MacAddress   DhcpGuard RouterGuard
------ ---------- --------------- ----------   --------- -----------
vm01   vs01                     0 00155D5D2A00       Off         Off
vm01   vs01                  4101 00155D5D2A02       Off         Off
vm02   vs01                     0 00155D5D2A01       Off         Off
vm02   vs01                  4101 00155D5D2A03       Off         Off

root@vm01:~# tail -n 4 /etc/dhcp/dhcpd.conf
subnet 192.168.46.0 netmask 255.255.255.0 {
        range 192.168.46.10 192.168.46.50;
        # option routers 192.168.46.1;
}

root@vm01:~# tcpdump -e -n -i eth1
17:20:28.909319 00:15:5d:5d:2a:03 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:15:5d:5d:2a:03, length 300
17:20:28.909603 00:15:5d:5d:2a:02 > 00:15:5d:5d:2a:03, ethertype IPv4 (0x0800), length 342: 192.168.46.2.67 > 192.168.46.10.68: BOOTP/DHCP, Reply, length 300
17:20:30.180282 00:15:5d:5d:2a:03 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:15:5d:5d:2a:03, length 300
17:20:30.180496 00:15:5d:5d:2a:02 > 00:15:5d:5d:2a:03, ethertype IPv4 (0x0800), length 342: 192.168.46.2.67 > 192.168.46.10.68: BOOTP/DHCP, Reply, length 300

root@vm02:~# tcpdump -e -n -i eth1
17:20:28.898397 00:15:5d:5d:2a:03 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:15:5d:5d:2a:03, length 300
17:20:30.185906 00:15:5d:5d:2a:03 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:15:5d:5d:2a:03, length 300

I've got a VM with vTPM and BitLocker enabled using an untrusted guardian.

This VM now won't start, the event log is showing the event:

The computed authentication tag did not match the input authentication tag

I've checked that the VM has a key protector, and that the signed and encrypted certificates match the installed certificates for the untrusted guardian.

If I disable the vTPM I can start the VM and it boots after asking for the bitlocker recovery key.

There are no errors in the HGS Client event log, so I'm not sure what is wrong with this VM.

Any suggestions as to where to start looking?

I have just set up a Hyper-V test lab on my office workstation for the purpose of testing network changes prior to implementation. The lab has a host server running Windows Server 2016 with DHCP, DNS, Windows Deployment Service and Active Directory. There are also 2 clients running Windows 10. Currently the lab is on a Private switch, so there is no risk of its traffic bleeding into my office network. I'm at the point where I need to connect this test lab to the internet, but in a way that there is no risk of introducing its traffic, rogue DHCP servers, DNS explosions or any other assorted goodies onto my office's production network. My workstation hosting this test network is a client on my office network which has a Windows 2012 R2 server also running DHCP, DNS and AD, so there's plenty to go wrong if don't do this properly. I've set my lab on a different subnet, 192.168.10.# vs the office's 192.168.20.#. I'm not sure if this is sufficient, or if there's more that I'm missing. 

I know I'm not the first person to do this, but despite all my searching, I can't seem to find anything that addresses my particular configuration. I'm still new to this, though, so maybe I'm not searching the right terms. Also, if someone knows a good tutorial to point me toward, that would be great too.

Thanks.

I'm connecting from a terminal client, with Windows 10, to a Server 2016 Hyper-V machine. All works well but from time to time I get black spots in the remote desktop session.

I found this article https://serverfault.com/questions/641255/mstsc-black-areas-on-remote-desktop, but that doesn't solve my problem. There are more users connecting to this server and not all are experiencing this problem. 

The strange thing is that it mostly happens in Microsoft Office 2016 applications, like for example Microsoft Outlook. See the screen below.

https://i.stack.imgur.com/ZH1Lh.jpg

By using the GPO, I already enabled the “Disable hardware graphics acceleration” option (article https://support.microsoft.com/en-us/help/2768648/display-issues-in-office-client-applications) and, for the specific users, I’ve recreated the Windows and Outlook account, but this also didn’t help fix the issue. Other steps taken:

1. Disabled the Enhanced Session Mode under the Hyper-V settings
2. Removed the Terminal Server cache
3. Enabled the option “disable hardware acceleration” under Outlook 

The above steps didn’t solve the issue as well. I’m using a host server with Server 2016 with the following specs:

HPE ML350 Gen9
Intel Xeon CPU-E5-2620 V4 2.1GHz
128GB RAM
2x 300GB in RAID 1
5x 900GB in RAID 5

On the host server Hyper-V is installed, with the following virtual servers:

1. Fileserver (domain controller)
2. Mail server
3. Terminal server

All virtual servers contain Server 2016 and the Terminal server uses Office 2016 Standard.

Is this a known issue and is there any way to solve it? The only way to get rid of the black spots is to close the program, and start it again.

I am setting up a new Domain environment. I have installed Hyper V 2019 on a server. I can not remote manage the server with Hyper V management tools, and it looks like it is because I am not in a domain environment. I can RDP to the server with no issues. But when I try to use the Hyper V management utility I get an error. Like i said currently I am in a workgroup environment.

"An error occurred while attempting to connect to a server 10.x.x.x" Check that the Virtual Manage Management service is running and that you are authorized to connect to the server"

I am not even sure how to check to see if the service is running. 

Any help is appreciated.

I've been having a problem for the last several months with my 2012 R2 (and older) VMs running on Windows Server 2016 Hyper-V hosts.

What's been happening is that after a Veeam backup runs, the Windows Update history of the VM is lost.  "Updates were installed" goes to "Never" and "View update history" opens a blank history.  It wouldn't happen immediately after the backup.  The earliest I've seen it is several hours after.  The bigger problem this has been causing is that updates then fail to install at the normally scheduled time and I'd have to do it manually on each VM. 

Recently, KB4072650 was installed on the VMs and it fixed the problem.  KB4072650 is an update for the integration services of down-level VMs hosted on Windows Server 2016.  The VMs that received that update no longer lose their Windows Update history.

The problem is, that KB4072650 is only applicable to Windows Server 2008 R2 and Windows Server 2012 R2 and I still have some "R1" versions of Windows Server 2008 and 2012 in the environment that this problem is happening to.  So, I am looking for a version of KB4072650 for the "R1" releases.

Running ANdroid Emulator on Hyper-V 2016

I am using Windows server 2016 Datacenter with Hyper-V installed. I created windows 10 VM for purpose of providing Android app developement to Developer.

I install Android Studio successfully. But cant able to run Android Emulator. 

If any one has the solution, let me know.

This event (16945) appears on my Windows server 2016 Datacenter. I have Hyper-v on this server and it crashes when this event starts to appear. I made a Nic-Team of 4 Gigabit cards. This is the message: MAC conflict: A port on the virtual switch has the same MAC as one of the underlying team members on Team Nic Microsoft Network Adapter Multiplexor Driver.

Already changed the mac of the virtual switch in Hyper-V but nothing has changed, I still have problems.
can anybody help me? thank you

hi,

we have multiple Hyper-V servers in a cluster.

we have a virtual service that uses internal network switches within hyper v and we are seeing slow performance on this.

to test connectivity i just spun up a basic windows server and added it to the internal network.

when i copy a file using the internal network IP range i barely get about 80MBps per sec (less than 1Gbps).

we have physical networking of 10Gbps and the internal network is showing a status of 10Gbps so i dont understand how the internal network which is purely virtual gets such slow network speed.

hope someone can help me out here.

thanks

I am running Hyper-V Manager on a Windows 2019 Standard server.  I am trying to install a Windows 2019 Standard guest OS.  I create the machine as a 2nd Gen machine and give it appropriate settings.  I a pointing it to an iso.  On startup it failes to boot off of iso.

I have search and tried most recommendations including

Disabling secure boot

Changing keyboard setting to physical

Changing boot order

Changing Template under secure boot

None have enabled me to load the Guest os

any thoughts

Hello,

I need help with running out of room issue and also understanding with checkpoints.  I am currently running Hyper-V Bear and hosting 2 VM's.  The host disk is running out of space so the VM's keep pausing-critical which I get.  Right Now I am trying to understand a few things.  The VM I am currently looking at has 3 checkpoints, the parent and then 2 others.

The parent is a win 7 build the first checkpoint, The second checkpoint is the win 10 upgrade, The third is the checkpoint with all the updates.

The disk is dynamic not fixed. the vhdx file is 87gb and the checkpoints avhdx files: CHKP1-100gb, CHKP2-165gb(added space to the c drive inside the vm) and CHKP-3 is 30GB

1.  If I merge the Checkpoints will it free up space by over writing or will it just combine.

2. I try to remove the first checkpoint but then the VM did not work. I am pretty sure it's because it part of the tree but I taught that by creating a new checkpoint would carry over all info so the previous checkpoint would only be needed for rollbacks. Was I wrong.

3.  The last checkpoint is the state I want to keep so how do I do so and get rid of the others without affecting the VM itself.

4.  I am able to add more space to the disk but wanted to learn how to also clean up VM. I also needed to understand how the space works because there is not alot of data stored on the VM.  The C drive is about 165 GB now and I am only using about 87gb so where is all the data coming from that is eating up the host disk?

5. Also in regards to a recycle bin, when I delete a fill is it stored somewhere that I can't see that may be eating up my disk space? 

Thanks for any insight that can be provided....

[Cross-posted from SCOM forum as deemed a Hyper-V specific question]

I have the Hyper-V 2016 Management Pack Extensions installed into my SCOM 2016 installation.

I'm seeing a bunch of the following errors:

Hyper-V MPE 2016 VHD Error Count Monitor

Instance PATH.avhdx
Object Hyper-V Virtual Storage Device
Counter Error Count
Has a value 5
At time 2019-12-12T13:58:06.0000000+00:00

This monitor is reporting the underlying VHD Error Counter, which also has the same value.  I don't know what this counter actually means, and I can find no information on the web that explains it.  The notes on this counter say "The Error count should always be zero for the virtual storage device", which of course has me concerned that it is a real problem.

Hi all, I apologies for the lengthy post, and any irrelevant information. I'm trying to provide as much information as I can.

I have been asked to log this ticket by Veeam, as they determine it is a Microsoft issue.

We use Veeam Backup and Replication to backup all of our Hyper-V guests.

We also use VeeamONE to report on issues.

Our environment is:

 - a standalone physical server running our Veeam software

 - two clustered servers with Fibre Channel storage (Cluster Shared Volumes) hosting our VMs (approx. 20 guests VMs)

For the most part, this all runs fine. Occasionally, however, VeeamONE reports the following error:

Description
Fired by event: 12240 Microsoft-Windows-Hyper-V-VMMS
Event description: '': Attachment 'C:\ClusterStorage\ServerName\Virtual Hard Disks\diskname_E40FF910-B414-4DFA-BDC3-BE02ACDCF27A.avhdx' not found. Error: 'The system cannot find the file specified.' (0x80070002). (Virtual machine ID )
Initiated by: DOMAIN\BackupAdmin
Knowledge
Cannot open VM attachment

It happens to random servers, on random dates, so no pattern to the issue.

The AVHDX files that is "not found" is the snapshot file created by Veeam during the Backup process.

Veeam uses an API to take the snapshot, then another one to remove it when the backup is complete.

So, in effect, the error is correct, as the file no longer exists, but why is it being logged, if the API is removing the snapshot correctly, should Windows be able to detect this and not log the error?

My main concern is that this then logs an error with VeeamONE, and makes our reports and KPIs look bad, with all these false reports.

I know that the easy solution is to turn off that Alert, but I would like to catch legitimate issues, not the false positives.

If relevant:

 - All servers fully patched and restarted

 - Integration services are up to date on most servers (issue happens regardless of version)

Again, I apologies for lengthy post. In summary, my question is: Why does Windows/Hyper-V log that error for a temporary Snapshot disk? Is it a bug in the API call? Is Veeam initiating the API call incorrectly?

I have a clean install on an HP ML350 G10 server of Windows 2019 standard now that it was re-released.

The HP SPP worked fine to get all drivers loaded since 2019 isn't supported yet for the intelligent provisioning process.

Server activated, all four network card work fine.  No bangs in device manager, all devices have drivers loaded and are recognized.

I've added the Hyper-V role, that goes fine. 

Then trying to add an adapter to the hyper-v switch, it fails.  Ultimately the error is that it can't find a file.  This is trying to get the adapter installed via the GUI.  So I dropped to powershell, tried to create it there, same error.  Tried every network card, same error. 

Removed Hyper-V role, re-added it, same error.

Removed Hyper-V role, then when I added it, tried to add the interface to the network switch during the GUI install of the Hyper-V role.  It didn't give an error, but when the install was done and system rebooted, there was nothing for the hyper-v switch.  And trying manually via GUI or powershell still does the same thing.

I'm not allowing the management operating system to share the adapter, although I tried with letting that happen and the result is the same.

Some of the things I've seen for older OS's like 2012 and 2016 said to remove the "Hyper-v Extensible Virtual Switch" from the bindings on the cards first then try again, but that won't uninstall.  I get an error 0x80071779

I've removed and reinstalled the drivers, and a few different versions of the drivers, including the ones it finds automatically when I just went to the network card properties and told it to find drivers to update as well as the current and previous versions on HP's website for this adapter.

Anyone else see this?  It always comes back to "Error applying virtual switch properties changes. Failed while adding virtual ethernet switch connections."  The details show the GUID of the adapter, with the final text, "The system cannot find the file specified." and an error code of 0x80070002

Another post mentioned they solved something similar on an earlier windows build by disabling internet connection sharing - that's already disabled.

Another post mentioned antivirus causing this in a previous Windows server build - but this is a clean windows install, no antivirus is installed here.

One of the joys of playing with a new server build right at release...

Just in case it WAS something that was corrupted from the original install, I nuked it, reinstalled clean from scratch, and the problem persists.

I wish I had another spare server I could test this with to see if it's a bug with Windows, or simply some incompatibility with HP.  But since other people have had this issue since 2012, I'm guessing there's just something I will have to wait to get updated with by MS or by HP.

I made the mistake of posting the question on spiceworks and got people "instructing" about everything EXCEPT the actual problem.  It's a bit like posting on an auto forum about a brake issue, and people "answer" complaining about the color of your car...

Since I have a business continuity device on this network I have no qualms about deploying 2019 this early for a Hyper-V role, as I can spin up any of its guests within minutes if something happens, so no complaining that "you shouldn't use 2019 in production until after the first service pack," or other such.  Let's please try to stick with the actual technical issue.  I prefer to NOT have to deploy a 3+ year old OS on a brand new server now if I don't have to.

Thanks for any guesses... 

John

John

Hi guys,

I have a standalone host (Windows Server 2016) with a 2 NICs Teaming in which 5 VLANs will pass. The VMs will be connected to the virtual switch linked to this Teaming and connected to a different VLAN.

To RDP to the host, I have to set the VLAN 3323 (Management).

Do I have to :
1. Set the VLAN 3323 in the Teaming parameters
2. Let the virtual switch without VLAN ids
3. Configure each VM with its dedicated VLAN

or 

1. Let the Teaming parameters without VLAN id
2. Set the VLAN 3323 in the virtual switch VLAN id
3. Configure each VM with its dedicated VLAN

Thank you for your help.

Cheers,

Hi Guys

            I have two brand new servers with 6 drives. 2 in Mirror, 3 Raid 5 with 1 hot spare. Both servers are identical and running Windows 2019 Datacenter. Both servers are running Hyper-V. I do not have any NAS/SAN devices being shared between these servers. I will call these servers server1 and server2 (for this example)

Is there a way to make it so that if a virtual machine on server1 dies and shuts off the replicated virtual machine on server2 will boot up automatically? The whole purpose of these servers is for virtual machine failover, I would like to do it per VM versus entire physical server. I can also format the Hyper-V partition since these servers are new and not running anything just yet.

Is Storage Spaces Direct (S2D) the answer I'm looking for? If so, how? Looks like Clustering needs as a requirement shared disks (SAN/NAS).

What do you guys think?

Thank You

Eddie

I am setting up a new Domain environment. I have installed Hyper V 2019 on a server. I can not remote manage the server with Hyper V management tools, and it looks like it is because I am not in a domain environment. I can RDP to the server with no issues. But when I try to use the Hyper V management utility I get an error. Like i said currently I am in a workgroup environment.

"An error occurred while attempting to connect to a server 10.x.x.x" Check that the Virtual Manage Management service is running and that you are authorized to connect to the server"

I am not even sure how to check to see if the service is running. 

Any help is appreciated.