From: Gleb Natapov <gleb@redhat.com>
To: Marius Vlad <mv@sec.uni-passau.de>
Cc: Arthur Chunqi Li <yzt356@gmail.com>, kvm <kvm@vger.kernel.org>,
Jan Kiszka <jan.kiszka@web.de>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v3] kvm-unit-tests : Basic architecture of VMX nested test case
Date: Tue, 30 Jul 2013 10:42:12 +0300 [thread overview]
Message-ID: <20130730074212.GN18009@redhat.com> (raw)
In-Reply-To: <20130730073115.GA2085@lea.sec.uni-passau.de>
On Tue, Jul 30, 2013 at 09:31:17AM +0200, Marius Vlad wrote:
> Hi Arthur,
>
> I'm trying to test your patch on a SandyBridge machine.
>
> Used 'nested=1' when loading kvm (from 3.9-1-amd64)
Should be kvm-intel, but you will get error otherwise, so I assume that
this is what you did.
> and qemu (emulator version 1.5.1 (Debian 1.5.0+dfsg-5)).
>
> Without nested=1 I get ``unhandled excecption 13'', so I presume
> this is OK, with it, the test_vmx_capability() fails at
> detecting vmx.
>
> I've used for qemu:
> $ qemu-system-x86_64 -enable-kvm -device pc-testdev -device
> isa-debug-exit,iobase=0xf4,iosize=0x4 -display none -serial stdio -device
> pci-testdev -kernel x86/vmx.flat -cpu SandyBridge,+vmx,+x2apic -smp 1
>
> Are there any knobs which I should further tune?
>
On the first glance you have everything that is needed. What is the output of
"cat /proc/cpuinfo" in the guest is?
--
Gleb.
next prev parent reply other threads:[~2013-07-30 7:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 14:00 [PATCH v3] kvm-unit-tests : Basic architecture of VMX nested test case Arthur Chunqi Li
2013-07-28 14:24 ` Arthur Chunqi Li
2013-07-28 14:32 ` Arthur Chunqi Li
2013-07-28 14:34 ` Gleb Natapov
2013-07-30 7:31 ` Marius Vlad
2013-07-30 7:42 ` Gleb Natapov [this message]
2013-07-30 7:59 ` Marius Vlad
2013-07-30 8:07 ` Gleb Natapov
2013-07-30 9:14 ` Arthur Chunqi Li
2013-07-30 11:51 ` Marius Vlad
2013-07-30 14:53 ` Paolo Bonzini
2013-07-30 14:57 ` Arthur Chunqi Li
2013-07-30 14:59 ` Paolo Bonzini
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=20130730074212.GN18009@redhat.com \
--to=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mv@sec.uni-passau.de \
--cc=pbonzini@redhat.com \
--cc=yzt356@gmail.com \
/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