From: Marius Vlad <mv@sec.uni-passau.de>
To: Gleb Natapov <gleb@redhat.com>
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 09:59:47 +0200 [thread overview]
Message-ID: <20130730075946.GA4010@lea.sec.uni-passau.de> (raw)
In-Reply-To: <20130730074212.GN18009@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2254 bytes --]
Hi Gleb,
On Tue, Jul 30, 2013 at 09:42:12AM +0200, Gleb Natapov wrote:
> 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.
Indeed.
>
> > 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?
(initramfs) cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel Xeon E312xx (Sandy Bridge)
stepping : 1
microcode : 0x1
cpu MHz : 3410.012
cache size : 4096 KB
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc arch_perfmon rep_good nopl eagerfpu pni pclmulqdq vmx ssse3 cx16 sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx hypervisor lahf_lm xsaveopt
bogomips : 6820.02
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
Used:
$ 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 /boot/vmlinuz-3.9-1-amd64 -initrd\
/boot/initrd.img-3.9-1-amd64 -append 'init=/bin/bash console=ttyS0' -cpu\
SandyBridge,+vmx,+x2apic -smp 1 -serial stdio
>
> --
> Gleb.
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-30 7:59 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
2013-07-30 7:59 ` Marius Vlad [this message]
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=20130730075946.GA4010@lea.sec.uni-passau.de \
--to=mv@sec.uni-passau.de \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--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