QEMU/KVM-or-HVF crash in installer

Having difficulties when installing the system? Your system runs slowly and requires some tweaking? You can get help here.
Post Reply

Topic author
adam
Contributor
Posts: 10
Joined: Wed Apr 19, 2023 2:46 am
Reputation: 0
Status: Offline

QEMU/KVM-or-HVF crash in installer

Post by adam » Wed Apr 19, 2023 2:59 am

On both a MacBook Air Intel and an HP EliteDesk 800 G2 Mini (cpus respectively "Intel(R) Core(TM) i5-8210Y CPU @ 1.60GHz" and "Intel(R) Core(TM) i5-6500T CPU @ 2.50GHz") I get similar crashes. I set NODUMP so that the machine doesn't just restart when it crashes, but the virtual disks have not been initialized yet.

The installer loads the ISO into RAM and then there are a bunch of MMG$PAGEFAULT IPLHI.

The weird thing is, I have no idea why it would be page faulting. There's no backing store to page to yet in any event, and it happens with both 8G and 15G defined to the virtual machine.

Anyone got any ideas of what to try?

this is the top...

Code: Select all

VSI Primary Kernel SYSBOOT Jan 23 2023 14:03:45


        VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, E9.2-1
                    Copyright 2023 VMS Software, Inc.

  MDS Mitigation active, variant verw(MD_CLEAR)

MMG$PAGEFAULT IPLHI:
  Fault_VA:  000000000080B000
  Err Code:  0000000000000000
  MMF_Flags: 0000000000000000
  Intstk_p:  FFFFFFFF8C2218A0
  RIP:       FFFF83007555E179
  Int_ps:    0000000000001F00

*** Page Fault IPL Too High ***


**************************************************************
* Exception taken before exception handler has been loaded!  *
* Unable to take crashdump.                                  *
**************************************************************

* Exception Frame Display: *

Exception taken at RIP FFFF8300.69FB39D2 from Kernel mode
Exception Frame at FFFFFFFF.8C221320
X86 Vector  00000020 (BREAK Instruction)

* = Value read directly from the register rather than the frame

Control Registers:
CR0    System Control Flags                 * 00000000.80010033
       PE = 1   MP = 1   EM = 0   TS = 0   ET = 1   NE = 1
       WP = 1   AM = 0   NW = 0   CD = 0   PG = 1
CR2    Page-Fault Linear Address            * 00000000.0080B000
CR3    Paging Control                       * 00000001.00030000
       PWT= 0   PCD= 0  PGDB= 00000001.00030000
CR4    Architectural Extension Flags        * 00000000.00070668
       VME= 0   PVI= 0   TSD= 0   DE = 1   PSE= 0   PAE= 1
       MCE= 1   PGE= 0   PCE= 0  FXSR= 1 XMMXC= 1  UMIP= 0
      LA57= 0  VMXE= 0  SMXE= 0  FSGS= 1 PCIDE= 1 XSAVE= 1
      SMEP= 0  SMAP= 0   PKE= 0
CR8    Task Priority Register (TPR)           * 00000000.0000000F
GSBASE GS Segment Base (SWIS data)            * FFFFFFFF.8C190000

RFLAGS Processor Flags                        00000000.00000006
       CF = 0   PF = 1   AF = 0   ZF = 0   SF = 0   TF = 0
       IF = 0   DF = 0   OF = 0  IOPL= 0   NT = 0   RF = 0   VM = 0
       AC = 0   VIF= 0   VIP= 0   ID = 0

Miscellaneous Registers:
Interrupt Priority Level (IPL)                0000001F
Stack Align                                   000001E8
PPrev Mode                                    0
Previous Mode                                 0
Interrupt Depth                               0

General Registers:
RAX  00000000.00000600     RBX  FFFFFFFF.8C221E00     RCX  00000000.0080B000
RDX  FFFFFFFF.8C2218A0     RSI  00000000.0000035C     RDI  00000000.00100002
RSP  FFFFFFFF.8C221508     RBP  FFFFFFFF.8C221620
R8   00000000.00000000     R9   00000000.0000001F     R10  00000000.0000035C
R11  00000000.0000035C     R12  FFFFFFFF.8C221518     R13  00000000.00000000
R14  00000000.00000000     R15  FFFF8300.69739306


******************************************
* Using INIBRK to get help from Xdelta!  *
******************************************

**************************************************************
* Exception taken before exception handler has been loaded!  *
* Unable to take crashdump.                                  *
**************************************************************

* Exception Frame Display: *

Exception taken at RIP FFFF8300.69FC4164 from Kernel mode
Exception Frame at FFFFFFFF.8C221330
X86 Vector  00000020 (BREAK Instruction)

* = Value read directly from the register rather than the frame

Control Registers:
CR0    System Control Flags                 * 00000000.80010033
       PE = 1   MP = 1   EM = 0   TS = 0   ET = 1   NE = 1
       WP = 1   AM = 0   NW = 0   CD = 0   PG = 1
CR2    Page-Fault Linear Address            * 00000000.0080B000
CR3    Paging Control                       * 00000001.00030000
       PWT= 0   PCD= 0  PGDB= 00000001.00030000
CR4    Architectural Extension Flags        * 00000000.00070668
       VME= 0   PVI= 0   TSD= 0   DE = 1   PSE= 0   PAE= 1
       MCE= 1   PGE= 0   PCE= 0  FXSR= 1 XMMXC= 1  UMIP= 0
      LA57= 0  VMXE= 0  SMXE= 0  FSGS= 1 PCIDE= 1 XSAVE= 1
      SMEP= 0  SMAP= 0   PKE= 0
CR8    Task Priority Register (TPR)           * 00000000.0000000F
GSBASE GS Segment Base (SWIS data)            * FFFFFFFF.8C190000

RFLAGS Processor Flags                        00000000.00000006
       CF = 0   PF = 1   AF = 0   ZF = 0   SF = 0   TF = 0
       IF = 0   DF = 0   OF = 0  IOPL= 0   NT = 0   RF = 0   VM = 0
       AC = 0   VIF= 0   VIP= 0   ID = 0

Miscellaneous Registers:
Interrupt Priority Level (IPL)                0000001F
Stack Align                                   000001E0
PPrev Mode                                    0
Previous Mode                                 0
Interrupt Depth                               0

General Registers:
RAX  00000000.00000600     RBX  FFFFFFFF.8C221E00     RCX  00000000.0080B000
RDX  FFFFFFFF.8C2218A0     RSI  00000000.0000035C     RDI  00000000.00100003
RSP  FFFFFFFF.8C221510     RBP  FFFFFFFF.8C221620
R8   00000000.00000000     R9   00000000.0000001F     R10  00000000.0000035C
R11  00000000.0000035C     R12  FFFFFFFF.8C221518     R13  00000000.00000000
R14  00000000.00000000     R15  FFFF8300.69739306

...and this is the bottom. There are hundreds of lines in between the two, all similar-looking.

Code: Select all


**************************************************************
* Exception taken before exception handler has been loaded!  *
* Unable to take crashdump.                                  *
**************************************************************

* Exception Frame Display: *

Exception taken at RIP FFFF8300.69FC4164 from Kernel mode
Exception Frame at FFFFFFFF.8C2173D0
X86 Vector  00000020 (BREAK Instruction)

* = Value read directly from the register rather than the frame

Control Registers:
CR0    System Control Flags                 * 00000000.80010033
       PE = 1   MP = 1   EM = 0   TS = 0   ET = 1   NE = 1
       WP = 1   AM = 0   NW = 0   CD = 0   PG = 1
CR2    Page-Fault Linear Address            * 00000000.7FFF0278
CR3    Paging Control                       * 00000001.00030000
       PWT= 0   PCD= 0  PGDB= 00000001.00030000
CR4    Architectural Extension Flags        * 00000000.00070668
       VME= 0   PVI= 0   TSD= 0   DE = 1   PSE= 0   PAE= 1
       MCE= 1   PGE= 0   PCE= 0  FXSR= 1 XMMXC= 1  UMIP= 0
      LA57= 0  VMXE= 0  SMXE= 0  FSGS= 1 PCIDE= 1 XSAVE= 1
      SMEP= 0  SMAP= 0   PKE= 0
CR8    Task Priority Register (TPR)           * 00000000.0000000F
GSBASE GS Segment Base (SWIS data)            * FFFFFFFF.8C190000

RFLAGS Processor Flags                        00000000.00000206
       CF = 0   PF = 1   AF = 0   ZF = 0   SF = 0   TF = 0
       IF = 1   DF = 0   OF = 0  IOPL= 0   NT = 0   RF = 0   VM = 0
       AC = 0   VIF= 0   VIP= 0   ID = 0

Miscellaneous Registers:
Interrupt Depth                               1

General Registers:
RAX  00000000.00000600     RBX  FFFFFFFF.8C221E00     RCX  00000000.7FFF0278
RDX  FFFFFFFF.8C217940     RSI  00000000.0000035C     RDI  00000000.00100003
RSP  FFFFFFFF.8C2175B0     RBP  FFFFFFFF.8C2176C0
R8   00000000.00000000     R9   00000000.00000008     R10  00000000.0000035C
R11  00000000.0000035C     R12  FFFFFFFF.8C2175B8     R13  00000000.00000000
R14  00000000.00000000     R15  FFFF8300.69739706


******************************************
* Using INIBRK to get help from Xdelta!  *
******************************************
MMG$PAGEFAULT IPLHI:
  Fault_VA:  000000007FFF0278
  Err Code:  0000000000000000
  MMF_Flags: 0000000000000000
  Intstk_p:  FFFFFFFF8C2173D0
  RIP:       FFFF830069FC3375
  Int_ps:    0000000000000800

*** Page Fault IPL Too High ***
Interrupt Depth                               1

General Registers:
RAX  00000000.00000600     RBX  FFFFFFFF.8C221E00     RCX  00000000.7FFF0278
RDX  FFFFFFFF.8C217940     RSI  00000000.0000035C     RDI  00000000.00100003
RSP  FFFFFFFF.8C2175B0     RBP  FFFFFFFF.8C2176C0
R8   00000000.00000000     R9   00000000.00000008     R10  00000000.0000035C
R11  00000000.0000035C     R12  FFFFFFFF.8C2175B8     R13  00000000.00000000
R14  00000000.00000000     R15  FFFF8300.69739706


******************************************
* Using INIBRK to get help from Xdelta!  *
******************************************
MMG$PAGEFAULT IPLHI:
  Fault_VA:  000000007FFF0278
  Err Code:  0000000000000000
  MMF_Flags: 0000000000000000
  Intstk_p:  FFFFFFFF8C2173D0
  RIP:       FFFF830069FC3375
  Int_ps:    0000000000000800

*** Page Fault IPL Too High ***

User avatar

volkerhalle
Master
Posts: 196
Joined: Fri Aug 14, 2020 11:31 am
Reputation: 0
Status: Offline

Re: QEMU/KVM-or-HVF crash in installer

Post by volkerhalle » Wed Apr 19, 2023 5:26 am

Adam,

some code running at High IPL (31.), tried to access a P0-space address (Fault_VA: 000000000080B000). This is illegal and causes a pagefault at high IPL. This happens in the very early stage of the OpenVMS boot and the system is not yet ready to take a crashdump.

This is most likely a software bug, question may be, whether this is a supported configuration.

You could try to determine by setting the FLAGS value at boot time, which component causes this error.

BOOTMGR> FLAGS has some help

Try with:

BOOTMGR> BOOT device 0 000000F0

Volker.


Topic author
adam
Contributor
Posts: 10
Joined: Wed Apr 19, 2023 2:46 am
Reputation: 0
Status: Offline

Re: QEMU/KVM-or-HVF crash in installer

Post by adam » Wed Apr 19, 2023 10:42 am

That seems a little more informative...looks like the page fault happens when...reading the clock?!?

Code: Select all

BOOTMGR> BOOT DKA200 000000F0
Booting...
%VMS_BOOTMGR-I-MAIN,    Allocating Kernel Memory.
%VMS_BOOTMGR-I-SMP,     Enumerating Processors.
%VMS_BOOTMGR-I-MEMDISK, [BLOCKIO] Booting a local ISO kit image.
%VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...

%VMS_BOOTMGR-I-MEMDISK, Loading ISO image into DMM1. This may take a few minutes...
100%

%VMS_BOOTMGR-I-MEMDISK, Extracting DMM0 from DMM1...
%VMS_BOOTMGR-I-MEMDISK, Extracting SYSBOOT from DMM0...
%VMS_BOOTMGR-I-HWRPB,   Initializing Kernel Data Structures.
%VMS_BOOTMGR-I-HWRPB,   Initializing HWRPB for Primary Kernel.
%VMS_BOOTMGR-I-HWRPB,   Configuring System Clocks... (~3 second delay)

%VMS_BOOTMGR-I-HWRPB,   Unable to determine System Serial Number



%VMS_BOOTMGR-I-TRANSFER: Starting VSI OpenVMS


%%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%


Current date and time: 04-19-2023 14:38:08
Welcome to VSI OpenVMS SYSBOOT, Baselevel XGF4, built on Jan 23 2023 14:03:45

HWRPB address 00000000.00600000, SWRPB address 00000000.00412400
SYSBOOT message flags address 0x00412418 value 0x00000000

_______________________________________________

      GRAPHICAL OUTPUT HAS BEEN SUSPENDED
      USE A TERMINAL UTILITY FOR ACCESS
_______________________________________________
%SYSBOOT-I-HPETTIMER, This system is using the HPET as the hardware timer

VSI Primary Kernel SYSBOOT Jan 23 2023 14:03:45
%SYSBOOT-I-TSCNOTINVAR, This CPU has a variable-rate Time Stamp Counter (TSC)
%SYSBOOT-I-ONEGB, 1-GB pages ARE available on this system
%SYSBOOT-I-MOUNT, Mounting the boot memory disk

%SYSBOOT-I-MEMDISKMNT, Boot memory disk mounted

%SYSBOOT-I-LOADPARAM, Loading parameter file X86_64VMSSYS.PAR
%SYSBOOT-I-LOADFILE, Loaded file [SYSF0.SYSEXE]X86_64VMSSYS.PAR
boo$usefile: startup file SYS$SYSTEM:SA_STARTUP.COM
%SYSBOOT-I-DISMOUNT, Dismounting the boot memory disk

%SYSBOOT-I-MEMDISKDISMNT, Boot memory disk dismounted
Best PXML memory PA ranges: 100000000:27fffffff and 0:0
System physical memory address range is 00000000.00000000 to 00000002.7fffffff
Total physical memory size is 0x00000002.80000000 bytes (10,240 MB)
Physical memory size excluding memory holes is 0x00000001.fff24000 bytes (8,191 MB)
%SYSBOOT-I-ALLOCMAPBLT, Allocation bitmap built

Allocation area 1   addresses 00000001.00000000 to 00000002.7fffffff, size 180000000 bytes
Allocation area 1   PFNs 100000 to 27ffff, count 180000 PFNs
Allocation bitmap 1 addresses 00000001.00000000 to 00000001.0002ffff, size 30000 bytes
There is no allocation area 2
Creating the S0 space page tables
%SYSBOOT-I-S0PT_CREATED, S0 space page tables created
Remapping Boot MemoryDisk to S2 space
MemoryDisk PA = 00000000.64000000, size = 0x6400000 bytes
Boot memdisk size 0x6400000 bytes
Mapping the boot memory disk into megapages
MemoryDisk VA = ffff8300.00000000, size = 0x6400000 bytes
%SYSBOOT-I-MAP_MD, Boot MemoryDisk remapped to S2 space
Remapping System MemoryDisk to S2 space
System MemoryDisk PA = 00000000.01800000, size = 0x62800000 bytes
System MemoryDisk VA = ffff8300.06400000, size = 0x62800000 bytes
%SYSBOOT-I-MAP_SYSMD, System MemoryDisk remapped to S2 space
%SYSBOOT-I-MOUNT, Mounting the boot memory disk

%SYSBOOT-I-MEMDISKMNT, Boot memory disk mounted
Base RAD memsize 0x280000 4-kB PFNs

system PHD sysphdln 0x10000 bytes
nonpaged pool 0x2400000 exec_data_bytes 0x2410000
paged pool 0x400000 exec_data_bytes 0x2810000
errorlogs 0x4000 exec_data_bytes 0x2814000
exec_data_pages 0x1600 8-kB pages exec_data_bytes 0x2814000

S2 pool size (initial param)= 0x2 MB
boo$gq_npagedynsz_s2 (initial) 0x200000
S2 erlbuf = 0x4000 bytes bufcnt 0x4 bufpagelets 0x8
 Final boo$gq_npagedynsz_s2 0x3fc000 Final: boo$gq_npagexpvir_s2 0x7fc000
giga page size 0x40000 pages slice size 0x400000 bytes
ldr$init_mem: LDRHP PA 00000001.00350000
ldr$map_huge_page: Mapping big pages, type 1
ldr$map_huge_page: Mapped huge page,  type 1, VA ffffffff.80400000, PA 00000001.00400000, size 0x01000000, alignment 0x00400000
ldr$map_huge_page: Mapped huge page,  type 2, VA ffffffff.81400000, PA 00000001.01400000, size 0x02c00000, alignment 0x00002000
ldr$map_huge_page: Mapped huge page,  type 3, VA ffffffff.8a7fe000, PA 00000001.04400000, size 0x00400000, alignment 0x00002000
ldr$map_huge_page: Mapped huge page,  type 4, VA ffffffff.8abfe000, PA 00000001.04c00000, size 0x00400000, alignment 0x00002000
ldr$map_huge_page: Mapped huge page,  type 5, VA ffff8300.68c00000, PA 00000001.05400000, size 0x00400000, alignment 0x00002000
ldr$map_huge_page: Mapping big pages, type 6
ldr$map_huge_page: Mapped huge page,  type 6, VA ffff8300.69400000, PA 00000001.05c00000, size 0x02000000, alignment 0x00400000
ldr$map_huge_page: Mapped huge page,  type 7, VA ffff8300.6b400000, PA 00000001.07c00000, size 0x01400000, alignment 0x00002000
ldr$map_huge_page: Mapped huge page,  type 8, VA ffff8300.6c800000, PA 00000001.09400000, size 0x00400000, alignment 0x00002000
ldr$map_huge_page: Mapping big pages, type 9
ldr$map_huge_page: Mapped huge page,  type 9, VA ffffffff.8b000000, PA 00000001.09c00000, size 0x00800000, alignment 0x00400000
ldr$map_huge_page: Mapped huge page,  type 10, VA ffffffff.8b800000, PA 00000001.0a400000, size 0x00800000, alignment 0x00002000
ldr$map_huge_page: Mapped huge page,  type 11, VA ffff8300.6cc00000, PA 00000001.0b000000, size 0x00400000, alignment 0x00002000
%SYSBOOT-I-ALLOCPGS, Loader huge pages allocated

Loading base system images
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYSLIB]SYS$PUBLIC_VECTORS.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]SYS$BASE_IMAGE.EXE
%SYSBOOT-I-LOADSYSIMGS, Base system images loaded
%SYSBOOT-I-CONIO, ConIoData: 0x7F9AC898, ComPortBAR: 0x3F8
PFN database ffff8300.6d400000, mapped 2, big 0
PFN database allocated starting at VA ffff8300.6d400000 ending at VA ffff8300.723fffff
%SYSBOOT-I-INITDATA, Key system data cells initialized

Balance set slots size 0x78 PFNs each 2 num 1e
 from PHD 388 maxpstct 100 SEC 30
Working set slots size 0x21c PFNs each 9
 from wslpte 4 emptpte 5 wsllen 8
 from pql$gdwsdefault_pages c00 sgn$gl_maxwscnt_pages 2000
Creating the SYSPHD
Allocating the error log buffers
%SYSBOOT-I-ALLOCERL, Allocated Error Log Buffers
Creating paged and nonpaged pools
Allocating USB Addressable Pool (UAP)
HWRPB 00000000.00600000 Kernel Base area PA 00000000.00100000
PK UAP offset 100000 size 100000
DK UAP offset 200000 size 100000
UAP allocated size 0x100000 bytes, mmg$gq_bap ffffffff.8c078000
UAP physical addresses 200000 to 2fffff
%SYSBOOT-I-POOLINIT, Created Paged and Nonpaged Pools
Copying PXML database to S2 space
PXML database copied to address ffff8300.7261e000
%SYSBOOT-I-PXMLCOPY, Copied PXML Database to S2 space
Primary CPU database ffffffff.81c00000
%SYSBOOT-I-CREATECPUDB, Created the CPU Database
Copying the SWRPB and remapping the HWRPB
HWRPB size 0x9a000 bytes
Remapped HWRPB to ffffffff.8c178000 copied SWRPB to ffffffff.81c01140
%SYSBOOT-I-REMAP, Moved HWRPB and SWRPB to system space
Gathering CPUID information
%SYSBOOT-I-CPUID, Gathered CPUID information
Remapping the IDT
IDT size 0x1000 bytes
Remapping IDT from 00000000.7f9a7000 to ffffffff.8c213000
%SYSBOOT-I-REMAPIDT, Remapped IDT to system space
Initializing the primary CPU database and kernel stack
Allocating the system kernel stack
kernel stack allocated at VA ffffffff.8c216000 for 0xc pages
Kernel stack pointer/base ffffffff.8c221e00 limit ffffffff.8c216000
icpudb: mcheck logout 00000000.00000000, still to be done
%SYSBOOT-I-INITCPUDB, Initialized Primary CPU Database
Slot VA ffffffff.8c17f000
Slot cycle counter freq = 94caa8de
Slot clock int freq = 0
Slot itc freq = 5f613c9
Initializing the global page table
GPT addr ffff8300.72622000 size 0x2002000 bytes
%SYSBOOT-I-INITGPT, Initialized Global Page Table
Creating the boot SYI and PFN memory maps
%SYSBOOT-I-PFNMAP, Created PFN Memory Map

%SYSBOOT-i-PFNDB, Creating the PFN database
%SYSBOOT-I-CREATEPFNDB, Created PFN Database

%SYSBOOT-I-UEFIREMAP, Remapping UEFI Services...
%SYSBOOT-I-UEFIRUNVIRT, Enabling Virtual Runtime Services.
%SYSBOOT-I-LOADEXEC, Loading execlets...
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]SYS$PLATFORM_SUPPORT.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]ERRORLOG.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]SYS$ACPI.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]SYSTEM_PRIMITIVES_7_MIN.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]SYS$OPDRIVER.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]EXEC_INIT.EXE
%SYSBOOT-I-LOADEXEC, Execlets loaded
Copying boot port allocation class list
empty paclist
%SYSBOOT-I-PARMSCOPIED, System parameters copied to the base image

Summary of Huge Pages
   Huge Page Type      Description                      Start VA          End VA        Physical Address    Size (Bytes)
 0 GH_EXEC_CODE      SHOULD BE EMPTY                00000000.00000000 00000000.00000000 00000000.00000000h             0h
 1 GH_EXEC_DATA      execlet image RW data  S0 URKW ffffffff.80400000 ffffffff.813fffff 00000001.00400000h       1000000h
 2 EXEC S0 region    exec runtime RW data   S0 ERKW ffffffff.81400000 ffffffff.83ffffff 00000001.01400000h       2c00000h
 3 GH_RES_CODE       resident image code    S0 URX  ffffffff.8a7fe000 ffffffff.8abfdfff 00000001.04400000h        400000h
 4 GH_RES_DATA       resident image data    S0 URKW ffffffff.8abfe000 ffffffff.8affdfff 00000001.04c00000h        400000h
 5 EXEC S2 region    exec runtime RW data   S2 ERKW ffff8300.68c00000 ffff8300.68ffffff 00000001.05400000h        400000h
 6 GH_EXEC_CODE_S2   execlet code           S2 URX  ffff8300.69400000 ffff8300.6b3fffff 00000001.05c00000h       2000000h
 7 GH_RES_CODE_S2    resident image code    S2 URX  ffff8300.6b400000 ffff8300.6c7fffff 00000001.07c00000h       1400000h
 8 GH_EXEC_DATA_S2   execlet image RW data  S2 ERKW ffff8300.6c800000 ffff8300.6cbfffff 00000001.09400000h        400000h
 9 GH_RO_EXEC_S0     execlet image RO data  S0 URX  ffffffff.8b000000 ffffffff.8b7fffff 00000001.09c00000h        800000h
10 GH_RO_RES_S0      resident image RO data S0 URX  ffffffff.8b800000 ffffffff.8bffffff 00000001.0a400000h        800000h
11 GH_RES_DATA_S2    resident image data    S2 ERKW ffff8300.6cc00000 ffff8300.6cffffff 00000001.0b000000h        400000h

       Bitmap VA     Bitmap Size (Bytes)  Slice Size (Bytes)     Used    Free    Total
 0 00000000.00000000  00000000.00000000h  00000000.00000000h        0       0        0
 1 ffffffff.80000680  00000000.00001000h  00000000.00000200h    1,381  31,387   32,768
 2 ffffffff.80001680  00000000.00000580h  00000000.00001000h   10,260   1,004   11,264
 3 ffffffff.80001c00  00000000.00000400h  00000000.00000200h        0   8,192    8,192
 4 ffffffff.80002000  00000000.00000400h  00000000.00000200h        0   8,192    8,192
 5 ffffffff.80002400  00000000.00000080h  00000000.00001000h    1,024       0    1,024
 6 ffffffff.80002480  00000000.00004000h  00000000.00000100h   14,405 116,667  131,072
 7 ffffffff.80006480  00000000.00000280h  00000000.00001000h        0   5,120    5,120
 8 ffffffff.80006700  00000000.00000400h  00000000.00000200h        0   8,192    8,192
 9 ffffffff.80006b00  00000000.00000800h  00000000.00000200h    2,026  14,358   16,384
10 ffffffff.80007300  00000000.00000800h  00000000.00000200h        0  16,384   16,384
11 ffffffff.80007b00  00000000.00000400h  00000000.00000200h        0   8,192    8,192
%SYSBOOT-I-TRANSFER, Transferring to EXEC_INIT at: ffff8300.6973c200
%EXECINIT-I-PERCPU, initializing per-CPU database
%EXECINIT-I-INITS, calling initialization routines
%LOADER-I-INIT, initializing SYS$BASE_IMAGE
%LOADER-I-INIT, initializing SYS$PLATFORM_SUPPORT
%LOADER-I-INIT, initializing ERRORLOG
%LOADER-I-INIT, initializing SYS$ACPI
%LOADER-I-INIT, initializing SYSTEM_PRIMITIVES_7_MIN
SWIS Logging is currently OFF.
Turn on by setting SWIS_LOG bit 1 or setting SYSTEM_CHECK non-0 and clearing SWIS_LOG bit 3.
%LOADER-I-INIT, initializing SYSTEM_SYNCHRONIZATION
%LOADER-I-INIT, initializing SYS$OPDRIVER


        VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, E9.2-1
                    Copyright 2023 VMS Software, Inc.

%EXECINIT-I-INIT_MMG, init free list, outer mode page tables and PFN database
%EXECINIT-I-DELBS, deleting bootstrap VA space
%EXECINIT-I-SWIS_PRIM, initializing SWIS on primary CPU
  MDS Mitigation active, variant verw(MD_CLEAR)
%EXECINIT-I-INITS, calling initialization routines
%LOADER-I-INIT, initializing SYSTEM_PRIMITIVES_7_MIN
SWIS Logging is currently OFF.
Turn on by setting SWIS_LOG bit 1 or setting SYSTEM_CHECK non-0 and clearing SWIS_LOG bit 3.
%LOADER-I-INIT, initializing SYSTEM_SYNCHRONIZATION
%LOADER-I-INIT, initializing SYSTEM_PRIMITIVES_7_MIN
SWIS Logging is currently OFF.
Turn on by setting SWIS_LOG bit 1 or setting SYSTEM_CHECK non-0 and clearing SWIS_LOG bit 3.
%EXECINIT-I-EPB, defining erase pattern buffer
%EXECINIT-I-SHELLF, building SHELL filespec
%EXECINIT-I-BTINIT, initializing boot driver

%SYSBOOT-I-MEMDISKMNT, Boot memory disk mounted
                                               %EXECINIT-I-RESMEMLIS, building reserved memory registry list
%EXECINIT-I-LDIMGS, loading exec images
%EXECINIT-I-LOADING, loading EXCEPTION.EXE
%LOADER-I-INIT, initializing EXCEPTION
%EXECINIT-I-LOADING, loading IO_ROUTINES.EXE
%LOADER-I-INIT, initializing IO_ROUTINES
%EXECINIT-I-LOADING, loading SYSDEVICE.EXE
%LOADER-I-INIT, initializing SYSDEVICE
%EXECINIT-I-LOADING, loading PROCESS_MANAGEMENT.EXE
%LOADER-I-INIT, initializing PROCESS_MANAGEMENT
%EXECINIT-I-LOADING, loading LOCKING.EXE
%LOADER-I-INIT, initializing LOCKING
%EXECINIT-I-LOADING, loading SHELL8K.EXE
%LOADER-I-INIT, initializing SHELL8K
%EXECINIT-I-LOADING, loading LOGICAL_NAMES.EXE
%LOADER-I-INIT, initializing LOGICAL_NAMES
%EXECINIT-I-LOADING, loading F11BXQP.EXE
%LOADER-I-INIT, initializing F11BXQP
%EXECINIT-I-LOADING, loading RMS.EXE
%LOADER-I-INIT, initializing RMS
%EXECINIT-I-LOADING, loading IMAGE_MANAGEMENT.EXE
%LOADER-I-INIT, initializing IMAGE_MANAGEMENT

%SYSBOOT-I-MEMDISKMNT, Boot memory disk mounted
                                               %EXECINIT-I-LOADING, loading SECURITY.EXE
%LOADER-I-INIT, initializing SECURITY
%EXECINIT-I-LOADING, loading SYSGETSYI.EXE
%LOADER-I-INIT, initializing SYSGETSYI
%EXECINIT-I-LOADING, loading SYS$XFCACHE.EXE
%LOADER-I-INIT, initializing SYS$XFCACHE
%EXECINIT-I-LOADING, loading SYS$VM.EXE
%LOADER-I-INIT, initializing SYS$VM
%EXECINIT-I-LOADING, loading MESSAGE_ROUTINES.EXE
%LOADER-I-INIT, initializing MESSAGE_ROUTINES
%EXECINIT-I-LOADING, loading SYSLICENSE.EXE
%LOADER-I-INIT, initializing SYSLICENSE
%EXECINIT-I-LOADING, loading SYS$VFS.EXE
%EXECINIT-E-LOADERR, error loading SYS$VFS.EXE, status = 00000910
%EXECINIT-I-LOADING, loading SYS$GFS2.EXE
%EXECINIT-E-LOADERR, error loading SYS$GFS2.EXE, status = 00000910
%EXECINIT-I-LOADING, loading SYS$VAFS.EXE
%EXECINIT-E-LOADERR, error loading SYS$VAFS.EXE, status = 00000910
%EXECINIT-I-LOADING, loading SYS$TRANSACTION_SERVICES.EXE
%LOADER-I-INIT, initializing SYS$TRANSACTION_SERVICES
%EXECINIT-I-LOADING, loading SYS$UTC_SERVICES.EXE
%LOADER-I-INIT, initializing SYS$UTC_SERVICES
%EXECINIT-I-LOADING, loading SYS$NETWORK_SERVICES.EXE
%EXECINIT-E-LOADERR, error loading SYS$NETWORK_SERVICES.EXE, status = 00000910
%EXECINIT-I-LOADING, loading SYS$IPC_SERVICES.EXE
%LOADER-I-INIT, initializing SYS$IPC_SERVICES
%EXECINIT-I-LOADING, loading SYSLDR_DYN.EXE
%LOADER-I-INIT, initializing SYSLDR_DYN

%SYSBOOT-I-MEMDISKMNT, Boot memory disk mounted
                                               %EXECINIT-I-LOADING, loading SYS$MME_SERVICES.EXE
%LOADER-I-INIT, initializing SYS$MME_SERVICES
%EXECINIT-I-LOADING, loading SYS$NTA.EXE
%EXECINIT-E-LOADERR, error loading SYS$NTA.EXE, status = 00000910
%EXECINIT-I-LOADING, loading SSPI.EXE
%EXECINIT-E-LOADERR, error loading SSPI.EXE, status = 00000910
%EXECINIT-I-LOADING, loading ACME.EXE
%LOADER-I-INIT, initializing ACME
%EXECINIT-I-LOADING, loading SWIS$DEBUG.EXE
%LOADER-I-INIT, initializing SWIS$DEBUG
%EXECINIT-I-IOCONFIG, configuring the I/O database
%GPS-I-ACPI_SUPPORT,  Initializing ACPI Operating System Layer...
%GPS-I-ACPI_SUPPORT,  Configuring IOAPICs...
%GPS-I-ACPI_SUPPORT,  Configuring ACPI Devices...

%SYSBOOT-I-MEMDISKMNT, Boot memory disk mounted
                                               %LOADER-I-INIT, initializing SYS$PCIE_SUPPORT
%LOADER-I-INIT, initializing SYS$ISA_SUPPORT
%GPS-I-ACPI_SUPPORT,  Configuring GPE Blocks...
%GPS-I-ACPI_SUPPORT,  Configuring ACPI CPUs...
%EXECINIT-I-HWCLOCK, reading the HW clock

MMG$PAGEFAULT IPLHI:
  Fault_VA:  000000000080B000
  Err Code:  0000000000000000
  MMF_Flags: 0000000000000000
  Intstk_p:  FFFFFFFF8C2218A0
  RIP:       FFFF83007555E179
  Int_ps:    0000000000001F00

*** Page Fault IPL Too High ***


**************************************************************
* Exception taken before exception handler has been loaded!  *
* Unable to take crashdump.                                  *
**************************************************************

* Exception Frame Display: *

Exception taken at RIP FFFF8300.69FB39D2 from Kernel mode
Exception Frame at FFFFFFFF.8C221320
X86 Vector  00000020 (BREAK Instruction)

* = Value read directly from the register rather than the frame

Control Registers:
CR0    System Control Flags                 * 00000000.80010033
       PE = 1   MP = 1   EM = 0   TS = 0   ET = 1   NE = 1
       WP = 1   AM = 0   NW = 0   CD = 0   PG = 1
CR2    Page-Fault Linear Address            * 00000000.0080B000
CR3    Paging Control                       * 00000001.00030000
       PWT= 0   PCD= 0  PGDB= 00000001.00030000
CR4    Architectural Extension Flags        * 00000000.00070668
       VME= 0   PVI= 0   TSD= 0   DE = 1   PSE= 0   PAE= 1
       MCE= 1   PGE= 0   PCE= 0  FXSR= 1 XMMXC= 1  UMIP= 0
      LA57= 0  VMXE= 0  SMXE= 0  FSGS= 1 PCIDE= 1 XSAVE= 1
      SMEP= 0  SMAP= 0   PKE= 0
CR8    Task Priority Register (TPR)           * 00000000.0000000F
GSBASE GS Segment Base (SWIS data)            * FFFFFFFF.8C190000

RFLAGS Processor Flags                        00000000.00000006
       CF = 0   PF = 1   AF = 0   ZF = 0   SF = 0   TF = 0
       IF = 0   DF = 0   OF = 0  IOPL= 0   NT = 0   RF = 0   VM = 0
       AC = 0   VIF= 0   VIP= 0   ID = 0

Miscellaneous Registers:
Interrupt Priority Level (IPL)                0000001F
Stack Align                                   000001E8
PPrev Mode                                    0
Previous Mode                                 0
Interrupt Depth                               0

General Registers:
RAX  00000000.00000600     RBX  FFFFFFFF.8C221E00     RCX  00000000.0080B000
RDX  FFFFFFFF.8C2218A0     RSI  00000000.0000035C     RDI  00000000.00100002
RSP  FFFFFFFF.8C221508     RBP  FFFFFFFF.8C221620
R8   00000000.00000000     R9   00000000.0000001F     R10  00000000.0000035C
R11  00000000.0000035C     R12  FFFFFFFF.8C221518     R13  00000000.00000000
R14  00000000.00000000     R15  FFFF8300.69739306


******************************************
* Using INIBRK to get help from Xdelta!  *
******************************************

**************************************************************
* Exception taken before exception handler has been loaded!  *
* Unable to take crashdump.                                  *
**************************************************************
Added in 10 minutes :
Setting -rtc clock=vm crashes in essentially the same way, but I get a dump on the terminal where I started the emulator:

Code: Select all

KVM: entry failed, hardware error 0x7
RAX=0000000000000000 RBX=ffffffff8c221e00 RCX=0000000000000000 RDX=0000000000000016
RSI=0000000000000100 RDI=0000000000000000 RBP=ffffffff8c218da0 RSP=ffffffff8c218c90
R8 =0000000080467400 R9 =0000000000000000 R10=0000000000000008 R11=ffff8300695ad460
R12=ffffffff8c218fa8 R13=0000000000000000 R14=0000000000000000 R15=ffff830069738308
RIP=ffff8300695ae937 RFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
CS =0008 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA]
SS =0010 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
DS =0010 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
FS =0010 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
GS =0028 ffffffff8c190000 000060c7 00109300 DPL=0 DS   [-WA]
LDT=0000 0000000000000000 0000ffff 00008200 DPL=0 LDT
TR =0028 ffffffff8c1901b0 0000006b 00108b00 DPL=0 TSS64-busy
GDT=     ffffffff8c267fc0 00000037
IDT=     ffffffff8c26c000 00000fff
CR0=80010033 CR2=000000007fff0278 CR3=0000000100030000 CR4=00070668
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000d01
Code=8b 45 a8 48 8b 40 38 48 89 45 d8 fa 31 c0 89 c1 44 0f 22 c1 <b0> 01 a8 01 75 02 eb 29 48 63 bd 7c ff ff ff b8 00 01 00 00 e8 c0 0a 00 00 89 c1 89 4d fc

User avatar

volkerhalle
Master
Posts: 196
Joined: Fri Aug 14, 2020 11:31 am
Reputation: 0
Status: Offline

Re: QEMU/KVM-or-HVF crash in installer

Post by volkerhalle » Wed Apr 19, 2023 11:06 am

Adam,

you would normally see these messages immediately adjacent to each other:

...
%EXECINIT-I-HWCLOCK, reading the HW clock
%INITIODB-I-BEGIN, Executing INIT_IO_DB.
...

If you see the first message, but not the second, chances are high, that the problem happened when trying to read the HW clock.

Ask yourself: are you trying to boot OpenVMS E9.2-1 on a supported configuration ?

Is there anything you can configure differently in your QEMU/KVM-or-HVF regarding the clock ? Others have apparently been able to boot OpenVMS on 'similar' configurations, but I don't know anything about QEMU/KVM-or-HVF to give any hints.

Volker.


Topic author
adam
Contributor
Posts: 10
Joined: Wed Apr 19, 2023 2:46 am
Reputation: 0
Status: Offline

Re: QEMU/KVM-or-HVF crash in installer

Post by adam » Wed Apr 19, 2023 12:04 pm

The Macs are running QEMU 7.2.1, and Darwin kernel 22.4.0. That's probably not a supported configuration. Same behavior with "Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz".

It is not one of the tested configurations (I can reinstall the host with Ubuntu 22.04 LTS tonight or sometime), but the Linux box is Debian Bookworm, fully patched, with QEMU 7.2+dfsg5 and kernel 6.1.20-2.

vmscheck.py is happy with all of these. But it doesn't seem like a CPU problem exactly--it's something about whatever is happening when the clock is read.

EDIT: I tried adding -no-hpet to the qemu options, as suggested by viewtopic.php?f=37&t=8592&start=10 ; it did not help.

I can give this a shot with QEMU 6.2.0 later on.
Last edited by adam on Wed Apr 19, 2023 1:06 pm, edited 2 times in total.


Topic author
adam
Contributor
Posts: 10
Joined: Wed Apr 19, 2023 2:46 am
Reputation: 0
Status: Offline

Re: QEMU/KVM-or-HVF crash in installer

Post by adam » Thu Apr 20, 2023 2:28 am

Ubuntu 22.04-LTS plus the apt-supplied QEMU, on the other hand, worked just fine.


Topic author
adam
Contributor
Posts: 10
Joined: Wed Apr 19, 2023 2:46 am
Reputation: 0
Status: Offline

Re: QEMU/KVM-or-HVF crash in installer

Post by adam » Thu Apr 20, 2023 8:07 pm

Well, I should have suspected earlier, since it was the same no matter the hypervisor accelerator.

My OVMF.fd was bad, or at least not what QEMU expected.

If you're searching for an OVMF.fd you will likely find the kraxel.org jenkins server. Do not use this one. It works well enough to get the installer to come up, but when you try to read the clock VMS explodes.

Instead, use the OVMF.fd packaged with the Ubuntu package ovmf, which ends up in /usr/share/qemu/OVMF.fd .

The correct OVMF.fd file has the md5sum f14e1df68c1c7e9b6f0414d06781a95e

Post Reply