Josef Söntgen 7c1a4522d6 virtualbox5: enable storage device flushing
The patches disable VBOX_IGNORE_FLUSH and a sanity check in the VMDK
backend. This enables passing an explicit flush request by the guest
down to the VFS.

Fixes #3743.
2020-08-25 11:50:10 +02:00
..
2019-02-19 11:08:17 +01:00
2018-02-14 20:41:06 +01:00
2018-05-30 13:36:15 +02:00
2020-07-06 14:43:04 +02:00
2017-05-31 13:15:59 +02:00
2020-07-06 14:43:04 +02:00
2019-02-19 11:08:17 +01:00
2018-08-28 17:10:58 +02:00
2020-07-06 14:43:04 +02:00
2019-02-19 11:08:17 +01:00
2020-07-06 14:43:04 +02:00
2019-02-19 11:08:17 +01:00
2019-05-29 10:20:52 +02:00
2018-05-30 13:36:15 +02:00
2020-07-06 14:43:04 +02:00
2020-05-18 10:16:12 +02:00
2019-05-29 10:20:52 +02:00
2020-07-06 14:43:04 +02:00
2019-02-19 11:08:17 +01:00
2020-07-06 14:43:04 +02:00
2020-07-06 14:43:04 +02:00
2017-05-31 13:15:59 +02:00
2019-05-29 10:20:52 +02:00

VirtualBox configuration options
################################

The configuration requires an attribute named vbox_file with the name of the
vbox configuration to be used (.vbox).

<config vbox_file="file.vbox">

XHCI controller
===============

The virtual XHCI controller can be enabled with the following
configuration option:

<config xhci="yes">

CAPSLOCK
========

<config capslock="ROM">

If the capslock attribute is set to "ROM", virtualbox will open a connection
to the ROM named "capslock" and expect in the top-level node a attribute
'enabled' (yes|no). If the ROM capslock differ from the internal VM capslock,
the VMM will trigger aritifical capslock key events to the VM.