Kicksecure™ Tuning
Donate
Making Kicksecure Faster. Tuning Kicksecure.
Choose your virtualizer to get started.
See below.
Introduction[edit]
Everything in this chapter is entirely optional.
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.
Tested Tuning Steps[edit]
Hardware-accelerated Graphics[edit]
VirtualBox
Warning: This procedure lessens security.
To enable hardware-accelerated graphics for Kicksecure™, perform these steps on the host:
- Power off the VM.
VirtualBox→click a VM→Settings→Display→Graphics Controller→Acceleration:checkEnable 3D Acceleration→OK- Restart the VM.
Also refer to the VirtualBox manual: Hardware-Accelerated Graphics
.
Forum discussion: VirtualBox 3D Acceleration
Increase Virtual Machine RAM[edit]
VirtualBox
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:
- Shutdown the VM.
- Assign more RAM:
Virtual machine→Menu→Settings→AdjustMemory slider to 4096→Hit: OK - Restart the VM.
See also: Advice for Systems with Low RAM.
Additional CPU Cores[edit]
VirtualBox
Warning: this procedure may increase fingerprinting risks.
On systems with multi-core processors, if minor identifiers are not of any concern [1] then the number of cores available to the Virtual Machine(s) can be increased in VirtualBox settings.
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. [2]
- Power off the VM.
VirtualBox→click a VM→Settings→System→Processor→Reduce to 3→OK- Restart the VM.
Untested Tuning Steps[edit]
Disable CPU Mitigations[edit]
Warning: this procedure lessens security.
Consider disabling the Spectre Meltdown mitigations. (Related forum discussion.)
This step should be performed in the VM intended for disabled CPU mitigations and on the host operating system if either Kicksecure or security-misc are in use.
1. Remove the relevant CPU mitigations file.
sudo rm /etc/default/grub.d/40_cpu_mitigations.cfg
2. Update grub.
sudo update-grub
3. Reboot.
4. Done.
Nested Paging and VPIDs[edit]
VirtualBox
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.
vboxmanage modifyvm Kicksecure-Xfce --largepages on
vboxmanage modifyvm Kicksecure-Xfce --largepages on
vboxmanage modifyvm Kicksecure-Xfce --vtxvpid on
vboxmanage modifyvm Kicksecure-Xfce --vtxvpid on
Memory Ballooning, Page Fusion and Memory Overcommitment[edit]
Warning: this procedure lessens security.
Memory ballooning worsens security because it is a vector for side channel attacks on memory; see here for further information. [3]
For other security considerations, refer to the VirtualBox manual: Memory Overcommitment.
Undocumented Tuning Settings[edit]
There are probably more tuning-related settings, but these are currently undocumented at Kicksecure. Interested readers can review the manual for relevant settings of their respective virtualizer, which are unlikely to be bundled under a "tuning" chapter.
VirtualBox
To view all settings, run.
vboxmanage showvminfo Kicksecure-Xfce
Next, learn about all of these settings by reviewing the VirtualBox manual.
PCI Passthrough[edit]
Warning: this procedure lessens security.
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.
See Also[edit]
Footnotes[edit]
- ↑ 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.
Unfinished: This wiki is a work in progress. Please do not report broken links until this notice is removed, use Search Engines First and contribute improving this wiki.
A secure by default operating system with the latest security research in place.
At Kicksecure we value freedom and trust, supporting Open Source and Freedom Software
2012-2023 ENCRYPTED SUPPORT LP
We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 11 year success story and maybe DONATE!