Kicksecure ™ Tuning
Applying steps in this chapter can improve Kicksecure ™ performance, but often at the cost of reduced security or an increased fingerprinting risk. Earlier entries in this chapter are easier to apply, while later tuning entries require a greater skill level.
At present the tuning steps are primarily focused on the VirtualBox virtualizer. However, contributions for other virtualizers will be happily considered.
Tested Tuning Steps
To enable hardware-accelerated graphics for Kicksecure ™, perform these steps on the host:
- Power off the VM.
click a VM→
Enable 3D Acceleration→
- Restart the VM.
Also refer to the VirtualBox manual: Hardware-Accelerated Graphics.
Forum discussion: VirtualBox 3D Acceleration
Increase Virtual Machine RAM
RAM available to Virtual Machines can be increased via VirtualBox settings.
To check how much RAM is free, use
free -m in a Terminal. Consider the example below:
See also: Advice for Systems with Low RAM.
Additional CPU Cores
Do not use the maximum since that could lead to system instability! Always leave at least one CPU unassigned; for example, if you have four CPUs then assign a maximum of three CPUs to the VM. 
Untested Tuning Steps
Disable CPU Mitigations
Nested Paging and VPIDs
It is possible to increase performance by using largepages and/or Virtual Processor Identifiers (VPIDs). It is unknown if this decreases security or stability. For further information refer to the VirtualBox manual: Nested Paging and VPIDs.
Memory Ballooning, Page Fusion and Memory Overcommitment
For other security considerations, refer to the VirtualBox manual: Memory Overcommitment.
Undocumented Tuning Settings
There are probably more tuning-related settings, but these are currently undocumented at Kicksecure ™. Interested readers can review the VirtualBox manual for relevant settings, which are unlikely to be bundled under a "tuning" chapter.
To view all settings, run.
Next, learn about all of these settings by reviewing the VirtualBox manual.
Since the Kicksecure ™ concept is flexible and distribution-agnostic, it is possible to create your own implementation. For example, Gentoo could be used with optimized build flags for a personal system. See:
This setting can improve graphics performance dramatically, but it worsens security because VMs should not have direct access to physical hardware.
In simple terms, this feature allows the direct use of physical PCI devices on the host by the guest even if the host does not have drivers for the particular device. For further information, refer to VirtualBox Manual: PCI Passthrough.
- Adding CPU cores is considered a minor risk.
- VirtualBox ticket: VirtualBox should now prohibit assigning all physical CPUs to a VM and/or fix VirtualBox CPU assignment manual.
- This entry relates to KVM but the research similarly applies to other virtualizers unless they have implemented and documented specific protections.