From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:46728) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qob9e-0007fg-KH for qemu-devel@nongnu.org; Wed, 03 Aug 2011 09:06:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qob9d-0000bB-Ip for qemu-devel@nongnu.org; Wed, 03 Aug 2011 09:06:34 -0400 Received: from mx1.redhat.com ([209.132.183.28]:28824) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qob9d-0000b2-9J for qemu-devel@nongnu.org; Wed, 03 Aug 2011 09:06:33 -0400 Date: Wed, 3 Aug 2011 16:07:06 +0300 From: "Michael S. Tsirkin" Message-ID: <20110803130706.GA12262@redhat.com> References: <4E36E5F7.6060202@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E36E5F7.6060202@cisco.com> Subject: Re: [Qemu-devel] qemu-kvm aborts - vhost_dev_unassign_memory: Assertion `to >= 0' failed. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Ahern Cc: aliguori@us.ibm.com, Avi Kivity , KVM mailing list , qemu-devel On Mon, Aug 01, 2011 at 11:44:23AM -0600, David Ahern wrote: > qemu-kvm.git as of: > > commit dacdc4b10bafbb21120e1c24a9665444768ef999 > Merge: 7b69d4f 0af4922 > Author: Avi Kivity > Date: Sun Jul 31 11:42:26 2011 +0300 > > Merge branch 'upstream-merge' into next > > is aborting with the error: > > qemu-kvm: qemu-kvm.git/hw/vhost.c:123: vhost_dev_unassign_memory: > Assertion `to >= 0' failed. > Aborted > > $ git bisect bad > 00cb2a99f5e7f73c4fff54ae16c7b6acf463ab5c is the first bad commit > commit 00cb2a99f5e7f73c4fff54ae16c7b6acf463ab5c > Author: Avi Kivity > Date: Tue Jul 26 14:26:17 2011 +0300 > > pc: convert pc_memory_init() to memory API > > Reviewed-by: Anthony Liguori > Signed-off-by: Avi Kivity > Signed-off-by: Anthony Liguori > > :040000 040000 3d709c2cab75b934030fb9fbdfa99024c855b2a6 > 720d362f9702f15d16519093555182169d0b09bd M hw > Thanks for the report. As Avi pointed out it's a vhost bug that got exposed by a memory API change. I have posted a patch which should fix that problem - could you please try it and let me know? Thanks! -- MST