VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface ISessi

Discussions about using Linux guests in VirtualBox.
Post Reply
diegob
Posts: 1
Joined: 30. Aug 2021, 10:06

VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface ISessi

Post by diegob »

Hi to all,
I'm trying to start my centos7 machine but I receive that error:

C:\vm\m2centos7new>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "e8483731-53e4-454b-a08b-3c5cf97cfc65", "--type", "headless"]

Stderr: VBoxManage.exe: error: The VM session was closed before any attempt to power it on
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface ISession

I'm attaching vbox.log.
Can you help me?
Thanks,

Diego
Attachments
vbox.zip
(26.22 KiB) Downloaded 24 times
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface IS

Post by scottgus1 »

Just so you're aware, Vagrant isn't supported here, we only handle Virtualbox.

And FWIW the log does show a running VM, not one that could not start.

However, the log from the VM shoes two possible problems.

Regular RAM is overcommitted:
00:00:00.887794 Host RAM: 16279MB (15.8GB) total, 5647MB (5.5GB) available
00:00:01.875232 RamSize <integer> = 0x0000000200000000 (8 589 934 592, 8 192 MB, 8.0 GB)
00:00:01.875744 VRamSize <integer> = 0x0000000000c00000 (12 582 912, 12 MB)
Host Hyper-V is enabled:
00:00:01.875971 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
Fix the RAM commitment, then if the VM still won't start or runs poorly, disable Hyper-V, see HMR3Init: Attempting fall back to NEM (Hyper-V is active)

One last thing, it's a CentOS/RedHat VM, so this wouldn't be a Windows Guests question, moving to Linux Guests. The Guest is the VM. the Host is the PC.
Post Reply