From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] lguest: fix on Intel when KVM loaded (unhandled trap 13) Date: Tue, 26 May 2009 16:54:25 +0300 Message-ID: <4A1BF491.1090501@redhat.com> References: <200905262054.42566.rusty@rustcorp.com.au> <20090526123914.1823adae@lxorguk.ukuu.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Cc: lguest , Linus Torvalds , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kvm-devel To: Alan Cox Return-path: In-Reply-To: <20090526123914.1823adae-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: lguest-bounces+glkvl-lguest=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org Errors-To: lguest-bounces+glkvl-lguest=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org List-Id: kvm.vger.kernel.org Alan Cox wrote: > On Tue, 26 May 2009 20:54:41 +0930 > Rusty Russell wrote: > > >> When KVM is loaded, and hence VT set up, the vmcall instruction in an >> lguest guest causes a #GP, not #UD. >> >> Signed-off-by: Rusty Russell >> > > Shouldn't that be fixed in KVM ? > KVM never saw that VMCALL or #GP. -- error compiling committee.c: too many arguments to function