Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 650660 - app-emulation/libvirt: update from 4.0.0 to 4.1.0 breaks with the error: ERROR this function is not supported by the connection driver: Network device allocation not available
Summary: app-emulation/libvirt: update from 4.0.0 to 4.1.0 breaks with the error: ERRO...
Status: RESOLVED DUPLICATE of bug 650872
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal major
Assignee: Matthias Maier
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-16 20:03 UTC by Maciej Piechotka
Modified: 2018-03-23 14:06 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Piechotka 2018-03-16 20:03:18 UTC 
Probably it doesn't make sense to report it upstream given that version in portage is 2 major releases old:

(gnome-boxes:19293): Boxes-WARNING **: machine.vala:611: Failed to start Windows: Unable to start domain: this function is not supported by the connection driver: Network device allocation not available

Downgrading to 4.0 fixes the problem. Commandline works.
Comment 1 Xiao Lin 2018-03-17 02:30:44 UTC 
Seems use flag virt-network needs to be enabled for app-emulation/libvirt if NAT is used.
Maybe this use flag should be a dependency for gnome-boxes.
Comment 2 Toralf Förster gentoo-dev 2018-03-20 18:33:56 UTC 
similar thing here - this helped :

# package.mask
#
#
~app-emulation/libvirt-4.1.0
~dev-python/libvirt-python-4.1.0

and pls see : https://forums.gentoo.org/viewtopic.php?p=8198544
Comment 3 Agostino Sarubbo gentoo-dev 2018-03-23 11:52:16 UTC 
I encountered the same error.

I reported it to upstream and here is the patch:
https://www.redhat.com/archives/libvir-list/2018-March/msg01461.html

The problem is not related to any gnome tool for me
Comment 4 Matthias Maier gentoo-dev 2018-03-23 13:54:21 UTC 

*** This bug has been marked as a duplicate of bug 650872 ***
Comment 5 Matthias Maier gentoo-dev 2018-03-23 14:04:34 UTC 
I am sorry for having missed this one in my smoke tests prior to bump and stabilization.

The problem with libvirt upstream is the fact that they primarily develop and bundle for Redhat, i.e. essentially all their configuration options are always enabled...

I will push 4.1.0-r2 to the tree in a minute, with above patch applied.
Comment 6 Larry the Git Cow gentoo-dev 2018-03-23 14:06:10 UTC 
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=68fdb138b9730d532c38cdf6fcef2a36f37a92cb

commit 68fdb138b9730d532c38cdf6fcef2a36f37a92cb
Author:     Matthias Maier <tamiko@gentoo.org>
AuthorDate: 2018-03-23 14:00:39 +0000
Commit:     Matthias Maier <tamiko@gentoo.org>
CommitDate: 2018-03-23 14:05:58 +0000

    app-emulation/libvirt: 4.1.0-r2: Apply upstream patch for bridge support
    
    Apply an upstream patch to reenable bridge support even if
    USE=-virt-network and automatic network support is compiled out of
    libvirt
    
    Thanks to Agostino Sarubbo for upstream report and mentioning the
    upstream patch.
    
    Patch: https://www.redhat.com/archives/libvir-list/2018-March/msg01461.html
    Bug: https://bugs.gentoo.org/650660
    Bug: https://bugs.gentoo.org/650872
    Package-Manager: Portage-2.3.24, Repoman-2.3.6

 .../files/libvirt-4.1.0-unbreak_my_bridge.patch    | 78 ++++++++++++++++++++++
 ...irt-4.1.0-r1.ebuild => libvirt-4.1.0-r2.ebuild} | 10 +--
 2 files changed, 80 insertions(+), 8 deletions(-)}