kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Tags added: kernel-da-key kernel-hyper-v

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440072

Title:
  [Hyper-V] Legacy network adapter is not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue description:
  Attaching a Legacy network adapter to a VM will not be detected on the VM side.
  This is not the case with synthetic adapters, which are properly identified.

  Steps to Reproduce: 
  1.     Add a Legacy Network adapter to the VM
  2.     Boot the vm
  3.     Verify the identified network adapter, the legacy NIC is missing

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter build 9600 and Microsoft Windows Server 2008 R2 Standard  SP 1 build 7601
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 SMP

  
  Hyper-V side:
  PS> Get-VMNetworkAdapter -VMName vivid1

  Name                   IsManagementOs VMName SwitchName MacAddress   Status IPAddresses
  ----                   -------------- ------ ---------- ----------   ------ -----------
  Network Adapter        False          vivid1 external   00155D06332D {Ok}   {IP, fe80::215:5dff:fe06:332d}
  Legacy Network Adapter False          vivid1 external   00155D063336 {Ok}   {}

  On the VM Side:
  root@ubuntu31:~# ls /sys/class/net/
  eth0  lo

  eth0 has the MAC of the Network Adapter, which is the synthetic
  interface.

  This has been verified with also 1 vCPU or with irqbalancer daemon
  disabled, as that is a common requirements when using legacy adapters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440072/+subscriptions