From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Stefan Hajnoczi <stefanha@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Peter Lieven <pl@kamp.de>, qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PULL for-2.4 3/7] block/nfs: add support for setting debug level
Date: Wed, 8 Jul 2015 19:48:58 +0200 [thread overview]
Message-ID: <559D628A.6000605@redhat.com> (raw)
In-Reply-To: <20150707134057.GF14035@noname.redhat.com>
On 07.07.2015 15:40, Kevin Wolf wrote:
> Am 07.07.2015 um 15:13 hat Stefan Hajnoczi geschrieben:
>> On Tue, Jul 7, 2015 at 1:50 PM, Peter Lieven <pl@kamp.de> wrote:
>>> Am 07.07.2015 um 14:08 schrieb Stefan Hajnoczi:
>>>>
>>>> From: Peter Lieven <pl@kamp.de>
>>>>
>>>> upcoming libnfs versions will support logging debug messages. Add
>>>> support for it in qemu through a per-drive option.
>>>>
>>>> Examples:
>>>> qemu -drive if=virtio,file=nfs://...,file.debug=2
>>>> qemu-img create -o debug=2 nfs://... 10G
>>>>
>>>> Signed-off-by: Peter Lieven <pl@kamp.de>
>>>> Reviewed-by: Fam Zheng <famz@redhat.com>
>>>> Message-id: 1436251847-16875-1-git-send-email-pl@kamp.de
>>>> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>>>
>>>
>>> Thanks for pulling this.
>>>
>>> Question: Is it possible to insert a CDROM other than with the 'change'
>>> command?
>>> The change command obviously does not support file.debug parameters...
>>
>> Not that I'm aware of.
>>
>> You may be able to hotplug SCSI CD-ROM drives, but that's not the same
>> as ejecting/inserting CD-ROM media.
>>
>> Sounds like an item for the block layer todo list:
>> http://qemu-project.org/Features/Block/Todo
>
> I think Max' media handling series might implement this or at least go a
> step in that direction. CCing Max.
Since with that series, you can insert any BDS as a medium, yes, it
naturally does.
But for now, wouldn't JSON file names work?
Max
next prev parent reply other threads:[~2015-07-08 17:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 12:08 [Qemu-devel] [PULL for-2.4 0/7] Block patches Stefan Hajnoczi
2015-07-07 12:08 ` [Qemu-devel] [PULL for-2.4 1/7] qcow2: remove unnecessary check Stefan Hajnoczi
2015-07-07 12:08 ` [Qemu-devel] [PULL for-2.4 2/7] block: update bdrv_drain_all()/bdrv_drain() comments Stefan Hajnoczi
2015-07-07 12:08 ` [Qemu-devel] [PULL for-2.4 3/7] block/nfs: add support for setting debug level Stefan Hajnoczi
2015-07-07 12:50 ` Peter Lieven
2015-07-07 13:13 ` Stefan Hajnoczi
2015-07-07 13:40 ` Kevin Wolf
2015-07-08 17:48 ` Max Reitz [this message]
2015-07-07 13:24 ` Stefan Hajnoczi
2015-07-07 13:41 ` Peter Lieven
2015-07-07 13:45 ` Kevin Wolf
2015-07-21 22:38 ` Eric Blake
2015-07-21 22:37 ` Eric Blake
2015-07-07 12:08 ` [Qemu-devel] [PULL for-2.4 4/7] block: Initialize local_err in bdrv_append_temp_snapshot Stefan Hajnoczi
2015-07-07 12:08 ` [Qemu-devel] [PULL for-2.4 5/7] block: Use bdrv_drain to replace uncessary bdrv_drain_all Stefan Hajnoczi
2015-07-07 12:08 ` [Qemu-devel] [PULL for-2.4 6/7] block/raw-posix: Don't think /dev/fd/<NN> is a floppy drive Stefan Hajnoczi
2015-07-07 12:08 ` [Qemu-devel] [PULL for-2.4 7/7] blockjob: add block_job_release function 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=559D628A.6000605@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.