After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 785066 - RHEL 7.2 VMs are set up with the wrong network device
RHEL 7.2 VMs are set up with the wrong network device
Status: RESOLVED OBSOLETE
Product: gnome-boxes
Classification: Applications
Component: general
3.22.x
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-07-18 14:10 UTC by Debarshi Ray
Modified: 2018-01-11 10:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
XML dump of RHEL 7.2 VM with virtio NIC (6.22 KB, text/plain)
2017-07-19 12:42 UTC, Debarshi Ray
Details
XML dump of RHEL 7.2 VM with rtl8139 NIC (6.22 KB, text/plain)
2017-07-19 12:45 UTC, Debarshi Ray
Details

Description Debarshi Ray 2017-07-18 14:10:53 UTC
RHEL 7.2 VMs don't have broken networking in Boxes. This can be fixed by changing the network device to rtl8139 from virtio. I was told that this is due to missing virtio drivers on the guest.

(Thanks to Pavel Grunt and Victor Toso for helping me narrow this down.)

Interestingly, RHEL 7.3 VMs are also set up with virtio, but have functional networking (I guess due to the drivers being present), while RHEL 7.4 gets set up with rtl8139.
Comment 1 Christophe Fergeau 2017-07-18 14:21:33 UTC
This would be an issue in libosinfo to be reported on https://libosinfo.org/bugs/#report
However, the kernel package on the 7.2 ISO I had around does have virtio-net:
/lib/modules/3.10.0-327.el7.x86_64/kernel/drivers/net/virtio_net.ko
so it looks like there is something more going on.
Comment 2 Debarshi Ray 2017-07-18 16:45:21 UTC
(In reply to Christophe Fergeau from comment #1)
> However, the kernel package on the 7.2 ISO I had around does have virtio-net:
> /lib/modules/3.10.0-327.el7.x86_64/kernel/drivers/net/virtio_net.ko
> so it looks like there is something more going on.

Oh, it is a kernel driver. I couldn't figure out what "missing drivers" meant. I also have virtio_net.ko on my VM:
$ rpm -q kernel
kernel-3.10.0-514.el7.x86_64
$ ls /lib/modules/3.10.0-514.el7.x86_64/kernel/drivers/net/virtio_net.ko 
/lib/modules/3.10.0-514.el7.x86_64/kernel/drivers/net/virtio_net.ko
Comment 3 Debarshi Ray 2017-07-18 17:04:56 UTC
Also:

$ lsmod | grep virtio_net
virtio_net             28024  0 
virtio_ring            21524  5 virtio_blk,virtio_net,virtio_pci,virtio_balloon,virtio_console
virtio                 15008  5 virtio_blk,virtio_net,virtio_pci,virtio_balloon,virtio_console
Comment 4 Debarshi Ray 2017-07-18 17:06:12 UTC
So, should I report it against libosinfo, or shall we debug why virtio isn't working?
Comment 5 Christophe Fergeau 2017-07-19 09:42:16 UTC
(In reply to Debarshi Ray from comment #4)
> So, should I report it against libosinfo, or shall we debug why virtio isn't
> working?

Blacklisting virtio-net for 7.2 in libosinfo while the drivers are there would be just hiding the actual bug in my opinion. So yes, the latter :) Could you attach the output of 'virsh -c qemu:///session dumpxml $vmname'  in the non-working case? (if you can easily reproduce) You can use 'virsh -c qemu:///session list --all' to figure out the name of the VM.
Comment 6 Debarshi Ray 2017-07-19 12:42:57 UTC
Created attachment 355943 [details]
XML dump of RHEL 7.2 VM with virtio NIC
Comment 7 Debarshi Ray 2017-07-19 12:45:32 UTC
Created attachment 355944 [details]
XML dump of RHEL 7.2 VM with rtl8139 NIC
Comment 8 Debarshi Ray 2017-07-25 10:13:23 UTC
If this is beginning to look like a problem in the VM, then maybe we should just workaround it in libosinfo by not using virtio NICs with RHEL 7.2. I doubt this is serious enough that even if a fix is identified it will trickle down into RHEL 7.2, given that it has been a while since it has been released.
Comment 9 GNOME Infrastructure Team 2018-01-11 10:56:22 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-boxes/issues/154.