MacOS Ventura and VirtualBox
Posted: Wed Apr 19, 2023 6:51 pm
Oracle doesn't support MacOS Ventura Version 13.3 (22E252) with VirtualBox 6.1.43-156565 or 7.0.7-156678, so I'm a little stuck for the moment.
With VirtualBox 7.0.7-156678, I do get the installation to run as documented, viewtopic.php?f=1&t=8623 is very helpful, but when I try to boot from the result, I get Invalid MemoryDisk, see below.
Notice that the device boot output does not list the volume labels, so I'm guessing there is something about how the disk volumes are read that is unexpected.
BdsDxe: loading Boot0001 "UEFI VBOX CD-ROM VB1-1a2b3c4d " from PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)
BdsDxe: starting Boot0001 "UEFI VBOX CD-ROM VB1-1a2b3c4d " from PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)
Scanning system devices and preparing the OpenVMS Boot Manager...
VSI OpenVMS Boot Manager: V9.2-1, Build 122
ENABLED: Symmetric Multi-Processing
ENABLED: Crash Dump Processing
ENABLED: Console output to Legacy COM 1 Port
Checking Required Processor Features:
PASSED
BOOT MANAGER DEVICE: DKA100
DEFAULT BOOT COMMAND: BOOT 0 00000000
VIRTUAL MACHINE GUEST:
VirtualBox (tm) No Mouse support; Use Commands or Arrow Keys
CONNECT A REMOTE TERMINAL SESSION NOW.
Enter the TERMINAL command for remote connection assistance.
BOOTMGR> device boot
DEVICE BOOT
BOOTABLE DEVICES (System Disks, Installation Kits, other):
DKA0 (HD) = FS0 UEFI: E9_2_1 VMS: 12288 MB SATA Disk
DKA100 (DVD) = FS1 UEFI: E9_2_1 VMS: None 1574 MB SATA DVD
BOOTMGR> boot dka0: 0 00000000
BOOT DKA0: 0 00000000
Booting...
%VMS_BOOTMGR-E-MEMDISK, Invalid MemoryDisk version: 0.0
%VMS_BOOTMGR-E-MEMDISK, Unable to load DMM0.
%VMS_BOOTMGR-E-MEMDISK, Unable to load selected boot image.
%VMS_BOOTMGR-F-MAIN, Unable to load MemoryDisk from boot device.
With VirtualBox 7.0.7-156678, I do get the installation to run as documented, viewtopic.php?f=1&t=8623 is very helpful, but when I try to boot from the result, I get Invalid MemoryDisk, see below.
Notice that the device boot output does not list the volume labels, so I'm guessing there is something about how the disk volumes are read that is unexpected.
BdsDxe: loading Boot0001 "UEFI VBOX CD-ROM VB1-1a2b3c4d " from PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)
BdsDxe: starting Boot0001 "UEFI VBOX CD-ROM VB1-1a2b3c4d " from PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)
Scanning system devices and preparing the OpenVMS Boot Manager...
VSI OpenVMS Boot Manager: V9.2-1, Build 122
ENABLED: Symmetric Multi-Processing
ENABLED: Crash Dump Processing
ENABLED: Console output to Legacy COM 1 Port
Checking Required Processor Features:
PASSED
BOOT MANAGER DEVICE: DKA100
DEFAULT BOOT COMMAND: BOOT 0 00000000
VIRTUAL MACHINE GUEST:
VirtualBox (tm) No Mouse support; Use Commands or Arrow Keys
CONNECT A REMOTE TERMINAL SESSION NOW.
Enter the TERMINAL command for remote connection assistance.
BOOTMGR> device boot
DEVICE BOOT
BOOTABLE DEVICES (System Disks, Installation Kits, other):
DKA0 (HD) = FS0 UEFI: E9_2_1 VMS: 12288 MB SATA Disk
DKA100 (DVD) = FS1 UEFI: E9_2_1 VMS: None 1574 MB SATA DVD
BOOTMGR> boot dka0: 0 00000000
BOOT DKA0: 0 00000000
Booting...
%VMS_BOOTMGR-E-MEMDISK, Invalid MemoryDisk version: 0.0
%VMS_BOOTMGR-E-MEMDISK, Unable to load DMM0.
%VMS_BOOTMGR-E-MEMDISK, Unable to load selected boot image.
%VMS_BOOTMGR-F-MAIN, Unable to load MemoryDisk from boot device.