DHCPv6 does not work in Hyper-V
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
When using Ubuntu (in this case the live 16.04.1 LTS ISO) as a Generation 2 (Gen1 untested) Hyper-V VM, an IPv6 address can't be gotten through DHCPv6. dhclient continues to send out solicitations but they never result in a response. I've looked on the router end (running AdvancedTomato and dnsmasq) and the router is getting the requests and is sending out a advertisement, but the VM never gets it. Using the exact same live ISO works in VirtualBox so I've convinced it is an issue with the Hyper-V network driver or something along those lines.
The only IPv6 address that is configured automatically is the fe80 link-local address.
Windows VMs and older Linux VMs (Debian jessie with 3.16 kernel) work just fine and receive an IPv6 via DHCPv6.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperVersion: 1.376
CurrentDesktop: Unity
Date: Sat Sep 17 19:56:42 2016
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Microsoft Corporation Virtual Machine
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.157.2
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2012
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: Hyper-V UEFI Release v1.0
dmi.board.
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: Hyper-V UEFI Release v1.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.
dmi.modalias: dmi:bvnMicrosof
dmi.product.name: Virtual Machine
dmi.product.
dmi.sys.vendor: Microsoft Corporation
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperVersion: 1.376
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Microsoft Corporation Virtual Machine
Package: linux (not installed)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.157.2
RfKill:
Tags: xenial
Uname: Linux 4.4.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2012
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: Hyper-V UEFI Release v1.0
dmi.board.
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: Hyper-V UEFI Release v1.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.
dmi.modalias: dmi:bvnMicrosof
dmi.product.name: Virtual Machine
dmi.product.
dmi.sys.vendor: Microsoft Corporation
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
summary: |
- DHCPv6 does not work + DHCPv6 does not work in Hyper-V |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1624722
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.