All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "henning.schild@siemens.com" <henning.schild@siemens.com>,
	Lange Norbert <norbert.lange@andritz.com>,
	"Xenomai (xenomai@xenomai.org)" <xenomai@xenomai.org>
Subject: Re: x86_64 kernel does not start under qemu
Date: Thu, 21 Mar 2019 12:57:54 +0100	[thread overview]
Message-ID: <3154485.mhzyMJEECq@blindfold> (raw)
In-Reply-To: <ddd256e9-0e93-30bc-ddf0-e4f333d24d7f@siemens.com>

Am Donnerstag, 21. März 2019, 12:02:45 CET schrieb Jan Kiszka:
> FWIW, I've just seen this issue as well, with QEMU in KVM mode: I ran into that 
> lockup when my host was under full load while Xenomai booted in the VM. And it 
> seems reproducible. Debugging...

Oh, good to hear that!
I played a little with your config but got badly interrupted with other stuff.
Your config seems to work but mostly because things are slower due to debugging stuff
you've enabled. Maybe this info helps.

Thanks,
//richard





  reply	other threads:[~2019-03-21 11:57 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
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 [this message]
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=3154485.mhzyMJEECq@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.