Actions

Whonix ™ in VirtualBox - Troubleshooting - Whonix ™ does not Start?

From Whonix

< VirtualBox



Vboxtroubleshoot123123.jpg
Failed to open a session for the virtual machine / NS_ERROR_FAILURE (0x80004005)See this.
VERR_VMX_MSR_VMXON_DISABLED / VERR_NEM_NOT_AVAILABLE → Enable VT-x in BIOS settings.
Black screen? → See this. Aborted Status? → See this. Guru Mediation? → See this.

Topics on this page are sorted roughly in order of issue prevalence. More common issues are on top.

General VirtualBox Troubleshooting Steps[edit]

Ambox notice.png In many situations, the following steps will fix VirtualBox issues.

  1. General Troubleshooting for issues such as freeze issues.
  2. In case of connectivity issues, see Connectivity Troubleshooting.
  3. Whonix old logo.png Use the stable version of Whonix ™ for VirtualBox 15.0.1.9.3.
  4. Computer n screen.png Virtualbox logo.png Use the recommended VirtualBox host software version 6.1.22.
  5. Cli3.png Virtualbox logo.png To ensure the recommended version of VirtualBox guest additions is installed in Whonix ™, in both Whonix-Gateway ™ VM and Whonix-Workstation ™ VM run.
    sudo apt-get update && sudo apt-get dist-upgrade

  6. Cd-699786640.jpg Virtualbox logo.png Do not use VirtualBox guest additions from CD. [1]
  7. Tux.png Linux users only: use the recommended host Linux kernel version. That the same version as Debian buster is using linux-image-amd64 [archive]. [2]
  8. Tux.png Linux users only: use the recommended Linux distribution Debian Linux [archive] version buster as host operating system.
  9. Tux.png Linux users only: Add your current user to group vboxusers. [3]
    sudo adduser $(whoami) vboxusers

  10. Windows logo - 2012.svg.png Windows users only: consider running Whonix ™ from a Linux computer rather than Windows computer, see Host Operating System Selection. [4]
  11. Do you have virtualizers other than VirtualBox installed at the same time such as Vmware.jpeg VMware, Hyper-V or Kvmbanner-logo26.png KVM? If you never heard of these product names or do not know what that means then this probably is not your issue. Otherwise don't; see the footnote for further information. [5]
  12. Perhaps a Low RAM issue? Free up Additional Memory Resources and try Whonix-Gateway ™ CLI RAM Saving Mode as per Advice for Systems with Low RAM.
  13. Exclude basic hardware issues.
  14. Run memtestx86+.
  15. Try a non-Whonix VM.
  16. VirtualBox Generic Bug Reproduction
  17. Windows logo - 2012.svg.png Windows 10 users only: Hash Sum mismatch? [archive]

Failed to open a session for the virtual machine[edit]

If you see the following error message:

Failed to open a session for the virtual machine Whonix-Gateway-XFCE

Failed to open a session for the virtual machine Whonix-Workstation-XFCE

Click details. If Result Code: NS_ERROR_FAILURE (0x80004005) is shown, then this chapter applies.

Happens with all Whonix ™ VirtualBox versions up to version 15.0.1.7.2 when using VirtualBox version 6.1.20.

VirtualBox version 6.1.20 solution: VirtualBoxSettingsStorageType: AHCIOK [6]

Other settings can be left as is.

This setting is the default in Whonix ™ version 15.0.1.7.3 (Point Release).

(This setting might lead the to issue High Disk Usage Causing Filesystem Corruption on some (slower) hardware configurations due to VirtualBox host software bug, High I/O causing filesystem corruption [archive]. It's speculation and unavoidable. There is no other solution at the moment. Wiki chapter High Disk Usage Causing Filesystem Corruption already contains approaches which might fix this issue in case it manifests.)

To avoid issues such as Failed to open a session for the virtual machine in the future, use the the recommended version of the VirtualBox host software and Stay Tuned.

forum discussion: Whonix VirtualBox - failed to start - NS_ERROR_FAILURE (0x80004005) - The VM session was aborted. [archive]

VirtualBox upstream bug report: VM Machine wont to start after upgrade to 6.1.20 [archive]

VT-x[edit]

VERR_SSM_FIELD_NOT_CONSECUTIVE[edit]

If the "Failed to load unit 'PATM' (VERR_SSM_FIELD_NOT_CONSECUTIVE)." error appears, VT-x must be enabled in BIOS settings, see instructions.

VT-x is disabled in BIOS[edit]

VERR_VMX_MSR_VMXON_DISABLED
VERR_NEM_NOT_AVAILABLE

If the following error message appears.

Failed to open a session for the virtual machine Whonix-Gateway-XFCE.

VT-x is disabled in the BIOS.
(VERR_VMX_MSR_VMXON_DISABLED).

Or.

AMD-V is disabled in the BIOS (or by the host OS).
(VERR_SVM_DISABLED).

Then enable VT-x in BIOS settings.

Enable VT-x in BIOS[edit]

Go to your BIOS settings. For basic instructions, see: How to Change Computer BIOS Settings [archive].

Then enable VT-x. This is sometimes also called AMD-V, virtualization, SVM mode or MIT perhaps under Advanced Core settings.

Updating/Upgrading while VMs are Running[edit]

Error In supR3HardenedWinReSpawn[edit]

VirtualBox supR3HardenedWinReSpawn.png
Do not update whilst the VMs are running, otherwise VirtualBox must be reinstalled.

VMMR0InitVM: Revision mismatch[edit]

debian kernel: VMMR0InitVM: Revision mismatch, r3=132055 r0=130347

This happens when upgrading VirtualBox on the host while existing VMs are still running. The solution is to shut down and restart all VMs.

Disk Space[edit]

E_INVALIDARG (0x80070057)[edit]

This might relate to a low disk space issue -- research the issue further with search engines.

Non-functional Shared Clipboard and Drag and Drop[edit]

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 Whonix and/or the version of VirtualBox running on the host. [7]

  1. Apply General VirtualBox Troubleshooting Steps.
  2. VirtualBoxSettingsGeneralAdvanced tab'Check' shared clipboard and drag and drop

It might still not work, see: VirtualBox Guest Additions Bugs Reporting.

Screen Issues[edit]

Screen Resolution Bug[edit]

VirtualBox Screen Resolution Bug
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 General VirtualBox Troubleshooting Steps.

If the issue still persists, try one of the following workarounds to correct the resolution.

VirtualBox Virtual Screen Menu Workaround

  1. Power off the VM.
  2. Restart the VM.
  3. Maximize the VM window after start of the VM as soon as possible.
  4. VirtualBox VM WindowViewVirtual Screen 1Choose any, resize to another resolution
  5. VirtualBox VM WindowViewAuto-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 MenuSettingsDisplayResolution:Choose a higher resolution resolutionApply


VirtualBox VMSVGA Graphics Controller Setting Workaround

If it still does not work, a final option is the following.

Inside the virtual machine [8]:

On the host:

  1. Power off the VM.
  2. VirtualBoxclick a VMSettingsDisplayGraphics ControllerVMSVGAOK (This is already the case in newer Whonix ™ versions.)
  3. VirtualBoxclick a VMSettingsDisplayGraphics Controllerincrease slider for Video Memory to 128OK (This is already the case in newer Whonix ™ versions.)
  4. Restart the VM.
  5. Maximize the VM window after start of the VM as soon as possible.
  6. If necessary, try again one of above workarounds.

VirtualBox Guest Additions Bugs Reporting

Occasionally screen resolution problems might still persist, see: VirtualBox Guest Additions Bugs Reporting.

Black Screen[edit]

If a black screen appears, try the following possible solutions.

  1. Install the recommended version of the VirtualBox host software.
  2. Apply the General VirtualBox Troubleshooting Steps.
  3. Reboot.
  4. If the issue persists, try the following workarounds.

If this solution or any of the workarounds worked for you, please report this in Whonix ™ forums [archive].


Workaround 1: Try Other VirtualBox Virtual Graphics Controller Settings

  1. Power off the VM.
  2. VirtualBoxclick a VMSettingsDisplayGraphics ControllerVMSVGAOK (Or try other settings there.) [9]
  3. VirtualBoxclick a VMSettingsDisplayGraphics Controllerincrease slider for Video Memory to 128OK (This is already the case in newer Whonix ™ versions.)
  4. Restart the VM.

Workaround 2: Boot Once Without Virtual Graphics Adapter This Workaround has been reported functional on a Windows 10 host with both Intel and nVidia GPU capabilities. It is OK to try this workaround on any host operating system.

  1. Power off the VM.
  2. VirtualBoxclick a VMSettingsDisplayGraphics ControllerNoneOK
  3. Start the VM. Wait 2-3 minutes. (Since you've disabled the display, you will see nothing happening)
  4. 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.
  5. Send Shutdown signal. If it doesn't shut down immediately, wait a short time and try again.
  6. Once the VM shuts down, restore the Graphics Controller to VMSVGA.
  7. Restart the VM.

If this workaround works, 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 boot with the nomodeset kernel parameter. If that works, please post a forum report and then make the change permanent. [10]


Workaround 4: Virtual Console

If it is possible to switch to a virtual console, this can help with debugging.

Slow Video Playback[edit]

Options:

What's better or worse for security, enable VirtualBox hardware-accelerated graphics (3D Acceleration) or disabling CPU mitigations? Please consider resolving that question through Free Support Principle and let us know what you found out. Please use a dedicated forum thread for that.

Miscellaneous[edit]

Host Crash[edit]

Same as below Aborted Status.

Aborted Status[edit]

If the virtual machine ever shows an aborted status, perform these steps:

  1. Try to Assign Less Virtual CPUs; this may help to avoid the issue.
  2. Apply General VirtualBox Troubleshooting Steps.
  3. Consider reporting a bug against upstream VirtualBox [archive] -- VirtualBox bugtracker [archive] / VirtualBox forums [archive]. Log is required by VirtualBox developers to be able to isolate the problem. [11]

Whonix ™ provides VM images 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:

  1. To capture the VirtualBox log: VirtualBoxright click a VMShow Log...LogSaveOK
  2. Zip the log.
  3. Report to VirtualBox support.
  4. Share link to VirtualBox support request in Whonix ™ forums.

Guru Mediation[edit]

Whonix ™ provides VM images 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. [12]

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 [archive] 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.

The above text does not contain any technical details which would help to advise how to fix the issue since VirtualBox Guru Meditation can happen for a wide variety of reasons.

Without the contents of the log, probably nobody will be able to help.

  1. Apply General VirtualBox Troubleshooting Steps.
  2. Consider looking through the log for yourself. Use search engines to search for any error messages if you can identify any. Likely the issue has already been discussed by others and likely there is already a solution for the issue described in the same place. Specifically useful it might be to search the offical VirtualBox website since that is presumed the place where most VirtualBox developers and experts are. Try the following search term to 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 text you actually want to investigate.
  3. Consider reporting a bug against upstream VirtualBox [archive] -- VirtualBox bugtracker [archive] / VirtualBox forums [archive]. Log is required by VirtualBox developers to be able to isolate the problem. [11]

Recommended steps:

  1. To capture the VirtualBox log: VirtualBoxright click a VMShow Log...LogSaveOK
  2. Zip the log.
  3. Report to VirtualBox support.
  4. Share link to VirtualBox support request in Whonix ™ forums.

NS_ERROR_FAILURE[edit]

NS_ERROR_FAILURE (0x80004005)

Quote VirtualBox forum moderator [archive]

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.

Kernel driver not installed[edit]

error happening in case Linux kernel headers package (linux-headers-amd64) is missing
output of sudo vboxconfig in case Linux kernel headers package (linux-headers-amd64) is missing

Kernel driver not installed (rc=-1908)

If this is happening on Linux based host operating systems, this is probably because the Linux headers package matching the currently running Linux image package is not installed.

Quote Recommended VirtualBox Version:

Instructions for installing VirtualBox on Debian.png Debian Tux.png Linux can be found for example on the Whonix old logo.png Whonix ™ for VirtualBox with XFCE page, which contains the following text.

* Linux Tux.png: please press expand on the right side.

Once expanded, the recommended instructions will explain how to install VirtualBox.

Instructions on how to install VirtualBox on Debian include, quote:

4. Install VirtualBox and Linux kernel headers.

sudo apt-get install virtualbox-6.1 linux-headers-$(dpkg --print-architecture)

This issue is unspecific to Whonix ™. Not only Whonix ™ VMs will be unable to start. All VMs from any vendor and/or self-created VMs will fail to start. It is a host operating system and VirtualBox issue. If above instructions did not fix the issue, the user can also access to further support resources, see also chapter #Try a non-Whonix VM.

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[edit]

Try assigning less virtual CPUs. [13]

In Whonix ™ 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.

  1. Power off the VM.
  2. VirtualBoxclick a VMSettingsSystemProcessorReduce to 3OK

INCONSISTENCY BETWEEN GRAIN TABLE AND BACKUP GRAIN TABLE[edit]

If this error appears, sometimes it helps to:

  1. Try and convert the vmdk to vdi.
  2. Remove the old vmdk from the VM.
  3. Attach the new vdi.

High Disk Usage Causing Filesystem Corruption[edit]

This is a VirtualBox host software bug, High I/O causing filesystem corruption [archive].

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 happened.

Enabling Host I/O Cache might help as it was reported by a user on the VirtualBox issue tracker [archive].

VirtualBoxSettingsStorageName: SATAType: AHCI → enable Use Host I/O CacheOK

Experimenting with other virtual machine hardware settings might help too.

VirtualBoxSettingsStorageName: → experiment with other settings → OK

Maybe Type: virtio-scsi could help.

Other things that might help:

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:

Import Whonix ™ Images[edit]

Using the VirtualBox GUI to import Whonix ™ images should work well in most cases. If not, follow the steps below.

1. Check if there is enough free disk space.

2. Refer to the Whonix ™ installation screenshots (VirtualBox/XFCE and click expand button) and/or Video Tutorials.

3. Delete any half-imported or otherwise broken virtual machine images.

4. Use the VBoxManage command line tool and copy the output.

VBoxManage unregistervm "Whonix-Gateway-XFCE" --delete

VBoxManage unregistervm "Whonix-Workstation-XFCE" --delete

5. Navigate to the folder where Whonix ™ was downloaded and import Whonix-Gateway ™ and Whonix-Workstation ™ by using the VBoxManage command line tool.

VBoxManage import Whonix-Gateway-XFCE-15.0.1.9.3.ova

6. Clean (anonymize) the output.

Remove operating system user name or any problematic paths.

7. Contact lead Whonix ™ developer Patrick Schleizer and send the output.

Try a non-Whonix VM[edit]

  1. "Forget" about Whonix ™ for a moment and imagine you had never heard of the platform. Test the VirtualBox host software first.
  2. Try a VM other than Whonix ™ such as for example Debian buster.
  3. If that does not fix the issue, that means the root issue is not caused by Whonix ™. I.e. unspecific to Whonix ™. Therefore it is recommended to attempt to resolve the issue as per Free Support Principle.

VirtualBox Generic Bug Reproduction[edit]

Based on Bug Report Recommendations, specifically Generic Bug Reproduction. Similar to above chapter Try a non-Whonix VM.

A manual reproduction of the Whonix ™ VirtualBox Integration.

  1. Use the recommended Linux distribution Debian Linux [archive] version buster as host operating system. (Debian Tips)
  2. Install VirtualBox host software from the upstream virtualbox.org Debian repository [archive] chapter Debian-based Linux distributions. Or see the simplified instructions Install VirtualBox from Oracle Repository by Whonix ™.
  3. No installation of non-freedom software required but the Debian nonfree repository needs to be at least temporarily enabled. Reason for that is documented below.
  4. virtualbox-guest-additions-iso [archive] (Freedom Software) from the Debian repository on the the Debian host operating system. Due to a Debian packaging bug the package is only available from Debian nonfree repository. But the package is not non-freedom. That package provides file /usr/share/virtualbox/VBoxGuestAdditions.iso.
  5. Install Debian buster inside a VirtualBox VM.
  6. Mount the VirtualBox Guest Additions CD iso file /usr/share/virtualbox/VBoxGuestAdditions.iso inside the Debian VM.
  7. Install VirtualBox Guest Additions from the virtual CD-ROM drive inside the Debian VM. Change to the directory where your CD-ROM drive is mounted and run the following command as root: sh ./VBoxLinuxAdditions.run
  8. Attempt to reproduce the original issue.

Submit a Bug Report[edit]

When reporting an issue in the Whonix ™ forums [archive], please add the exact steps which led to the problem. Also include as much relevant information as possible; see below.

  • Does the problem resolve itself if Whonix-Gateway ™ is launched without starting Whonix-Workstation ™?
  • Which Whonix ™ version was downloaded and from where?
  • Do both Whonix-Gateway ™ and Whonix-Workstation ™ have this issue?
  • Did you:
    • Only download, import Whonix ™ VMs and start Whonix ™?; or
    • Did you start Whonix ™, use Whonix ™, install more software and perform other activities before the issues emerged?
  • Have you previously used older versions of Whonix ™ 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:

Bugs can also be reported against upstream VirtualBox [archive]: VirtualBox bugtracker [archive] / VirtualBox forums [archive]. Bug reports must be well written and thorough otherwise it will not lead to a solution, see: bug reporting instructions [archive].

See Also[edit]

Footnotes[edit]

  1. Installation of VirtualBox guest additions from CD might also cause issues. [archive]
  2. Host freezing reported with newer kernel version: https://forums.whonix.org/t/recommended-specs/9679/14 [archive]
  3. Optional: See: https://www.virtualbox.org/manual/ch02.html#install-linux-vboxusers [archive] Also spams ~/.config/VirtualBox/VBoxSVC.log log if not done.
  4. A user reported issues which were gone once switching to Linux [archive].
  5. Virtualizers are incompatible with co-installation of other virtualizers at the same time. This is virtualizer specific, not a Whonix ™ 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 [archive]
  6. For reasons, see Storage Controller Setting.
  7. VirtualBox VMSVGA graphics controller is based on the VMware graphics controller.
  8. VBoxManage modifyvm Whonix-Gateway-XFCE --graphicscontroller vmsvga

    VBoxManage modifyvm Whonix-Gateway-XFCE --graphicscontroller vboxvga

    VBoxManage modifyvm Whonix-Gateway-XFCE --graphicscontroller vboxsvga

  9. http://forums.whonix.org/t/whonix-cli-15-0-0-9-4-gateway-shows-a-black-screen/9174/2 [archive]
  10. 11.0 11.1 Reasons of vm to get into "aborted" state [archive]:

    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.

  11. http://www.fixedbyvonnie.com/wp-content/uploads/2014/09/fixedbyvonnie-virtualbox-guru-meditation.png [archive]
  12. VirtualBox ticket: VirtualBox should now prohibit assigning all physical CPUs to a VM and/or fix VirtualBox CPU assignment manual [archive].


Fosshost is sponsors Kicksecure stage server Whonix old logo.png
Fosshost About Advertisements

Search engines: YaCy | Qwant | ecosia | MetaGer | peekier | Whonix ™ Wiki


Follow: 1024px-Telegram 2019 Logo.svg.png Iconfinder Apple Mail 2697658.png Twitter.png Facebook.png Rss.png Reddit.jpg 200px-Mastodon Logotype (Simple).svg.png

Support: 1024px-Telegram 2019 Logo.svg.png Discourse logo.png Matrix logo.svg.png

Donate: Donate Bank Wire Paypal Bitcoin accepted here Monero accepted here Contriute

Whonix donate bitcoin.png Monero donate Whonix.png United Federation of Planets 1000px.png

Twitter-share-button.png Facebook-share-button.png Telegram-share.png Iconfinder Apple Mail 2697658.png Reddit.jpg Hacker.news.jpg 200px-Mastodon Logotype (Simple).svg.png

Please help us to improve the Whonix ™ Wikipedia Page. Also see the feedback thread.

https link onion link Priority Support | Investors | Professional Support

Whonix | © ENCRYPTED SUPPORT LP | Heckert gnu.big.png Freedom Software / Osi standard logo 0.png Open Source (Why?)

The personal opinions of moderators or contributors to the Whonix ™ project do not represent the project as a whole.

By using our website, you acknowledge that you have read, understood and agreed to our Privacy Policy, Cookie Policy, Terms of Service, and E-Sign Consent.