virt-manager doesn't create or change the bridge and gives an error message

Bug #1802727 reported by dementor5
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
virt-manager (Ubuntu)
Expired
Medium
Unassigned
Bionic
Expired
Medium
Unassigned
Cosmic
Expired
Medium
Unassigned

Bug Description

Fresh install ubuntu 18.10 desktop.
sudo apt update && sudo apt dist-upgrade -y && sudo apt install virt-manager -y && reboot
virt-manager version: 1:1.5.1-0ubuntu2

When i try to switch on existing not working bridge virbr0, i receive a error:
Error starting interface 'virbr0': this function is not supported by the connection driver: virInterfaceCreate

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in newfn
    ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/interface.py", line 68, in start
    self._backend.create(0)
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3084, in create
    if ret == -1: raise libvirtError ('virInterfaceCreate() failed', net=self)
libvirtError: this function is not supported by the connection driver: virInterfaceCreate

When i try to create new bridge, i receive another error:
Error creating interface: 'Could not define interface: this function is not supported by the connection driver: virInterfaceDefineXML'

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/createinterface.py", line 1145, in do_install
    self.interface.install(meter, create=activate)
  File "/usr/share/virt-manager/virtinst/interface.py", line 258, in install
    raise RuntimeError(_("Could not define interface: %s") % str(e))
RuntimeError: Could not define interface: this function is not supported by the connection driver: virInterfaceDefineXML

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: virt-manager 1:1.5.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 11 16:44:41 2018
ExecutablePath: /usr/share/virt-manager/virt-manager
InstallationDate: Installed on 2018-11-11 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
SourcePackage: virt-manager
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
dementor5 (dementor5) wrote :
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi dementor,
I just wanted to reply so you know this has been seen.
I really want to take a look at it and keep it in my inbox, but this week I'm way too busy and won't get to it :-/

Until I get to it it would be nice if you could outline "When i try to switch on existing not working bridge virbr0" a bit more.
is virbr0 already existing, if so who/how was it created.
What do you switch to it - a guest config switching from a former network to use that?
Or a network definition to use virbr0.
Since it is a UI thing a screenshot or video often helps to disambiguize.

Do the same actions work if you use virsh as a commandline tool to do so?

Revision history for this message
dementor5 (dementor5) wrote :

Hi Christian Ehrhardt, thank you for operational feedback.

I just simple use gui. I got an error by simle selecting any default bridge after installing virt-manager and click on "Start interface" or
"Add Interface" => "Interface type Bridge" => "Forward" => "Finish".

I didn't try to use virsh for this.
Can you write for me an example full virsh command for test it in console?

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Upstreaming complete:
https://libvirt.org/git/?p=libvirt.git;a=commit;h=6aa75b94627c9ad3bf6a836cc821750979a2fe05

I already have a working backport version from our PPA Tests on Bionic before.

Changed in virt-manager (Ubuntu):
status: New → Triaged
Changed in virt-manager (Ubuntu Bionic):
status: New → Triaged
Changed in virt-manager (Ubuntu Cosmic):
status: New → Triaged
Changed in virt-manager (Ubuntu):
importance: Undecided → Medium
Changed in virt-manager (Ubuntu Bionic):
importance: Undecided → Medium
Changed in virt-manager (Ubuntu Cosmic):
importance: Undecided → Medium
Changed in virt-manager (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hmm, I just realized that I mixed this and bug 1802906 into one.
Sorry.
The last update was meant for the other.

@Brian - is this actually the same thing?
If it is not, could you here enable libvirt logging [1] and then provide that libvirt logfile ad well as a dmesg output just after triggering the issue?

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :
Revision history for this message
dementor5 (dementor5) wrote :

Excellent news! i very much wait it on cosmic. Thanks you!

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi,
I assume you replied on my comment #4 which was actually for bug 1802906
Would you mind clarifying if this is the same/different issue as I asked for in comment #5 please ?

Revision history for this message
Abner Freitas (abner-rego-freitas) wrote :

Facing the exact same problem here with 18.10. Hope to get a fix before christmas XD

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hrm, there is no work on this bug here atm afaik.
To be clear, there are:
- bug 1802906 which is fixed in Disco Dingo (upcoming Ubuntu 19.04)
- this bug here which is unclear what it actually is about atm.
  - is it the same bug as bug 1802906?
    - please test the code in 19.04 against your case
    - if it works, then we can consider 1802906 as SRU for Bionc/Cosmic
    - if so please provide a use case this is for on bug 1802906
  - is it not the same?
    - please explain what makes this use case different.
    - please provide steps to re-produce this
    - only then can it be further discussed/debugged/fixed

Changed in virt-manager (Ubuntu):
status: In Progress → Incomplete
Changed in virt-manager (Ubuntu Bionic):
status: Triaged → Incomplete
Changed in virt-manager (Ubuntu Cosmic):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for virt-manager (Ubuntu Bionic) because there has been no activity for 60 days.]

Changed in virt-manager (Ubuntu Bionic):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for virt-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in virt-manager (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for virt-manager (Ubuntu Cosmic) because there has been no activity for 60 days.]

Changed in virt-manager (Ubuntu Cosmic):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.