From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: daggs <daggs@gmx.com>, qemu-discuss@nongnu.org
Cc: qemu-devel <qemu-devel@nongnu.org>, Qemu-block <qemu-block@nongnu.org>
Subject: Re: cdrom scsi passthough not working well
Date: Wed, 3 Feb 2021 17:48:52 +0100 [thread overview]
Message-ID: <46ec2226-2e5b-4e73-9b01-4e55f1f1fcbc@redhat.com> (raw)
In-Reply-To: <trinity-9b27278b-c96f-472f-a115-9bf29b44c103-1603862318112@3c-app-mailcom-bs15>
Cc'ing qemu-block@ developers.
On 10/28/20 6:18 AM, daggs wrote:
> Greetings,
>
> I have a vm running under qemu 5.1.0 with a cdrom scsi passthough into it.
> I can eject the device in and out but when I insert a disc, is isn't detected and the dmesg on the guest is filled with these prints:
> [384216.443262] sr 0:0:0:0: ioctl_internal_command return code = 8000002
> [384216.443268] sr 0:0:0:0: Sense Key : 0xb [current]
> [384216.443272] sr 0:0:0:0: ASC=0x0 ASCQ=0x6
> [384218.504142] sr 0:0:0:0: ioctl_internal_command return code = 8000002
> [384218.504150] sr 0:0:0:0: Sense Key : 0xb [current]
> [384218.504153] sr 0:0:0:0: ASC=0x0 ASCQ=0x6
> [384220.561302] sr 0:0:0:0: ioctl_internal_command return code = 8000002
> [384220.561308] sr 0:0:0:0: Sense Key : 0xb [current]
> [384220.561312] sr 0:0:0:0: ASC=0x0 ASCQ=0x6
>
> the vm is uefi q35 based, generated by libvirt 6.8.0, the cdrom part is this:
> -blockdev {"driver":"host_device","filename":"/dev/sg0","node-name":"libvirt-2-backend","read-only":true}
> -device scsi-generic,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=libvirt-2-backend,id=hostdev0
>
> id there something bad with the config or have I encountered a bug?
>
> Thanks,
>
> Dagg.
>
next parent reply other threads:[~2021-02-03 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <trinity-9b27278b-c96f-472f-a115-9bf29b44c103-1603862318112@3c-app-mailcom-bs15>
2021-02-03 16:48 ` Philippe Mathieu-Daudé [this message]
2021-02-03 16:56 ` cdrom scsi passthough not working well daggs
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=46ec2226-2e5b-4e73-9b01-4e55f1f1fcbc@redhat.com \
--to=philmd@redhat.com \
--cc=daggs@gmx.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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).