From: David Ahern <daahern@cisco.com>
To: Avi Kivity <avi@redhat.com>, aliguori@us.ibm.com
Cc: qemu-devel <qemu-devel@nongnu.org>,
KVM mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] qemu-kvm aborts - vhost_dev_unassign_memory: Assertion `to >= 0' failed.
Date: Mon, 01 Aug 2011 12:04:41 -0600 [thread overview]
Message-ID: <4E36EAB9.3010807@cisco.com> (raw)
In-Reply-To: <4E36E5F7.6060202@cisco.com>
On 08/01/2011 11:44 AM, David Ahern wrote:
> qemu-kvm.git as of:
>
> commit dacdc4b10bafbb21120e1c24a9665444768ef999
> Merge: 7b69d4f 0af4922
> Author: Avi Kivity <avi@redhat.com>
> 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
BTW, happens when I pass a kernel and initrd on the command line.
qemu-kvm -kernel vmlinuz -initrd initrd.img ...
David
>
> $ git bisect bad
> 00cb2a99f5e7f73c4fff54ae16c7b6acf463ab5c is the first bad commit
> commit 00cb2a99f5e7f73c4fff54ae16c7b6acf463ab5c
> Author: Avi Kivity <avi@redhat.com>
> Date: Tue Jul 26 14:26:17 2011 +0300
>
> pc: convert pc_memory_init() to memory API
>
> Reviewed-by: Anthony Liguori <aliguori@us.ibm.com>
> Signed-off-by: Avi Kivity <avi@redhat.com>
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>
> :040000 040000 3d709c2cab75b934030fb9fbdfa99024c855b2a6
> 720d362f9702f15d16519093555182169d0b09bd M hw
>
next prev parent reply other threads:[~2011-08-01 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 17:44 [Qemu-devel] qemu-kvm aborts - vhost_dev_unassign_memory: Assertion `to >= 0' failed David Ahern
2011-08-01 18:04 ` David Ahern [this message]
2011-08-03 9:01 ` Avi Kivity
2011-08-03 9:33 ` Wen Congyang
2011-08-03 11:48 ` Avi Kivity
2011-08-03 12:24 ` Michael S. Tsirkin
2011-08-03 13:55 ` David Ahern
2011-08-03 15:00 ` Michael S. Tsirkin
2011-08-04 18:48 ` David Ahern
2011-08-04 19:17 ` Michael S. Tsirkin
2011-08-04 19:23 ` David Ahern
2011-08-03 13:07 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E36EAB9.3010807@cisco.com \
--to=daahern@cisco.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).