VirtualBox/Troubleshooting

From Kicksecure
< VirtualBox
Revision as of 18:37, 14 February 2016 by imported>Patrick (Created page with "= Troubleshooting = <translate> == Whonix does not start? == <!--T:10--></translate> <translate> === PAE crash === <!--T:11--></translate> <translate><!--T:12--> Try this:<b...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Troubleshooting

<translate>

Whonix does not start?

</translate>

<translate>

PAE crash

</translate>

<translate> Try this:
Virtual Box -> Right Click on Whonix-Gateway -> Settings -> System -> Processor -> Uncheck the Enable PAE/NX Box -> OK.</translate>

<translate> Repeat that for Whonix-Workstation as well.</translate>

<translate> Read the [[<tvar|3>#Boot Options|</> Boot Options]] chapter and use the 486 kernel.</translate>

VERR_VMX_MSR_VMXON_DISABLED

Try this:
Virtual Box -> Right Click on Whonix-Gateway -> Settings -> System -> Acceleration -> Uncheck the "Enable VT-x/AMD-V" Box -> OK.

<translate> Repeat that for Whonix-Workstation as well.</translate>

<translate> Read the [[<tvar|4>#Boot Options|</> Boot Options]] chapter and use the 486 kernel.</translate>

If it still doesn't work, also try:
Virtual Box -> Right Click on Whonix-Gateway -> Settings -> System -> Acceleration -> Uncheck the "Enable Nested Paging" Box -> OK.

VERR_SSM_FIELD_NOT_CONSECUTIVE

<translate> If you see "Failed to load unit 'PATM' (VERR_SSM_FIELD_NOT_CONSECUTIVE).", please enable VT-x in BIOS.</translate>

Kernel Panic

<translate> This probably similar to PAE crash and VERR_SSM_FIELD_NOT_CONSECUTIVE issues above. If you can, enable VT-x in BIOS. If you cannot, then disable PAE/NX in VirtualBox (see PAE crash above for instructions on how to do so) and then read the [[<tvar|5>#Boot Options|</> Boot Options]] chapter and use the 486 kernel.</translate>

<translate>

VT-x is disabled in the BIOS.

</translate> <translate> If you see this error message.</translate> 

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

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

<translate> Then please enable VT-x in BIOS.</translate>

Error In supR3HardenedWinReSpawn


Don't update whilst the VMs are running and if you do, you need to reinstall VirtualBox.

<translate>

Other reasons

</translate> <translate> Please have a look at the VirtualBox page. It contains instructions on how to properly download and verify the Whonix virtual machine images. There is also help available in form of screenshot or video instructions.

If you still need help, please go to the [<tvar|6>https://forums.whonix.orgarchive.org iconarchive.today icon</> Whonix User Help Forum].</translate>

<translate>

Boot Options

</translate>

<translate> In the grub boot menu you can choose for two seconds. Two kernels are installed by default.

  • The default 686-pae kernel.
  • A 486 kernel for compatibility.

If Whonix works out of the box, you do not need to change anything and you can stick to the default 686-pae kernel.

In case you need to [[<tvar|7>#PAE_crash|</> disable PAE]], use the 486 kernel.</translate>

Virtual Box Disk Images

INCONSISTENCY BETWEEN GRAIN TABLE AND BACKUP GRAIN TABLE

Maybe this will help: Try convert the vmdk to vdi, remove the old vmdk from the VM and attach the new vdi.

Footnotes


Your support makes
all the difference!

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 12 year success story and maybe DONATE!

Retrieved from "https://www.kicksecure.com/w/index.php?title=VirtualBox/Troubleshooting&oldid=33385"