From: Luiz Capitulino <lcapitulino@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [BUG 1.0] -cpu host breaks linux guest boot
Date: Fri, 25 Nov 2011 12:37:04 -0200 [thread overview]
Message-ID: <20111125123704.57f933b6@doriath> (raw)
In-Reply-To: <20111125141237.GB12628@garlic.privatebox>
On Fri, 25 Nov 2011 16:12:37 +0200
Alon Levy <alevy@redhat.com> wrote:
> On Thu, Nov 24, 2011 at 04:03:55PM -0200, Luiz Capitulino wrote:
> > Avi,
> >
>
> I have the same panic and the same bisection result. It doesn't happen
> with recent (3.2.0 rc1 and rc3) kernels.
Would be nice to test a recent kernel with 66e3dd9 reverted. It'll be funny
if it fails :)
>
> > I'm getting the following panic very early on boot on a F16 VM (latest
> > qemu.git head 40897c9):
> >
> > [ 0.068018] Kernel panic - not syncing: Boot APIC ID in local APIC unexpected (-1 vs 0)
> > [ 0.070006] Pid: 1, comm: swapper Not tainted 3.1.0-7.fc16.x86_64 #1
> > [ 0.071004] Call Trace:
> > [ 0.072035] [<ffffffff814acb8e>] panic+0x91/0x1a5
> > [ 0.073027] [<ffffffff81b831ca>] native_smp_prepare_cpus+0x24c/0x300
> > [ 0.075010] [<ffffffff81b76c0d>] kernel_init+0x85/0x158
> > [ 0.075993] [<ffffffff810527eb>] ? schedule_tail+0x27/0x6c
> > [ 0.076017] [<ffffffff814be5f4>] kernel_thread_helper+0x4/0x10
> > [ 0.077022] [<ffffffff81b76b88>] ? start_kernel+0x3b6/0x3b6
> > [ 0.078009] [<ffffffff814be5f0>] ? gs_change+0x13/0x13
> >
> > After some debugging and I found out that this only happens when '-cpu host'
> > is passed, and according to git bisect it's caused by the following commit:
> >
> > commit 66e3dd9282141b5ae75637c9676002cf3ceeb988
> > Author: Avi Kivity <avi@redhat.com>
> > Date: Wed Nov 9 15:44:36 2011 +0200
> >
> > i386: derive '-cpu host' from KVM_GET_SUPPORTED_CPUID
> >
> > Not sure if this is important, but here's procinfo information about
> > one of my host's cpus:
> >
> > processor : 0
> > vendor_id : GenuineIntel
> > cpu family : 6
> > model : 23
> > model name : Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz
> > stepping : 6
> > cpu MHz : 2801.000
> > cache size : 6144 KB
> > physical id : 0
> > siblings : 2
> > core id : 0
> > cpu cores : 2
> > apicid : 0
> > initial apicid : 0
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 10
> > wp : yes
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm tpr_shadow vnmi flexpriority
> > bogomips : 5585.87
> > clflush size : 64
> > cache_alignment : 64
> > address sizes : 36 bits physical, 48 bits virtual
> > power management:
> >
>
next prev parent reply other threads:[~2011-11-25 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 18:03 [Qemu-devel] [BUG 1.0] -cpu host breaks linux guest boot Luiz Capitulino
2011-11-25 14:12 ` Alon Levy
2011-11-25 14:37 ` Luiz Capitulino [this message]
2011-11-25 15:44 ` Alon Levy
2011-11-27 13:04 ` Avi Kivity
2011-11-27 17:13 ` Anthony Liguori
2011-11-28 14:00 ` Luiz Capitulino
2011-11-28 14:11 ` Anthony Liguori
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=20111125123704.57f933b6@doriath \
--to=lcapitulino@redhat.com \
--cc=alevy@redhat.com \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).