From: Daniel Bareiro <daniel-listas@gmx.net>
To: KVM General <kvm@vger.kernel.org>
Cc: Alexander Graf <agraf@suse.de>
Subject: Re: Testing nested virtualization
Date: Sat, 2 Jan 2010 11:18:50 -0300 [thread overview]
Message-ID: <20100102141850.GB8741@defiant.freesoftware> (raw)
In-Reply-To: <C754047A-8AC2-4DEF-9215-520AE5A28AC7@suse.de>
[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]
Hi, Alex.
On Saturday, 02 January 2010 14:48:26 +0100,
Alexander Graf wrote:
> >>>> In this guest I'm using Linux 2.6.32, with userspace kvm-85 of
> >>>> backports. For the VM booted within of 'test', I am using a qcow2
> >>>> file. But when connecting via VNC, the boot process is hung in
> >>>> "Press for F12 boot menu". Sometimes it gets to pass this
> >>>> instance and I see the Debian install menu, but while I cross the
> >>>> options, it is hung.
> >>> Also I was trying to use qemu-kvm-0.12.1.1 with to Linux 2.6.32 in
> >>> guest within 'test'. And here it happens something similar.
> >>> Sometimes I get to select the option of the menu of the installer,
> >>> but after boot, the installation is hung again.
> >> Can your host do nested paging? Shadow shadow paging can be a bit
> >> flaky at times :-(.
> > Hmmm... is there some way to verify that?
> >
> > The CPUs model is AMD Athlon 64 X2 Dual Core 3800+. Perhaps some flag
> > related? In such case, these are the available ones in the host:
> >
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> > mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
> > fxsr_opt rdtscp lm 3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy
> > svm extapic cr8_legacy
> >
> >
> > When loading the module with "kvm_amd nested=1", /var/log/messages
> > registers the following thing:
> >
> > kvm: Nested Virtualization enabled
> With nested paging it would show something like this in dmesg:
>
> kvm: Nested Paging enabled
Hmmm... dmesg shows just like /var/log/messages:
kvm: Nested Virtualization enabled
"Nested Paging enabled" would have to be a complementary message?
> All family 10 AMD CPUs have nested paging (read: quad-core and above).
But this model is dual-Core :-(. That would mean that it cannot do
nested paging?
> So I guess you found something going wrong with shadow-shadow paging.
> CC'ing Jörg. He's more into memory management than me :-).
We hope then that Jörg can illuminate a little more to us :-).
Thanks for your reply.
Regards,
Daniel
--
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Lenny - Linux user #188.598
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2010-01-02 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 20:20 Testing nested virtualization Daniel Bareiro
2010-01-01 20:56 ` Daniel Bareiro
2010-01-02 13:11 ` Alexander Graf
2010-01-02 13:45 ` Daniel Bareiro
2010-01-02 13:48 ` Alexander Graf
2010-01-02 13:49 ` Alexander Graf
2010-01-04 11:11 ` Joerg Roedel
2010-01-04 14:20 ` Daniel Bareiro
2010-01-04 15:07 ` Alexander Graf
2010-01-04 15:52 ` Daniel Bareiro
2010-01-04 16:04 ` Joerg Roedel
2010-01-04 23:56 ` Daniel Bareiro
2010-01-02 14:18 ` Daniel Bareiro [this message]
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=20100102141850.GB8741@defiant.freesoftware \
--to=daniel-listas@gmx.net \
--cc=agraf@suse.de \
--cc=dbareiro@gmx.net \
--cc=kvm@vger.kernel.org \
/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