Bug 1321718

Summary: ipv6 test failure in virt-manager and gnome-boxes
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: agedosier, berrange, bgalvani, clalancette, crobinso, dcbw, dyuan, itamar, jforbes, laine, libvirt-maint, lkundrak, psimerda, shyu, veillard, virt-maint, yalzhang
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-08 22:06:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
journal.log none

Description Chris Murphy 2016-03-29 02:48:37 UTC
Created attachment 1141066 [details]
journal.log

Description of problem: Google search for ipv6 tests, and run any of them, they all fail when Fedora 24 Alpha is run from within a libvirt VM. On the host, this works fine.


Version-Release number of selected component (if applicable):
NetworkManager-1.2.0-0.6.beta2.fc24.x86_64

How reproducible:
Always when in VM, never on baremetal.


Steps to Reproduce:
1.
2.
3.

Actual results:

No IPv6 address is available.

Expected results:

Seems like IPv6 should be supported in guests when the host has IPV6 connectivity.

Additional info:


1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 52:54:00:3f:7e:76 brd ff:ff:ff:ff:ff:ff
    inet 192.168.124.70/24 brd 192.168.124.255 scope global dynamic ens3
       valid_lft 3558sec preferred_lft 3558sec
    inet6 fe80::c88a:7779:6c8a:6424/64 scope link 
       valid_lft forever preferred_lft forever

Comment 1 Chris Murphy 2016-03-29 03:03:51 UTC
Above ip addr is the guest.

This is on the host.

# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether c8:2a:14:02:88:99 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.4/24 brd 10.0.0.255 scope global dynamic enp2s0f0
       valid_lft 588395sec preferred_lft 588395sec
    inet6 2601:282:702:b960:7d43:76b3:7ddc:14e7/64 scope global temporary dynamic 
       valid_lft 345590sec preferred_lft 69393sec
    inet6 2601:282:702:b960:ca2a:14ff:fe02:8899/64 scope global mngtmpaddr noprefixroute dynamic 
       valid_lft 345590sec preferred_lft 345590sec
    inet6 fe80::ca2a:14ff:fe02:8899/64 scope link 
       valid_lft forever preferred_lft forever
3: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:54:00:83:90:be brd ff:ff:ff:ff:ff:ff
    inet 192.168.124.1/24 brd 192.168.124.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue master virbr0 state DOWN group default qlen 500
    link/ether 52:54:00:83:90:be brd ff:ff:ff:ff:ff:ff
11: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master virbr0 state UNKNOWN group default qlen 500
    link/ether fe:54:00:3f:7e:76 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe3f:7e76/64 scope link 
       valid_lft forever preferred_lft forever

Comment 2 Chris Murphy 2016-03-29 03:13:54 UTC
Not a regression. Same problem with clean installation of Fedora-Live-Workstation-x86_64-23-10.iso (final) as a guest.

Comment 3 Beniamino Galvani 2016-03-29 07:06:05 UTC
(In reply to Chris Murphy from comment #0)
> Created attachment 1141066 [details]
> journal.log
> 
> Description of problem: Google search for ipv6 tests, and run any of them,
> they all fail when Fedora 24 Alpha is run from within a libvirt VM. On the
> host, this works fine.

I suppose the virtual interface is configured to do IPv4 NAT and masquerading but doesn't provide IPv6 connectivity to the guest; NM tries to configure both IPv4 and IPv6 on the guest but only the first succeeds.

This looks like a request for enhancement on libvirt side, so I'm reassigning this bug to that component.

Comment 4 Cole Robinson 2016-04-08 22:06:15 UTC
I assume this is just using the 'default' virtual network/virbr0? If so, it doesn't have any ipv6 config, it's just ipv4 nat, so ipv6 in the VM doesn't work out of the box. Unfortunately there really isn't any easy out of the box IPv6 option for VMs unless you manually bridge your host interface