Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Hyper-V Legacy NIC

    Scheduled Pinned Locked Moved Virtualization
    2 Posts 2 Posters 652 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • _
      _rp
      last edited by

      I'm running a Gen1 Hyper-V VM with legacy NIC's and non-legacy NIC's due to the amount of NIC's that we require for the pFsense instance.

      We see issues with the CPU running almost 100% and from what I see in the system activity logs there's reference to the three legacy NIC interfaces so I'm thinking the issues is related to that. This doesn't happen all the time and isn't related to the amount of traffic going through the firewall, the VM has plenty of resources to cope with the traffic etc.

      I've had a quick search around and I've spotted a few posts which say to not use legacy NIC's when using Hyper-V but nobody says why.

      My question here is; can anyone shed any light on why not to use legacy NIC's for Hyper-V VM's? or is it just because the nonlegacy NIC's have better drivers?

      1 Reply Last reply Reply Quote 0
      • provelsP
        provels
        last edited by

        IIRC, legacy NICs are limited to 100Mbps.

        Peder

        MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
        BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.