CD-ROM errors (2.0 beta)
Bill Wohler
problems. Hit eject. Get a Linux-side pop-up warning whose title is
VMware Warning and contents is:
The cdrom drive failed to eject the disc with the error: 'Device
or resource busy'. Please make sure the CDROM is not in use by the
host or Attached to any other virtual machines.
That's bug #1 (buglet #2 is that the A in attached should be
downcased). Then I then have to hit the OK button 30 times to
dismiss the dialog! That's bug #3. No messages are logged to syslog
(besides the normal "VFS: Disk change detected" message when
connecting and disconnecting).
The workaround to eject the disc is to disconnect the CD-ROM and
eject via the CD player on the Linux side.
Bug #4: I got this group of errors in my syslog about 400 times in a
7 hour period. I haven't gotten it since I turned off "Auto insert
notification" in Win98.
Feb 8 10:39:14 gbr kernel: hda: command error: status=0x51 { DriveReady SeekComplete Error }
Feb 8 10:39:14 gbr kernel: hda: command error: error=0x54
Feb 8 10:39:14 gbr kernel: end_request: I/O error, dev 03:00 (hda), sector 68
Feb 8 10:39:14 gbr kernel: ATAPI device hda:
Feb 8 10:39:14 gbr kernel: Error: Illegal request -- (Sense key=0x05)
Feb 8 10:39:14 gbr kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
Running Debian GNU/Linux 2.1 with kernel 2.2.1. VMware 2.0 beta
build 440.
--
Bill Wohler <woh...@newt.com>
Say it with MIME. Maintainer of comp.mail.mh and news.software.nn FAQs.
If you're passed on the right, you're in the wrong lane.
Jeremy.
> Connect the IDE CD-ROM, fire up the CD player, play a CD. No
> problems. Hit eject. Get a Linux-side pop-up warning whose title is
> VMware Warning and contents is:
>
> The cdrom drive failed to eject the disc with the error: 'Device
> or resource busy'. Please make sure the CDROM is not in use by the
> host or Attached to any other virtual machines.
>
> That's bug #1 (buglet #2 is that the A in attached should be
> downcased). Then I then have to hit the OK button 30 times to
> dismiss the dialog! That's bug #3. No messages are logged to syslog
> (besides the normal "VFS: Disk change detected" message when
> connecting and disconnecting).
If you have a 2.2.14 kernel, you'll find that the 2.0 beta is incapable of
unlocking the CDROM door and probably incapable of ejecting because the
linux kernel driver changed. This is already fixed internally. You get the
message repeatedly becasue you get it once for each failed attempt by the
(fairly stubborn) CD Player in the virtual machine. Once the first problem
goes away, the second will as well.
>
> Bug #4: I got this group of errors in my syslog about 400 times in a
> 7 hour period. I haven't gotten it since I turned off "Auto insert
> notification" in Win98.
>
>Feb 8 10:39:14 gbr kernel: hda: command error: status=0x51 { DriveReady SeekComplete Error }
>Feb 8 10:39:14 gbr kernel: hda: command error: error=0x54
>Feb 8 10:39:14 gbr kernel: end_request: I/O error, dev 03:00 (hda), sector 68
>Feb 8 10:39:14 gbr kernel: ATAPI device hda:
>Feb 8 10:39:14 gbr kernel: Error: Illegal request -- (Sense key=0x05)
>Feb 8 10:39:14 gbr kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
It's unclear to me how that's a bug. The VM requests that VMware check the
drive for a CDROM, VMware asks the kernel if there's a CDROM, and in the
process of detecting whether it's a data or audio cdrom, the kernel manages
to taunt itself into printing that message. If you disconnect the CDROM or
disable the auto insert notification then, as you discovered, the messages
stop.
Yours,
Jeremy.
Bill Wohler
> >Feb 8 10:39:14 gbr kernel: hda: command error: status=0x51 { DriveReady SeekComplete Error }
> >Feb 8 10:39:14 gbr kernel: hda: command error: error=0x54
> >Feb 8 10:39:14 gbr kernel: end_request: I/O error, dev 03:00 (hda), sector 68
> >Feb 8 10:39:14 gbr kernel: ATAPI device hda:
> >Feb 8 10:39:14 gbr kernel: Error: Illegal request -- (Sense key=0x05)
> >Feb 8 10:39:14 gbr kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
>
> It's unclear to me how that's a bug. The VM requests that VMware check the
> drive for a CDROM, VMware asks the kernel if there's a CDROM, and in the
> process of detecting whether it's a data or audio cdrom, the kernel manages
> to taunt itself into printing that message. If you disconnect the CDROM or
> disable the auto insert notification then, as you discovered, the messages
Makes sense. I suppose the bug is that Win98 doesn't back off when
it can't communicate with the CDROM.