[Info-vax] X8691AOE boots OK - X8692OE fails as follows
Mark Daniel
mark.daniel at wasd.vsm.com.au
Fri Apr 15 19:46:16 EDT 2022
On 16/4/22 6:13 am, hb wrote:
> In your "original config (ISO at port 2)", before you boot, check the
> version of the boot manager.
>
> It is shown at the top of the screen. It can be displayed with the
> SYSINFO command.
>
> It needs to be a version V9.2 boot manager.
X86E92OE ISO on port 2; quoted to prevent wrapping:
+++++++++++++++++++++++++++++++++++++++++++++++
> BOOTMGR> DEVICES
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>>>> Press any key to continue:
>
> DKA0 (HD) = FS0 UEFI: V9_1_A OpenVMS: X86SYS 0 MB SATA Disk
------------------------------^^^^^^^^^^^^
> DKA200 (DVD) = FS2 UEFI: E9_2 OpenVMS: None 1263MB SATA DVD
>
> BOOTMGR> SYSINFO
>
> OpenVMS Boot Manager: V9.1-x Build 101 - Jul 13 2021
------------------------^^^^^^^^^^^^^^^^
>>>> Enter 'Y' to display decoded CPU ID information:
> PROCESSORS: Actual: 1, Max: 64, SMP? Yes, Hyperthreads? No
> Type: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
>
> PERFORMING HARDWARE COMPATIBILITY TEST.
>
> Checking Required Processor Features:
> PASSED
>
> Checking Optional Features:
> - No x2APIC (Extended Advanced Programmable Interrupt Controller)
> - No XSAVEOPT instruction
> - No TSX-HLE instruction
> - No TSX-RTM instruction
> - No UMIP instruction
> FAILED
>
> **********************************************************************
> This machine lacks some features used by OpenVMS, BUT CAN CONTINUE.
> **********************************************************************
>
> **********************************************************************
> This machine satisfies the requirements for running OpenVMS
> **********************************************************************
>
>>>> Enter 'E' to Exit or any other key to decode the CPU ID fields:
>
>>>> Enter 'Y' to display APIC information:
>
>>>> Enter 'Y' to list ACPI Tables:
>
>>>> Enter 'Y' to display SMBIOS Tables:
>
>
> BOOTMGR> BOOT DKA200
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %VMS_BOOTMGR-F-MEMDISK, Invalid MemoryDisk image. ID:2.0, Sig:0x24534D56, Exp:0x24534D56
>
> %VMS_BOOTMGR-F-MEMDISK, Unable to load DMM0.
>
> %VMS_BOOTMGR-E-MEMDISK, Unable to load memory disk.
>
> %VMS_BOOTMGR-F-MEMDISK, Unable to load selected boot image.
>
> %VMS_BOOTMGR-F-MAIN, Unable to load MemoryDisk from boot device.
--------------------------------------------------------
X86E92OE ISO on port 0; quoted to prevent wrapping:
+++++++++++++++++++++++++++++++++++++++++++++++
> BOOTMGR> DEVICES
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA100 (HD) = FS2 UEFI: V9_1_A OpenVMS: X86SYS 16384 MB SATA Disk
> DKA0 (DVD) = FS1 UEFI: E9_2 OpenVMS: None 1263 MB SATA DVD
------------------------------^^^^^^^^^^
> BOOTMGR> SYSINFO
>
> OpenVMS Boot Manager: V9.2 Build 112 (Feb 4 2022)
------------------------^^^^^^^^^^^^^^
>>>> Enter 'Y' to display decoded CPU ID information:
> PROCESSORS: Max Supported: 64, SMP? Yes, Hyperthreads? No
> Type: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
>
> PERFORMING HARDWARE COMPATIBILITY TEST.
>
> Checking Required Processor Features:
> PASSED
>
> Checking Optional Features:
> - No x2APIC (Extended Advanced Programmable Interrupt Controller)
> - No XSAVEOPT instruction
> - No TSX-HLE instruction
> - No TSX-RTM instruction
> - No UMIP instruction
> FAILED
>
> **********************************************************************
> This machine lacks some features used by OpenVMS, BUT CAN CONTINUE.
> **********************************************************************
>
> **********************************************************************
> This machine satisfies the requirements for running OpenVMS
> **********************************************************************
>
>>>> Enter 'Q' to Quit or any other key to decode the CPU ID fields:
>
>>>> Enter 'Y' to display APIC information:
>
>>>> Enter 'Y' to list ACPI Tables:
>
>>>> Enter 'Y' to display SMBIOS Tables:
>
>
> BOOTMGR> BOOT DKA0
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%
>
>
> _______________________________________________
>
> GRAPHICAL OUTPUT HAS BEEN SUSPENDED
> USE A TERMINAL UTILITY FOR ACCESS
> _______________________________________________
>
> VSI Primary Kernel SYSBOOT Mar 8 2022 14:47:10
>
> %SYSBOOT-I-VMTYPE, Booting as a VirtualBox (tm) Guest
>
>
> VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, E9.2
> Copyright 2022 VMS Software, Inc.
>
> MDS Mitigation active, variant verw(MD_CLEAR)
>
> %SMP-I-CPUTRN, CPU #2 has joined the active set.
> %SMP-I-CPUTRN, CPU #1 has joined the active set.
>
>
>
> Installing required known files...
>
> Configuring devices...
>
> %EIA0, Link up: 1000 mbit, fdx, flow control (rcv only), 08-00-27-1C-76-CA
>
>
> ****************************************************************
>
> You can install or upgrade the OpenVMS X86-64 operating system
> or you can install or upgrade layered products that are included
> on the OpenVMS X86-64 distribution media.
>
> You can also execute DCL commands and procedures to perform
> "standalone" tasks, such as backing up the system disk.
>
> Please choose one of the following:
>
> 1) Upgrade, install or reconfigure OpenVMS X86-64 Version E9.2
> 2) Display layered products that this procedure can install
> 3) Install or upgrade layered products
> 4) Show installed products
> 5) Reconfigure installed products
> 6) Remove installed products
> 7) Find, Install or Undo patches; Show or Delete Recovery Data
> 8) Execute DCL commands and procedures
> 9) Shut down this system
>
> Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 9
>
> Shutting down the system
>
>
>
> VSI Dump Kernel SYSBOOT Mar 8 2022 14:47:10
>
> ** Error logs not dumped, system disk is write locked
> SYSTEM SHUTDOWN COMPLETE
>
> **** Hit any key to reboot system ****
--------------------------------------------------------
So the upshot appears to be the VMS_BOOTMGR is taken from the first
bootable device (FS0...FSn), meaning you need to have the latest version
first in the device list.
> Also, before you boot, check the BOOT MANAGER DEVICE output. It should
> show the E9.2 DVD. That's where the device where the V9.2 boot manager
> lives.
>
> By the way, your DKA0 (in the original config) looks small.
I cloned the entire VM so that represents the system disk of 9.1-A. I
was planning to clobber it (the clone device) with 9.2 install. Which I
can now proceed with :-)
> On 4/15/22 22:05, Mark Daniel wrote:
>> On 16/4/22 5:19 am, Robert A. Brooks wrote:
>>> On 4/15/2022 3:44 PM, Mark Daniel wrote:
>>>
>>>> So there appears to be a change in behaviour between the 9.1-A and
>>>> 9.2 ISOs, requiring 9.2 to be at dka0 (or some such).
>>>
>>> I'm not aware of that restriction; file a case with us.
>>>
>>
>> Sure Rob. Exactly how is that gone about again? :-) I'm an ISV.
--
Anyone, who using social-media, forms an opinion regarding anything
other than the relative cuteness of this or that puppy-dog, needs
seriously to examine their critical thinking.
More information about the Info-vax
mailing list