From: Jan Kiszka <jan.kiszka@web.de>
To: "Koehrer Mathias (ETAS/ESS2)" <mathias.koehrer@etas.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: VirtualBox 4.2.4 freezes PC using RT_PREEMPT kernel
Date: Sat, 15 Dec 2012 11:14:35 +0100 [thread overview]
Message-ID: <50CC4D8B.9050004@web.de> (raw)
In-Reply-To: <F9467A784CC48947B1D879F07370839E0EBCE44D@fe20099s.ecn.etasgroup.com>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
On 2012-12-14 09:58, Koehrer Mathias (ETAS/ESS2) wrote:
> Hi all,
>
> I have detected the following issue:
> I use an x86 PC using kernel 3.2.34-rt51 and I want to run VirtualBox 4.2.4 using this PC as host.
> However, the PC freezes completely when loading the vbox driver "vboxdrv".
> Using the very same kernel without the RT_PREEMPT patch shows no issues.
>
> Using an older version of VirtualBox (V4.1.22) works fine as well.
>
> I know that this might be slightly off-topic. However there might be some RT_PREEMPT users that have detected the same issue and know a solution for this.
>
> I have attached my kernel .config file.
>
> Thanks for any feedback on this.
Try enabling lock debugging. Likely there is an incompatibility in the
vbox driver or even a bug, and that may reveal more details.
Otherwise: KVM is the better choice on Linux hosts, and it works fine
over -rt.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next prev parent reply other threads:[~2012-12-15 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 8:58 VirtualBox 4.2.4 freezes PC using RT_PREEMPT kernel Koehrer Mathias (ETAS/ESS2)
2012-12-15 10:14 ` Jan Kiszka [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-19 14:44 Koehrer Mathias (ETAS/ESS2)
2012-12-20 18:20 ` 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=50CC4D8B.9050004@web.de \
--to=jan.kiszka@web.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=mathias.koehrer@etas.com \
/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.