Virtualization vs refurbished Alpha systems

Alpha systems that run in the factories and offices are old now. Many of them are used for critical tasks. The risk of failure increases with the flow of time. The support and maintenance are expensive. There are the following main ways to solve the problem:

  • Migrate to a virtual Alpha system using virtualization software like AlphaVM
  • Purchase a refurbished Alpha system to replace the existing Alpha system.
  • Port the applications software to run on modern hardware and supported operating system (Windows, Linux).
  • Write the software for modern hardware and OS from scratch.

AlphaVM is a virtual Alpha

Our product AlphaVM can be used to create a virtual Alpha system(s) running on your Intel Xeon based host system. It allows to get rid of aging Alpha AXP based hardware. AlphaVM is a virtualization solution for DEC/Compaq/HP Alpha AXP systems. The AlphaVM solution is based on an Alpha system emulator. AlphaVM emulates a whole Alpha system. It emulates the CPU, the motherboard core logic chipset, the SCSI controllers, the disks, the tapes, the Ethernet controllers.


Using COM3 and COM4 in Tru64

Usually an Alpha system has one or two serial ports. The first port is often used as a serial console. AlphaVM currently supports only serial console. Thus, there is only one serial port left for other purposes. Often it is desired to have more serial lines. Therefore, since the 1.6 release our implementation supports additional COM3 and COM4. The guest OS (OpenVMS or Tru64) has to be configured to use these additional ports. The serial drivers have to be loaded.

The additional serial lines are serial ISA devices, the same as COM1 and COM2. Our implementation registers the devices in the ISA configuration table. When a serial driver is loaded, it uses the information from the ISA configuration table.

Below are the instructions.

  • Edit the kernel configuration /sys/conf/EMU. Add the new serial lines after ace0 and ace1.
controller ace2 at isa0 slot 2 vector aceintr
controller ace3 at isa0 slot 3 vector aceintr

  • Rebuild and copy the kernel.
# doconfig -c EMU
# cp /vmunix /vmunix.saved
# cp /sys/EMU/vmunix /vmunix
  • Create the device nodes.
# cd /dev
# ./MAKEDEV ace2 ace3
MAKEDEV: special file(s) for ace2:
MAKEDEV: special file(s) for ace3:
  • Optionally, enable the tty02 and tty03 for logging in. Add the following lines to /etc/inittab
tty02:23:respawn:/usr/sbin/getty /dev/tty02 9600 vt100
tty03:23:respawn:/usr/sbin/getty /dev/tty03 9600 vt100
  • Optionally, enable root login. Add /dev/tty02 and /dev/tty03 to /etc/securettys.
  • You may also need to edit /etc/remote. For instance, add

10 years since starting the development of AlphaVM

10 years ago we started the development of AlphaVM. Several month later the first build of AlphaVM was released (AlphaVM-Free 1.0.5).

Now AlphaVM is a mature and stable product that has hundreds of installations worldwide. Many of them run in 24/7 mode.

For most workloads AlphaVM performance can match any existing Alpha system on modern and fast Xeon based hardware.