From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60126) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UfVdD-0003pp-Ui for qemu-devel@nongnu.org; Thu, 23 May 2013 09:32:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UfVcy-0005ze-Av for qemu-devel@nongnu.org; Thu, 23 May 2013 09:32:35 -0400 Received: from mail-qe0-f52.google.com ([209.85.128.52]:54270) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UfVcy-0005zF-61 for qemu-devel@nongnu.org; Thu, 23 May 2013 09:32:20 -0400 Received: by mail-qe0-f52.google.com with SMTP id 1so1855782qec.39 for ; Thu, 23 May 2013 06:32:19 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20130523094809.GM4725@redhat.com> References: <519D6478.8060403@us.ibm.com> <20130523005355.GA11949@hj.localdomain> <20130523094809.GM4725@redhat.com> Date: Thu, 23 May 2013 15:32:19 +0200 Message-ID: From: Stefan Hajnoczi Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] qemu seabios issue with vhost-scsi List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: Asias He , Badari , qemu-devel , "Nicholas A. Bellinger" On Thu, May 23, 2013 at 11:48 AM, Gleb Natapov wrote: > On Thu, May 23, 2013 at 08:53:55AM +0800, Asias He wrote: >> On Wed, May 22, 2013 at 05:36:08PM -0700, Badari wrote: >> > Hi, >> > >> > While testing vhost-scsi in the current qemu git, ran into an earlier issue >> > with seabios. I had to disable scsi support in seabios to get it working. >> > >> > I was hoping this issue got resolved when vhost-scsi support got >> > merged into qemu. Is this still being worked on ? >> >> Hmm, can you try seabios.git? Not sure if seabios shipped by qemu picked >> up the fixes for vhost-scsi. >> > Nothing in seabios should crash qemu. Agreed. I'm pretty sure it's the scenario that I posted in my other reply to this thread. The common virtio-scsi code in QEMU should guard against this. In virtio-blk data plane I hit a similar case and ended up starting the data plane thread (equivalent to vhost here) *before* the status register is set to DRIVER_OK. Stefan