All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kashyap Chamarthy <kchamart@redhat.com>
To: kvm@vger.kernel.org
Cc: jan.kiszka@siemens.com, pbonzini@redhat.com
Subject: nSVM: Booting L2 results in L1 hang and a "skip_emulated_instruction"
Date: Wed, 11 Feb 2015 19:12:07 +0100	[thread overview]
Message-ID: <20150211181207.GM8956@tesla.redhat.com> (raw)

Hi, 

This was tested with kernel-3.19.0-1.fc22) and QEMU (qemu-2.2.0-5.fc22)
on L0 & L1.


Description
-----------

Inside L1, boot a nested KVM guest (L2) . Instead of a full blown
guest, let's use `qemu-sanity-check` with KVM:

    $ qemu-sanity-check --accel=kvm

Wwich gives you this CLI (run from a different shell), that confirms
that the L2 guest is indeed running on KVM (and not TCG):

  $ ps -ef | grep -i qemu
  root       763   762 35 11:49 ttyS0    00:00:00 qemu-system-x86_64 -nographic -nodefconfig -nodefaults -machine accel=kvm -no-reboot -serial file:/tmp/tmp.rl3naPaCkZ.out -kernel /boot/vmlinuz-3.19.0-1.fc21.x86_64 -initrd /usr/lib64/qemu-sanity-check/initrd -append console=ttyS0 oops=panic panic=-1


Which results in:

  (a) L1 (guest hypervisor) completely hangs and is unresponsive. But
      when I query libvirt, (`virsh list`) the guest is still reported
      as 'running'

  (b) On L0, I notice a ton of these messages:

        skip_emulated_instruction: ip 0xffec next 0xffffffff8105e964


I can get `dmesg`, `dmidecode` , `x86info -a` on L0 and L1 if it helps
in narrowing down the issue.


Related bug and reproducer details
----------------------------------


https://bugzilla.redhat.com/show_bug.cgi?id=1191665 --  Nested KVM with
AMD: L2 (nested guest) fails with "divide error: 0000 [#1] SMP"




-- 
/kashyap

             reply	other threads:[~2015-02-11 18:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 18:12 Kashyap Chamarthy [this message]
2015-02-12  6:12 ` nSVM: Booting L2 results in L1 hang and a "skip_emulated_instruction" Jan Kiszka
2015-02-17 11:30   ` Kashyap Chamarthy

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=20150211181207.GM8956@tesla.redhat.com \
    --to=kchamart@redhat.com \
    --cc=jan.kiszka@siemens.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.