From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:35062) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UfZMD-0002jV-Ch for qemu-devel@nongnu.org; Thu, 23 May 2013 13:31:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UfZMC-0001Wn-Aa for qemu-devel@nongnu.org; Thu, 23 May 2013 13:31:17 -0400 Received: from mx3-phx2.redhat.com ([209.132.183.24]:49476) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UfZMC-0001Wi-3z for qemu-devel@nongnu.org; Thu, 23 May 2013 13:31:16 -0400 Date: Thu, 23 May 2013 13:31:12 -0400 (EDT) From: Paolo Bonzini Message-ID: <691725107.6754511.1369330272368.JavaMail.root@redhat.com> In-Reply-To: References: <519D6478.8060403@us.ibm.com> <20130523152758.GA21158@hj.localdomain> <519E361B.9070702@redhat.com> <519E3FCE.5040401@us.ibm.com> <519E4197.7030605@redhat.com> <519E45F3.4070709@us.ibm.com> <519E4808.6040403@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] qemu seabios issue with vhost-scsi List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Asias He , Badari Pulavarty , qemu-devel , "Nicholas A. Bellinger" , Gleb Natapov ----- Messaggio originale ----- > Da: "Stefan Hajnoczi" > A: "Paolo Bonzini" > Cc: "Badari Pulavarty" , "Asias He" , "Nicholas A. Bellinger" > , "qemu-devel" , "Gleb Natapo= v" > Inviato: Gioved=C3=AC, 23 maggio 2013 19:18:26 > Oggetto: Re: qemu seabios issue with vhost-scsi >=20 > On Thu, May 23, 2013 at 6:47 PM, Paolo Bonzini wrot= e: > > Il 23/05/2013 18:38, Badari Pulavarty ha scritto: > >>> If that is with the old SeaBIOS, then SIGABRT is intended. :) The gu= est > >>> is buggy, the problem in QEMU only lies in _how_ it fails. > >>> > >>> Paolo > >>> > >>> > >> > >> I am confused now. Without above changes, seabios fix makes the > >> guest boot. But with the above changes, I run into this (even with > >> seabios fix) > > > > Ah, okay. I understood it crashed only with the SeaBIOS fix. > > > > I'll work on a more proper fix then. >=20 > Maybe use the same approach as data plane - activate vhost when > userspace sees the first virtqueue kick. That way it works with weird > guests and never aborts. Good idea. Paolo