From: John Snow <1863441@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1863441] Re: cmd_mode_sense always reports 0x70, no CDROM present
Date: Fri, 10 Apr 2020 02:56:39 -0000 [thread overview]
Message-ID: <158648739981.5491.10260814958879587102.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 158179973601.15520.14709037359293558924.malonedeb@soybean.canonical.com
Roger that, thanks!
I don't think we're very careful about which version we try to emulate.
In practice it's "Whatever seems to work across the largest swatch of
guest operating systems simultaneously".
If this comes up again, feel free to file against a specific guest OS
that appears to be non-functioning.
Thanks!
--js
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1863441
Title:
cmd_mode_sense always reports 0x70, no CDROM present
Status in QEMU:
New
Bug description:
cmd_mode_sense
https://git.qemu.org/?p=qemu.git;a=blob;f=hw/ide/atapi.c;hb=refs/heads/master#l852
always reports 0x70 in byte 2 returned, indicating no CD-ROM present.
If CD-ROM is present, should report 0x01 (or 0x11).
If CD-ROM absent, should report 0x70.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1863441/+subscriptions
next prev parent reply other threads:[~2020-04-10 3:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 20:48 [Bug 1863441] [NEW] cmd_mode_sense always reports 0x70, no CDROM present Benjamin David Lunt
2020-04-06 19:21 ` [Bug 1863441] " John Snow
2020-04-07 2:01 ` Benjamin David Lunt
2020-04-10 2:56 ` John Snow [this message]
2020-04-11 12:18 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=158648739981.5491.10260814958879587102.malone@chaenomeles.canonical.com \
--to=1863441@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).