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:
I'm running the latest RHEL 6.4 beta and beyond packages.  Guest networking stopped working and I cannot determine why.


Version-Release number of selected component (if applicable):
$ rpm -qa | grep virt
python-virtinst-0.600.0-13.el6.noarch
virtio-win-1.5.3-1.el6_3.noarch
libvirt-python-0.10.2-11.el6.x86_64
libvirt-client-0.10.2-11.el6.x86_64
libvirt-0.10.2-11.el6.x86_64
virt-manager-0.9.0-18.el6.x86_64
virt-what-1.11-1.2.el6.x86_64
virt-viewer-0.5.2-17.el6.x86_64


How reproducible:
100%


Steps to Reproduce:
1. Start a guest
2. Log into guest
3. Watch wired networking fail with NetworkManager
  
Actual results:


Expected results:


Additional info:

kvm and kernels:

qemu-kvm-0.12.1.2-2.342.el6.x86_64
kernel-2.6.32-347.el6.x86_64

Laine, this looks like BZ 884957 to me, what do you think?

Very likely.

If it starts working again after downgrading to dnsmasq-2.48-9.el6.x86_64 (and restarting all the networks/guests), then definitely that's the problem.

John, does that fix it for you?

I'm running 2.48-10.el6.  

Can you point me to where I can find 2.48-9.el6 or just send it to me?

Try running "yum downgrade dnsmasq" and see what that gives you.

(In reply to comment #6)
> Try running "yum downgrade dnsmasq" and see what that gives you.

Bingo.  Downgraded to dnsmasq-2.48-6.el6.x86_64.rpm and networking works again!

Ok, closing as a duplicate of bug 884957.

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