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.
+++ This bug was initially created as a clone of Bug #506899 +++
Description of problem:
With a line like
disk = ['tap:aio:/....,xvda,w', 'phy:/dev/cdrom,hdc:cdrom,r' ]
in the Xen configuration and no physical CDROM in the tray, the PV guest will wait for the 300 seconds timeout to occur
Version-Release number of selected component (if applicable):
5.4
How reproducible:
Add the 'phy:/dev/cdrom,hdc:cdrom,r' item to an existing PV configuration and start the VM.
Actual results:
300 seconds timeout
Expected results:
No timeout.
Additional info:
The bug is probably due to the device being Closed (as shown by the timeout message) but not ready. The configuration is quite bogus, but this is a regression and, if my diagnosis is right, the fix should be easy and safe.
--- Additional comment from berrange on 2009-06-19 06:38:38 EDT ---
Is this really a regression - have you verified that this works in RHEL-5.3 ?
I'm surprised if this has ever worked, since AFAIK the Xen version RHEL5 is based on has never supported CDROM devices for paravirt guests. It was only added later when Solaris paravirt support CDROm devices.
That all said, timeouts are always the wrong answer to unsupported features - there should be explicit error message given back where required. In this case though, since the host does not really know whether the guest supports CDROM or not, it would have to attach it anyway and just hope the guest knows what todo with it.
--- Additional comment from pbonzini on 2009-06-19 07:04:41 EDT ---
The regression is that it takes 300 seconds instead of 10 to boot. The configuration is bogus indeed.
--- Additional comment from berrange on 2009-06-19 07:10:20 EDT ---
The fact that the length of the timeout changed does not really make this is regression. It was broken before & it is still broken now.
Comment 2RHEL Program Management
2009-09-14 09:56:46 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.
Bug 523630 - [RHEL6 Xen]: Forward port 5 minute timeout for device connection was created and used for the same bug. Closing this one as a duplicate.
*** This bug has been marked as a duplicate of bug 523630 ***