OpenVMS LAVC network communication broke after version 3.1.8

[John Malmberg]

I have the following configuration:

Host: OS-X 10.6.5. Virtual Box 3.1.8 Guest 1: Windows 7 64 bit (dual processor) Guest 2: Ubuntu 10.10 Guest additions for virtual networking from Virtual Box 3.2.12 installed.

Guest 1 is running FreeAXP, an Alpha system emulator with OpenVMS 8.3. Guest 2 is running SimH, a VAX system emulator with VAX/VMS 7.3.

Each guest has 4 network adapters. Two are bridged to the real ethernet adapter on the host, and two are bridged to an internal lan named 'internal'.

The intent is for the cluster network communications to use the internal network, and also use the internal network for any NFS mounting of shared resources between the guests and the emulated systems.

The two VMS systems are formed in a LAVC cluster.

This all works when running on Virtual Box 3.1.8. It also works when running under VMware Fusion with the appropriate network drivers on the Guest OSs.

I have not been able to get this to work on anything after 3.1.8 up to 3.2.12.

With later Virtual Box releases, as soon as the two VMS systems start LAVC communications, it looks like the network adapter stops passing most traffic.

The LAVC communication uses a different MAC address than the primary MAC address of an ethernet adapter, but as far as I know does not put the adapter in promiscuous mode.

[John Malmberg]

With VirtualBox 4.1.8 r75467 and the network adapters set to Promiscuous mode: Allow VMs, LAVC OpenVMS cluster works.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.