From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: VIA Nano support
Date: Sun, 02 May 2010 09:05:28 +0300
Message-ID: <4BDD1628.5060004@redhat.com>
References: <t2mf9c482c41004251814s3d16aa16h73ccd3f50b07c31b@mail.gmail.com> <4BD53C0A.7070102@redhat.com> <loom.20100502T003957-585@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Yuhong Bao <yuhongbao_386@hotmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:20632 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754337Ab0EBGFc (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 2 May 2010 02:05:32 -0400
In-Reply-To: <loom.20100502T003957-585@post.gmane.org>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 05/02/2010 01:40 AM, Yuhong Bao wrote:
>> It's a known bug in the Nano's vmx implementation.
>>      
> Any details or workarounds?
>    

There's a bug in the vm86/vmx interaction that happens to hit kvm.  No 
known workarounds.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.