kvm/queue still ahead of kvm/next

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/next.

The good news is that nested EPT works pretty well. :)

Quoted 9 lines

Quoted 9 lines

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/next.

The good news is that nested EPT works pretty well. :)

Paolo/others, I'm trying to test nEPT, so I'm trying to start this way:

   $ git clone git://git.kernel.org/pub/scm/virt/kvm/kvm.git
   $ git branch --all
   $ git checkout remotes/origin/queue

Compile, and proceed.

Or would you suggest to use

http://git.kiszka.org/?p=kvm-kmod.git;a=blob;f=README

to test latest stuff?

Il 19/08/2013 06:36, Kashyap Chamarthy ha scritto:

Quoted 21 lines · Paolo Bonzini

Quoted 9 lines

Quoted 9 lines

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/next.

The good news is that nested EPT works pretty well. :)

Paolo/others, I'm trying to test nEPT, so I'm trying to start this way:

   $ git clone git://git.kernel.org/pub/scm/virt/kvm/kvm.git
   $ git branch --all
   $ git checkout remotes/origin/queue

Compile, and proceed.

Or would you suggest to use

Quoted 3 lines

http://git.kiszka.org/?p=kvm-kmod.git;a=blob;f=README

to test latest stuff?

If you prefer not to build your own kernel, kvm-kmod works too. However, please build it with the latest 3.10.x kernel to make the environment as similar as possible to what you'd get with kvm.git.

Quoted 22 lines · Paolo Bonzini

Il 19/08/2013 06:36, Kashyap Chamarthy ha scritto:

Quoted 21 lines · Paolo Bonzini

Quoted 9 lines

Quoted 9 lines

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/next.

The good news is that nested EPT works pretty well. :)

Paolo/others, I'm trying to test nEPT, so I'm trying to start this way:

   $ git clone git://git.kernel.org/pub/scm/virt/kvm/kvm.git
   $ git branch --all
   $ git checkout remotes/origin/queue

Compile, and proceed.

Or would you suggest to use

Quoted 7 lines

Quoted 3 lines

http://git.kiszka.org/?p=kvm-kmod.git;a=blob;f=README

to test latest stuff?

If you prefer not to build your own kernel, kvm-kmod works too. However, please build it with the latest 3.10.x kernel to make the environment as similar as possible to what you'd get with kvm.git.

I'm fine building news Kernels. I just started this way:

  $ git remote -v
  origin  git://git.kernel.org/pub/scm/virt/kvm/kvm.git (fetch)
  origin  git://git.kernel.org/pub/scm/virt/kvm/kvm.git (push)

  $ git checkout -b test_nept origin/queue

  $ make defconfig

  $ make -j8 && make modules

  $ make install && make modules_install

And, booting into the just built 3.11.0-rc1+ kernel (this is on bare-metal), hangs at:
-------------
.
.
.

[    5.437220] systemd[1]: Failed to mount /dev: No such device
[    5.523997] usb 2-1: New USB device found, idVendor=8087, idProduct=8000
[    5.531600] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    5.540188] hub 2-1:1.0: USB hub found
[    5.544573] hub 2-1:1.0: 8 ports detected
[    5.757452] Switched to clocksource tsc
[    5.879287] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off

-------------

(This is on a Haswell machine).

Am I missing anything here?

/kashyap

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/next.

The good news is that nested EPT works pretty well. :)