From: Jan Kiszka <jan.kiszka@siemens.com>
To: duy hai nguyen <haind93@gmail.com>
Cc: Kashyap Chamarthy <kashyap.cv@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: nested EPT
Date: Fri, 17 Jan 2014 12:40:12 +0100 [thread overview]
Message-ID: <52D9169C.7090005@siemens.com> (raw)
In-Reply-To: <CAOaxAcYEyryPgSQupvRO+rBuTZ7hB2NjHbxhCdhptgPnOuXRXw@mail.gmail.com>
On 2014-01-17 12:29, Kashyap Chamarthy wrote:
> On Fri, Jan 17, 2014 at 2:51 AM, duy hai nguyen <haind93@gmail.com> wrote:
>> Now I can run an L2 guest (nested guest) using the kvm kernel module
>> of kernel 3.12
>>
>> However, I am facing a new problem when trying to build and use kvm
>> kernel module from git://git.kiszka.org/kvm-kmod.git: L1 (nested
>> hypervisor) cannot boot L2 and the graphic console of virt-manager
>> hangs displaying 'Booting from Hard Disk...'. L1 still runs fine.
>>
>> Loading kvm_intel with 'emulate_invalid_guest_state=0' in L0 does not
>> solve the problem. I have also tried with different kernel versions:
>> 3.12.0, 3.12.8 and 3.13.0 without success.
>>
>> Can you give me some suggestions?
>
> Maybe you can try without graphical managers and enable serial console
> ('console=ttyS0') to your Kernel command-line of L2 guest, so you can
> see where it's stuck.
Tracing can also be helpful, both in L1 and L0:
http://www.linux-kvm.org/page/Tracing
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2014-01-17 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 16:10 nested EPT duy hai nguyen
2014-01-16 17:07 ` Jan Kiszka
2014-01-16 17:09 ` Paolo Bonzini
2014-01-16 18:17 ` duy hai nguyen
2014-01-17 1:51 ` duy hai nguyen
2014-01-17 11:29 ` Kashyap Chamarthy
2014-01-17 11:40 ` Jan Kiszka [this message]
2014-01-17 18:41 ` duy hai nguyen
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=52D9169C.7090005@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=haind93@gmail.com \
--cc=kashyap.cv@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.