OpenVMS V9.2-2

OpenVMS V9.2-2 for x86 now available!

Evaluation License
Welcome to OpenVMS (TM) x86_64 Operating System, Version V9.2-2

VSI OpenVMS V9.2-2 for x86-64 is now available as part of our ongoing development of the port to the industry-standard CPU architecture.

VMS Software, Inc. has migrated OpenVMS and its layered products to the industry standard x86-64 architecture to help customers protect their investment in OpenVMS infrastructure, especially in virtualized environments and in the cloud. This commercial release of OpenVMS V9.2-2 is available for porting development and production use on x86-64. Its main focus is on addressing issues found since V9.2-1. It also includes updates for several layered and open-source products, such as SSL, OpenSSH, and TCP/IP, provided as part of the default installation.

For hypervisors on which OpenVMS has been tested by VSI, please scroll down to the bottom of the page. To determine if the CPU in your system provides the features required to run OpenVMS V9.2 or later, run this Python script. Information on the virtual machine hosts tested by VSI is provided below and in the release notes. Depending on your source language and the availability of native compilers, you can compile your code using OpenVMS I64-hosted cross-compilers or natively on OpenVMS x86.

Check lists of open-source and layered products that work with OpenVMS here (filter by architecture to see those available on x86).

CPU Requirements

  • Intel or AMD x86 CPU
  • 64-bit Instruction set
  • NX processor bit (NX)
  • Streaming SIMD Extensions 4.1 (SSE4.1)
  • Virtualization Technology (VT-x/AMD-V)
  • XSAVE instructions
  • Time Stamp Counter (TSC)
  • Advanced Programmable Interrupt Controller (APIC)
  • Memory Type Range Registers (MTRR)

Most Intel CPUs from 2016/AMD (Zen) CPUs from 2017 and later support these processor features.

Optional Features:

  • Process-Context Identifier feature (PCID)
  • Extended Advanced Programmable Interrupt Controller (x2APIC)
  • XSAVEOPT instruction
  • FSGSBASE instructions
  • Microarchitectural Data Sampling Mitigation (MD_CLEAR)

Tested Platforms

For more about compatibility issues, refer to the Release Notes.

Virtual Machines Tested:

KVMExternal Link
  • openSUSE Leap 15.4 (SUSE Linux Enterprise 15); QEMU emulator version 6.2.0
  • Rocky Linux 8.6; QEMU emulator version 6.2.0 (qemu-kvm-6.2.0-11.module+el8.6.0+1052+ff61d164.6)
  • Rocky Linux 8.7; QEMU emulator version 6.2.0 (qemu-kvm-6.2.0-32.module+el8.8.0+1279+230c2115)
  • Rocky Linux 9.1; QEMU emulator version 7.0.0-13
  • Ubuntu 22.04 LTS; QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.5)
  • Oracle Linux 8.8; QEMU emulator version 4.2.1 (qemu-kvm-4.2.1-26)
VMwareExternal Link*
  • Workstation Pro V16.2.x, V17.0.x
  • Workstation Player V17.0.x
  • Fusion Pro V13.0.x
  • Fusion Player V12.2.x
  • ESXi V6.7.x, V7.0.x, V8.0.x (with compatibility of 8, 7U2, 7U1, 6.7U2)
  • vSphere Client 8.0.x
Oracle VM VirtualBoxExternal Link
  • VirtualBox 6.1.x, 7.0.x

For a list of Windows settings required to run OpenVMS as a VM guest on VirtualBox installed on a Windows host system, visit our wiki.

* Warning!If you choose to upgrade from a previous version of VMware Fusion to VMware Fusion 13, from a previous version of VMware Workstation to VMware Workstation 17, or from a previous version of VMware ESXi to VMware ESXi 8, you will not be able to run any VMs with VSI OpenVMS x86-64 versions prior to V9.2-2. However, VMs running VSI OpenVMS x86-64 V9.2 can be upgraded to VSI OpenVMS x86-64 V9.2-1, which will run under VMware Fusion 13/VMware Workstation 17/VMware ESXi 8. In turn, VSI OpenVMS x86-64 V9.2-1 can then be upgraded to the current version, VSI OpenVMS x86-64 V9.

Note: VSI does not impose any limitations on any virtual machines running OpenVMS with respect to the number of SCSI or SAS storage controllers. Please refer to the appropriate hypervisor configuration guidelines for information on SCSI and SAS storage controller configuration limitations.

For the previous release info, refer to this page.


Check out our x86 Port Q&A or contact us.