Virtualization
-
Fix Mac Address spoofing in Hyper-V 2019
When we have a virtual router as a VM on Hyper-V 2019 running a setup that requires Mac Address Spoofing to be enabled, then performance is really bad.
We have testet with routers based on Windows Server 2019, Linux and BSD, and the results are the same.
Migrating the same VM's to a Windows Server 2016 node, the problem is gone.It seems to be a problem related to Hyper-V 2019 "Mac Address Spoofing" function
3 votes -
VMNetworkAdapter: Allow arp out for multicast mac addresses (even if MacAddressSpoofing is off)
VMNetworkAdapter on vSwitch: Please allow arp out for multicast mac addresses even if MacAddressSpoofing is off (or add another option to do so). It's not spoofing telling the switch about a multicast mac - how else would it know about it? It belongs to everyone! NLB is nice L4 active/active redundancy but relies on multicast or unicast flood. Multicast traffic is always received on default queue (understandable as multicast mac is not associated with vNic and can't be allocated a VMQ - but, default queue has finite cpu scalability). If you have MacAddressSpoofing enabled, then Windows unfortunately does not allocate…
2 votes -
Support for Microsoft Hosted Network Virtual Adapter
Allow a Virtual Switch to connect to the Microsoft Hosted Network Virtual Adapter. Other virtualization products allow this; Hyper-V doesn't. This is a severe limitation.
3 votes -
LACP in Virtual Environment
Hi,
Please allow LACP configurations for NIC teaming in virtual environments. This is a possible solution. The only allowed option is "Switch Independent", which is limiting to me. I run LACP configurations in my VMware environment for all my 2012R2 servers now, no issues from this design. Allow me to do this again please.
Thanks,
Nick7 votes -
Configure VLAN in Virtual Switch on Hyper-V Manager
Enable on Hyper-V Manager options configure VLAN on vSwitches.
29 votes -
Incorporate building of host vNICs and configuration into Hyper-V GUI
Add functionality in Hyper-V GUI to create host vNICs and manage them rather than requiring Powershell.
17 votes -
Match physical network list in virtual switch manager
In the Hyper-V virtual switch manager, when you go to create a virtual switch, the list of physical network adapters in the machine do not match the names of the physical network adapters in the server control panel network connections list.
This makes finding the matching physical network adapter that is mapped to the virtual switch a trial and error process.
It would be nice if you could either rename the virtual switch physical network adapter names in the dropdown list OR just have the virtual switch manager actually use the name the control panel uses for the physical network…
3 votes -
NAT IPv6
It would be nice to allow devices behind the NAT to access ipv6 resources as well externally. Right now this is not possible and as such the default switch for example, sends traffic out only if something is reachable via IPv4.
2 votes -
Check MAC Address before create Teaming
I found a strange problem with a host WS2012R2 (HP Proliant DL 380 g9 with 1 NIC 4 ports) during Teaming creation. For an astral reason, when I create a team, Windows assign the same MAC Address to Team NIC and also to Hyper-V Virtual Switch; the result is the total fail of everything.
Why Windows Server 2012 R2 hasn’t a pre-check task to understand both NIC have the same MAC Address? Much better is check the MAC Address of the entire host.
3 votes -
VM VLAN defined at vswitch port level
It is more clear the vmware strategy to create portgroups on a vswitch that specifies the VLAN. All VMs connected to that portgroup are connected to same VLAN.
What is the point on defining per VM, you are allowing users to create VM and they have to guess what is the VLAN id.
Please review this and allow move VLAN VM definition to the vswitch.
9 votes -
Isolate replication traffic.
There should be an option to chose the physical NIC or team one would want to send the Replication traffic thru while using kerberos for authentication. It can be achieved while using certificate based replication. but not in an AD environment.
5 votes -
vSwitch default minimumbandwidthmode should be weight
When vSwitch is created from Hyper-V console or Posh, minimumbandwidthmode is absolute.
5 votes
- Don't see your idea?