virtualbox.org

Hi Folks,

Im trying to create a guest Fedora VM install on win10 Host but get repeated failure to start.

log gives some errors

00:00:36.964209 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:00:36.969562 Console: Machine state changed to 'PoweredOff'
00:00:37.499488 GUI: Passing request to close Runtime UI from machine-logic to UI session.
00:00:37.781253 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:37.781371 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up (Display::setVideoModeHint)}, preserve=false aResultDetail=0
00:00:37.782288 GUI: Aborting startup due to invalid machine state detected: 1

and earlier in the log...
00:00:08.753629 ERROR [COM]: aRC=E_INVALIDARG (0x80070057) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Argument aWidth is invalid (must be aWidth != 0 && aWidth <= 32767)}, preserve=false aResultDetail=0

So thinking it must be something related to the VGA setting, but in truth i'm stuck,.

Any guidance would be most welcome.

Thanks
Paul

The error you highlighted may only be something trying to run while the VM environment has turned off. (I may be wrong.) The actual error happened earlier:

00:00:08.739505 Changing the VM state from 'POWERING_ON' to 'RUNNING'
00:00:08.739524 Console: Machine state changed to 'Running'
00:00:08.740187 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:08.740214 Console: Machine state changed to 'GuruMeditation'
00:00:08.740375 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:08.740376 !!
00:00:08.740377 !! VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)

VERR_VMM_SET_JMP_ABORTED_RESUME has been happening recently on Windows 7 hosts, but I haven't seen it on 10 yet. (This might change how I'm advising Windows 7 users, btw.)

Are you running 3rd-party non-Windows-Defender AV?

VBox.log file wrote:00:00:08.755915 CPU[0]: VM-exit history:
00:00:08.755915 Exit No.: TSC timestamp / delta RIP (Flat/*) Exit Name
00:00:08.755919 1: 0x00006898203f693a/+0 00000000000fe05b 0x01030 VMX_EXIT_EPT_VIOLATION - 48 - EPT violation.
00:00:08.755925 0: 0x00006898203d6adc/-130654 00000000fffffff0 0x01030 VMX_EXIT_EPT_VIOLATION - 48 - EPT violation.

FWIW, we're very early in the guest's life here: In the legacy BIOS, the second assembly instruction created the second page fault (as expected), and the Guru Meditation already occurred when handling it.

VBox.log file wrote:00:00:05.469754 Host RAM: 8043MB (7.8GB) total, 3932MB (3.8GB) available
00:00:05.688702 RamSize <integer> = 0x0000000080000000 (2 147 483 648, 2 048 MB)
[...]
00:00:36.907987 /PGM/LargePage/Refused 1 times

This log message indicates that the host OS already refuses to provide a 2 MB "large" page and forces VirtualBox to allocate smaller 4 kB pages, which is somewhat unusual that early. For a test, please open a command prompt, enter the following commands

Code: Select all

cd "C:\Program Files\Oracle\VirtualBox"
VBoxManage modifyvm "fedora test" --largepages off

and test if it makes a difference.

scottgus1 wrote:VERR_VMM_SET_JMP_ABORTED_RESUME has been happening recently on Windows 7 hosts, but I haven't seen it on 10 yet.

Additionally, the (admittedly weak) theory of older host CPUs playing a role is refuted. It has been weak anyway, since Windows 7 hosts will naturally have older CPUs.

Thanks for the suggestions, however took a break for coffee - removed all the install files -rebooted machine and it reinstalled without any issues.
For reference I have AVAST AV running.

Again thanks for being so responsive, a total noob to the linux and VM world, so its great to see such an active forum functioning.

A user of Avast pinned this down: Avast is using hardware virtualization, which prevents Virtualbox from using it. See viewtopic.php?f=1&t=105661#p515784

virtualbox.org

Failure to start new Fedora VM - GUI: Aborting startup due to invalid machine state detected: 1

Failure to start new Fedora VM - GUI: Aborting startup due to invalid machine state detected: 1

Re: Failure to start new Fedora VM - GUI: Aborting startup due to invalid machine state detected: 1

Re: Failure to start new Fedora VM - GUI: Aborting startup due to invalid machine state detected: 1

Re: Failure to start new Fedora VM - GUI: Aborting startup due to invalid machine state detected: 1

Re: Failure to start new Fedora VM - GUI: Aborting startup due to invalid machine state detected: 1