RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

On default install of RHEL 6 Snapshot 1 and above, running as KVM guest on a RHEL 5.x host, the default network configuration conflicts between guest and host.

Service libvirtd comes enabled by default, and uses 192.168.122.1 as the virbir0 interface. This is the same IP range used by the KVM host when the network is set to NAT.

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

Host: RHEL 5.5, NAT network
Guest: RHEL 6 Snapshot >= 1

How reproducible:

Steps to Reproduce:
1. Install RHEL 5.5 as host.
2. Use virt-manager to create a new guest with type RHEL 6.
3. Install RHEL 6 on the guest.
4. Boot guest.
5. ping any IP on the "real" network. ping will stop after 10 packages or so.
6. service libvirtd stop
7. service network restart
8. ping works forever
  
Actual results:

After 10 ping packets or so, network communications stall.

Expected results:

Network should work out of the box.

Additional info:

I suggest there should be a way to detect if the installed system is a guest under KVM, and do one of the options:

a) disable libvirtd

or

b) use a different IP on the guest's virbr0 interface

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

(In reply to comment #0)
> Additional info:
> 
> I suggest there should be a way to detect if the installed system is a guest
> under KVM, and do one of the options:
> 
> a) disable libvirtd

You don't want to do this; you can, in theory, run guests in a guest (it's called Nested Virtualization).

> 
> or
> 
> b) use a different IP on the guest's virbr0 interface    

We actually already have a patch for this queued up for the next RHEL-6 release.  Closing as a dup.

Chris Lalancette

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