----- Messaggio originale ----- > Da: "Stefan Hajnoczi" <stefa...@gmail.com> > A: "Paolo Bonzini" <pbonz...@redhat.com> > Cc: "Badari Pulavarty" <pbad...@us.ibm.com>, "Asias He" <as...@redhat.com>, > "Nicholas A. Bellinger" > <n...@linux-iscsi.org>, "qemu-devel" <qemu-devel@nongnu.org>, "Gleb Natapov" > <g...@redhat.com> > Inviato: Giovedì, 23 maggio 2013 19:18:26 > Oggetto: Re: qemu seabios issue with vhost-scsi > > On Thu, May 23, 2013 at 6:47 PM, Paolo Bonzini <pbonz...@redhat.com> wrote: > > Il 23/05/2013 18:38, Badari Pulavarty ha scritto: > >>> If that is with the old SeaBIOS, then SIGABRT is intended. :) The guest > >>> 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. > > 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
