From: Avi Kivity <avi@qumranet.com>
To: Bernd Schubert <bs@q-leap.de>
Cc: kvm@vger.kernel.org
Subject: Re: [kvm-devel] can't boot 2.6.26-rcX
Date: Wed, 21 May 2008 15:40:24 +0300 [thread overview]
Message-ID: <48341838.6000304@qumranet.com> (raw)
In-Reply-To: <200805211213.28127.bs@q-leap.de>
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
Bernd Schubert wrote:
> On Wednesday 21 May 2008 11:54:03 Avi Kivity wrote:
>
>> Bernd Schubert wrote:
>>
>>> It is CONFIG_KVM_GUEST, with CONFIG_KVM_CLOCK=y is boots fine!
>>>
>> Works fine here. Can you post your non-booting config?
>>
>
> CONFIG_KVM_GUEST=y doesn't work on my workstation, while the same kernel works
> fine in a kvm-session on a laptop of a colleague. So it seems to be dependent
> on the host hardware.
>
Yes. Attached patch fixes hypercalls on AMD.
--
error compiling committee.c: too many arguments to function
[-- Attachment #2: fix-amd-hypercall.patch --]
[-- Type: text/plain, Size: 407 bytes --]
diff --git a/kernel/x86_emulate.c b/kernel/x86_emulate.c
index 8a96320..932f216 100644
--- a/kernel/x86_emulate.c
+++ b/kernel/x86_emulate.c
@@ -1727,7 +1727,8 @@ twobyte_insn:
if (rc)
goto done;
- kvm_emulate_hypercall(ctxt->vcpu);
+ /* Let the processor re-execute the fixed hypercall */
+ c->eip = ctxt->vcpu->arch.rip;
/* Disable writeback. */
c->dst.type = OP_NONE;
break;
next prev parent reply other threads:[~2008-05-21 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 10:02 can't boot 2.6.26-rcX Bernd Schubert
2008-05-15 7:36 ` Avi Kivity
2008-05-15 10:29 ` Bernd Schubert
2008-05-15 10:54 ` Avi Kivity
2008-05-15 16:47 ` Bernd Schubert
2008-05-21 9:54 ` [kvm-devel] " Avi Kivity
2008-05-21 10:13 ` Bernd Schubert
2008-05-21 12:40 ` Avi Kivity [this message]
2008-06-11 18:29 ` Bernd Schubert
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=48341838.6000304@qumranet.com \
--to=avi@qumranet.com \
--cc=bs@q-leap.de \
--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 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.