On 26/12/2022 14:35, Robin Klitscher wrote:
On 26/12/2022 13:06, Masaru Nomiya wrote:
Hello,
<snip>
Robin, please show us the selectorwindow.log (which is in ~/.VirtualBox) when the problem occurred.
BEGINS
00:00:00.375408 VirtualBox GUI VM Selector Window 7.0.4_SUSE r154605 linux.amd64 (no date no time) release log 00:00:00.375410 Log opened 2022-12-26T01:15:19.040872000Z 00:00:00.375410 Build Type: release 00:00:00.375412 OS Product: Linux 00:00:00.375413 OS Release: 5.14.21-150400.24.38-default 00:00:00.375413 OS Version: #1 SMP PREEMPT_DYNAMIC Fri Dec 9 09:29:22 UTC 2022 (e9c5676) 00:00:00.375429 DMI Product Name: Z490 VISION G 00:00:00.375432 DMI Product Version: -CF 00:00:00.375436 Firmware type: UEFI 00:00:00.375552 Secure Boot: Disabled 00:00:00.375575 Host RAM: 32028MB (31.2GB) total, 27106MB (26.4GB) available 00:00:00.375578 Executable: /usr/lib/virtualbox/VirtualBox6 00:00:00.375578 Process ID: 12355 00:00:00.375578 Package type: LINUX_64BITS_GENERIC (OSE) 00:00:00.375594 Qt version: 5.15.7 00:00:00.375902 GUI: UIMediumEnumerator: Initial medium-enumeration finished! 00:00:00.404356 GUI: UIMediumEnumerator: Medium-enumeration started...
ENDS
The Secure Boot line looks a bit odd. When the GUI manager was working Secure Boot was marked as enabled - which as I understand it must have been the case for Win 11 to install at all, let alone to work properly when called from the command line with VBoxManage startvm <name> (although, on inspection after starting one of the Win 11 VMs with VBoxManage I see the related VBoxSVC log also says Secure Boot is disabled, so maybe it doesn't matter).
Oops. I guess that Secure Boot line is referring to the physical machine setup in BIOS, not the VM environment????? -- Robin K Wellington "Harbour City" New Zealand