No external network access for VMs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-boxes (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
libvirt (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
VMs under Boxes no longer have external network access - there seems to be a private internal network that is functioning fine, but when the host is connected to a network it is not possible to access this external network from VMs. Eg. It is possible to resolve DNS names, but it is not possible to ping external hosts from a VM when the host connected to the Internet.
This is a regression from zesty.
Looking at virt-manager, qemu:///system has a NAT network defined using virbr0, but qemu:///session (which Boxes uses) has no network, and it is not possible to create one - attempting to do so results in a "Operation not permitted" error:
> Error creating virtual network: error creating bridge interface virbr1: Operation not permitted
>
> Traceback (most recent call last):
> File "/usr/share/
> callback(asyncjob, *args, **kwargs)
> File "/usr/share/
> net.install()
> File "/usr/share/
> net.create()
> File "/usr/lib/
> if ret == -1: raise libvirtError ('virNetworkCre
> libvirtError: error creating bridge interface virbr1: Operation not permitted
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-boxes 3.26.1-1
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Oct 18 15:01:42 2017
InstallationDate: Installed on 2015-07-22 (819 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: gnome-boxes
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in libvirt (Ubuntu): | |
status: | Invalid → Confirmed |
Added libvirt since I can't add a NAT network to the qemu:///session using virt-manager, either.