From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: qemu-kvm aborts - vhost_dev_unassign_memory: Assertion `to >= 0' failed. Date: Thu, 4 Aug 2011 22:17:17 +0300 Message-ID: <20110804191717.GB25722@redhat.com> References: <4E36E5F7.6060202@cisco.com> <4E393575.4090003@redhat.com> <20110803122441.GB10538@redhat.com> <4E395363.5000200@cisco.com> <20110803150021.GA13515@redhat.com> <4E3AE991.1080009@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: aliguori@us.ibm.com, Avi Kivity , KVM mailing list , qemu-devel To: David Ahern Return-path: Content-Disposition: inline In-Reply-To: <4E3AE991.1080009@cisco.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org On Thu, Aug 04, 2011 at 12:48:49PM -0600, David Ahern wrote: > > > On 08/03/2011 09:00 AM, Michael S. Tsirkin wrote: > > On Wed, Aug 03, 2011 at 07:55:47AM -0600, David Ahern wrote: > >> Tested-by: David Ahern > >> > >> David > > > > Applied, thanks very much. > > > > I assume this will make 0.15 since it is a regression? How is this a regression in 0.15? I thought it's an old bug exposed by the memory API which I expect is not going into 0.15. > haven't seen the > patch applied to that branch yet. > > David My branch will have to get merged in trunk first. -- MST