From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: [bug 1.1] -M pc-1.0 + vhost = SIGSEGV
Date: Sun, 01 Jul 2012 19:26:45 +0400
Message-ID: <4FF06C35.2010908@msgid.tls.msk.ru>
References: <4FF06770.905@msgid.tls.msk.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
To: KVM list <kvm@vger.kernel.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from isrv.corpit.ru ([86.62.121.231]:48817 "EHLO isrv.corpit.ru"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1750837Ab2GAP0r (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 1 Jul 2012 11:26:47 -0400
In-Reply-To: <4FF06770.905@msgid.tls.msk.ru>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 01.07.2012 19:06, Michael Tokarev wrote:
> When running current git version of qemu-kvm with -M pc-1.0
> and with vhost-net enabled, it crashes with SIGSEGV right when
> linux guest loads a virtio-net module.

And when this happens when a persistent tap device is used,
that tap device becomes unusable until removed and recreated --
it "works" but no network packet goes on.  So it looks like
we've two bugs, one in userspace qemu 1.1 and another in
host kernel (3.0).

Thanks,

/mjt