From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35472) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z4ssz-0004BW-MK for qemu-devel@nongnu.org; Tue, 16 Jun 2015 11:34:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z4sst-0000vT-Mi for qemu-devel@nongnu.org; Tue, 16 Jun 2015 11:34:49 -0400 MIME-Version: 1.0 In-Reply-To: <55803637.3060607@kamp.de> References: <55803637.3060607@kamp.de> Date: Tue, 16 Jun 2015 16:34:42 +0100 Message-ID: From: Stefan Hajnoczi Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [Qemu-block] RFC cdrom in own thread? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven Cc: qemu-devel , qemu block On Tue, Jun 16, 2015 at 3:44 PM, Peter Lieven 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