From: Jan Kiszka <jan.kiszka@web.de>
To: Nadav Har'El <nyh@math.technion.ac.il>
Cc: "Nakajima, Jun" <jun.nakajima@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Bug 53611] New: nVMX: Add nested EPT
Date: Tue, 26 Feb 2013 20:43:13 +0100 [thread overview]
Message-ID: <512D1051.4050302@web.de> (raw)
In-Reply-To: <20130226141129.GA15375@fermat.math.technion.ac.il>
[-- Attachment #1: Type: text/plain, Size: 2468 bytes --]
On 2013-02-26 15:11, Nadav Har'El wrote:
> On Thu, Feb 14, 2013, Nakajima, Jun wrote about "Re: [Bug 53611] New: nVMX: Add nested EPT":
>> We have started looking at the pataches first. But I couldn't
>> reproduce the results by simply applying the original patches to v3.6:
>> - L2 Ubuntu 12.04 (64-bit) (smp 2)
>> - L1 Ubuntu 12.04 (64-bit) KVM (smp 2)
>> - L0 Ubuntu 12.04 (64-bit)-based. kernel/KVM is v3.6 + patches (the
>> ones in nept-v2.tgz).
>> https://bugzilla.kernel.org/attachment.cgi?id=93101
>>
>> Without the patches, the L2 guest works. With it, it hangs at boot
>> time (just black screen):
>> - EPT was detected by L1 KVM.
>> - UP L2 didn't help.
>> - Looks like it's looping at EPT_walk_add_generic at the same address in L0.
>>
>> Will take a closer look. It would be helpful if the test configuration
>> (e.g kernel/commit id used, L1/L2 guests) was documented as well.
>
> I sent the patches in August 1st, and they applied to commit
> ade38c311a0ad8c32e902fe1d0ae74d0d44bc71e from a week earlier.
>
> In most of my tests, L1 and L2 were old images - L1 had Linux 2.6.33,
> while L2 had Linux 2.6.28. In most of my tests both L1 and L2 were UP.
>
> I've heard another report of my patch not working with newer L1/L2 -
> the report said that L2 failed to boot (like you reported), and also
> that L1 became unstable (running anything in it gave a memory fault).
> So it is very likely that this code still has bugs - but since I already
> know of errors and holes that need to be plugged (see the announcement file
> together with the patches), it's not very surprising :( These patches
> definitely need some lovin', but it's easier than starting from scratch.
FWIW, I'm playing with them on top of kvm-3.6-2 (second pull request for
3.6) for a while. They work OK for my use case (static mapping) but
apparently lock up L2 when starting KVM on KVM, just as reported. I
didn't look into any details there, still busy with fixing other issues
like CR0/CR4 handling (which I came across while adding unrestricted
guest support on top of EPT).
Given that I'm porting now patches between that branch and "next" back
and forth (I depend on EPT), it would be really great if someone
familiar with the KVM MMU (or enough time) could port the series to the
current git head. That would not solve remaining bugs but could trigger
more development, maybe also help me jumping into this.
Thanks,
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-02-26 19:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 12:49 [Bug 53611] New: nVMX: Add nested EPT bugzilla-daemon
2013-02-11 12:50 ` [Bug 53611] " bugzilla-daemon
2013-02-11 13:16 ` [Bug 53611] New: " Jan Kiszka
2013-02-11 13:27 ` Nadav Har'El
2013-02-11 14:53 ` Jan Kiszka
2013-02-12 19:13 ` Nakajima, Jun
2013-02-13 7:43 ` Jan Kiszka
2013-02-15 2:07 ` Nakajima, Jun
2013-02-26 14:11 ` Nadav Har'El
2013-02-26 19:43 ` Jan Kiszka [this message]
2013-02-26 20:14 ` Gleb Natapov
2013-03-05 4:45 ` Nakajima, Jun
2013-03-05 8:28 ` Jan Kiszka
2013-03-22 6:23 ` Nakajima, Jun
2013-03-22 16:45 ` Jan Kiszka
2013-04-24 7:25 ` Jan Kiszka
2013-04-24 15:55 ` Nakajima, Jun
2013-04-24 15:57 ` Jan Kiszka
2013-04-25 8:00 ` Nakajima, Jun
2013-04-25 9:19 ` Gleb Natapov
2013-04-26 6:26 ` Jan Kiszka
2013-04-26 16:07 ` Nakajima, Jun
2013-04-28 10:03 ` Jan Kiszka
2013-02-27 8:14 ` [Bug 53611] " bugzilla-daemon
2015-03-17 3:53 ` bugzilla-daemon
2015-04-08 9:02 ` bugzilla-daemon
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=512D1051.4050302@web.de \
--to=jan.kiszka@web.de \
--cc=jun.nakajima@intel.com \
--cc=kvm@vger.kernel.org \
--cc=nyh@math.technion.ac.il \
/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).