From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 2/2] scsi-bus: Convert DeviceClass init to realize
Date: Mon, 11 Aug 2014 15:32:14 +0100 [thread overview]
Message-ID: <20140811143214.GC496@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1407746718-16527-3-git-send-email-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
On Mon, Aug 11, 2014 at 04:45:18PM +0800, Fam Zheng wrote:
> diff --git a/tests/qemu-iotests/051.out b/tests/qemu-iotests/051.out
> index d7b0f50..f6d9dc1 100644
> --- a/tests/qemu-iotests/051.out
> +++ b/tests/qemu-iotests/051.out
> @@ -122,7 +122,7 @@ QEMU_PROG: -drive if=virtio: Device 'virtio-blk-pci' could not be initialized
>
> Testing: -drive if=scsi
> QEMU X.Y.Z monitor - type 'help' for more information
> -(qemu) QEMU_PROG: -drive if=scsi: Device needs media, but drive is empty
> +(qemu) QEMU_PROG: Device needs media, but drive is empty
> QEMU_PROG: Device initialization failed.
> QEMU_PROG: Initialization of device lsi53c895a failed
>
Have you checked where error_report()'s "location" was set to "-drive
if=scsi"?
Maybe something similar can be implemented.
> @@ -149,13 +149,11 @@ QEMU_PROG: -device ide-hd,drive=disk: Device 'ide-hd' could not be initialized
> Testing: -drive if=none,id=disk -device lsi53c895a -device scsi-disk,drive=disk
> QEMU X.Y.Z monitor - type 'help' for more information
> (qemu) QEMU_PROG: -device scsi-disk,drive=disk: Device needs media, but drive is empty
> -QEMU_PROG: -device scsi-disk,drive=disk: Device initialization failed.
> QEMU_PROG: -device scsi-disk,drive=disk: Device 'scsi-disk' could not be initialized
>
> Testing: -drive if=none,id=disk -device lsi53c895a -device scsi-hd,drive=disk
> QEMU X.Y.Z monitor - type 'help' for more information
> (qemu) QEMU_PROG: -device scsi-hd,drive=disk: Device needs media, but drive is empty
> -QEMU_PROG: -device scsi-hd,drive=disk: Device initialization failed.
> QEMU_PROG: -device scsi-hd,drive=disk: Device 'scsi-hd' could not be initialized
Not a big loss, I found the generic "Device initialization failed"
followed by a specific error message pointless. After this patch we
only get the specific error message. I'm happy with that.
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-08-11 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 8:45 [Qemu-devel] [PATCH v3 0/2] scsi: Change device init to realize Fam Zheng
2014-08-11 8:45 ` [Qemu-devel] [PATCH v3 1/2] block: Pass errp in blkconf_geometry Fam Zheng
2014-08-11 11:20 ` Andreas Färber
2014-08-11 14:24 ` Stefan Hajnoczi
2014-08-11 8:45 ` [Qemu-devel] [PATCH v3 2/2] scsi-bus: Convert DeviceClass init to realize Fam Zheng
2014-08-11 14:32 ` Stefan Hajnoczi [this message]
2014-08-12 2:04 ` Fam Zheng
2014-08-12 8:59 ` Stefan Hajnoczi
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=20140811143214.GC496@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).