Booting on Proxmox

[compctech]

I am new to OpenVMS and trying to get it to boot. This is as far as I get:

Code: Select all

BdsDxe: loading Boot0001 "UEFI QEMU HARDDISK QM00013 " from PciRoot(0x0)/Pci(0x1E,0x0)/Pci(0x1,0x0)/Pci(0x7,0x0)/Sata(0x0,0xFFFF,0x0)
BdsDxe: starting Boot0001 "UEFI QEMU HARDDISK QM00013 " from PciRoot(0x0)/Pci(0x1E,0x0)/Pci(0x1,0x0)/Pci(0x7,0x0)/Sata(0x0,0xFFFF,0x0)

Scanning devices and preparing the OpenVMS Boot Manager Build 136...

VSI OpenVMS Boot Manager: V9.2-x Build 136

  ENABLED:  Symmetric Multi-Processing
  ENABLED:  Crash Dump Processing
  ENABLED:  Console output to Legacy COM 1 Port
  ENABLED:  Using Environment ROM

  Checking Required Processor Features:
  PASSED

  BOOT MANAGER DEVICE:  DKA0
  DEFAULT BOOT COMMAND: BOOT DKA0 0x00 0x00000000

  VIRTUAL MACHINE GUEST:
  KVM (tm) No Mouse support; Use Command or Arrow Keys


  CONNECT A REMOTE TERMINAL SESSION NOW.

BOOTMGR> BOOT DKA0
Booting...

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


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


_______________________________________________

      GRAPHICAL OUTPUT HAS BEEN SUSPENDED
      USE A TERMINAL UTILITY FOR ACCESS
_______________________________________________

VSI Primary Kernel SYSBOOT Nov  9 2023 12:17:04

%SYSBOOT-I-VMTYPE, Booting as a KVM (tm) Guest


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

  MDS Mitigation active, variant verw(MD_CLEAR)
%DECnet-I-LOADED, network base image loaded, version = 05.92.05

%DECnet-W-ZEROLEN, length of file is zero -- SYS$SYSROOT:[SYSEXE]NET$CONFIG.DAT

%SMP-I-CPUTRN, CPU #1 has joined the active set.

It only gets to activating CPU#1 and stops. Stats show that the CPU usage goes to 100%, but I am not seeing any disk activity. I did convert the image from vmdk to raw. The RAM usage is only at 610MB.

This is my config of my VM:
acpi: 1
bios: ovmf
boot: order=sata0
cores: 2
cpu: host
efidisk0: local:101/vm-101-disk-2.raw,efitype=4m,size=528K
machine: q35
memory: 8000
meta: creation-qemu=9.0.2,ctime=1733714353
name: OpenVMS
net0: e1000=02:00:00:b4:15:d9,bridge=vmbr0,firewall=1
numa: 0
ostype: other
sata0: local:101/vm-101-disk-0.raw,size=5G
sata1: local:101/vm-101-disk-1.raw,size=32G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=571e3c91-4d56-4bf4-b3a9-d9ec7b8c4345
sockets: 1
tablet: 0
vmgenid: b09d20cf-5c4f-4bf5-9e7f-03406a25d076

Thanks in advanced for any assistance.

--
Sam L.

Added in 43 seconds:
wow, was working on this to long. Just learned that I needed to just add "args: -machine hpet=off" to the config file.

I guess that this is good post for others that see the same issue.

--
Sam L.

Added in 18 seconds:
wow, was working on this to long. Just learned that I needed to just add "args: -machine hpet=off" to the config file.

I guess that this is good post for others that see the same issue.

--
Sam L.

[reinhardtjh]

Yes, the "args: -machine hpet=off" is required for OpenVMS to boot correctly. It's buried in several thread here but you have to be lucky enough to find it. Searching for ProxMox usually does.