Virtualization

How can we improve the virtualization platform and management in Windows Server?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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,
    Nick

    7 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  8. Configure VLAN in Virtual Switch on Hyper-V Manager

    Enable on Hyper-V Manager options configure VLAN on vSwitches.

    28 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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.

    16 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  10. vSwitch default minimumbandwidthmode should be weight

    When vSwitch is created from Hyper-V console or Posh, minimumbandwidthmode is absolute.

    5 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base