From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: KVM exit on UD interception Date: Wed, 07 May 2014 08:55:17 +0200 Message-ID: <5369D8D5.7020000@redhat.com> References: <53691446.7070706@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: "kvm@vger.kernel.org" To: =?UTF-8?B?QWxleGFuZHJ1IER1xaN1?= Return-path: Received: from mail-ee0-f46.google.com ([74.125.83.46]:38706 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753468AbaEGGzX (ORCPT ); Wed, 7 May 2014 02:55:23 -0400 Received: by mail-ee0-f46.google.com with SMTP id t10so349022eei.5 for ; Tue, 06 May 2014 23:55:22 -0700 (PDT) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: Il 06/05/2014 22:11, Alexandru Du=C5=A3u ha scritto: > What is puzzling thought is the fact that even if there is an > instruction that can't be emulated by KVM, re-entering virtualized > mode is still attempted. Re-entering will produce a double fault, That would be a bug. It should inject the #UD into the guest. Paolo