Opened 3 years ago
Last modified 3 years ago
#20785 new defect
VM will not start, Guru Meditation -79 (VERR_INVALID_STATE)
Reported by: | DeHouthakker | Owned by: | |
---|---|---|---|
Component: | VM control | Version: | VirtualBox 6.1.22 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Linux |
Description
Virtual machines will not start any more. Both Windows and Ubuntu guests seem to be having the same project. I am using VirtualBox 6.1.22_Ubuntu r144080 and I am running Ubuntu 20.04 Linux 5.13.0-27-lowlatency #29~20.04.1-Ubuntu SMP PREEMPT
Yesterday everything works fine and now machines wont start. When exporting and importing a machine to a different host, the machine does start so it seems the issue is related to the virtual box host.
In the logfile I see:
00:00:04.713444 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 00:00:04.713532 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=720x400, Sending to async-handler 00:00:04.713611 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=720x400 00:00:04.713634 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=720x400 00:00:04.713659 GUI: UIFrameBufferPrivate::performResize: Size=720x400, Directly using source bitmap content 00:00:10.049433 PIT: mode=3 count=0x4dae (19886) - 60.00 Hz (ch=0) 00:00:10.069842 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION' 00:00:10.069860 Console: Machine state changed to 'GuruMeditation' 00:00:10.070003 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 00:00:10.070003 !! 00:00:10.070004 !! VCPU0: Guru Meditation -1701 (VERR_MM_HYPER_NO_MEMORY) 00:00:10.070037 !! 00:00:10.070063 !! 00:00:10.070063 !! {mappings, <NULL>} 00:00:10.070064 !!
I will attach the logfile to this ticket.
Any help is highly appreciated
Attachments (2)
Change History (5)
by , 3 years ago
comment:1 by , 3 years ago
This is a known issue. Linux kernel 5.13 is supported in VirtualBox 6.1.24 and newer.
comment:2 by , 3 years ago
After some more investigation and a reinstallation of Virtual Box, the virtual machine worked again.
So, this issue can be closed.
Sorry for the confusion...
With regards, De Houthakker
comment:3 by , 3 years ago
@fth0, sorry, but I did not see you comment. You are right, reinstalling did the thing. Thanks for your comment.
log file