Bug 22236 - CD-ROM not accessible from VMware Windows NT guest
Summary: CD-ROM not accessible from VMware Windows NT guest
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel   
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
high
high
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-13 16:26 UTC by ken_laird
Modified: 2005-10-31 22:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-05 22:43:47 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description ken_laird 2000-12-13 16:26:43 UTC 
I realize that RedHat is not responsible for VMware; however, the
successful operation of VMware with RedHat Linux is critical to our plans
to deploy
Linux workstations here at the Spokane site of Agilent Technologies.  And,
something that changed between release 6.2 and 7.0 has rendered the CD-ROM
drive essentially inaccessible from a VMware guest machine.  I have filed
an incident with VMware as well, of course.  I think it would behoove
RedHat to 
look into this as well.

	If I "disconnect" the CD-ROM in the VMware window, I can successfully
mount, unmount, and access it from Linux.   The VMware windows NT
guest, on the other hand reports the following errors in its log:
Dec 05 15:19:06: DISK/CDROM timeout of 2.790 seconds (ok)
Dec 05 15:19:06: ATAPI_CDROM: read for /dev/cdrom failed: Invalid argument

	I did make sure that the CD was unmounted in the Linux host OS and that
autorun was not going.
Comment 1 Arjan van de Ven 2001-01-04 15:53:39 UTC 
This is a duplicate of bug 21577
VMWare seems require either a kernel <= 2.2.15 or >= 2.2.17 for the CDROM
to work.
Comment 2 Alan Cox 2003-06-05 22:44:13 UTC 
Both vmware and the kernel have moved far on since this issue
Note You need to log in before you can comment on or make changes to this bug.