From: Richard Weinberger <richard@nod.at>
To: Jan Kiszka <jan.kiszka@siemens.com>,
"henning.schild@siemens.com" <henning.schild@siemens.com>
Cc: Lange Norbert <norbert.lange@andritz.com>,
"Xenomai (xenomai@xenomai.org)" <xenomai@xenomai.org>
Subject: Re: x86_64 kernel does not start under qemu
Date: Wed, 06 Mar 2019 16:33:31 +0100 [thread overview]
Message-ID: <3942851.pmMsEQ3ikD@blindfold> (raw)
In-Reply-To: <089ad64d-f76c-44a7-a1f4-75c215b6ab29@siemens.com>
Am Mittwoch, 6. März 2019, 14:43:55 CET schrieb Jan Kiszka:
> On 06.03.19 14:10, Jan Kiszka wrote:
> > On 06.03.19 12:28, Lange Norbert via Xenomai wrote:
> >> Hello,
> >>
> >> I have a similar issue on real hardware (cc Philippe). Can you try booting
> >> with notscdeadline?
> >>
> >
> > I would be surprised if it's that: QEMU does not emulate this APIC feature, only
> > KVM does.
> >
> > I need to reproduce. Which QEMU version?
> >
>
> Just booted current ipipe-x86-4.14.y (4.14.103) in QEMU 3.1+ (some development
> snapshot) with -smp 4 - works fine. But these are likely quite a few variations
> from your setup.
I'm on qemu 2.11.2.
Is this plain ipipe? Just figured that you need to prepare the kernel
with Xenomai to trigger the problem.
Xenomai is 3.0.8.
Kernel config is defconfig.
Thanks,
//richard
next prev parent reply other threads:[~2019-03-06 15:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 10:17 x86_64 kernel does not start under qemu Richard Weinberger
2019-03-06 11:28 ` Lange Norbert
2019-03-06 13:10 ` Jan Kiszka
2019-03-06 13:43 ` Jan Kiszka
2019-03-06 14:00 ` Philippe Gerum
2019-03-06 15:33 ` Richard Weinberger [this message]
2019-03-06 16:39 ` Jan Kiszka
2019-03-08 11:19 ` Richard Weinberger
2019-03-08 11:28 ` Jan Kiszka
2019-03-21 11:02 ` Jan Kiszka
2019-03-21 11:57 ` Richard Weinberger
2019-03-21 16:07 ` Jan Kiszka
2019-03-22 20:50 ` Jan Kiszka
2019-03-23 10:04 ` Philippe Gerum
2019-03-23 10:16 ` Philippe Gerum
2019-03-23 16:58 ` Philippe Gerum
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=3942851.pmMsEQ3ikD@blindfold \
--to=richard@nod.at \
--cc=henning.schild@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=norbert.lange@andritz.com \
--cc=xenomai@xenomai.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.