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.
(In reply to Gerd Hoffmann from comment #2)
> Identifiers must start with a letter, so '111a' isn't considered an valid id.
Hi, Gerd
I test this in a rhel6.5/rhel6.4 host, the 111a can be used, so I filed this bug.
Can we unify the rule for these 2 products?
If identifiers must start with a letter in both rhel6 and rhel7 hosts, we should file a bug against rhel6.
So do we need file a bug against rhel6 or reopen this bug for rhel7?
Thanks!
Qian Guo
qemu got better at checking parameters over time, so rhel7 can be more strict than rhel6. So, yes, rhel6 should refuse to accept those too in theory. I doubt it is worth bothering though.
(In reply to Gerd Hoffmann from comment #4)
> qemu got better at checking parameters over time, so rhel7 can be more
> strict than rhel6. So, yes, rhel6 should refuse to accept those too in
> theory. I doubt it is worth bothering though.
Hi, Gerd
Thank you for your reply, and I found all virtual devices/drivers must start w/ letter in rhel7 and need not in rhel6, so I will file a low low bug in rhel6 to track.
Since this is just a bug about the rule of identifiers, I will change the bug summary.
Thank you
Qian Guo.