Failed to start

Discussions related to using VirtualBox on Linux hosts.
Post Reply
yamen
Posts: 1
Joined: 27. Apr 2021, 16:45

Failed to start

Post by yamen »

Hello

Host Machine: ubuntu 20.04
VBbox Version: Latest

I took a copy of my windows machine using disk2vhd and attached the VHD to a virtual box machine, and it wokred.

today i formated my machine and trying to do the same with the same VHD file, but it is failing to start.

i have attached the log file from VBox

please advise
Thanks
Yamen
Attachments
VBoxLog.zip
(57.71 KiB) Downloaded 9 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: Failed to start

Post by scottgus1 »

yamen wrote:VBbox Version: Latest
In a short time, future readers of this post will be mislead by "latest". And unfortunately, it's not true now:
the posted log wrote:00:00:00.844139 VirtualBox VM 6.1.16_Ubuntu r140961 linux.amd64 (Dec 17 2020 22:06:23) release log
The latest official release as of my post today is 6.1.20. And you're running the Ubuntu fork, which we don't support here.

You can try updating to official Virtualbox: https://www.virtualbox.org/wiki/Linux_Downloads, don't forget the prerequisites https://www.virtualbox.org/manual/ch02. ... nux-prereq

Your VM crashes before it tries to use the VM's disk:
00:00:01.087261 AIOMgr: Endpoints without assigned bandwidth groups:
00:00:01.087269 AIOMgr: /media/yamen/Data&Backup/VirtualDisks/Windows 10_1.vhd
00:00:01.087273 AIOMgr: /media/yamen/Data&Backup/VirtualDisks/YAMEN-PC.vhd
00:00:01.087352 Changing the VM state from 'POWERING_ON' to 'RUNNING'
00:00:01.087357 Console: Machine state changed to 'Running'
00:00:01.089704 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:01.089718 Console: Machine state changed to 'GuruMeditation'
00:00:01.091254 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:01.091255 !!
00:00:01.091255 !! VCPU0: Guru Meditation -79 (VERR_INVALID_STATE)
"Invalid State" so soon probably means something is wrong with the configuration of the VM, but I can't see what. Except that you have all four physical host cores available for the VM. Reduce to 2 for now.

After fixing the above items, try the VM again. If it still does not work, please zip and post a new vbox.log. Also please zip and post a vbox.log from the VM on the working host, let's compare that one.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Failed to start

Post by fth0 »

Please disable QEMU/KVM on your host before starting a VirtualBox VM.
Post Reply