From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 65561] KVM:Entry failed on Single stepping sti instruction
Date: Wed, 21 May 2014 16:39:42 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path:
Received: from mail.kernel.org ([198.145.19.201]:52030 "EHLO mail.kernel.org"
rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
id S1751018AbaEUQjp (ORCPT );
Wed, 21 May 2014 12:39:45 -0400
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id 002DC203AA
for ; Wed, 21 May 2014 16:39:43 +0000 (UTC)
Received: from bugzilla1.web.kernel.org (bugzilla1.web.kernel.org [172.20.200.51])
by mail.kernel.org (Postfix) with ESMTP id 87F972037D
for ; Wed, 21 May 2014 16:39:42 +0000 (UTC)
In-Reply-To:
Sender: kvm-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=65561
--- Comment #12 from Paolo Bonzini ---
> Hi, Paolo, thanks for your explanation. I am interested in fixing this. So
> what's the technical challenge here?
The first step is to reproduce the failure. To do this you can make a
patch to kvm-unit-tests
(git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git).
0x80000021 means invalid guest state in the VMCS (the VM information
that is passed to the processor). So you could try adding some printk
to understand what is the invalid guest state. To do this you need to
download the Intel manuals (known as "Intel SDM", google is your
friend). You can post the testcase patch on kvm@vger.kernel.org once
you have a reproducer.
> When you say "support for single-stepping and breakpoints in the emulator is
> quite minimal", do you mean it's a problem in the Qemu side, rather than
> something wrong in the kvm kernel modules? If so, and if we want to fix this,
> we need to make some changes in the Qemu code, right?
No, the emulator is part of KVM, see arch/x86/kvm/emulate.c. I have
some pending patches for it, destined to 3.17. There is a small chance
that they fix the bug.
--
You are receiving this mail because:
You are watching the assignee of the bug.