Cannot launch VirtualBox VM

Virtual Box is not working anymore since a few weeks. I get stuck there when I launch a VM (even if I just created it):

And I get those error logs, not always.

00:01:35.203004 nspr-5   ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={300763af-5d6b-46e6-aa96-273eac15538a} aComponent={MachineWrap} aText={The machine is not mutable (state is Starting)}, preserve=false aResultDetail=0

00:05:49.937704 ERROR [COM]: aRC=NS_ERROR_UNEXPECTED (0x8000ffff) aIID={c0447716-ff5a-4795-b57a-ecd5fffa18a4} aComponent={SessionWrap} aText={The session is not locked (session state: Unlocked)}, preserve=false aResultDetail=0

I tried to change the VM folder, it doesn’t change anything. I tried to uninstall/reinstall. I tried the AUR version.

Any idea?

What is the terminal output of:
pacman -Q | grep ^linux && pacman -Q virtualbox

Are your VM’s stored on an NTFS partition or some NFS mount?

2 Likes

No output. And no, it’s an ext4 partition.
Thanks for your support.

There is nothing up with VirtualBox.

A readonly snapshot perhaps or insufficient permissions on the file structure where the image is stored.

This part could also point to the vhd file being damaged - in that case it may be a filesystem error or a physical disk error.

1 Like

Not sure I understand what you mean :slight_smile: I have this version installed:

pacman -Q | grep virtualbox
virtualbox-bin 7.0.8-1
virtualbox-ext-oracle 7.0.8-1

But maybe I should try another one?
I tried to remove/recreate several times a VM but it always fails when I launch it.

The versions you have installed is not from Manjaro repo.

sudo pacman -Rns virtualbox-bin virtualbox-ext-oracle

Use Manjaro documentation to install and configure VirtualBox

1 Like

Ok I removed it and resintalled following the wiki and the forum instructions you gave me. I tried to create a VM and to launch it:

00:00:27.847866 nspr-2 Launched VM: 604302624 pid: 24437 (0x5f75) frontend: GUI/Qt name: linux
00:00:27.864250 nspr-3 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={300763af-5d6b-46e6-aa96-273eac15538a} aComponent={MachineWrap} aText={The machine is not mutable (state is PoweredOff)}, preserve=false aResultDetail=0
00:00:28.221979 nspr-6 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={300763af-5d6b-46e6-aa96-273eac15538a} aComponent={MachineWrap} aText={The machine is not mutable (state is PoweredOff)}, preserve=false aResultDetail=0
00:00:28.651216 nspr-8 Load [/usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxHostWebcam.so] vrc=VINF_SUCCESS
00:00:28.860119 nspr-4 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={300763af-5d6b-46e6-aa96-273eac15538a} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:28.883698 nspr-4 NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for wlp0s20f3: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:28.907236 nspr-4 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={300763af-5d6b-46e6-aa96-273eac15538a} aComponent={MachineWrap} aText={The machine is not mutable (state is Starting)}, preserve=false aResultDetail=0
00:00:29.152114 nspr-6 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={300763af-5d6b-46e6-aa96-273eac15538a} aComponent={SessionMachine} aText={The machine is not mutable or saved (state is Starting)}, preserve=false aResultDetail=0
00:00:29.155525 nspr-6 Saving settings file “/home/aaa/VirtualBox VMs/linux/linux.vbox” with version “1.19-linux”
00:00:29.166381 nspr-6 Finished saving settings file “/home/aaa/VirtualBox VMs/linux/linux.vbox”

==> selectorwindow.log <==
00:00:29.501258 GUI: UIMediumEnumerator: Medium-enumeration finished!

==> VBoxSVC.log <==
00:00:29.174185 nspr-3 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={300763af-5d6b-46e6-aa96-273eac15538a} aComponent={MachineWrap} aText={The machine is not mutable (state is Starting)}, preserve=false aResultDetail=0

VirtualBox is not a fault here - I don’t know what it is you are doing.

VirtualBox works flawless OOB on Manjaro - I use VBox VMs each and every day as part of my paid work as freelance contractor.

I therefore has firsthand knowledge that VirtualBox is not at fault - and I can tell from experience - this is a local issue - which is very hard for anyone to help you with myself included.

I have no idea and all I can offer at this point is speculation and questions. The answers may guide you in the right direction - and I have no idea where it is taking you.

What is the output of below commands

uname -a
lsb_release -a
vboxmanage --version

I am guessing the extension pack or remnants from a manual non-package-manager tracked installation is at fault here.

A normal installation does - at least in my experience - not try to load webcam libraries so something appears complete off.

  • Is the vm from some kind of backup you have made at some point?
  • e.g. a copied vm folder with all files?
  • Is the vm imported from an appliance you had created previously?
  • Is the vm imported from an appliance you downloaded from some website?

Remove the extension pack from your installaion and confirm if you can create a vm from scratch and boot it from a bootable ISO e.g. Manjaro ISO.

EDIT:

This could also point to a VM using EFI boot where the efi image located in the VM folder is from a previous version of VBox.

Such incidents has been seen mainly when upgrading VBox from v6 to v7 - but it only manifest if the VM is configured to use EFI boot.

1 Like

Thanks a lot for your time. I understand that it’s hard to provide support in such a case :confused:

From the beginning I have issues every time I create a new VM. I’m not importing or copying a VM. And I do it with a very basic configuration (Manjaro XFCE iso, default RAM, CPU, VM folder etc…).

uname -a
Linux xxxxxx 6.1.26-1-MANJARO #1 SMP PREEMPT_DYNAMIC Wed Apr 26 22:07:35 UTC 2023 x86_64 GNU/Linux

lsb_release -a
LSB Version: n/a
Distributor ID: ManjaroLinux
Description: Manjaro Linux
Release: 22.1.1
Codename: Talos

vboxmanage --version
7.0.8r156879

I completely removed VirtualBox and Extension Packs and tried again to create a VM but it failed to launch, without writing any log…

I installed Qemu which worked immediately and for now it covers my needs. I may come back to Virtual Box later if I really need it.

Thanks again for your help.

Eventually I tried to change my kernel from 6.1.26 to 6.3.0 and it worked immediately…

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.