From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Andy Lutomirski <luto@amacapital.net>,
kvm list <kvm@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Cc: jamie@audible.transient.net
Subject: Re: [bisected] KVM in 3.19-rc1 is completely broken
Date: Tue, 23 Dec 2014 16:19:29 +0800 [thread overview]
Message-ID: <54992591.5070206@intel.com> (raw)
In-Reply-To: <CALCETrVENw+a_deJn1J-A+dKv-R=zbqGy+1gmkRUN48Yo0Zqpw@mail.gmail.com>
On 2014/12/23 9:38, Andy Lutomirski wrote:
> I can't get it to work at all. It fails with:
>
How can we reproduce this? I just try the following command,
qemu-system-x86_64 -machine pc,accel=kvm -m 2048 -smp 2 -hda ubuntu.img
but at least I can boot that successfully and already live for a while.
Here I installed ubuntu14.04 as a guest, and
Linux commit: aa39477b5692611b91ac9455ae588738852b3f60
Qemu commit: 7e58e2ac7778cca3234c33387e49577bb7732714
So any specific Kconfigs need to be enabled?
Tiejun
> KVM internal error. Suberror: 1
> emulation failure
> EAX=000dee58 EBX=00000000 ECX=00000000 EDX=00000cfd
> ESI=00000059 EDI=00000000 EBP=00000000 ESP=00006fc4
> EIP=000f17f4 EFL=00010012 [----A--] CPL=0 II=0 A20=1 SMM=0 HLT=0
> ES =0010 00000000 ffffffff 00c09300 DPL=0 DS [-WA]
> CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
> SS =0010 00000000 ffffffff 00c09300 DPL=0 DS [-WA]
> DS =0010 00000000 ffffffff 00c09300 DPL=0 DS [-WA]
> FS =0010 00000000 ffffffff 00c09300 DPL=0 DS [-WA]
> GS =0010 00000000 ffffffff 00c09300 DPL=0 DS [-WA]
> LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
> TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy
> GDT= 000f6c58 00000037
> IDT= 000f6c96 00000000
> CR0=60000011 CR2=00000000 CR3=00000000 CR4=00000000
> DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
> DR3=0000000000000000
> DR6=00000000ffff0ff0 DR7=0000000000000400
> EFER=0000000000000000
> Code=e8 75 fc ff ff 89 f2 a8 10 89 d8 75 0a b9 74 17 ff ff ff d1 <5b>
> 5e c3 5b 5e e9 76 ff ff ff 57 56 53 8b 35 38 65 0f 00 85 f6 0f 88 be
> 00 00 00 0f b7 f6
>
> The problem started with:
>
> commit 0e60b0799fedc495a5c57dbd669de3c10d72edd2
> Author: Igor Mammedov <imammedo@redhat.com>
> Date: Mon Dec 1 17:29:26 2014 +0000
>
> kvm: change memslot sorting rule from size to GFN
>
> it will allow to use binary search for GFN -> memslot
> lookups, reducing lookup cost with large slots amount.
>
> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>
>
> --Andy
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2014-12-23 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 1:38 [bisected] KVM in 3.19-rc1 is completely broken Andy Lutomirski
2014-12-23 8:19 ` Chen, Tiejun [this message]
2014-12-23 8:30 ` Paolo Bonzini
2014-12-23 8:33 ` Andy Lutomirski
[not found] ` <CALCETrWJUUytHNjq_ft5Ajf6DZ47QoegohCLDj3p-g9FuTTWgA@mail.gmail.com>
2014-12-23 21:13 ` Paolo Bonzini
2014-12-23 21:29 ` Andy Lutomirski
2014-12-24 8:23 ` Chen, Tiejun
2014-12-24 17:11 ` Andy Lutomirski
2014-12-25 0:55 ` Chen, Tiejun
2014-12-25 8:57 ` Chen, Tiejun
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=54992591.5070206@intel.com \
--to=tiejun.chen@intel.com \
--cc=imammedo@redhat.com \
--cc=jamie@audible.transient.net \
--cc=kvm@vger.kernel.org \
--cc=luto@amacapital.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox