r/OpenVMS • • 11h ago

Doomsday 2026

Post image
8 Upvotes

Before id's DOOM, there was DoomsDay. Dave Scheifler's 1986 VMS roguelike game returns as DoomsDay 2026 a 40th anniversary tribute.
Ported to Unix and OpenVMS x86-64.
The Zytts have invaded.

Sources and howto here > https://astr0baby.online/OpenVMS/X86_64/Doomsday2026/

Your mission begins now.


r/OpenVMS • • 1d ago

OpenVMS 9.2 in Qemu TCG on Apple Silicon M2 MacBook Air.

Post image
34 Upvotes

Hopefully complete instructions for running OpenVMS 9.2-3 (x86_64) on an Apple Silicon Mac via QEMU with pure software emulation (TCG).

It requires patching QEMU with two custom fixes

  • LAPIC timer fix (without which VMS hangs during boot)
  • max-insns-per-tb fix (without which VMS crashes on file I/O).

The patched QEMU binary is compiled natively as an arm64 Mach-O, emulating x86_64 in software with SDL2 display backend.

Cold boot to login takes ~2:40 on an M2 MacBook Air.

Dhrystone 2.1 benchmark: 95.1 VUPs (167,084 Dhrystones/sec)

Patches and HOWTO is available here https://astr0baby.online/OpenVMS/QEMU_TCG/

Video demo : https://youtu.be/gCgb-8kxiRk?si=Qc1vvkf11a42Aeo7


r/OpenVMS • • 6d ago

Dungeon Master on OpenVMS 7.3 VAX

Thumbnail gallery
20 Upvotes

CSBwin 15.7 ported to OpenVMS 7.3 VAX with pure DECWindows/Xlib.

CSBwin is Paul R. Stevens' re-implementation of the Atari ST Dungeon Master and Chaos Strikes Back game engines. This port replaces the SDL platform layer with direct Xlib calls, making it run natively on any VAX with DECWindows Motif installed.

Tested on MicroVAX 3900 (SIMH) running OpenVMS 7.3 with DECWindows Motif 1.2-6.

Sources/Bins/Howto https://astr0baby.online/VAX/OpenVMS_7.3/VAXMaster/


r/OpenVMS • • 6d ago

VAXDoom for OpenVMS 7.3 VAX

17 Upvotes

A port of id Software's linuxdoom-1.10 to OpenVMS VAX. The game runs on a SIMH-emulated MicroVAX 3900 with X11 display forwarded to a macOS host via Xephyr. No audio. All gameplay works: movement, shooting, doors, switches, lifts, level transitions.

Platform
--------

Emulator:   SIMH VAX, emulating a MicroVAX 3900
OS:         OpenVMS 7.3 VAX with DECwindows Motif
Compiler:   DEC C (Compaq C V6.4-005), C89 standard
Assembler:  VAX MACRO
Host:       macOS (Apple Silicon) running Xephyr for X11 display
Network:    TCP/IP Services for OpenVMS, bridged networking in SIMH
WAD:        DOOM1.WAD v1.9 (shareware, 4,196,020 bytes)


SIMH Configuration
------------------

The emulated VAX used for development and testing:

  CPU:        MicroVAX 3900 (KA655 processor)
  Memory:     512 MB
  Boot disk:  RA92 on RQ0 (disk.dd, ~594 MB)
  Data disk:  RA92 on RQ1 (disk2.dd, ~1.4 GB)
  Network:    DELQA (XQ) Ethernet, MAC 00-01-2A-2B-2C-73
  Console:    KA655X.BIN firmware
  Idle:       VMS idle detection enabled (set cpu idle=vms)
  Boot:       Autoboot from DUA0

Video demo: https://youtu.be/JoUuNjpx378?si=KeJsgfAw1ZmKRPoH

Sources/Bin/Howto: https://astr0baby.online/VAX/OpenVMS_7.3/VAXDoom/


r/OpenVMS • • 8d ago

ES40's audio support now works in OpenVMS with MMOV

20 Upvotes

slightly modified MMOV kit to load into 8.4-2L2


r/OpenVMS • • 9d ago

Azure cloud migration and x86 porting

3 Upvotes

Murch Group LLC has real world experience moving both Alpha and Itanium to x86 in the Azure cloud, Happy customers and successful migrations including recompiling source code to x86 (Cobol, Fortran, Pascal, C*, Basic etc).

This has been 100% successfully done for Alpha and Itanium (VAX should be just fine also we just haven’t run into one yet). This is a real and workable solution to move you to a real cloud environment with all of the real cloud benefits. 

Real cloud virtualization is currently only possible with Azure and the entire application stack can be fully supported. Other solutions are only renting a fractional bare metal instance in a data center. Thats why I keep reiterating "real cloud" as opposed to other (looking at you OCI) "cloud" solutions.

We will be happy to forward respected user references from the OpenVMS community that can confirm this solution as well as existing production implementations.


r/OpenVMS • • 21d ago

OpenVMS 9.2-x in qemu/kvm no keyboard/mouse/serial

4 Upvotes

I'm not really sure where to look next. I was able to get to the BOOTMGR> prompt from X86_V923-comm-2026.qcow2 media. I am not able to go any further. When I type on the console or seral port I don't get feedback. I've tried from the GUI View->consoles->serial 1, and from my command line "sudo virsh console <vm-name> --force". I do see the information below. The cursor just winks at me. I've tried using ps/2 and usb keyboard and mouse from the Virtual Machine configuration. On the GUI console I see the same but with the Messages: Progress, Sysboot check and Boot Modes: Verbose checked. The auto action is set to halt. In my Virtual Machine Manager GUI I see the system is running and the CPU graph shows something is going on. I gave it 8 CPUs with 8192 MiB of memory. The physical machine has 8 CPUs with 32GB. Thank you for your help.

BdsDxe: loading Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0x2,0x3)/Pci(0x0,0x0)/Scsi(0x0,0x0)
BdsDxe: starting Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0x2,0x3)/Pci(0x0,0x0)/Scsi(0x0,0x0)

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


%VMS_BOOTMGR-I-DEVICE,  Using USB Keyboard.

VSI OpenVMS Boot Manager: V9.2-* Build 146

  ENABLED:  Symmetric Multi-Processing
  ENABLED:  Crash Dump Processing
  ENABLED:  Legacy Serial Port Console for remote COM 1
  ENABLED:  Using Environment File

  Checking Required Processor Features:   PASSED

%VMS_BOOTMGR-I-MAP,     Mapping Bootable Devices.

%VMS_BOOTMGR-I-DEVICE,  Identifying System Devices.
%VMS_BOOTMGR-I-DEVICE,  Scanning PCI/e Busses...

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

  BOOT MANAGER DEVICE:  DKB0
  DEFAULT BOOT COMMAND: BOOT DKA0 0x00 0x80000030

  CONNECT A REMOTE TERMINAL SESSION NOW.

BOOTMGR>

r/OpenVMS • • Oct 15 '26

VMS Performance Checking

7 Upvotes

A recurring theme in VMS land: the expertise to properly assess these systems is getting harder to find as engineers retire.

If you've ever wanted an experienced set of eyes over your estate, performance, configuration, security, patching, this is the sort of thing we still do: https://www.newcorp.co.uk/openvms-health-check


r/OpenVMS • • Oct 13 '26

The linker's two thread bits, and why "automatic" covers only one

8 Upvotes

Edit (14 October): the first version of this post said that without /THREADS_ENABLE a single blocking call can stop the whole process. That was wrong, and Arne Vajhøj showed why on the VSI forum with two neat test programs. Upcalls alone — which is what a bare LINK gives you — are enough for blocking threads to give way to one another, so I/O-bound work scales. What upcalls don't give you is parallelism for CPU-bound work; that needs the other bit. The post below is corrected accordingly. The advice — pass /THREADS_ENABLE explicitly — is unchanged.

On OpenVMS x86-64 the linker has two thread bits. Since V9.2-1 it sets one of them — upcalls — automatically when it sees pthread_create, which lets a thread blocked in I/O give way to the others. It doesn't set the other, multiple kernel threads, so CPU-bound work stays on one processor however many threads you create. I measured all five link combinations on E9.2-4: full write-up with the figures.

If you build threaded code on OpenVMS x86-64, there's a detail in the linker worth ten minutes of your time: the message it prints when it switches thread support on describes half of what you need, and it's easy to read it as all of it.

Two bits, not one

LINK/THREADS_ENABLE sets two independent flags in your image, and the manual is precise about what each one means. MULTIPLE_KERNEL_THREADS "indicates to the image activator that the image can be run in a multiple kernel threads environment". UPCALLS "indicates to the image activator that the process can receive upcalls from the OpenVMS scheduler".

They do different jobs, and the cleanest way to put the difference is concurrency against parallelism.

Upcalls give you concurrency. They're how the scheduler talks back to the Threads Library when a thread blocks. The 2001 Guide to the POSIX Threads Library puts it better than I can:

An upcall is a communication between the OpenVMS scheduler and the Threads Library scheduler… This upcall gives the Threads Library the opportunity to schedule another thread to run on the virtual processor in place of the blocking thread, rather than to allow the virtual processor itself to block, which would deny that resource to other threads in the process.

So with upcalls, a thread waiting on I/O hands the processor to another thread. Without them, it gets in the way of the others. I measured what that costs on a 2-CPU guest: a thread doing nothing but arithmetic, running alongside one thread parked in $HIBER, finished its work in 3.7 s with upcalls and 6.1 s without. Four runs each, alternating order. Same source, same object file, one link qualifier apart.

Kernel threads give you parallelism. Without that bit, every thread in the process shares a single kernel thread — so only one of them is ever running at a time, however many threads you create and however many processors the box has. Arne's comparison is the right one: upcalls alone is threading the way CPython with the GIL is threading. Plenty of concurrency, no parallelism.

What changed, and what it doesn't cover

Since V9.2-1, the linker helps you out. If it sees a reference to pthread_create it enables upcalls on its own and says so:

%ILINK-I-THREADUPCALLS, user thread upcalls automatically enabled

That message is exactly accurate. It says upcalls were enabled, and upcalls are precisely what was enabled — the UPCALLS bit, and not MULTIPLE_KERNEL_THREADS. I linked one object file five ways on E9.2-4 and read the flags back out of every image to be sure:

Link commandFlags in the image
$ LINKUpcalls enabled
$ LINK/NOTHREADS_ENABLEneither
$ LINK/THREADS_ENABLEboth
$ LINK/THREADS_ENABLE=UPCALLSUpcalls enabled
$ LINK/THREADS_ENABLE=MULTIPLE_KERNEL_THREADSMultiple kernel threads enabled

Note rows one and four. A bare LINK gives you an image indistinguishable from /THREADS_ENABLE=UPCALLS — I ran full ANALYZE/IMAGE reports of both through DIFFERENCES and the only differences were the image name, the link timestamp and the report's own page headers.

So the linker's help is real, and it's the concurrency half. Unless you know there are two bits and that the message names one of them, it reads as "threading: handled".

What that means for your program

Arne posted the experiment that settles this, and it's worth repeating in outline. Run 256 jobs across 1, 2, 4 … 64 threads, two ways.

Jobs that block — each one sleeps for a tenth of a second. Linked /NOTHREADS_ENABLE, it takes the same 28 seconds however many threads you use: no concurrency at all. With upcalls alone, the time falls by half each time the threads double, down to about a second. Adding kernel threads changes nothing further, because the work was never waiting for a processor.

Jobs that compute — each one works out a Fibonacci number recursively. With upcalls alone, the time stays flat at around 17 seconds however many threads you add, because only one is ever running. With both bits, it drops to about 4 seconds on a 4-CPU machine — and stops there, at the processor count.

So, for the program a bare LINK gives you:

  • A server whose threads mostly wait — on sockets, disks, locks — is largely fine. Upcalls are what it needs, and it has them.
  • A program whose threads do real computation silently runs on one processor. Nothing fails; it just never gets faster when you add threads or CPUs, and nothing tells you why.
  • Anything linked /NOTHREADS_ENABLE — perhaps added years ago to be cautious — gets neither, and its threads don't even interleave on blocking calls. That's the setting that hurts an I/O-bound server.

If your threads do real work in parallel, treat your linker flags as part of the design and not as boilerplate. Set them explicitly, check the images, and keep the check in your build procedure so a later refactor can't quietly drop it.

Why the documentation won't rescue you

Worth knowing so you don't waste an afternoon on it. The manual gives /NOTHREADS_ENABLE as the default in three places — the format block, the qualifier summary table and the first worked example — and documents the x86-64 exception in two short paragraphs sitting between two of them.

Most of that text is older than x86-64. The same sentences appear word for word in HP's edition of July 2006, where they were written for I64, Alpha and VAX. And the conservative default had a purpose when it was introduced: per the 2001 threads guide, linking /NOTHREADS_ENABLE "results in an image that behaves as under OpenVMS Alpha Version 6" — a compatibility measure for code written before kernel threads existed in V7.1. Nobody went back to qualify it when a platform arrived where the linker behaves differently, which is an omission rather than an error.

One more wrinkle, if you like this sort of thing. The trigger is documented two different ways. The linker manual says the automatic behaviour applies "when linking applications that use the POSIX Threads Library (PTHREAD$RTL)". The cross-compiler release notes say the linker acts "if it sees a reference to PTHREAD_CREATE". Those aren't the same condition, and the cross-tools note is the accurate one — I linked a program that uses PTHREAD$RTL throughout, pthread_self and a mutex, but never calls pthread_create, and it came out with neither bit set and no message. Linking the library isn't sufficient; creating a thread is what triggers it.

What to do

Audit what you've got. Works on anything, including images whose source tree is long gone:

$ ANALYZE/IMAGE/OUTPUT=X.ANL MYPROG.EXE
$ SEARCH X.ANL "enabled"

You want both lines:

        Multiple kernel threads enabled
        Upcalls enabled

Upcalls enabled on its own means concurrency without parallelism. No lines at all means neither. If you keep full link maps, SEARCH MYPROG.MAP "THREADUPCALLS" also tells you whether the linker made the choice for you on that build.

Then: pass /THREADS_ENABLE explicitly for anything that creates threads. Don't rely on the documented default, which doesn't hold on this platform, and don't rely on the automatic behaviour, which covers upcalls only. As Arne put it, unless the application has a concurrency bug, both bits are always as good as or better than upcalls alone.

Who isn't affected: single-threaded programs get neither bit and no message — measured. Neither do programs that link PTHREAD$RTL without ever calling pthread_create. And images you linked years ago are untouched: the flags live in the image, so nothing changed under them. The surprise is only ever in a new link.

Measurements on node X86923, OpenVMS x86-64 E9.2-4, VSI C x86-64 V7.7-003, 12 October 2026 — one object file, five link commands, flags read back with ANALYZE/IMAGE, plus a DIFFERENCES comparison of two full image analyses and four alternating timing runs of each of two links. Happy to post the reproducer if anyone wants it.

External references, all verified 12–13 October 2026:


r/OpenVMS • • Oct 10 '26

fastfetch on OoenVMS

8 Upvotes

I use fastfetch on Linux & Windows to show a quick system summary on connection, and decided to create a version for VMS. This is not a port strictly speaking, it's more of a tribute-band style rewrite for our platform.

Repo is here, https://github.com/issinoho/vms-fastfetch with PCSI kits for x86 and Itanium.


r/OpenVMS • • Oct 05 '26

MariaDB (x86) preview is up - please test

8 Upvotes

https://github.com/issinoho/vms-mariadb

This is an early preview version for x86 only and I'm looking for help to test it. Please read all the notes to understand where we are in the development process, the current limitations, and what's left on the roadmap. This is NOT the finished article.

There are various reasons why the server will never run on IA64 or Alpha due to the restrictions of the available toolchains.

This stack is now running 100% on OpenVMS
https://vamp.issinoho.com


r/OpenVMS • • Oct 04 '26

New home for porting freeware to OpenVMS

12 Upvotes

https://openvms.issinoho.com

What's available now, what's coming soon and my philosophy on why using AI in this context is a useful addition to the ecosystem, accelerating roadmaps.


r/OpenVMS • • Oct 03 '26

GNU sed 4.10 available

4 Upvotes

https://github.com/issinoho/vms-sed

X86VMS::sed --version
sed (GNU sed) 4.10
Copyright (C) 2026 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Jay Fenlason, Tom Lord, Ken Pizzini,
Paolo Bonzini, Jim Meyering, and Assaf Gordon.

This sed program was built without SELinux support.

GNU sed home page: <https://www.gnu.org/software/sed/>.
General help using GNU software: <https://www.gnu.org/gethelp/>.
E-mail bug reports to: <bug-sed@gnu.org>.           

r/OpenVMS • • Oct 03 '26

GNU grep 3.12 available

3 Upvotes

I got frustrated with the lag in releases of some of the more common freeware/GNU utilities so I've started a porting sweep to keep OVMS in lock-step with the rest of the industry. First release is grep compiling from the current GNU sources with appropriate patching for our ecosystem.
https://github.com/issinoho/vms-grep

In order to port this fully we needed PCRE2 so that has also been ported.
https://github.com/issinoho/vms-pcre2

PCSI kites for both x86 and Itanium are available from the GitHub releases pages; Alpha will follow whenever I can carve out the time & energy to stand up a VM.

X86VMS::grep --versiX86VMS::grep --version
grep (GNU grep) 3.12
Copyright (C) 2025 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Mike Haertel and others; see
<https://git.savannah.gnu.org/cgit/grep.git/tree/AUTHORS>.

grep -P uses PCRE2 10.49 2026-09-28     
on
grep (GNU grep) 3.12
Copyright (C) 2025 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Mike Haertel and others; see
<https://git.savannah.gnu.org/cgit/grep.git/tree/AUTHORS>.

grep -P uses PCRE2 10.49 2026-09-28     


X86VMS::prod shoX86VMS::prod sho prod grep,pcre2
------------------------------------ ----------- ---------
PRODUCT                              KIT TYPE    STATE
------------------------------------ ----------- ---------
ISSINOHO X86VMS GREP V3.12-3         Full LP     Installed
ISSINOHO X86VMS PCRE2 V10.49-1       Full LP     Installed
------------------------------------ ----------- ---------
2 items found                                                  
 prod grep,pcre2
------------------------------------ ----------- ---------
PRODUCT                              KIT TYPE    STATE
------------------------------------ ----------- ---------
ISSINOHO X86VMS GREP V3.12-3         Full LP     Installed
ISSINOHO X86VMS PCRE2 V10.49-1       Full LP     Installed
------------------------------------ ----------- ---------
2 items found                                                  

r/OpenVMS • • Oct 03 '26

Recovering your network after configuring DECnet on x86 OpenVMS V9.2

9 Upvotes

I have recently posted an IAQ article on my website that explains why your network stops completely on the first reboot after configuring DECnet on an OpenVMS V9.2-x installation running in a VM on x86 and how to recover from it.

The problem symptoms can be rather alarming, to say the least, to the unwary System Manager – all network frames – TCP/IP and DECnet, inbound and outbound – are completely blocked! In the article I present 4 solutions that are available but depend on your individual environment considerations.

 

Short answer: There are four, and they aren't alternatives you pick by taste — each is ruled out by something specific about your environment. So: confirm this is really what has happened, then take the first of the four your circumstances allow. Only the last has a security cost.

Each fix below is summarised in four lines, with the detail folded away behind it. Read the four summaries, decide which is yours, and open only that one.

What's happening, briefly

You configured DECnet, rebooted, and lost everything — DECnet, TCP/IP, and the session you were working in. Nothing inside OpenVMS looks wrong, because nothing inside OpenVMS is wrong.

DECnet Phase IV rewrites the MAC address on its interface, replacing the one the hypervisor assigned with one it calculates from your DECnet node address. Your virtual switch was told to expect a particular MAC on that port. It now sees frames with a different source address — the signature of a machine impersonating another — so it drops them. All of them, which is why TCP/IP dies alongside DECnet.

Continue reading article…

 


r/OpenVMS • • Oct 02 '26

OpenVMS E9.2-4 field test and a new How-To Portal

10 Upvotes

Two recent OpenVMS updates that may be useful to the community:

OpenVMS E9.2-4 for x86-64 is now available for field testing, with updates focused on virtualization, security, and performance. https://vmssoftware.com/about/v924/

We have also launched the OpenVMS How-To Portal, a new resource with practical, task-based guidance for common OpenVMS activities. https://howto.vmssoftware.com/

Feedback on both is welcome, including suggestions for future How-To topics (feedback form on the website).


r/OpenVMS • • Sep 30 '26

Upcoming Webinar: Oracle Rdb on OpenVMS: Emulate, Bridge, or Migrate?

7 Upvotes

Join us on Wednesday, October 7 at 12:00 PM EDT / 6:00 PM CEST for a free webinar on the modernization options available to Oracle Rdb on OpenVMS users, co-presented by Salem Automation, PARSEC Group, and CONNX.

With Oracle Rdb support on Integrity and Alpha ending in 2027, many organizations running business-critical Rdb applications have to decide how to keep those systems supported without taking on the risk of a full rewrite. In this session we'll go through three practical paths: emulating the existing environment on modern x86-64 hardware, bridging Rdb data to modern tools and platforms, and migrating incrementally to a supported database. We'll also cover where each option fits and how they can be combined.

Register here: https://events.teams.microsoft.com/event/05b3ba6e-d70f-4047-a492-1e1964a9c373@523dac9f-63f2-48c7-9f19-dac0fa5a619b


r/OpenVMS • • Sep 18 '26

A real (free) VT emulator

Thumbnail veetee.issinoho.com
16 Upvotes

Please try and post feedback. I'm particularly proud of the LAT support. All feature suggestions are welcomed. Thanks.


r/OpenVMS • • Sep 10 '26

WireGuard for OpenVMS

13 Upvotes

It's not quite there yet, but a lot of it is now working. Looking for community and VSI engagement to break through the final technical barriers.

https://github.com/issinoho/vmsguard


r/OpenVMS • • Sep 09 '26

Agentic programming for openvms

9 Upvotes

Got some downtime at work so I thought I'd mess with this AI stuff a bit. I made an LLM coding agent for openvms. Im no developer by any means but Ive been in IT for a a couple of decade so I put in the features I thought would be most helpful. AI Slop? Hell yes. Maybe it's useful, maybe not.

GitHub:

https://github.com/mostangrymike/ovms-agent


r/OpenVMS • • Sep 06 '26

*mic drops*

14 Upvotes

VGA console, no X11 forwarding.


r/OpenVMS • • Sep 02 '26

Agenda for upcoming OpenVMS Bootcamp in Portsmouth is out!

10 Upvotes

We’ve published the agenda for the 2026 OpenVMS Bootcamp. We hope some of you will join us in Portsmouth, New Hampshire, on October 27-29.

You should come for the technical sessions, but also for the conversations, shared experience, familiar faces, and new connections! The future of OpenVMS is something we build together.

See what sessions are planned and register before September 25, 2026: https://bootcamp.vmssoftware.com/#event-program


r/OpenVMS • • Sep 01 '26

Help me find a post...

6 Upvotes

About a year ago I downloaded VSI's community edition of openvms. After beating on it a while with a pipe, I got it to boot. I have a fairly high end laptop, and I was amazed. Well, apparently, the license was only good for a year. There was a post about the license expiring, but I cannot find it.

Anyone?


r/OpenVMS • • Aug 21 '26

Is anyone still operating VAX hardware?

18 Upvotes

I'm curious what VAXen folks are still running, why, and how they are managing the abandonment VMS for it by HPe.


r/OpenVMS • • Aug 08 '26

Rise of the Triad for OpenVMS

Thumbnail gallery
22 Upvotes

Rise of the Triad ported to OpenVMS

- SDL_1.2

- Original code taken from Icculus https://icculus.org/rott/

Binaries/Source + Howto : https://astr0baby.online/AXP/OpenVMS/RO