Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause: missing support for secrc field on e1000 emulation.
Consequence: Triggering netdump on a RHEL3 i386 guest, it failed when using e1000 NIC emulation.
Fix: Added support for secrc field on e1000 emulation code.
Result: netdump on RHEL3 guests using e1000 emulation now work.
Description of problem:
Triggering netdump on a RHEL3 i386 guest, it failed for both 8139cp and e1000 NICs. The host system is a RHEL6 Intel based x200 laptop.
Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.71.el6.x86_64
kernel-2.6.32-33.el6.x86_64
libvirt-0.8.1-7.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. install a RHEL3.9 i386 guest with 2 vcpu and 1G memory.
2. setup and trigger netdump from the guest.
Comment 4RHEL Program Management
2010-06-13 01:32:57 UTC
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.
Tested with latest build:
======================================================================
[root@ibm-hs21-01 ~]# rpm -q qemu-kvm libvirt kernel
qemu-kvm-0.12.1.2-2.120.el6.x86_64
libvirt-0.8.1-27.el6.x86_64
kernel-2.6.32-83.el6.x86_64
Guest is RHEL3-U9 with 2 vcpu and 1G memory.
Netdump success to dump vmcore, no hang was found.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: missing support for secrc field on e1000 emulation.
Consequence: Triggering netdump on a RHEL3 i386 guest, it failed when using e1000 NIC emulation.
Fix: Added support for secrc field on e1000 emulation code.
Result: netdump on RHEL3 guests using e1000 emulation now work.
Hi,Moritoshi
It is PM not QE to decide whether this can be go into z-steam.
BTW, RHEL6.1 release is around the corner and the fix is in it, so i don't think it is necessary to fix it in rhel6.0.z, thanks, :).
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0534.html
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0534.html