From: Dongli Zhang <dongli.zhang@oracle.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Corentin Labbe <clabbe.montjoie@gmail.com>,
qemu-discuss@nongnu.org, mingo@redhat.com, bp@alien8.de,
hpa@zytor.com, x86@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: qemu-x86: kernel panic when host is loaded
Date: Thu, 2 Apr 2020 07:04:57 -0700 [thread overview]
Message-ID: <18354be1-8dba-84f1-bdf5-6821a5013d78@oracle.com> (raw)
In-Reply-To: <87eet6nra7.fsf@nanos.tec.linutronix.de>
On 4/2/20 2:57 AM, Thomas Gleixner wrote:
> Corentin,
>
> Corentin Labbe <clabbe.montjoie@gmail.com> writes:
>> On our kernelci lab, each qemu worker pass an healtcheck job each day and after each job failure, so it is heavily used.
>> The healtcheck job is a Linux boot with a stable release.
>>
>> Since we upgraded our worker to buster, the qemu x86_64 healthcheck randomly panic with:
>> <0>[ 0.009000] Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option.
>>
>> After some test I found the source of this kernel panic, the host is
>> loaded and qemu run "slower". Simply renicing all qemu removed this
>> behavour.
>>
>> So now what can I do ?
>> Appart renicing qemu process, does something could be done ?
>
> As the qemu timer/ioapic routing is actually sane, you might try to add
> "no_timer_check" to the kernel command line.
>
The no_timer_check is already permanently disabled in below commit?
commit a90ede7b17d1 ("KVM: x86: paravirt skip pit-through-ioapic boot check")
In addition, hyperv and vmware also disabled that:
commit ca3ba2a2f4a4 ("x86, hyperv: Bypass the timer_irq_works() check").
commit 854dd54245f7 ("x86/vmware: Skip timer_irq_works() check on VMware")
Dongli Zhang
next prev parent reply other threads:[~2020-04-02 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 9:31 qemu-x86: kernel panic when host is loaded Corentin Labbe
2020-04-02 9:57 ` Thomas Gleixner
2020-04-02 14:04 ` Dongli Zhang [this message]
2020-04-02 14:31 ` Thomas Gleixner
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=18354be1-8dba-84f1-bdf5-6821a5013d78@oracle.com \
--to=dongli.zhang@oracle.com \
--cc=bp@alien8.de \
--cc=clabbe.montjoie@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qemu-discuss@nongnu.org \
--cc=tglx@linutronix.de \
--cc=x86@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 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).