Bug 1734479 - stock rhel8 install installed libvirt-* and caused conflicting 192.168.122.1 IP address
Summary: stock rhel8 install installed libvirt-* and caused conflicting 192.168.122.1 ...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libvirt
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Virtualization Maintenance
QA Contact: Luyao Huang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-30 16:19 UTC by Paul Wouters
Modified: 2020-02-11 03:34 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Paul Wouters 2019-07-30 16:19:23 UTC
I installed an iso of rhel8 using my fedora laptop running libvirtd/kvm.

My laptop has virbr0 of 192.168.122.1/24 with dhcp/dns - default stuff

The RHEL8 guest installed, but since it installed libvirt* packages, it _also_ created its own virbr0 device with 192.168.122.1, causing the virtio ethernet interface to have no IP whatsoever, presumably due to the conflict of its native ethernet with its own bridge device.

the rhel8 guest virbr0 was not managed with NetworkManager or with ifcfg files. It was created by the libvirt "default" network via /etc/libvirt/qemu/networks/default.xml

Maybe one fix is to not install libvirt* packages per default on a new install of rhel8 when it is detected that it is running in a virtualized environment? Otherwise, if the uplink is 192.168.122.0/24, perhaps the libvirt* install should pick a randomized 192.168.X.0/24 instead to avoid this conflict.

Comment 1 Radek Vykydal 2019-08-01 11:44:29 UTC
Reassigning to libvirt for knowledgeable input.

Comment 2 Jaroslav Suchanek 2019-08-01 12:27:00 UTC
I believe this has been addressed in rhel-7.2 bug 956891 and discussed mostly in fedora bug 811967.

Laine, any thoughts?

Comment 3 Jonathan Briggs 2019-10-10 03:22:59 UTC
I just ran into this exact thing with the Fedora 31 Beta running on a Ubuntu 18.04 host. I was running ip addr flush dev virbr0 until I figured out that the libvirt packages were installed and running on boot.

Comment 4 Laine Stump 2019-10-15 19:03:37 UTC
You can make comments specific to Fedora and this issue here: Bug 1146284. Be sure to read the history in Bug 811967

Comment 6 Laine Stump 2020-02-11 03:34:20 UTC
This is very closely connected to 1628074


Note You need to log in before you can comment on or make changes to this bug.