From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: lars.kurth.xen@gmail.com, xen-devel@lists.xenproject.org,
lars.kurth@xen.org, Jeff_Zimmerman@McAfee.com,
Ian.Campbell@citrix.com
Subject: Re: Intermittent fatal page fault with XEN 4.3.1 (Centos 6.3 DOM0 with linux kernel 3.10.16.)
Date: Thu, 7 Nov 2013 17:02:27 +0000 [thread overview]
Message-ID: <527BC7A3.7030405@citrix.com> (raw)
In-Reply-To: <527BD38E0200007800100DA4@nat28.tlf.novell.com>
On 07/11/13 16:53, Jan Beulich wrote:
>>>> On 07.11.13 at 17:02, <Jeff_Zimmerman@McAfee.com> wrote:
>> On Nov 7, 2013, at 7:57 AM, Jan Beulich <JBeulich@suse.com>
>> wrote:
>>
>>>>>> On 07.11.13 at 16:41, <Jeff_Zimmerman@McAfee.com> wrote:
>>>> On Nov 7, 2013, at 1:30 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>>>>> I was also wondering about the behaviour of using vmx instructions in a
>>>>> guest despite vmx not being visible in cpuid...
>>>>>
>>>> We have found in our situation this is exactly the case. To verify we wrote
>>>> some
>>>> test code that makes vmx calls without checking cupid. On bare hardware the
>>>> program
>>>> executes as expected. In a VM on Xen it causes the hypervisor to panic.
>>> You trying it doesn't yet imply that Windows also does so.
>>>
>>> Also, you say "program" - are you using these from user mode code?
>> Yes, from windows run as a privileged user. Windows XP sp3 can cause the
>> crash.
>> It seems windows 7 has better security, we cannot crash the system from a
>> win7 guest.
> Which is sort of odd. Anyway - care to try the attached patch?
>
> Jan
>
While the patch does look plausible, there is still clearly an issue
that an HVM guest with nested_virt disabled can even use the VMX
instructions, rather than getting flat out #UD exceptions.
~Andrew
next prev parent reply other threads:[~2013-11-07 17:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 19:54 Intermittent fatal page fault with XEN 4.3.1 (Centos 6.3 DOM0 with linux kernel 3.10.16.) Lars Kurth
2013-11-04 20:00 ` Andrew Cooper
2013-11-05 9:53 ` Ian Campbell
2013-11-05 10:04 ` Jan Beulich
2013-11-05 15:46 ` Lars Kurth
2013-11-05 21:55 ` Jeff_Zimmerman
[not found] ` <5E2B3362-4D93-4FEF-987A-E477B0DCEE51@mcafee.com>
2013-11-06 14:09 ` Jan Beulich
2013-11-06 16:05 ` Jeff_Zimmerman
2013-11-06 16:16 ` Jan Beulich
2013-11-06 16:18 ` Ian Campbell
2013-11-06 16:48 ` Jeff_Zimmerman
2013-11-06 16:54 ` Andrew Cooper
2013-11-06 17:06 ` Ian Campbell
2013-11-06 17:07 ` Andrew Cooper
2013-11-07 9:10 ` Jan Beulich
2013-11-07 9:30 ` Ian Campbell
2013-11-07 15:41 ` Jeff_Zimmerman
2013-11-07 15:54 ` Andrew Cooper
2013-11-07 16:00 ` Jan Beulich
2013-11-07 16:06 ` Andrew Cooper
2013-11-07 16:12 ` Jeff_Zimmerman
2013-11-07 15:57 ` Jan Beulich
2013-11-07 16:02 ` Jeff_Zimmerman
2013-11-07 16:53 ` Jan Beulich
2013-11-07 17:02 ` Andrew Cooper [this message]
2013-11-08 7:50 ` Jan Beulich
2013-11-07 18:13 ` Andrew Cooper
2013-11-07 18:33 ` Jeff_Zimmerman
[not found] <CE9EAEF6.59305%asit.k.mallick@intel.com>
2013-11-05 22:46 ` Jeff_Zimmerman
2013-11-05 23:17 ` Mallick, Asit K
2013-11-06 0:23 ` Andrew Cooper
2013-11-06 10:05 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=527BC7A3.7030405@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=Jeff_Zimmerman@McAfee.com \
--cc=lars.kurth.xen@gmail.com \
--cc=lars.kurth@xen.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).