[Info-vax] X8691AOE boots OK - X8692OE fails as follows

[Mark Daniel]

On 16/4/22 9:16 am, Mark Daniel wrote:
8< snip 8<
> 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.

*** NOT (strictly) TRUE - RTFM ***

The "2.1. Booting the Virtual Machine" states:

1. The following figure shows the graphics console that comes up when 
the VM is started. At the Shell> prompt, enter the command map fs* to 
display the file systems available on your system.

2. Choose the file system that maps to the .ISO file that you have 
downloaded and set up as a CDROM/DVD. The shell sees the .ISO file as a 
CDROM, so you need to choose an FSn that is labeled CDROM. In the above 
example, we know that fs1 is the .ISO that we want to boot.

3. Knowing that fs1 is associated with the CDROM that is the .ISO, enter 
the following command to run the Boot Manager:
    fs1:\efi\vms\vms_bootmgr.efi

I must have gotten into the habit of running the BootMgr

Shell> vms_bootmgr

and then booting 9.1-A VMS with a simple

BOOTMGR> BOOT

which was happy as long as DKA0 (bootable system disk) had the 9.1-A 
BootMgr.  It was a poor recipe when "upgrading".

And of course...

Had the 9.2 installation had a non-bootable .VDI (DKA0) the previous 
BootMgr would not have been invoked and the simple BOOT would have 
picked up the most recent ISO as DKA200 (only bootable device).

Confirmed that suspicion (quoted to prevent wrapping):

++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Shell> vms_bootmgr
8< snip 8<
> BOOTMGR> DEVICES
> 
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
> 
>   DKA200     (DVD) = FS1    UEFI: E9_2         OpenVMS: None         1263  MB  SATA DVD
> 
> BOOTMGR> BOOT
> 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.
8< snip 8<
-------------------------------------------------------

Couple of gotchas here.

But not suspect, only expected behaviour it seems.

My regrets Rob.

>> 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.