{{tag>virtualbox troubleshooting networking}}

====== Virtualbox troubleshooting ======
===== Problem with assigning static ip to vm =====
Error:

<code>
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "ipconfig", "vboxnet0", "--ip", "10.0.0.1", "--netmask", "255.255.255.0"]

Stderr: VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp
</code>

From virtualbox version 6.1.28 you need to whitelist the IPs from which the virtualbox can assign addresses. Create a file ///etc/vbox/networks.conf// with content:
<code>
  * 10.0.0.0/8 192.168.0.0/16
</code>
Note the asterisk at the beginning.
This will allow the above IP ranges to be assigned to the vms.


==== Tested on ====
  * Ubuntu 20.04.4 LTS
  * virtualbox     6.1.32-dfsg-1~ubuntu1.20.04.1


===== Date and time wrong (frozen) in VM? =====
Restart the timedate service. In Debian 11 do

  systemctl restart chronyd

Seems to be caused by the [[https://www.virtualbox.org/ticket/14605|absence of VBoxService]].

==== Tested on ====
  * Debian 11
  * vagrant install

===== Virtualbox Guru meditation =====

<code>
00:00:00.872547 EFI: debug point SEC_PREMEM
00:00:00.921122 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:00.921158 Console: Machine state changed to 'GuruMeditation'
00:00:00.921814 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:00.921816 !!
00:00:00.921818 !!         VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)
00:00:00.921879 !!
00:00:00.921925 !! ACTIVE TRAP=0e ERRCD=2 CR2=0000000002600000 PC=00000000fffcdf92 Type=0 cbInstr=ff fIcebp=false (Guest!)
00:00:00.921930 !!
00:00:00.921930 !! CallRing3JmpBuf:
00:00:00.921930 !!
00:00:00.921931 SavedEsp=ffffab35ca6737f0 SavedEbp=ffffab35ca6737f8 SpResume=ffffab35ca6737c8 SpCheck=ffffab35ca673ae8
00:00:00.921933 pvSavedStack=ffffab35cbbef000 cbSavedStack=0x320  fInRing3Call=true 
00:00:00.921935 cbUsedMax=0x0 cbUsedAvg=0x0 cbUsedTotal=0x0 cUsedTotal=0x0
00:00:00.921936 pfn=ffffab35c8bd9a50 pvUser1=ffffab35ca68d000 pvUser2=ffffab35ca69e000
00:00:00.921938 rax=volatile         rbx=ffffab35ca69e000 rcx=volatile         rdx=volatile
00:00:00.921938 rsi=volatile         rdi=volatile          r8=volatile          r9=volatile        
00:00:00.921938 r10=volatile         r11=volatile         r12=0000000002600000 r13=0000000002600000
00:00:00.921939 r14=ffffab35ca75af70 r15=ffffab35ca69e000
00:00:00.921939 rip=ffffab35c8c018d1 rsp=ffffab35ca6737e8 rbp=ffffab35ca673818 rflags=00000246
00:00:00.924554 !!
00:00:00.924555 !! Call Stack:
</code> 

Solved by upgrading to Virtualbox 7.0
==== Tested on ====
  * Ubuntu 22.04.4 LTS
  * virtualbox     6.1.32-dfsg-1~ubuntu1.20.04.1


===== 'poweroff' state =====

<code>
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.
</code>

Happened when running the vagrant installed as a single binary. Resolved by [[https://developer.hashicorp.com/vagrant/downloads#linux|installing via repo]].

===== References =====
  * http://virtualbox.org/manual/ch06.html#network_hostonly
  * https://github.com/hashicorp/vagrant/issues/13318#issuecomment-2200731628