← Back to team overview

kernel-packages team mailing list archive

[Bug 1581132] Missing required logs.


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

apport-collect 1581132

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.

  [XENAIL] net: updates to ethtool and virtio_net for speed/duplex

Status in linux package in Ubuntu:

Bug description:
  Post 4.4, several changes landed upsteam to allow users to set interface
  speed for virtio_net backed devices.  This feature is extremely useful
  for those doing large-scale networking simulations where Ubuntu-based
  VMs are used to simulate hosts.  Not only does it allow hosts to report
  the same speed in simulations for monitoring tools, but it is required
  to simulate 802.3ad bonding where link-speed is reported to the peer
  device.  Without proper speed setting there are cases where establishing
  LACP adjacency is not possible.  

  After this patch setting the link speed and duplex now works just as one would
  expect.  I'm running the kernel that contains this patch for these commands:

  $ sudo ethtool -s enp0s8 speed 100000 duplex full 
  $ sudo ethtool enp0s8
  Settings for enp0s8:
  	Supported ports: [ ]
  	Supported link modes:   Not reported
  	Supported pause frame use: No
  	Supports auto-negotiation: No
  	Advertised link modes:  Not reported
  	Advertised pause frame use: No
  	Advertised auto-negotiation: No
  	Speed: 100000Mb/s
  	Duplex: Full
  	Port: Other
  	PHYAD: 0
  	Transceiver: internal
  	Auto-negotiation: off
  	Link detected: yes

  I've already submitted patches to the kernel-team mailing list.  Those
  patches can be found in this thread: https://lists.ubuntu.com/archives

To manage notifications about this bug go to: