AlphaVM on VMware

This article shows how to run AlphaVM on VMware. Here we assume the following software versions and emulated Alpha parameters:

The idea of this artcile can also be applied to other versions of VMware, Windows and AlphaVM and other Alpha configurations, although the details may differ.

The idea is also the same when Linux or FreeBSD are used instead of Windows. The major difference is that there is no AlphaVM GUI. AlphaVM is configured by editing the configuration file.

VMware virtual machine creation and configuration

  1. Create a new virtual machine. Assume it is called WS2012R2.
  2. Create a single disk. We set 50GB.
  3. Create 2 E1000 NICs.

    • The first NIC will be used for communication between Windows and the outer world. For instance, you will download AlphaVM software via this network.
    • The second NIC will be used by the AlphaVM NIC. We call it a dedicated NIC, because it will be used only by AlphaVM.

      If you need more NICs in your virtual Alpha, create a VMware NIC for each Alpha NIC.

      On ESXi the NIC does not pass Ethernet packets targeted to a MAC address different from the NIC's MAC address. This is the reason why NIC sharing does not work with ESXi and why a dedicated NIC is required for each emulated NIC.

  4. If you need to use DECNET, set the second NIC MAC address to the desired DECNET MAC address (AA-00-04-00-02-04). Otherwise, leave the MAC address at the default value provided by VMware.

    DECNET changes the MAC address to something that corresponds to the DECNET address. In our example the DECNET address is 1.2 and the corresponding MAC is AA-00-04-00-02-04. Assume the original VMware NIC MAC is 00-0C-29-9A-7B-28. There is a problem when DECNET changes the address from 00-0C-29-9A-7B-28 to AA-00-04-00-02-04. VMware NIC would not deliver packets to the new MAC address AA-00-04-00-02-04, because it delivers only to 00-0C-29-9A-7B-28. The problem can be solved by setting the VMware NIC MAC address to AA-00-04-00-02-04, which means that the address would not change. It is always and everywhere the same AA-00-04-00-02-04: in VMware, Windows, AlphaVM and VMS.

  5. Configure 2 CPU cores.
  6. Configure the memory size. We set 3Gb.
  7. Install Windows on the VMware virtual machine.

Windows configuration

Windows will have two NICs, one for each VMware NIC.

AlphaVM configuration

  1. Install AlphaVM.
  2. Configure the system type to DS10 6/466.
  3. For AlphaVM-Pro you may wish to set the CPU server fro basic to JIT2. AlphaVM-Free supports only the basic server.
  4. Set Alpha memory size. We assume 512MB here.
  5. Create SCSI controller.
  6. Create a disk. Set the disk image to whatever image you will to use. If you need an empty disk, create it first using the disk creator available via the Tools menu.
  7. Create a NIC. Map it to "Ethernet 2". Set the MAC address to the same MAC address as the host MAC address. The host MAC address is the MAC address of the VMware NIC. It is displayed by the AlphaVM GUI next to the AlphaVM MAC address.

    Note that if you use DECNET, the DECNET MAC address (AA-00-04-00-02-04) will be your host MAC address here. Remember, we configured the VMware NIC with this address.

    WARNING: if you have multiple Alpha NICs, each of them needs a separate dedicated VMware NIC with unique MAC addresss.

  8. For AlphaVM-Pro you need to configure the licensing. The licensing configuration instructions are provided with the professional software.

    For AlphaVM-Free the you do not have to configure the licensing. The licensing configuration page is ignored. Remember that AlphaVM-Free is limited to 1 basic CPU and 512MB RAM.

  9. Save the configuration to a configuration file.
  10. Now you are ready to boot AlphaVM.


You can use the VMware VMXNET3 NIC instead of the E1000 NICs. However, the VMXNET3 NIC does not pass any RX packets when all Windows protocols are disabled. It has to do with tighter integration of this para-virtualized NIC with VMware and Windows.

The solution is to leave some Windows protocols enabled, which makes sure that the NIC is active.