From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Lieven <pl@kamp.de>
Cc: qemu-devel <qemu-devel@nongnu.org>, qemu block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block] RFC cdrom in own thread?
Date: Tue, 16 Jun 2015 16:34:42 +0100 [thread overview]
Message-ID: <CAJSP0QXmsS4K0G-sByQYnLn6Uv5cYKS+47qxGtgsoYQJL1noOg@mail.gmail.com> (raw)
In-Reply-To: <55803637.3060607@kamp.de>
On Tue, Jun 16, 2015 at 3:44 PM, Peter Lieven <pl@kamp.de> wrote:
> I wonder how difficult it would be to have the IDE CDROM run in its own
> thread?
> We usually have ISOs mounted on an NFS share as CDROM. Problem: If the NFS
> Share
> goes down, it takes down monitor, qmp, vnc etc. with it.
>
> Maybe its already possible to do this via cmdline args?
>
> Any ideas, comments?
If QEMU hangs in the read/write/flush/discard code path due to NFS
downtime it is a bug.
QEMU is expected to hang in open/reopen because those are performed in
a blocking fashion.
Which of these cases applies to what you are seeing? Maybe it can be fixed.
Stefan
next parent reply other threads:[~2015-06-16 15:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55803637.3060607@kamp.de>
2015-06-16 15:34 ` Stefan Hajnoczi [this message]
2015-06-17 8:35 ` [Qemu-devel] [Qemu-block] RFC cdrom in own thread? Kevin Wolf
2015-06-18 6:03 ` Peter Lieven
2015-06-18 6:57 ` Markus Armbruster
2015-06-18 6:39 ` Peter Lieven
2015-06-18 6:59 ` Paolo Bonzini
2015-06-18 7:03 ` Peter Lieven
2015-06-18 7:12 ` Peter Lieven
2015-06-18 7:45 ` Kevin Wolf
2015-06-18 8:30 ` Peter Lieven
2015-06-18 8:42 ` Kevin Wolf
2015-06-18 9:29 ` Peter Lieven
2015-06-18 9:36 ` Stefan Hajnoczi
2015-06-18 9:53 ` Peter Lieven
2015-06-19 13:14 ` Peter Lieven
2015-06-22 9:25 ` Stefan Hajnoczi
2015-06-22 13:09 ` Peter Lieven
2015-06-22 21:54 ` John Snow
2015-06-23 6:36 ` Peter Lieven
2015-08-14 13:43 ` Peter Lieven
2015-08-14 14:08 ` Kevin Wolf
2015-08-14 14:21 ` Peter Lieven
2015-08-14 14:45 ` Peter Lieven
2015-08-15 19:02 ` Peter Lieven
2015-06-18 10:17 ` Peter Lieven
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=CAJSP0QXmsS4K0G-sByQYnLn6Uv5cYKS+47qxGtgsoYQJL1noOg@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--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 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.