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.
Description of problem:
When PXE booting a VM using a pcnet emulated interface, the VM enters a paused state and cannot be unpaused.
Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.90.el6.x86_64
How reproducible:
Every time.
Steps to Reproduce:
1. Create a VM with a pcnet NIC.
2. PXE boot it.
Actual results:
VM pauses at:
gPXE initialising devices...
pcnet32.c: Found pcnet32, Vendor=0x1022 Device=0x2000
10
Expected results:
Link should be initiated and DHCP invoked.
Additional info:
Changing the emulated NIC type fixes the problem.
(In reply to comment #3)
> Does the part in the "Additional info" section of the original post answer your
> question?
yes, sorry for missing it.
Is there a reason for you to pick pcnet specifically?
It seems very shoddy and unprofessional to have things that are broken in an enterprise distribution. The pcnet emulation should either be fixed or removed completely. Having it broken yet existing as an option is the worst possible thing to do.
Bug 620657 - Unsupported device uses need to be documented in release notes
The above bug depicts the supported devices. Pcnet is not one of them.
At the time it was too intrusive to remove pcnet from the code so we used release notes approach for it. Sorry for the noise.
IMO, treating "documented as broken" as a "fix" is perhaps something that might be good enough as a bodge on Fedora, but it really doesn't do much good for the perception of quality in what is supposed to be an enterprise grade distribution that has been in stabilization and polish process for over a year.
It's documented as not supported.
I admit that we should have compiled it out but there are other restrictions to consider - we're 100% open source and we like to stay close as possible to upstream. There are times where we manage to change upstream on time so it will be easy to configure features out. This was not the case so this was the mechanism we used this time.
We never intended to support it since there are other better alternatives.
As you can see the alternatives should be fixed in respect to gPxe so that's why we like to focus on fewer/better devices than what's supported upstream.
On a perfect world, this should have been compiled out. You're right here.