{{Header}} {{#seo: |description=VT-x is disabled in the BIOS. / VERR_VMX_MSR_VMXON_DISABLED / VERR_SSM_FIELD_NOT_CONSECUTIVE / supR3HardenedWinReSpawn / Enable VT-x in BIOS / Aborted Status / Guru Mediation |image=Vboxtroubleshoot123123.jpg }} {{title|title= {{project_name_long}} in VirtualBox - Troubleshooting - Does not Start? Slow? Other Issues? }} [[image:Vboxtroubleshoot123123.jpg|thumb]] {| class="wikitable" style="background-color:#fff;text-align:center" |- style="background-color: #f9f9f9" | Slow? → Try [[#General VirtualBox Troubleshooting Steps|General VirtualBox Troubleshooting Steps]]. | Failed to open a session for the virtual machine → [[#Failed_to_open_a_session_for_the_virtual_machine|See this.]] |- |NS_ERROR_FAILURE (0x80004005) → [[#NS_ERROR_FAILURE|See this.]] |} {| class="wikitable" style="background-color:#fff;text-align:center" |- style="background-color: #f9f9f9" | [[#VT-x_is_disabled_in_BIOS|VERR_VMX_MSR_VMXON_DISABLED / VERR_NEM_NOT_AVAILABLE]] → [[#BIOS|Enable VT-x in BIOS settings.]] | E_INVALIDARG (0x80070057) → [[#E_INVALIDARG_(0x80070057)|See this.]] |} {| class="wikitable" style="background-color:#fff;text-align:center" |- style="background-color: #f9f9f9" | Black screen? → [[#Black Screen|See this]]. | Aborted Status? → [[#Aborted Status|See this]]. | Guru Mediation? → [[#Guru Mediation|See this]]. |} {{intro| There are many issues which might prevent a normal operation of the VirtualBox host virtualization software. This wiki page documents common issues and potential solutions. }} Topics on this page are sorted roughly in order of issue prevalence. More common issues are on top. __TOC__ = General VirtualBox Troubleshooting Steps = [[File:Ambox_notice.png|25px|link=]] In many situations, the following steps will fix VirtualBox issues. {{Box|text= # [[Troubleshooting#General_Troubleshooting|General Troubleshooting]] for issues such as VM freezing. # In case of connectivity issues, see [[Troubleshooting#Connectivity_Troubleshooting|Connectivity Troubleshooting]]. # [[File:Kicksecure-basic-logo.png|25px|link=]] Use the stable version of [[VirtualBox|{{project_name_short}} for VirtualBox]] {{VersionNew}}. # [[File:Computer_n_screen.png|25px|link=]] [[File:Virtualbox_logo.png|25px|link=]] Use the [[VirtualBox/Recommended_Version|recommended]] VirtualBox host software version, which is currently: {{VirtualBox_Version}} # [[File:cli3.png|25px|link=]] [[File:Virtualbox_logo.png|25px|link=]] To ensure the recommended version of [[VirtualBox/Guest_Additions#VirtualBox_Guest_Additions|VirtualBox guest additions]] is installed in {{project_name_short}} run: {{CodeSelect|code= sudo apt update && sudo apt full-upgrade }} # [[File:Cd-rom-icon.png|25px|link=]] [[File:Virtualbox_logo.png|25px|link=]] Do not use [[VirtualBox/Guest_Additions#VirtualBox_Guest_Additions_CD|VirtualBox guest additions from CD]]. [https://forums.whonix.org/t/virtualbox-guest-additions/8998/3 Installation of VirtualBox guest additions from CD might also cause issues.] # [[File:logo-linux-500x500.png|15px|link=]] Linux users only: Host kernel version: use the recommended host Linux kernel version. It should be the same version that Debian {{stable project version based on Debian codename}} is using ([https://packages.debian.org/{{Stable project version based on Debian codename}}/linux-image-amd64 linux-image-amd64]). Otherwise many [[Kernel#Kernel_Issues|kernel issues]] are likely to occur. # [[File:logo-linux-500x500.png|15px|link=]] Linux users only: Host operating system: use a recommended Linux distribution -- [https://www.debian.org/ Debian] {{Stable project version based on Debian codename}} or {{Kicksecure}} {{VersionShort}} -- as the host operating system. # [[File:logo-linux-500x500.png|15px|link=]] Linux users only: Linux user groups: Add your current user to group vboxusers. Optional: See: https://www.virtualbox.org/manual/ch02.html#install-linux-vboxusers Also spams ~/.config/VirtualBox/VBoxSVC.log log if not done. {{CodeSelect|code= sudo adduser $(whoami) vboxusers }} # [[File:Logo-windows-500x500.png|15px|link=]] Windows users only: Host operating system: Consider running {{project_name_short}} from a Linux computer rather than Windows computer. [https://forums.whonix.org/t/gateway-startup-error-not-syncing-no-working-init-found/9481/13 A user reported issues which were gone once switching to Linux]. # Virtualizers Conflicts: Do you have virtualizers other than VirtualBox installed at the same time such as [[image:Vmware.jpeg|25px|link=]] VMware, Hyper-V or [[Image:Kvm-new-logo.png|25px|link=]] KVM? If you never heard of these product names or do not know what that means then this is not an issue, But if you have multiple virtualizers/hypervisors installed its preferable to use only one (in this section only virtualbox) see the footnote for further information. Virtualizers are incompatible with co-installation of other virtualizers at the same time. This is virtualizer specific, not a {{project_name_short}} specific limitation. Uninstall any other virtualizers and perhaps re-install VirtualBox if it still not functional. https://forums.whonix.org/t/starting-xcfe-virtualbox-give-guru-meditation/10378/6 # Low RAM Issues: Perhaps a [[Troubleshooting#Low_RAM_Issues|Low RAM issue]]? [[Troubleshooting#Free_up_Additional_Memory_Resources|Free up Additional Memory Resources]] and try {{project_name_gateway_long}} CLI RAM Saving Mode as per [[RAM|Advice for Systems with Low RAM]]. # Hardware Issues: Exclude basic [[Troubleshooting#Hardware Issues|hardware issues]]. # RAM Hardware Issues: Run memtestx86+. # [[#Testing with a Debian VM|Testing with a Debian VM]]. # [[#VirtualBox Generic Bug Reproduction|VirtualBox Generic Bug Reproduction]] # [[File:Logo-windows-500x500.png|15px|link=]] Windows 10 users only: Hash Sum mismatch: [[#Core Isolation|Disable Core Isolation]]. }} = Linux Host Kernel versus Tor Browser and other Crashes = This issue happens after a Linux host kernel upgrade. Common symptoms of this issue are: * APT showing hashsum mismatch. * {{kicksecure_wiki |wikipage=Kernel#Kernel_Issues |text=other kernel issues }} * Tor Browser crashes. 
ERROR: Tor Browser ended with non-zero (error) exit code!

Tor Browser was started with:

/home/user/.tb/tor-browser/Browser/start-tor-browser --verbose --allow-remote .

Tor Browser exited with code: 139
This is fixed since VirtualBox version 6.1.36 and above. For installation instructuctions, see [[VirtualBox/Recommended Version|recommended VirtualBox version]]. Forum discussion: https://forums.whonix.org/t/tor-browser-crashing-in-whonix-virtualbox-since-upgrade-to-host-linux-kernel-version-5-10-0-15/13767 = Failed to open a session for the virtual machine = If you see the following error message:
Failed to open a session for the virtual machine {{project_name_short}}-Xfce
Click details. If Result Code: NS_ERROR_FAILURE (0x80004005) is shown, then this chapter applies. Should be fixed in VirtualBox version 6.1.22 and above. This occurs with all {{project_name_short}} VirtualBox versions up to version 15.0.1.7.2 when using VirtualBox version 6.1.20. VirtualBox version 6.1.20 solution: * VirtualBox → Settings → Storage → Type: AHCI → OK For reasons, see [[Dev/VirtualBox#Storage_Controller_Setting|Storage Controller Setting]]. * Other settings remain unchanged. This setting is the default in {{project_name_short}} version 15.0.1.7.3 and above ([[Point Release]]). Note this setting might cause [[#High Disk Usage Causing Filesystem Corruption|High Disk Usage Causing Filesystem Corruption]] on some (slower) hardware configurations due to a VirtualBox host software bug, [https://www.virtualbox.org/ticket/10031 High I/O causing filesystem corruption]. This is speculation and unavoidable because there is no other solution at present. The [[#High Disk Usage Causing Filesystem Corruption|High Disk Usage Causing Filesystem Corruption]] chapter has approaches which might fix this issue if it manifests. To avoid issues like Failed to open a session for the virtual machine in the future, use the the [[VirtualBox/Recommended_Version|recommended]] version of the VirtualBox host software and [[Stay Tuned]]. Forum discussion: [https://forums.whonix.org/t/whonix-virtualbox-failed-to-start-ns-error-failure-0x80004005-the-vm-session-was-aborted/11471 {{project_name_short}} VirtualBox - failed to start - NS_ERROR_FAILURE (0x80004005) - The VM session was aborted.] VirtualBox upstream bug report: [https://www.virtualbox.org/ticket/20323 VM Machine wont to start after upgrade to 6.1.20] = VT-x = == VERR_SSM_FIELD_NOT_CONSECUTIVE == If the "{{Code2|Failed to load unit 'PATM' (VERR_SSM_FIELD_NOT_CONSECUTIVE).}}" error appears, VT-x must be enabled in BIOS settings, see [[#BIOS|instructions]]. {{Anchor|VT-x_is_disabled_in_the_BIOS.}} {{Anchor|VT-x}} == VT-x is disabled in BIOS == File:VirtualBox_VERR_VMX_MSR_LOCKED_OR_DISABLED.png|'''Figure:''' VERR_NEM_NOT_AVAILABLE / VERR_SVM_DISABELD File:VERR_VMX_MSR_VMXON_DISABLED.png|'''Figure:''' ''VERR_VMX_MSR_VMXON_DISABLED / VERR_NEM_NOT_AVAILABLE'' If the following error message appears. {{quotation| quote=Failed to open a session for the virtual machine Kicksecure-Xfce. VT-x is disabled in the BIOS. (VERR_VMX_MSR_VMXON_DISABLED). }} Or. {{quotation| quote=AMD-V is disabled in the BIOS (or by the host OS). (VERR_SVM_DISABLED). }} Then [[#BIOS|enable VT-x in BIOS settings]]. {{Anchor|BIOS}} == VT-x / SVM Errors == [[File:Enable-vt-x-in-bios.png|thumb|enabling VT-x in BIOS]] These errors arise when the host's hardware virtualization extension is not available. The reasons are either/and/or: * '''A)''' it is controlled by another hypervisor running on the system, * '''B)''' an anti-virus suite or * '''C)''' it is not present/enabled by the machine BIOS. To check, go to your BIOS settings. For basic instructions, see: [https://www.wikihow.com/Change-Computer-BIOS-Settings How to Change Computer BIOS Settings]. Then enable VT-x. This is sometimes also called AMD-V, virtualization, SVM mode or MIT perhaps under Advanced Core settings. = Updating/Upgrading while VM are Running = == Error In supR3HardenedWinReSpawn == {{ContentImage| [[File:VirtualBox_supR3HardenedWinReSpawn.png|400px]] }} Do not update whilst the VM are running, otherwise [[VirtualBox]] must be reinstalled. == VMMR0InitVM: Revision mismatch == 
debian kernel: VMMR0InitVM: Revision mismatch, r3=132055 r0=130347
This happens when upgrading VirtualBox on the host while existing VM are still running. The solution is to shut down and restart all VM. = Disk Space = == E_INVALIDARG (0x80070057) == This '''might''' relate to a '''low disk space issue''' -- [[Unspecific|unspecific to {{project_name_short}}]] -- [[Please_Use_Search_Engines_And_See_Documentation_First|research the issue further with search engines]]. A user reported:
During Import, on Application Settings pop up. Setting called "Additional Options: __ Import hard drives as VDI". Unselecting this got me past this error.
This might be the case because if no conversion to VDI is required that less disk space might be sufficient. = Non-functional Shared Clipboard and Drag and Drop = If the shared clipboard and drag’n’drop to/from host is non-functional, this can relate to the version of guest additions installed in {{project_name_short}} and/or the version of VirtualBox running on the host. * https://forums.whonix.org/t/whonix-15-shared-clipboard-and-dragndrop-not-working/7723 * Upstream bug report: [https://www.virtualbox.org/ticket/19336 Linux guest: shared clipboard doesn't work (on fresh VirtualBox-6.1.4-136177) => fixed in 6.1.6] # Apply [[#General_VirtualBox_Troubleshooting_Steps|General VirtualBox Troubleshooting Steps]]. # VirtualBox → Settings → General → Advanced tab → 'Check' shared clipboard and drag and drop It might still not work, see: [[Dev/VirtualBox#VirtualBox_Guest_Additions_Bugs|VirtualBox Guest Additions Bugs Reporting]]. = Screen Issues = == Screen Resolution Bug == {{Anchor|VirtualBox Screen Resolution Bug}} [[File:cli4.png|thumb|VirtualBox Screen Resolution Bug]] [[File:cli3.png|thumb|Normal presentation]] If the display presents like the image on the right-hand side, then you are affected by a screen resolution bug which only occurs in VirtualBox. To correct the resolution, first apply the [[VirtualBox/Troubleshooting#General_VirtualBox_Troubleshooting_Steps|General VirtualBox Troubleshooting Steps]]. If the issue still persists, try one of the following workarounds to correct the resolution. '''VirtualBox Virtual Screen Menu Workaround''' # Power off the VM. # Restart the VM. # Maximize the VM window after start of the VM as soon as possible. # VirtualBox VM Window → View → Virtual Screen 1 → Choose any, resize to another resolution # VirtualBox VM Window → View → Auto-resize Guest Display ----- '''Desktop Resolution Settings Workaround''' If the method above did not work, another option is the following. Inside the virtual machine: Xfce Start Menu → Settings → Display → Resolution: → Choose a higher resolution resolution → Apply ----- '''VirtualBox VMSVGA Graphics Controller Setting Workaround''' If it still does not work, a final option is the following. Inside the virtual machine VirtualBox VMSVGA graphics controller is based on the VMware graphics controller. : On the host: # Power off the VM. # VirtualBox → click a VM → Settings → Display → Graphics Controller → VMSVGA → OK (This is already the case in newer {{project_name_short}} versions.) # VirtualBox → click a VM → Settings → Display → Graphics Controller → increase slider for Video Memory to 128 → OK (This is already the case in newer {{project_name_short}} versions.) # Restart the VM. # Maximize the VM window after start of the VM as soon as possible. # If necessary, try again one of above workarounds. ----- '''VirtualBox Guest Additions Bugs Reporting''' Occasionally screen resolution problems might still persist, see: [[Dev/VirtualBox#VirtualBox_Guest_Additions_Bugs|VirtualBox Guest Additions Bugs Reporting]]. == Black Screen == If a black screen appears, try the following possible solutions. # Install the [[VirtualBox/Recommended_Version|recommended]] version of the VirtualBox host software. # Apply the [[#General_VirtualBox_Troubleshooting_Steps|General VirtualBox Troubleshooting Steps]]. # Reboot. # If the issue persists, try the following workarounds. If this solution or any of the workarounds worked for you, please report this in [https://forums.{{project_clearnet}} {{project_name_short}} forums]. ----- '''Workaround 1: Try Other VirtualBox Virtual Graphics Controller Settings''' # Power off the VM. # VirtualBox → click a VM → Settings → Display → Graphics Controller → VMSVGA → OK (Or try other settings there.) {{CodeSelect|code= VBoxManage modifyvm Kicksecure-Xfce --graphicscontroller vmsvga }} {{CodeSelect|code= VBoxManage modifyvm Kicksecure-Xfce --graphicscontroller vboxvga }} {{CodeSelect|code= VBoxManage modifyvm Kicksecure-Xfce --graphicscontroller vboxsvga }} # VirtualBox → click a VM → Settings → Display → Graphics Controller → increase slider for Video Memory to 128 → OK (This is already the default in recent releases of {{project_name_short}}.) # Restart the VM. ----- '''Workaround 2: Boot Once Without Virtual Graphics Adapter''' This workaround has been reported as functional on a Windows 10 host with both Intel and nVidia GPU capabilities. It is okay to try this workaround on any host operating system. # Power off the VM. # VirtualBox → click a VM → Settings → Display → Graphics Controller → None → OK # Start the VM. Wait 2-3 minutes. ''(Since the display is disabled, you will see nothing happening)'' # Click the VirtualBox pane's [X] button. VirtualBox will offer a dialog with 3 options. If Send Shutdown signal is greyed out, cancel the dialog and try this step again every 10-20 seconds. # Send Shutdown signal. If it does not shut down immediately, wait a short time and try again. # Once the VM shuts down, restore the Graphics Controller to VMSVGA. # Restart the VM. ''If this workaround succeeds, the screen will again be black for 2-3 minutes, but then chkdsk will run and the VM should start normally.'' ----- '''Workaround 3: nomodeset Kernel Parameter''' Try to [[Grub#Kernel_Boot_Parameter_Change|boot with the nomodeset kernel parameter]]. If that works, please post a forum report and then [[Grub#Permanent_Configuration_Changes|make the change permanent]]. https://forums.whonix.org/t/whonix-cli-15-0-0-9-4-gateway-shows-a-black-screen/9174/2 ----- '''Workaround 4: Virtual Console''' If it is possible to switch to a [[Desktop#Virtual_Consoles|virtual console]], this can help with debugging. == Slow Video Playback == Possible solutions: # Untested: Try downloading a video using [https://whonix.org/wiki/yt-dlp yt-dlp] ([http://www.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/wiki/yt-dlp .onion]) and then play the video in VLC. # Tested: Consider [[Tuning]], specifically [[Tuning#Hardware-accelerated_Graphics|enable hardware-accelerated graphics]]. Note that this configuration worsens security. # Untested: Consider [[Tuning#Disable_CPU_Mitigations|disabling CPU mitigations]]. This configuration also worsens security. It is unknown whether enabling VirtualBox hardware-accelerated graphics (3D Acceleration) or disabling CPU mitigations is worse for security. Contributors are asked to research this issue ([[Self_Support_First_Policy|Self Support First Policy]]) and report what is found in a dedicated forum thread. = Miscellaneous = == Host Crash == See the [[#Aborted Status|Aborted Status]] instructions below. == Aborted Status == If the virtual machine ever shows an aborted status, perform these steps: # Try to [[#Assign Less Virtual CPUs|Assign Less Virtual CPUs]]; this may help to avoid the issue. # Check for [[Troubleshooting#Low_RAM_Issues|Low RAM issues]]. # Apply [[#General_VirtualBox_Troubleshooting_Steps|General VirtualBox Troubleshooting Steps]]. # Consider reporting a bug against upstream [https://www.virtualbox.org VirtualBox] -- [https://www.virtualbox.org/wiki/Bugtracker VirtualBox bugtracker] / [https://forums.virtualbox.org VirtualBox forums]. VirtualBox developers require logs to identify the problem. [https://forums.virtualbox.org/viewtopic.php?f=7&t=77663#p361694 Reasons of vm to get into "aborted" state]:
Would you mind sharing with us one of those logs so that we can judge for ourselves? From a machine that got aborted? ZIP it before using the "Upload attachment" at the bottom of your reply form.
{{project_name_short}} provides VM image that operate inside of the VM. Whatever occurs inside a VM should never lead to a crash (status aborted) of the host virtualization software, VirtualBox. Recommended steps: # To capture the VirtualBox log: VirtualBox → right click a VM → Show Log... → Log → Save → OK # Zip the log. # Report to VirtualBox support. # Share the VirtualBox support request link in {{project_name_short}} forums. == Guru Mediation == {{project_name_short}} provides VM image that operate inside of the VM. Whatever occurs inside a VM should never lead to a Guru Mediation of the host virtualization software, VirtualBox. Posting a screenshot of the Guru Mediation screen is probably not required since these all look very similar. http://www.fixedbyvonnie.com/wp-content/uploads/2014/09/fixedbyvonnie-virtualbox-guru-meditation.png
VirtualBox Guru Meditation A critical error has occurred while running the virtual machine and the machine execution has been stopped. For help, please see the Community section on https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the /home/sk/VirtualBox VMs/Ubuntu 20.04 Server/Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window. Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special knowledge and tools, so it is recommended to press OK now.
This example text does not contain any technical details which could help to fix the issue, since VirtualBox Guru Meditation can occur for many reasons. Recommended steps to resolve VirtualBox Guru Meditation issues: '''1.''' Apply [[#General_VirtualBox_Troubleshooting_Steps|General VirtualBox Troubleshooting Steps]]. These often help resolving such issues. '''2.''' Capture the VirtualBox log Without log contents, developers will probably be unable to help. VirtualBox → right click a VM → Show Log... → Log → Save → OK '''3.''' Consider inspecting the log yourself. Use search engines to try and locate any similar or identical error messages. Usually the issue will already have been reported, and a solution might be documented in the same place. It is recommended to search the offical VirtualBox website because most VirtualBox developers and experts will utilize this resource. The following search term will limit search results to the VirtualBox website (this is a feature which most search engines support): site:virtualbox.org error message here. Replace error message here with the issue being investigated. '''4.''' Consider reporting a bug against upstream [https://www.virtualbox.org VirtualBox]. * Zip the log. * Post the log at [https://www.virtualbox.org/wiki/Bugtracker VirtualBox bugtracker] or [https://forums.virtualbox.org VirtualBox forums]. * VirtualBox developers require logs to investigate the problem. '''5.''' Share the VirtualBox support request link in {{project_name_short}} forums. '''6.''' Done. Hopefully help can be provided. == NS_ERROR_FAILURE == 
NS_ERROR_FAILURE (0x80004005)
[https://forums.virtualbox.org/viewtopic.php?f=8&t=87306 Quote VirtualBox forum moderator]
NS_ERROR_FAILURE (0x80004005) is a general failure message when loading a VM. Subsequent lines in the error dialog will give the exact cause of the error. You do NOT have the same error just because you see the generic leader. If you don't provide a log or the supplemental error description then we can't help you.
While this is not the same error as Guru Mediation, all the same information and advice from that chapter applies. Therefore please follow chapter [[#Guru Mediation|Guru Mediation]]. == Kernel driver not installed == [[File:Virtualbox kernel driver not installed.png|thumb|error happening in case Linux kernel headers package (linux-headers-amd64) is missing]] [[File:Virtualbox kernel driver not installed vboxconfig.png|thumb|output of sudo vboxconfig in case Linux kernel headers package (linux-headers-amd64) is missing]] Kernel driver not installed (rc=-1908) If this occurs on Linux based host operating systems, then it is likely the Linux headers package matching the currently running Linux image package is not installed. To attempt to fix the issue: '''1.''' Go to the [[VirtualBox/Recommended Version|Recommended VirtualBox Version]] wiki page. '''2.''' Press the expand button for your operating system. If you Linux, press the Expand button on that wiki page. Once expanded, the recommended instructions will explain how to install VirtualBox for select Linux distributions as well as generic recommendations for other Linux distributions. '''4.''' Apply the installation instructions from that wiki page. '''5.''' Issue resolved? This issue is unspecific to {{project_name_short}}. Any VM from any vendor and/or self-created VM will fail to start, not just {{project_name_short}} VM. This is because it is a host operating system and VirtualBox issue. If the instructions above did not fix the issue, then try accessing further support resources including the [[#Testing with a Debian VM|Testing with a Debian VM]] chapter. '''6.''' Support requests. For support requests, please provide the following debug output. Is package linux-headers-amd64 installed? To check, run: 
dpkg -l | grep linux-headers-amd64
Is package linux-image-amd64 installed? To check, run: 
dpkg -l | grep linux-image-amd64
== Assign Less Virtual CPUs == Try assigning less virtual CPUs. VirtualBox ticket: [https://www.virtualbox.org/ticket/19500 VirtualBox should now prohibit assigning all physical CPUs to a VM and/or fix VirtualBox CPU assignment manual]. In {{project_name_short}} 15.0.1.3.4 and above 3 virtual CPUs is now the default setting; 4 were previously used. As a result, this workaround should no longer be required for most users. # Power off the VM. # VirtualBox → click a VM → Settings → System → Processor → Reduce to 3 → OK == INCONSISTENCY BETWEEN GRAIN TABLE AND BACKUP GRAIN TABLE == If this error appears, sometimes it helps to: # Try and convert the vmdk to vdi. # Remove the old vmdk from the VM. # Attach the new vdi. == High Disk Usage Causing Filesystem Corruption == This is a VirtualBox host software bug, [https://www.virtualbox.org/ticket/10031 High I/O causing filesystem corruption]. The following settings cannot fix already existing filesystem corruption inside the virtual harddrive. However, these settings might prevent future filesystem corruption. Therefore the best time to experiment with these settings is before starting a virtual machine for the first time or at least before issues appear. Enabling Host I/O Cache might help as it was [https://www.virtualbox.org/ticket/10031#comment:22 reported by a user on the VirtualBox issue tracker]. VirtualBox → Settings → Storage → Name: SATA → Type: AHCI → enable Use Host I/O Cache → OK Experimenting with other virtual machine hardware settings might also help. VirtualBox → Settings → Storage → Name: → experiment with other settings → OK Maybe Type: virtio-scsi could help. Other settings that might help: * https://www.virtualbox.org/manual/ch12.html#ts_config-periodic-flush * https://www.virtualbox.org/manual/ch12.html#ts_ide-sata-flush * Quote https://www.virtualbox.org/ticket/10031#comment:2
Try to tune host os page flusher behavior to avoid accumulating of significant amount of dirty pages in host file system buffers. For example, set vm.dirty_background_ratio to 5 or below (this is still large size - about 1Gb) or set vm.dirty_background_bytes to something smaller like 20971520 to make page flusher more active. Note that this may make host file system cache less effective, but it prevents write operation stuck during buffer flush.
References: * VirtualBox host software bug, [https://www.virtualbox.org/ticket/10031 High I/O causing filesystem corruption] * Old issue tracker discussion: [https://web.archive.org/web/20210122015240/https://github.com/Whonix/Whonix/issues/274 VirtualBox AHCI] * [https://www.virtualbox.org/manual/ch05.html#harddiskcontrollers VirtualBox manual: Hard Disk Controllers] == Import {{project_name_short}} Image == Using the VirtualBox GUI to import {{project_name_short}} image should work well in most cases. If not, follow the steps below. {{Box|text= '''1.''' Check if there is enough free disk space. '''2.''' Refer to the {{project_name_short}} installation screenshots ([[VirtualBox]] and click expand button) and/or [[Videos|Video Tutorials]]. '''3.''' Delete any half-imported or otherwise broken virtual machine image. '''4.''' Use the VBoxManage command line tool and copy the output. {{CodeSelect|code= VBoxManage unregistervm "{{project_name_short}}-Xfce" --delete }} '''5.''' Navigate to the folder where {{project_name_short}} was downloaded and import {{project_name_short}} by using the VBoxManage command line tool. {{CodeSelect|code= VBoxManage import {{project_name_short}}-Xfce-{{VersionNew}}.ova }} '''6.''' Clean the output. Remove operating system user name or any problematic file paths. '''7.''' [[Contact|Contact lead {{project_name_short}} developer]] Patrick Schleizer and send the output. }} == No Sound in {{project_name_workstation_long}} == If sound is unavailable in {{project_name_workstation_short}} when using VLC or browsing Internet sites, try: [https://forums.whonix.org/t/whonix-workstation-no-sound/12155 {{project_name_short}} workstation no sound] Settings → Audio → Host audio driver → Select Also audio If may also be necessary to install alsamixergui. {{Anchor|Try a non-Whonix VM}} == Core Isolation == Host operating system specific: * [[File:logo-linux-500x500.png|15px|link=]] Linux users: No special steps required. This chapter should be skipped. * [[File:Logo-windows-500x500.png|15px|link=]] Windows 10 users: This should be fixed in recent VirtualBox versions. Fixed in VirtualBox version 6.1.32 (and above). Quote [https://www.virtualbox.org/wiki/Changelog VirtualBox changelog]:
VMM: Changed the guest RAM management when using Hyper-V to be more compatible with HVCI (bug [https://www.virtualbox.org/ticket/20627 #20627] and [https://www.virtualbox.org/ticket/20694 #20694])
 Disabling core isolation should be no longer required. In case of issues, the user could try to disable core isolation anyhow. Core Isolation is also called Windows Hypervisor-enforced Code Integrity (HVCI). Start Menu → Settings → Update & security → Windows Security → Device security → Core isolation details, turn off Memory integrity → reboot the host operating system Related: [https://forums.whonix.org/t/hash-sum-mismatch-downloads-all-fail-since-win10-2004-update/9740/2 forum discussion on Windows core isolation] = Testing with a Debian VM = {{Anchor|Test a non-{{project_name_short}} VM}} Before diving into issues related to {{project_name_short}}, it's a good idea to first ensure that the underlying platform and software are functioning correctly. # Start by testing the VirtualBox host software as if you've never encountered {{project_name_short}}. This will give you a baseline. # As a next step, try using a VM that isn't based on {{project_name_short}}. A good candidate would be Debian {{Stable project version based on Debian codename}}. # If you continue to face issues with the Debian VM, it indicates that the problem isn't specific to {{project_name_short}}. Such issues that are [[unspecific]] to {{project_name_short}} should be tackled according to these guidelines: * [[VirtualBox/Troubleshooting#VirtualBox_Generic_Bug_Reproduction|VirtualBox Generic Bug Reproduction]] * [[Self_Support_First_Policy|Self Support First Policy]] * [[Reporting_Bugs#Generic_Bug_Reproduction|Generic Bug Reproduction]] = VirtualBox Generic Bug Reproduction = This entry is based on [[Reporting_Bugs#Bug_Report_Recommendations|Bug Report Recommendations]], specifically [[Reporting_Bugs#Generic_Bug_Reproduction|Generic Bug Reproduction]]. The content is similar to the [[#Testing with a Debian VM|Testing with a Debian VM]] chapter above. The following is a manual reproduction of the [[Dev/VirtualBox#VirtualBox_Integration|{{project_name_short}} VirtualBox Integration]]. {{box|text= '''1.''' Host operating system choice. Use the [https://www.whonix.org/wiki/Host_Operating_System_Selection#Recommended_Linux_Distribution recommended] ([http://www.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/wiki/Host_Operating_System_Selection .onion]) Linux distribution. Either, * '''A)''' [https://www.debian.org/ Debian] {{Stable project version based on Debian version short}} "{{Stable project version based on Debian codename}}", or * '''B)''' Debian testing. Debian {{Stable project version based on Debian version short}} is preferable. See also [[Debian Tips]]. During installation, preferably choose the same desktop environment that {{project_name_short}} is using, which is Xfce at time of writing. '''2.''' Install the [[VirtualBox/Recommended_Version|recommended version of the VirtualBox host software]] and follow the instructions from that wiki page. '''3.''' Install Debian {{Stable project version based on Debian codename}} inside a VirtualBox VM. '''4.''' Install the VirtualBox Guest Additions inside the VirtualBox VM. Choose either option '''A)''' or '''B)'''. {{Tab| type=controller |content= {{Tab |title= {{headline|h=2|content=A) Install VirtualBox Guest Additions from the Debian fasttrack repository}} |content= '''A)''' Inside the VirtualBox VM. Open a terminal. '''B)''' Add the Debian fasttrack repository. Update the package lists. {{CodeSelect|code= sudo apt update }} '''C)''' Install the Debian fasttrack signing key. {{CodeSelect|code= sudo apt install fasttrack-archive-keyring }} '''D)''' Add the Debian fasttrack repository. {{CodeSelect|code= echo 'deb https://fasttrack.debian.net/debian/ {{Stable_project_version_based_on_Debian_codename}}-fasttrack main contrib non-free' {{!}} sudo tee /etc/apt/sources.list.d/fasttrack.list }} '''E)''' Update the package lists again. This is to acquire the Debian fasttrack repository package sources. {{CodeSelect|code= sudo apt update }} '''F)''' Install the VirtualBox Guest Additions. {{CodeSelect|code= sudo apt install virtualbox-guest-x11 }} '''G)''' Reboot required. {{CodeSelect|code= sudo reboot }} '''H)''' VirtualBox Guest Additions should now be installed. The procedure of installing the VirtualBox Guest Additions is complete. }} {{Tab |title= {{Headline|h=2|content=B) Install VirtualBox Guest Additions from the Debian sid repository}} |content= '''NOTE:''' This works only when using Debian testing. '''A)''' Inside the VirtualBox VM. Open a terminal. '''B)''' Add APT pinning preferences. The purpose of this is to install only as few applications from Debian unstable as possible. 1) {{Open with root rights|filename= /etc/apt/preferences.d/40-pinning }} 2) Paste the following content. {{CodeSelect|code= Package: * Pin: release a=testing Pin-Priority: 700 Package: * Pin: release a=unstable Pin-Priority: 650 }} 3) Save and close the file. '''C)''' Add the Debian unstable repository. {{CodeSelect|code= echo 'deb https://deb.debian.net/debian/ unstable main contrib non-free' {{!}} sudo tee /etc/apt/sources.list.d/unstable.list }} '''E)''' Update the package lists. {{CodeSelect|code= sudo apt update }} '''F)''' Install the VirtualBox Guest Additions. {{CodeSelect|code= sudo apt install virtualbox-guest-x11 }} '''G)''' Reboot required. {{CodeSelect|code= sudo reboot }} '''H)''' VirtualBox Guest Additions should now be installed. The procedure of installing the VirtualBox Guest Additions is complete. }} }} '''5.''' Attempt to reproduce the original issue. * '''A)''' If the original issue is reproducible: That means the root issue is not caused by {{project_name_short}}. In other words, the issue is [[unspecific]] to {{project_name_short}}. In that case it is recommended to try and resolve the issue as per [[Self_Support_First_Policy|Self Support First Policy]]. If a solution was found, please consider editing the [[Documentation|{{project_name_short}} Documentation]] as a contribution and/or providing a complete answer in the {{project_name_short}} User Forums. * '''B)''' If the original issue is not reproducible: Please report this in [https://forums.{{project_clearnet}} {{project_name_short}} forums]. }} The following deprecated instructions chapter [[Deprecated#VirtualBox Generic Bug Reproduction using virtualbox-guest-additions-iso|VirtualBox Generic Bug Reproduction using virtualbox-guest-additions-iso]] is probably not required but kept here in case it will be needed again in the future. = Submit a Bug Report = When reporting an issue in the [https://forums.{{project_clearnet}} {{project_name_short}} forums], please add the exact steps which led to the problem. Also include as much relevant information as possible; see below. * Which {{project_name_short}} version was downloaded and from where? * Do other non-{{project_name_short}}-VMs such as Debian VMs have this issue? * Did you: ** Only download, import {{project_name_short}} VM and start {{project_name_short}}?; or ** Did you start and use {{project_name_short}} then installed more software and perform other activities before the issues emerged? * Have you previously used older versions of {{project_name_short}} that worked? * What is the host operating system and version? * What is the VirtualBox version? * How much RAM does the host have? * In case of black screen issues: ** Can you switch to a [[Desktop#Virtual_Consoles|virtual console]]? This can help with debugging. Bugs can also be reported against upstream [https://www.virtualbox.org VirtualBox]: [https://www.virtualbox.org/wiki/Bugtracker VirtualBox bugtracker] / [https://forums.virtualbox.org VirtualBox forums]. Bug reports must be well written and thorough otherwise it will not lead to a solution, see: [https://forums.virtualbox.org/viewtopic.php?f=3&t=87130#p416223 bug reporting instructions]. = See Also =
* [[Troubleshooting]] * [[RAM|Advice for Systems with Low RAM]] * [[Support]] * [[Reporting Bugs]] * [[VirtualBox/Guest_Additions|VirtualBox Guest Additions and Shared Folders]] * [[VirtualBox/Guest_Additions#VirtualBox_Guest_Additions|VirtualBox Guest Additions]] * [[VirtualBox]] * [[VirtualBox Testers Only Version]] * [[VirtualBox/Recommended Version|Recommended VirtualBox Version]] * [[VirtualBox/Other Versions|Install Newer Versions of VirtualBox]] * [[VirtualBox/Appliance is not signed|VirtualBox "Appliance is not signed" Error Message]] * [[VirtualBox/Higher Screen Resolution without installing VirtualBox Guest Additions|Higher Screen Resolution without VirtualBox Guest Additions]] * [[Virtualization Platform Security]] * [[Dev/VirtualBox]] ** [[Dev/VirtualBox#VirtualBox_Integration|VirtualBox Integration]]
= Footnotes = {{reflist|close=1}} {{Footer}} [[Category:Documentation]]