kernel-packages team mailing list archive

[Brad Figg <brad.figg@xxxxxxxxxxxxx>]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1360580

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
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/1360580

Title:
  [Hyper-V] IP injection does not occur on Ubuntu 14.10

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  System details:
  Linux ubuntu 3.16.0-9-generic #14-Ubuntu SMP Fri Aug 15 15:03:57 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu Server 14.10 Daily build from 19th Aug (first build picked up for testing)
  Ubuntu 3.16.0-9.14-generic 3.16.1

  IP injection is not working in 14.10 and no changes have been made on
  the LIS side. There are also no logged error messages to identify the
  issue. IP injection has been fixed and was working in previous
  releases.

  Repro steps:
  1) Create an Ubuntu 14.10 VM in a HA cluster Hyper-V environment.

  2) Attach a synthetic NIC and set it with DHCP mode. Other test was
  done with a statically assigned IP.

  cat /etc/network/interfaces
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).
  # The loopback network interface
  auto lo
  iface lo inet loopback
  # The primary network interface
  auto eth0
          iface eth0 inet dhcp

  3) Enable Replication.

  4) Set Failover IP settings like for eg:
  Set-VMNetworkAdapterFailoverConfiguration -ComputerName $computerName -VMName $vmname -IPv4Address 192.168.100.10 -IPv4SubnetMask 255.255.0.0 -IPv4PreferredDNSServer 192.168.100.101 -IPv4DefaultGateway 192.168.100.1

  5) Simulating the IP injection shows the following behavior:
  a.  /etc/network/interfaces remains unchanged.
  b. no messages/errors are recorded in dmesg.

  The testing script used shows that the IP remains the same:

  IPAddresses:      : {192.168.100.107, 2001:4898:e0:f35b:215:5dff:fe3b:7210, fe80::215:5dff:fe3b:7210}
  ProtocolIFType:   : 4098
  DHCPEnabled:      : True
  InstanceID:       : Microsoft:GuestNetwork\6EBA4425-BB01-4BDE-A1FC-403389B9B6DC\0CBB124B-3102-4473-A3BD-8FF02B5879F2
  Subnets:          : {255.255.254.0, /64, /64}
  DNSServers:       : {8.8.4.4, OTHER DNS}
  DefaultGateways:  : {192.168.100.1, fe80::c262:6bff:feb0:9ddf, fe80::c262:6bff:feb1:6217}

  SetGuestNetworkAdapterConfiguration
  Msvm_GuestNetworkAdapterConfiguration After update .. please make sure VM is running ...
  IPAddresses:      : {192.168.100.107, 2001:4898:e0:f35b:215:5dff:fe3b:7210, fe80::215:5dff:fe3b:7210}
  ProtocolIFType:   : 4098
  DHCPEnabled:      : True
  InstanceID:       : Microsoft:GuestNetwork\6EBA4425-BB01-4BDE-A1FC-403389B9B6DC\0CBB124B-3102-4473-A3BD-8FF02B5879F2
  Subnets:          : {255.255.254.0, /64, /64}
  DNSServers:       : {same as above}
  DefaultGateways:  : {192.168.100.1, fe80::c262:6bff:feb0:9ddf, fe80::c262:6bff:feb1:6217}

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