On Fri, May 10, 2013 at 8:54 PM, Jan Kiszka <jan.kiszka@xxxxxxxxxxx> 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: > >> > >> 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 > > > > Please recheck with kvm.git, next branch. > > Hmm, looks like your branch already contains the patch I was thinking of > (03b28f8). Yes. > > You could try if leaving shadow VMCS off makes a difference, but I bet > that is unrelated. Right. I could try. But, like you said, does it *really* make a difference. > You get that backtrace in L1, correct? Yes. If you have any further tracing pointers, I could do some debugging. > I'll have to > see if I can reproduce it. Thanks. If you're looking for a clear reproducer, this is how I conducted my tests, and here's where I'm capturing all of the related work: [1] Setup -- https://raw.github.com/kashyapc/nvmx-haswell/master/SETUP-nVMX.rst [2] Simple scripts used to create L1 and L2 -- https://github.com/kashyapc/nvmx-haswell/tree/master/tests/scripts [3] Libvirt XMLs I used (for reference) -- https://github.com/kashyapc/nvmx-haswell/tree/master/tests/libvirt-xmls-for-l1-l2 Thanks in advance. /kashyap -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
