Crash on installation kit media boot

[vmseagle]

I have confirmed that I have the same problem.

When you have a new executable/loadable image, please let me know.

I have a way to create an updated installation media so I can test this fairly quickly and before field test closes. It will also allow me to continue field test work.

Thanks.

[reinhardtjh]

I saw that this was on a NUC and got worried. I hadn't had a chance to try E9.2-3 and I have several NUC's running V9.2-2. But I upgraded one to E9.2-3 and it runs with no errors. Mine are NUC 9 Extreme. One has an i9 and the other has a Xeon. I'm guessing that because they are higher level CPU's that they have the needed avx/avx2 support.

Where did you run that cpuinfo command? In the bios/efi page before booting?

[sms]

Code: Select all

>  Where did you run that cpuinfo command? In the bios/efi page before
> booting?

   If by "that cpuinfo command" you mean "hwinfo --cpu", then I wondered
that too.  I know nothing, but my quick Web search found:

      https://www.hwinfo.com/

which suggested that it's a program "for Windows and DOS."  (I haven't
tried it yet.)

   What did _your_ search find?

[reinhardtjh]

What did _your_ search find?

Okay Steven, you caught me. I didn't search. I was lazy and just hoped the previous posters would tell me. The HWINFO may have come from a command I found in the EFI Shell that did give me some detailed information on the CPU, but not in the format of the information in the previous posts. I suspect they ran it on the VM host and they are using VirtualBox or KVM and running it at the Linux (or Windows CMD prompt). I am using ESXi and I don't think it's CLI has that command. Though, again, I haven't attempted checking the ESXi CLI (because I don't want to shut down the host to get to the CLI) or Googling it (lazy).

[issinoho]

Yeah I'm running QEMU/KVM on Debian so executing the HWINFO command on the Linux host.

[hb]

"hwinfo" is a tool contained in the Debian package "hwinfo". The tool is probably available for other Linux distributions as well.

I don't know of any EFI command to display the cpu features. But the VMS BOOTMGR can show you all the cpu features. Enter SYSINFO at the BOOTMGR prompt and respond to the SYSINFO prompts.

[m_detommaso]

To determine if your system's CPU provides the functionality required to run OpenVMS V9.2 or later, you can run also a special Python script provided by VSI at the following link :

https://vmssoftware.com/openkits/alpope ... scheck.zip

Code: Select all

C:\>python vmscheck.py

OpenVMS 9.x compatibility quick-check

Vendor ID : GenuineIntel
CPU name  : 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz

Necessary for OpenVMS 9.x:
Intel CPU : Yes
SSE 4.1   : Yes
XSAVE     : Yes
TSC       : Yes
APIC      : Yes
MTRR      : Yes

Optional for OpenVMS 9.x:
PCID      : Yes
X2APIC    : Yes
FSGSBASE  : Yes
MD_CLEAR  : Yes
XSAVEOPT  : Yes

Possible future optionals:
TSX-HLE   : --
TSX-RTM   : --
UMIP      : Yes

/Maurizio

[reinhardtjh]

"hwinfo" is a tool contained in the Debian package "hwinfo". The tool is probably available for other Linux distributions as well.

But not on the VMWare ESXi command line as far as I can tell.

I don't know of any EFI command to display the cpu features. But the VMS BOOTMGR can show you all the cpu features. Enter SYSINFO at the BOOTMGR prompt and respond to the SYSINFO prompts.

Yes, that's the one I found. Unfortunately my terminal emulator didn't log it so I can't post what I found, but it's a very different format than hwinfo.

[hb]

To determine if your system's CPU provides the functionality required ...

Obviously the python script does not print the AVX features. Do you suggest to enhance it? Anybody can easily add something like:

Code: Select all

--- vmscheck.py~        2023-02-16 12:46:14.000000000 +0100
+++ vmscheck.py 2024-08-30 17:08:47.833288731 +0200
@@ -242,6 +242,9 @@
     print("Optional for OpenVMS 9.x:")
     print("PCID             : %s" % is_set(cpu, 1, 0, 2, 17))
     print("X2APIC           : %s" % is_set(cpu, 1, 0, 2, 21))
+    print("AVX              : %s" % is_set(cpu, 1, 0, 2, 28))
     print("FSGSBASE         : %s" % is_set(cpu, 7, 0, 1, 0))
+    print("AVX2             : %s" % is_set(cpu, 7, 0, 1, 5))
+    print("AVX512F          : %s" % is_set(cpu, 7, 0, 1, 16))
     print("MD_CLEAR         : %s" % is_set(cpu, 7, 0, 3, 10))
     print("XSAVEOPT         : %s" % is_set(cpu, 0xd, 1, 0, 0))

which prints the correct information from my system, but there is no guarantee that the leafs, subleafs and bits are correct; consult the documentation provided by Intel, Google or ChatGTP

[vmseagle]

Any update on a fix for this ?

I have a KVM environment on top of UBUNTU and have made a writable installation kit. If I could get the updated image(s)/execlets(s), I can update and test immediately.