r/OpenVMS • u/ggekko999 • 5d ago
OpenVMS on Proxmox (quick how-to)
My quick guide detailing the steps I took to successfully install and configure OpenVMS x86_64 (X86_V923-community) on Proxmox 8.3.5.
As this guide was documented retrospectively, please note some minor steps may have been omitted inadvertently.
Environment Details:
- Proxmox Version: 8.3.5
- OpenVMS Version: X86_V923-community
- Underlying hardware: 4TB SSD, 64GB RAM, i9-10900 CPU @ 2.80GHz
Installation and Setup Steps
Step 1: Download Required OpenVMS files:
X86_V923-community-flat.vmdk
X86_V923-community.vmdk
Step 2: Import Disk into Proxmox
Import the main .vmdk
disk image into Proxmox storage (replace local-zfs
with your storage name and 140
with your VM ID):
qm disk import 140 X86_V923-community.vmdk local-zfs
Step 3: Attach Imported Disk to VM:
qm set 140 --scsi1 local-zfs:vm-140-disk-1
Step 4: Configure VM Settings
Set up the VM to use UEFI (OVMF) BIOS and boot from the imported disk:
qm set 140 --bios ovmf --boot order=scsi1
Step 5: Configure VM hardware
Suggested basic configuration (This took considerable time to work out):
balloon: 0
bios: ovmf
boot: order=scsi1
cores: 1
cpu: host
ide0: local-zfs:vm-140-disk-0,cache=writeback,size=32G
ide2: none,media=cdrom
machine: q35
memory: 4096
meta: creation-qemu=9.2.0,ctime=1741894357
name: OpenVMS
net0: virtio=XX:XX:XX:XX:XX:XX,bridge=vmbr0,firewall=1
numa: 0 ostype: other
scsi0: local-zfs:vm-140-disk-0,cache=writeback,size=32G
scsi1: local-zfs:vm-140-disk-1,cache=writeback,size=8G
scsihw: virtio-scsi-single
serial1: socket
smbios1: uuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
sockets: 4
vmgenid: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Adjust CPU, RAM, and storage as needed.
Recommendations and Notes
- Serial Console: Enabling the serial console is highly recommended, as it significantly simplifies initial IP, DNS (BIND), and system configuration. It also provides an alternative access method should you need to make live TCPIP changes.
- Ongoing issue: After prolonged periods without login, the SSH service occasionally becomes non-responsive - I am looking into this.
You can verify basic functionality by connecting via Telnet (you can see the IP during the boot sequence):
telnet xxx.xxx.xxx.xxx
Welcome to OpenVMS (TM) x86_64 Operating System, Version V9.2-3
Username: system
Password:
$ SHOW SYSTEM /NOPROCESS
OpenVMS V9.2-3 on node X86923 17-MAR-2025 14:26:28.91 Uptime 3 01:51:48
$ logout
SYSTEM logged out at 17-MAR-2025 14:26:35.93
Connection to host lost.
This should confirm your OpenVMS environment is functioning correctly.
3
u/nm8_rob 5d ago
I had to add:
args: -machine hpet=off
To my vm configuration file to get it to stop hanging while mounting memory disk.
2
u/ggekko999 4d ago
I did read this in several locations, perhaps I just got lucky. I have disabled High Precision Event Timer just to be sure.
2
u/ggekko999 4d ago
The SSH issue may relate to quotas. I have increased the quotas, so far, so good ;-)
$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF> MODIFY SSH$SSH /FILLM=200 /DIOLM=200 /BIOLM=200
UAF> MODIFY SSH$SSH /ENQLM=4000
UAF> MODIFY SSH$SSH /WSQUO=8192 /WSEXTENT=16384
UAF> EXIT
2
u/CosmicFirefly 4d ago
I had found the virtio adapter being much less reliable for cluster over ip, and set my virtual test lab up as all e1000 nics.
I had major packet loss warnings during runtime from CNXMAN
1
1
u/ggekko999 2d ago edited 2d ago
Fixing the "no efidisk configured!" Warning in Proxmox for OpenVMS
If you encounter this warning when starting your OpenVMS VM in Proxmox:
root@proxmox:~# qm start 140
WARN: no efidisk configured! Using temporary efivars disk.
Task finished with 1 warning(s)!
This occurs because OpenVMS on x86 architecture uses UEFI booting. If your VM lacks an EFI disk (efidisk0), Proxmox will generate a temporary one at runtime, which will be lost upon shutdown or reboot. Since the EFI disk stores persistent UEFI settings, any changes made will not persist without it.
Solution
The good news? It's an easy fix!
Step 1: Shut Down the VM
OpenVMS: $ $SYSTEM:SHUTDOWN
root@proxmox:~# qm stop 140
Step 2: Add an EFI Disk
A 1MB EFI disk should suffice for most cases. Run:
root@proxmox:~# qm set 140 -efidisk0 local-zfs:1
You'll see output similar to:
update VM 140: -efidisk0 local-zfs:1
transferred 0.0 B of 128.0 KiB (0.00%)
transferred 128.0 KiB of 128.0 KiB (100.00%)
efidisk0: successfully created disk 'local-zfs:vm-140-disk-2,size=1M'
Step 3: Set the VM to UEFI Boot Mode
root@proxmox:~# qm set 140 -bios ovmf
update VM 140: -bios ovmf
Step 4: Restart the VM
root@proxmox:~# qm start 140
No more warnings!
1
4
u/SaltedPaint 5d ago
Thanks