All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland <rolandtollenaar@gmail.com>
To: Jan Kiszka <jan.kiszka@web.de>, xenomai@xenomai.org
Subject: Re: [Xenomai] xenomia on virtual box
Date: Wed, 25 Mar 2015 17:38:10 +0200	[thread overview]
Message-ID: <5512D662.2030504@gmail.com> (raw)
In-Reply-To: <55117766.4090003@web.de>

   Thanks Jan.
   Will try KVM on top of PREEMPT-RT.
   Is there a distribution particulalry suited to patch with PREEMPT-RT?
   Kind regards,
   Roland.
   Jan Kiszka wrote:

On 2015-03-24 12:54, r t wrote:


Hi,

perhaps a silly question but we are trying to get our pre- xenomai patched
kernel to run on VirtualBox. Playing about a bit. Well we already have it
running that is not the problem.

The question is whether there is any chance that we will get good (or any)
latency/ realtime performance if the kernel was compiled on another machine
other than the host environment currently hosting the VirtualBox?

Instructions to achieve what we are playing with explicitly state that the
kernel must be compiled on the host then installed on the guest which leads
to believe (as I would intuitively expect) that it is not possible to
abstract a xenomai environement from the hardware. However to my surprize
the xenomai patched kernel does noet seeem to have to run on the host.  How
does xenomai on the guest machine achieve good realtime performance if the
host is still free to act as it wishes in terms of accessing hardware?


Can anyone perhaps shed some light on this?


Virtualization, specifically if VirtualBox-based, destroys real-time for
a Xenomai guest system. You can use such setups very well for functional
tests provided they do not fail due to longer delays or high jitters.

VirtualBox has a fairly poor interface for Linux guests /wrt virtual
clocks and their calibration. Therefore, we frequently run into issues
when setting up Xenomai tests on Windows hosts.

The best real-time environment you can get right now out of a common
hypervisor is stacking KVM on top of PREEMPT-RT. But that alone will not
suffice, you will also have to tune the guest to avoid priority
inversions in the hypervisor's machine emulation.

Jan




  reply	other threads:[~2015-03-25 15:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 11:54 [Xenomai] xenomia on virtual box r t
2015-03-24 14:40 ` Jan Kiszka
2015-03-25 15:38   ` Roland [this message]
2015-03-25 15:54     ` [Xenomai] Antw: " jonas.platte
2015-03-25 18:13     ` [Xenomai] " Jan Kiszka

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=5512D662.2030504@gmail.com \
    --to=rolandtollenaar@gmail.com \
    --cc=jan.kiszka@web.de \
    --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.