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 <avi@xxxxxxxxxx> > 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 <avi@xxxxxxxxxx> > Date: Tue Jul 26 14:26:17 2011 +0300 > > pc: convert pc_memory_init() to memory API > > Reviewed-by: Anthony Liguori <aliguori@xxxxxxxxxx> > Signed-off-by: Avi Kivity <avi@xxxxxxxxxx> > Signed-off-by: Anthony Liguori <aliguori@xxxxxxxxxx> > > :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 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
