Page 1 of 1
VBox Windows 11
Posted: 12. Apr 2022, 00:23
by Ricardo Rocha
Goodnight! I have an AMD Ryzen 3200g and I am not able to use VirtualBox. When the machine is going to boot the ISO it displays an error message and asks to consult the log. I don't know how to consult this log. Can someone help me?
Re: VBox Windows 11
Posted: 12. Apr 2022, 02:37
by scottgus1
Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.
Re: VBox Windows 11
Posted: 12. Apr 2022, 23:03
by Ricardo Rocha
Thank you scottgus1.
Follow the log as requested.
Re: VBox Windows 11
Posted: 13. Apr 2022, 00:54
by scottgus1
Windows 11 host & VM, 6.1.32 Virtualbox, Hyper-V is off. VM guru meditated triple-fault:
00:00:06.124636 EFI: VBoxDbg> loadimage64 'cdboot.efi' 0x10000000 LB 0x119000
00:00:11.682060 IEM: wrmsr(0xc0000080,0x0`00000d00) -> #GP(0)
00:00:11.682070 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:11.682111 Console: Machine state changed to 'GuruMeditation'
00:00:11.682329 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:11.682330 !!
00:00:11.682330 !! VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
00:00:11.682502 !!
00:00:11.682506 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT
I don't know why this happened. We'll have to wait for a forum guru to look in on this.
Meanwhile, do you have other working VMs? If you have only this one, please try to get an Ubuntu ISO, make a new Ubuntu VM and see if it boots.
Re: VBox Windows 11
Posted: 13. Apr 2022, 15:21
by fth0
@Ricardo Rocha:
Please see
NX/XD.
scottgus1 wrote:I don't know why this happened. We'll have to wait for a forum guru to look in on this.
You were close (quoting the "IEM: wrmsr..." log message), but your "NX detection in log files" doesn't seem to work.
Seriously, I'd suggest to detect the following log message, which is identical on Intel CPUs and AMD CPUs:
Windows 11-2022-04-12-18-01-13.log wrote:00:00:04.816546 CPUM: WARNING! Can't turn on NX/XD when the host doesn't support it!
Re: VBox Windows 11
Posted: 13. Apr 2022, 17:14
by scottgus1
Ha ha! You're right, I missed that! I did have this line set:
00:00:04.816974 NX - No-Execute/Execute-Disable = 0 (0)
but it didn't stand out in the report, and yours is even more explicit. Thanks!
Re: VBox Windows 11
Posted: 13. Apr 2022, 20:58
by fth0
You're welcome. But ... this line from the CPUID dump also exists in the provided log file (even twice, as always).
Whitespace problems perhaps? You'll have to cope with variable amounts of whitespace before the "=", because the CPUID feature list gets enlarged from time to time, and if a new description text is longer than all the previous ones ... take
AVX512ER for example, or
XSaveErPtr.
Re: VBox Windows 11
Posted: 13. Apr 2022, 22:44
by scottgus1
The "No-Execute/Execute-Disable = 0 (0)" line was in my report, I just missed looking for it. I added the "WARNING!" to the ini, too. Should make the NX/XD status stand out more.
