Bug 1788923

Summary: missing eth0 device for RHEL6 VMI when created with interface model type as virtio
Product: Container Native Virtualization (CNV) Reporter: Kedar Bidarkar <kbidarka>
Component: NetworkingAssignee: Petr Horáček <phoracek>
Status: CLOSED DUPLICATE QA Contact: Meni Yakove <myakove>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.2.0CC: ailan, cnv-qe-bugs, danken, ncredi
Target Milestone: ---   
Target Release: 2.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-12 14:26:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
RHEL6 DV file none

Description Kedar Bidarkar 2020-01-08 11:37:27 UTC
Description of problem:

Missing eth0 device for RHEL6 VMI when created with interface model type as virtio.

Images used to create the RHEL6 VM: Latest image from, 
https://access.redhat.com/downloads/content/69/ver=/rhel---6/6.10/x86_64/product-software

Templates used to create the RHEL6VM: rhel6-server-medium-v0.7.0 from openshift namespace.


Version-Release number of selected component (if applicable):

Latest cnv-2.2


How reproducible:

Always


Steps to Reproduce:
1. Create DV with attached file, by fixing the HTTPServer name
2. Create a VM with the templates.

oc process rhel6-server-medium-v0.7.0 -p NAME=rhel610-vm -p PVCNAME=dv-rhel-610 | oc create -f -
3. Start the VM, login to console, to notice that there is no eth0 device.

As seen from "ip addr"

Actual results:

No eth0 device available, when interface model type is VIRTIO

Expected results:

eth0 device available, when interface model type is VIRTIO

Additional info:

eth0 device is available, when interface model type is set to "e1000", after the RHEL6 VM is created. 

By using, "model: e1000" under interfaces

Comment 1 Kedar Bidarkar 2020-01-08 11:39:56 UTC
Created attachment 1650663 [details]
RHEL6 DV file

Comment 4 Kedar Bidarkar 2020-01-08 11:42:51 UTC
Below is the virtio output, from the RHEL6-10 VMI

[cloud-user@rhel-610-vm ~]$ lsmod | grep virtio
virtio_console         19089  0
virtio_pci              7544  0
virtio_ring             8891  2 virtio_console,virtio_pci
virtio                  5671  2 virtio_console,virtio_pci
[cloud-user@rhel-610-vm ~]$ cat "/boot/config-`uname -r`" | grep -i vir
CONFIG_PARAVIRT_GUEST=y
CONFIG_PARAVIRT=y
# CONFIG_PARAVIRT_SPINLOCKS is not set
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_PARAVIRT_DEBUG is not set
CONFIG_VIRT_TO_BUS=y
CONFIG_NET_9P_VIRTIO=m
CONFIG_VIRTIO_BLK=m
CONFIG_SCSI_VIRTIO=m
CONFIG_VIRTIO_NET=m
CONFIG_VIRTIO_CONSOLE=m
CONFIG_HW_RANDOM_VIRTIO=m
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
CONFIG_FB_VIRTUAL=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_VIRTUOSO=m
# CONFIG_DEBUG_VIRTUAL is not set
CONFIG_VIRTUALIZATION=y
CONFIG_VIRTIO=m
CONFIG_VIRTIO_RING=m
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIO_BALLOON=m

Comment 5 Petr Horáček 2020-01-08 11:44:02 UTC
Dan, virtio_net kernel module is not loaded on RHEL6. Is that a known limitation? The other virtio drivers are listed in `lsmod`.

Comment 6 Kedar Bidarkar 2020-01-08 11:49:28 UTC
Tried few things below,

1) Not 100% sure if this is how to load the virtio_net module, at boot time, but tried the below and no luck.

[cloud-user@rhel-610-vm rules.d]$ cat /etc/sysconfig/modules/virtionet.modules 
#!/bin/sh
/sbin/modprobe virtio_net


2) Removed the 70-persistent-net.rules  from /etc/udev/rules.d/
But no luck, this file does not get recreated.

Comment 7 Dan Kenigsberg 2020-01-08 12:29:32 UTC
(In reply to Petr Horáček from comment #5)
> Dan, virtio_net kernel module is not loaded on RHEL6. Is that a known
> limitation? The other virtio drivers are listed in `lsmod`.

It is certainly not known to me. I suspect that it had worked before (see KNIP-431).

Kedar, please specify the kernel versions on host and guest, as well as kvm and qemu versions from the host and pod.

Share your `lspci -vvv` and kernel log messages right after you run `modprobe virtio_net`.

When done, please set a needinfo on ailan ;-)

Comment 12 Dan Kenigsberg 2020-03-12 14:26:32 UTC
Ok, so this is a dup of bug 1794243. We must use virtio-non-transitional in order to support RHEL6 guests.

*** This bug has been marked as a duplicate of bug 1794243 ***

Comment 13 Red Hat Bugzilla 2023-09-14 05:49:32 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days