On Wed, Aug 24, 2011 at 9:04 AM, wrote:
>
>
> Hello all,
>
> I have just started working with KVM and
> virtualization in general. I have setup a client using Suse 9.3 x64
> as the base and Fedora 15 x64 as the host. The kernel in the client
> has been upgraded to a custom 2.6.28.4 build.
>
> E
On Wed, Apr 11, 2012 at 6:14 PM, Guido Winkelmann
wrote:
> Hi,
>
> Nested virtualization on Intel does not work for me with qemu-kvm. As soon as
> the third layer OS (second virtualised) is starting the Linux kernel, the
> entire second layer freezes up. The last thing I can see console of the thi
On Wed, Apr 11, 2012 at 11:34 PM, Guido Winkelmann
wrote:
> Am Mittwoch, 11. April 2012, 23:14:07 schrieb Kashyap Chamarthy:
>> On Wed, Apr 11, 2012 at 6:14 PM, Guido Winkelmann
>> wrote:
> [...]
>> Here is my complete notes on nested virtualization w/ Intel --
>>
On Sun, Apr 14, 2013 at 1:48 PM, Jan Kiszka wrote:
> On 2013-04-13 20:24, Mohit Dhingra wrote:
>> Hi All,
>>
>> I am Mohit Dhingra, planning to work in GSoC project "Improve nested
>> virtualization support for x86". I got in touch with Jan
>> (jan.kis...@web.de) few days back.
>>
>> As suggested
Heya,
This is on Intel Haswell.
First, some version info:
L0, L1 -- both of them have same versions of kernel, qemu:
=
$ rpm -q kernel --changelog | head -2
* Thu May 09 2013 Josh Boyer - 3.10.0-0.rc0.git23.1
- Linux v3.9-11789-ge0fd9af
=
=
$ uname -r ; rpm -q qemu-kvm libvirt-dae
On Fri, May 10, 2013 at 8:03 PM, Kashyap Chamarthy wrote:
> Also,
>
> I'm able to reproduce this consistently: When I create an L2 guest:
>
> --
> [.]
>
> [ 463.655031] Dazed and confused, but trying to continue
> [ 463.975563] Uhhuh. NMI receive
On Fri, May 10, 2013 at 8:54 PM, Jan Kiszka wrote:
>
> On 2013-05-10 17:12, Jan Kiszka wrote:
> > On 2013-05-10 15:00, Kashyap Chamarthy wrote:
> >> Heya,
> >>
> >> This is on Intel Haswell.
> >>
> >> First, some version info:
> >&
> [3] Libvirt XMLs I used (for reference) --
> https://github.com/kashyapc/nvmx-haswell/tree/master/tests/libvirt-xmls-for-l1-l2
Oops, forgot to add, here we go --
https://github.com/kashyapc/nvmx-haswell/tree/master/tests/libvirt-xmls-for-l1-l2
/kashyap
--
To unsubscribe from this list: send the
>
> We know after you tried. I don't have access to a Haswell box, so we
> better exclude this beforehand.
Fair enough. I'll try that too, and let you know.
>
>>
>>> You get that backtrace in L1, correct?
>>
>> Yes.
>>
>> If you have any further tracing pointers, I could do some debugging.
>
> Th
On Fri, May 10, 2013 at 11:39 PM, Jan Kiszka wrote:
> On 2013-05-10 19:40, Nakajima, Jun wrote:
>> On Fri, May 10, 2013 at 9:33 AM, Jan Kiszka wrote:
>>> On 2013-05-10 17:39, Kashyap Chamarthy wrote:
>>>> On Fri, May 10, 2013 at 8:54 PM, Jan Kiszka wrote:
>&g
Side note: While testing nVMX, I was hitting a libvirt bug, and filed this one:
-- https://bugzilla.redhat.com/show_bug.cgi?id=961665 -- [virsh]
Attempt to force destroy a guest fails due to 'unknown' reason, leaves
a defunct qemu process
which I was told is possibly a Kernel/KVM bug.
Any further
>>
>> I tried to reproduce such a problem, and I found L2 (Linux) hangs in
>> SeaBIOS, after line "iPXE (http://ipxe.org) ...". It happens with or
>> w/o VMCS shadowing (and even without my virtual EPT patches). I didn't
>> realize this problem until I updated the L1 kernel to the latest (e.g.
>> 3
On Sun, May 12, 2013 at 6:08 PM, Gleb Natapov wrote:
> On Sun, May 12, 2013 at 06:00:38PM +0530, Kashyap Chamarthy wrote:
>> >>
>> >> I tried to reproduce such a problem, and I found L2 (Linux) hangs in
>> >> SeaBIOS, after line "iPXE (http://ipxe.
On Sun, May 12, 2013 at 6:29 PM, Abel Gordon wrote:
>
>
> Kashyap Chamarthy wrote on 12/05/2013 03:42:33 PM:
>
>> Again, sorry :(. I was just about to reply that this was physical host.
>>
>> I'm testing by disabling VMCS Shadowing per Jan Kiszka's
> So, from the above info shadow-vmcs is ruled-out. I'm trying to
> investigate further, will post details if I have new findings.
Update:
-
I just tried to create L2 w/ Fedora-19 TC4 compose of 11MAY2013, I
contibuously see the below fragment (F18/F19, whatever the L2 guest
is):
--
>
>
> [ 217.938034] Uhhuh. NMI received for unknown reason 30 on CPU 0.
> [ 217.938034] Do you have a strange power saving mode enabled?
> .[ 222.523373] Uhhuh. NMI received for unknown reason 20 on CPU 0.
> [ 222.524073] Do you have a strange power saving mode enabled
> Yep, shadow-vmcs enabled :)
:) Good to clarify.
>
>
>> Just for reference, here's the detailed procedure I noted while
>> testing it on Haswell --
>> https://raw.github.com/kashyapc/nvmx-haswell/master/SETUP-nVMX.rst
>>
>> Also note you can disable
>> > shadow-vmcs using the kvm-intel kernel
>>
>>
>> [ 217.938034] Uhhuh. NMI received for unknown reason 30 on CPU 0.
>> [ 217.938034] Do you have a strange power saving mode enabled?
>> .[ 222.523373] Uhhuh. NMI received for unknown reason 20 on CPU 0.
>> [ 222.524073] Do you have a strange power saving mode e
Heya,
A simple test below:
Setup Info:
-
L0:
- 4 pCPU, 8G pMEM.
- Version:
$ uname -r; rpm -q qemu-kvm libvirt-daemon-kvm libguestfs
3.10.0-0.rc0.git26.1.fc20.x86_64
qemu-kvm-1.4.1-1.fc19.x86_64
libvirt-daemon-kvm-1.0.5-2.fc19.x86_64
li
> Thanks for the detailed configurations and steps about the nVMX test.
> I have some suggestions if you want to test more:
> 1. you can make L2 guest have 4vCPU and 4Mem
Yeah, will try it. L0 has a max of 8G MEM.
> 2. as L2 is SMP system, you can try 'time make -j 4' instead of 'time make'.
Thi
On Mon, May 13, 2013 at 11:51 AM, Kashyap Chamarthy
wrote:
>> Thanks for the detailed configurations and steps about the nVMX test.
>> I have some suggestions if you want to test more:
>> 1. you can make L2 guest have 4vCPU and 4Mem
>
> Yeah, will try it. L0 has a max of
On Mon, May 13, 2013 at 12:46 PM, Abel Gordon wrote:
>
>
> Kashyap Chamarthy wrote on 13/05/2013 10:07:02 AM:
>
>> 1/ With VMCS Shadowing *disabled* :
>>
>> - On L0 (Side note: I did reboot the host, once I disabled shadow VMCS)
>>
>>
On Mon, May 13, 2013 at 1:00 PM, Ren, Yongjie wrote:
>> -Original Message-
>> From: Kashyap Chamarthy [mailto:kashyap...@gmail.com]
>> Sent: Monday, May 13, 2013 3:07 PM
>> To: Ren, Yongjie
>> Cc: kvm@vger.kernel.org
>> Subject: Re: [nVMX Test] Bui
>
> Yep, kvm_stat is the simplest way to monitor the exits frequency.
Attached is kvm_stat results from L1, captured from several seconds of
intervals.
/kashyap
kvm_entry
Thanks Gleb. Here we go:
This time results appear more closer to what Ren mentioned in his
previous email - i.e. enabling VMCS Shadowing didn't "degrade", the
Kernel compile time in L2.
1] VMCS Shadowing *enabled* on L0; Kernel build on L2,
3.10.0-0.rc0.git26.1.fc20.x86_64
Kernel build time on
>>
>> - NOTE: The below statistics are from intervals ranging from
>> 30 seconds to 6,10,13.. minutes.
>>
>> Looks better ?
>
> Much better :) Now seems the results were improved by 25% (reduced 10m of
> 40m)
:) I wonder how it differed the first time.
>
>> (Note to self: Maybe I should r
>
> Not exactly. With short a make I was a referring to a run that does not
> take
> more than few minutes and with a long a make I was referring to a run
> that may take an hour.
Ah, sorry for misinterpreting it. I'll try to spend more time on it.
> Note that "make clean" clears the output but t
Another point I totally forgot to note - these tests were
performed"debug" enabled kernels from Fedora's Rawhide.
I'll also try w/ Nodebug ones --
http://fedoraproject.org/wiki/RawhideKernelNodebug
/kashyap
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a messag
A small update:
Yesterday, I also ran a simple libguestfs test[1], which creates a
light weight appliance (i.e. an L2) guest , with and without nesting
to see some over-head.
Summary:
-
L0 (bare-metal):
- guestfish run: ~ 3 seconds
L1 (guest):
- w/o nesting, guestfish run
Heya,
So, Gleb suggested (thank you) to try kvm unit tests in L1, here's some
(incomprehensive) detail. I also ran a defconfig in a 20 loop iteration
(in L2) where subsequent runs after the first one are from page cache.
1. A couple of unit tests w/ 64 bit compiled:
-
Heya,
So, I invoked this in L1 with:
===
[test@foo kvm-unit-tests]$ time qemu-system-x86_64 -enable-kvm -device
pc-testdev -serial stdio -nographic -no-user-config -nodefaults
-device
isa-debug-exit,iobase=0xf4,iosize=0x4 -kernel ./x86/eventinj.flat |
tee /var/tmp/eventinj-test
Adding Jan, Jun, to see if they have any inputs here.
/kashyap
On Tue, Jun 4, 2013 at 6:14 PM, Kashyap Chamarthy wrote:
> Heya,
>
> So, I invoked this in L1 with:
> ===
> [test@foo kvm-unit-tests]$ time qemu-system-x86_64 -enable-kvm -device
> pc-tes
if you need any further testing help or
want me to try something specific.
Thanks.
>
> Jan
>
>>
>> /kashyap
>>
>> On Tue, Jun 4, 2013 at 6:14 PM, Kashyap Chamarthy
>> wrote:
>>> Heya,
>>>
>>> So, I invoked this in L1 with:
>
On Wed, Jun 26, 2013 at 10:49 PM, Jan Kiszka wrote:
> On 2013-06-26 10:03, Kashyap Chamarthy wrote:
>>> Thanks for the note, it's very helpful! This test actually fails on
>>> older CPUs as well, and I can finally reproduce the issue that Jay also
>>> reported.
On Sat, Aug 10, 2013 at 12:56 AM, Paolo Bonzini wrote:
>
> Hi all,
>
> I'm seeing some breakage of shadow-on-shadow and shadow-on-EPT nested
> VMX. Until I can track more precisely whether it is a regression, and
> on which hosts I can reproduce it, I'm going to leave the patches out of
> kvm/nex
On Mon, Aug 19, 2013 at 2:56 PM, Paolo Bonzini wrote:
> Il 19/08/2013 06:36, Kashyap Chamarthy ha scritto:
>> On Sat, Aug 10, 2013 at 12:56 AM, Paolo Bonzini wrote:
>>> >
>>> > Hi all,
>>> >
>>> > I'm seeing some breakage of shadow-on
On Mon, Aug 19, 2013 at 3:12 PM, Kashyap Chamarthy wrote:
> On Mon, Aug 19, 2013 at 2:56 PM, Paolo Bonzini wrote:
>> Il 19/08/2013 06:36, Kashyap Chamarthy ha scritto:
>>> On Sat, Aug 10, 2013 at 12:56 AM, Paolo Bonzini wrote:
>>>> >
>>>> > H
On Tue, Aug 27, 2013 at 2:48 PM, Jan Kiszka wrote:
> On 2013-08-27 10:29, 缪天翔 wrote:
>> Hi all
>>
>> I am doing a research project similar to "Turtles" using the nested
>> vmx feature of kvm. In detail, I launch a guest kvm (donated as L1) on
>> the underlying kvm (donated as L0) and then set up a
On Fri, Sep 12, 2014 at 01:43:18PM +0100, Stefan Hajnoczi wrote:
> On Thu, Sep 11, 2014 at 01:48:51PM +0200, Oliver Rath wrote:
> > after hours for searching in google-world, i didnt find any appropriate
> > for this problem:
> >
> > I want to boot a live-cd (i.e. ubuntu 14.04.1-desktop) in qemu,
Hi,
This error occurs when using using '-cpu host'. And, is consistently
reproducible with Fedora 21's Kernels.
One way to reproduce the issue
--
a) Enable nested virt on host, I use this procedure[1]
b) Boot a a guest (ensure /dev/kvm character device shows up)
I have EPT enabled on L0, disabled on L1, and when attempted to boot
an L2 guest, it results in cursor just blinking on the serial console.
(All of them are Fedora 19 minimal guests.)
To be clear, by "disable" I mean, the below KVM parameter is N
$ cat /sys/module/kvm_intel/parameters/ep
Discussed with Gleb on IRC: I'll have to try with kvm.git and a simple
qemu-kvm command line.
Thanks, Gleb.
On Fri, Oct 4, 2013 at 2:01 PM, Kashyap Chamarthy wrote:
> I have EPT enabled on L0, disabled on L1, and when attempted to boot
> an L2 guest, it results in cursor just blin
On Fri, Oct 4, 2013 at 3:09 PM, Gleb Natapov wrote:
> On Fri, Oct 04, 2013 at 03:03:17PM +0530, Kashyap Chamarthy wrote:
>> Discussed with Gleb on IRC: I'll have to try with kvm.git
I just compiled kernel from kvm.git queue on both L0 and L1.
For completeness' sake, this ho
On Fri, Oct 4, 2013 at 6:38 PM, Gleb Natapov wrote:
> On Fri, Oct 04, 2013 at 04:05:50PM +0300, Gleb Natapov wrote:
>> On Fri, Oct 04, 2013 at 06:03:33PM +0530, Kashyap Chamarthy wrote:
>> > On Fri, Oct 4, 2013 at 3:09 PM, Gleb Natapov wrote:
>> > > On Fri, Oc
Gleb, so I just did a trace of KVM MMU to try to understand why L2 is
stuck with shadow on EPT
Ensure, EPT is enabled on L0 & disabled on L1
On L0:
-
$ cat /sys/module/kvm_intel/parameters/ept
Y
On L1
-
$ cat /sys/module/kvm_intel/parameters/ept
N
Build and install trace
On Mon, Oct 7, 2013 at 6:29 PM, Kashyap Chamarthy wrote:
> Gleb, so I just did a trace of KVM MMU to try to understand why L2 is
> stuck with shadow on EPT
Paolo, were you able to reproduce this again? Yesterday, on #qemu you
mentioned you'll test it again :-)
I was using kvm.git qu
I've seen this crash at-least twice on an Intel Haswell machine. I
can't pin-point to an exact trigger. As of now, it crashed when I
tried to reboot a linux guest. Thought I'll post the trace here, just
in case someone wants to take a look.
I compiled kernel from kvm.git queue on both L0 and L1:
On Tue, Oct 8, 2013 at 8:18 PM, Paolo Bonzini wrote:
> Il 08/10/2013 15:03, Paolo Bonzini ha scritto:
>> Il 08/10/2013 07:38, Kashyap Chamarthy ha scritto:
>>> On Mon, Oct 7, 2013 at 6:29 PM, Kashyap Chamarthy
>>> wrote:
>>>> Gleb, so I just did a trace of
On Wed, Oct 9, 2013 at 1:46 PM, Gleb Natapov wrote:
> On Wed, Oct 09, 2013 at 11:52:29AM +0530, Kashyap Chamarthy wrote:
>> On Tue, Oct 8, 2013 at 8:18 PM, Paolo Bonzini wrote:
>> > Il 08/10/2013 15:03, Paolo Bonzini ha scritto:
>> >> Il 08/10/2013 07:38, Kashyap C
On Fri, Jan 17, 2014 at 2:51 AM, duy hai nguyen wrote:
> Now I can run an L2 guest (nested guest) using the kvm kernel module
> of kernel 3.12
>
> However, I am facing a new problem when trying to build and use kvm
> kernel module from git://git.kiszka.org/kvm-kmod.git: L1 (nested
> hypervisor) c
On Mon, Sep 17, 2012 at 4:03 PM, Sasha Levin wrote:
> We used wrong prototypes for sdl init/exit when libsdl wasn't installed when
> building. This would cause build errors.
>
> Reported-by: Kashyap Chamarthy
> Signed-off-by: Sasha Levin
> ---
> tools/kvm/include/kv
On Mon, Sep 17, 2012 at 4:46 PM, Sasha Levin wrote:
> If SDL isn't compiled in we shouldn't die unless we actually try using it.
>
> Signed-off-by: Sasha Levin
> ---
> tools/kvm/include/kvm/sdl.h | 10 --
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/tools/kvm/includ
On Mon, Sep 17, 2012 at 5:14 PM, Kashyap Chamarthy wrote:
> On Mon, Sep 17, 2012 at 4:46 PM, Sasha Levin wrote:
>> If SDL isn't compiled in we shouldn't die unless we actually try using it.
>>
>> Signed-off-by: Sasha Levin
>> ---
>> tools/kvm/i
On Wed, Feb 26, 2014 at 09:27:17PM +0100, Stefan Bader wrote:
> On 26.02.2014 21:25, Paolo Bonzini wrote:
[. . .]
> >>
> >> I bisected this and ended up on the following commit which, when reverted
> >> made
> >> the launch work again:
> >>
> >> Author: Anthoine Bourgeois
> >> Date: Wed Nov 1
On Thu, Feb 27, 2014 at 02:14:23AM +0530, Kashyap Chamarthy wrote:
> On Wed, Feb 26, 2014 at 09:27:17PM +0100, Stefan Bader wrote:
> > On 26.02.2014 21:25, Paolo Bonzini wrote:
>
> [. . .]
>
> > >>
> > >> I bisected this and ended up on the followin
On Thu, Feb 27, 2014 at 05:40:56PM +0530, Kashyap Chamarthy wrote:
> On Thu, Feb 27, 2014 at 02:14:23AM +0530, Kashyap Chamarthy wrote:
> > On Wed, Feb 26, 2014 at 09:27:17PM +0100, Stefan Bader wrote:
> > > On 26.02.2014 21:25, Paolo Bonzini wrote:
> appliance):
>
>
On Thu, Feb 27, 2014 at 05:58:46PM +0100, Paolo Bonzini wrote:
> Il 27/02/2014 18:01, anthoine.bourge...@bertin.fr ha scritto:
> >OK, so your patch works perfectly well with both of my test machines (a
> >Ubuntu guest or
> >a ChorusOS guest).
> >I join the patch, can you signof it ?
>
> I'll post
On Tue, Mar 04, 2014 at 09:13:40AM +0100, Paolo Bonzini wrote:
> Il 04/03/2014 03:40, Ian Pilcher ha scritto:
> >Is this a known problem? I just tried using nested vmx for the first
> >time since upgrading my system from F19 (3.12.?? at the time) to F20,
> >and I cannot start any L2 guests. The L
On Tue, Mar 04, 2014 at 03:00:22PM +0530, Kashyap Chamarthy wrote:
> On Tue, Mar 04, 2014 at 09:13:40AM +0100, Paolo Bonzini wrote:
> > Il 04/03/2014 03:40, Ian Pilcher ha scritto:
> > >Is this a known problem? I just tried using nested vmx for the first
> > >time sin
On Fri, Mar 21, 2014 at 12:22:54PM +0800, Kai Huang wrote:
> Hi,
>
> I see the virtio-balloon is designed for memory auto balloon between
> KVM host and guest, but from latest linux kernel mainline code, looks
> currently there's no consumer actually using it? Would you let me know
> who is the co
On Sat, Mar 22, 2014 at 08:07:42AM +, Prof. Dr. Michael Schefczyk wrote:
> Dear Recipients,
>
> As per http://www.linux-kvm.org/page/Bugs, I am seeking advice
> regarding where to file the following bug:
If you're experiencing it on CentOS
http://bugs.centos.org/
If you're experiencing
On Mon, Feb 1, 2010 at 9:32 AM, wrote:
> Hi folks,
>
> Host – Fedora 12 64bit
> KVM – virtualization software
>
>
> I have 8 VMs on this virtual machine running different OS. Can VMs be
> moved/copied to another PC of similar hardware config running Fedora 12
> (64bit) as host and KVM
The below
On Wed, Jan 21, 2015 at 11:39:44AM +0100, Paolo Bonzini wrote:
>
>
> On 21/01/2015 11:32, Zhang Haoyu wrote:
> > Hi,
> >
> > Does drive_mirror support incremental backup a running vm?
> > Or other mechanism does?
> >
> > incremental backup a running vm requirements:
> > First time backup, all o
On Wed, Jan 21, 2015 at 11:39:44AM +0100, Paolo Bonzini wrote:
>
>
> On 21/01/2015 11:32, Zhang Haoyu wrote:
> > Hi,
> >
> > Does drive_mirror support incremental backup a running vm?
> > Or other mechanism does?
> >
> > incremental backup a running vm requirements:
> > First time backup, all o
Hi,
This was tested with kernel-3.19.0-1.fc22) and QEMU (qemu-2.2.0-5.fc22)
on L0 & L1.
Description
---
Inside L1, boot a nested KVM guest (L2) . Instead of a full blown
guest, let's use `qemu-sanity-check` with KVM:
$ qemu-sanity-check --accel=kvm
Wwich gives you this CLI (run f
I can observe this only one of the Intel Xeon machines (which has 48
CPUs and 1TB memory), but very reliably reproducible.
Reproducer:
- Just ensure physical host (L0) and guest hypervisor (L1) are running
3.20.0-0.rc0.git5.1 Kernel (I used from Fedora's Rawhide).
Preferably on an Inte
On Tue, Feb 17, 2015 at 07:02:14AM +0100, Jan Kiszka wrote:
> On 2015-02-16 21:40, Kashyap Chamarthy wrote:
> > I can observe this only one of the Intel Xeon machines (which has 48
> > CPUs and 1TB memory), but very reliably reproducible.
> >
> >
> > Reproducer:
On Thu, Feb 12, 2015 at 07:12:06AM +0100, Jan Kiszka wrote:
> On 2015-02-11 19:12, Kashyap Chamarthy wrote:
> > Hi,
> >
> > This was tested with kernel-3.19.0-1.fc22) and QEMU (qemu-2.2.0-5.fc22)
> > on L0 & L1.
> >
> >
> > Description
>
On Tue, Feb 17, 2015 at 07:07:21PM +0100, Jan Kiszka wrote:
> On 2015-02-17 19:00, Bandan Das wrote:
> > Kashyap Chamarthy writes:
> > ..
> >>>
> >>> Does enable_apicv make a difference?
> >>
> >> Actually, I did perform a test (on Paolo&
On Wed, Feb 18, 2015 at 05:42:37PM +0100, Paolo Bonzini wrote:
>
>
> On 17/02/2015 12:24, Kashyap Chamarthy wrote:
> > Afraid, I didn't bisect it, but I just wanted to note that the above
> > specific WARN was introduced in the above commit.
> >
> > I'
On Thu, Feb 19, 2015 at 05:02:22PM +0100, Radim Krčmář wrote:
> 2015-02-19 16:01+0100, Radim Krčmář:
> > 2015-02-19 13:07+0100, Kashyap Chamarthy:
> > 5f3d5799974b8 KVM: nVMX: Rework event injection and recovery:
> > This concept is based on the rule that a pending vmlaunch/
On Thu, Feb 19, 2015 at 10:10:11PM +0100, Kashyap Chamarthy wrote:
> On Thu, Feb 19, 2015 at 05:02:22PM +0100, Radim Krčmář wrote:
[. . .]
> > Can you try if the following patch works?
>
> Sure, will test a Kernel built with the below patch and report back.
Hmm, I'm stuck w
On Fri, Feb 20, 2015 at 05:14:15PM +0100, Radim Krčmář wrote:
> 2015-02-19 23:28+0100, Kashyap Chamarthy:
> > On Thu, Feb 19, 2015 at 10:10:11PM +0100, Kashyap Chamarthy wrote:
> > > On Thu, Feb 19, 2015 at 05:02:22PM +0100, Radim Krčmář wrote:
[. . .]
> >
Radim,
I just tested with your patch[1] in this thread. I built a Fedora
Kernel[2] with it, and installed (and booted into) it on both L0 and L1.
Result: I don't have good news, I'm afraid: L1 *still* reboots when an
L2 guest is booted. And, L0 throws the stack trace that was
pre
On Mon, Feb 23, 2015 at 02:56:11PM +0100, Radim Krčmář wrote:
> 2015-02-22 16:46+0100, Kashyap Chamarthy:
> > Radim,
> >
> > I just tested with your patch[1] in this thread. I built a Fedora
> > Kernel[2] with it, and installed (and booted into) it on both L0 and L1
On Mon, Feb 23, 2015 at 05:14:37PM +0100, Kashyap Chamarthy wrote:
> On Mon, Feb 23, 2015 at 02:56:11PM +0100, Radim Krčmář wrote:
> > 2015-02-22 16:46+0100, Kashyap Chamarthy:
> > > Radim,
> > >
> > > I just tested with your patch[1] in this thread. I built a
Tested with the _correct_ Kernel[1] (that has Radim's patch) now --
applied it on both L0 and L1.
Result: Same as before -- Booting L2 causes L1 to reboot. However, the
stack trace from `dmesg` on L0 is took slightly different path than
before -- it's using MSR handling:
. . .
[Fe
On Tue, Feb 24, 2015 at 05:30:06PM +0100, Radim Krčmář wrote:
> 2015-02-23 19:05+0100, Kashyap Chamarthy:
> > Tested with the _correct_ Kernel[1] (that has Radim's patch) now --
> > applied it on both L0 and L1.
> >
> > Result: Same as before -- Booting L2 c
7e35 ("KVM: nVMX: Disable unrestricted mode if ept=0")
> Cc: sta...@vger.kernel.org
> Tested-By: Kashyap Chamarthy
Thanks Radim, for resending it. I was trying to find it in one of the
recent pull requests. :-)
Just for forerence, test confirmation:
http://article.gmane.org/g
79 matches
Mail list logo
