| Author |
VirtualBox Bridged Adapter - runs LAT/DECnet but not SCS? |
etmsreec
Member
Posts: 18
Joined: 15.02.07 |
| Posted on February 15 2013 01:13 |
|
|
I'm running FreeAXP and EMU VM on a Windows 7 laptop and bridging the two adapters with the VirtualBox Bridge that also has a Solaris VM connected to it.
The VirtualBox bridge passes LAT and DECnet without any issue, but it seems that it doesn't like SCS? I can create two single-host clusters, but the two systems seem unable to become a single cluster.
Any ideas please?
The situation is the same if using the Microsoft network bridge too.
I'm reluctant to put the emulators onto a real ethernet on the laptop as it's on a corporate network.
Thanks in advance
Steve |
|
|
| Author |
RE: VirtualBox Bridged Adapter - runs LAT/DECnet but not SCS? |
Bruce Claremont
Member
Posts: 623
Joined: 07.01.10 |
| Posted on February 15 2013 03:20 |
|
|
SCS is very sensitive to timing. One of the following might help:
- Limit the NIC speed in Windows device settings to 100Mb or 10Mb.
- Connect some USB NICs, one per emulator. Test running through a 10/100 switch.
It is also possible that somewhere along the way the SCS packets are not recognized and are thrown out. Make sure the virtual network components are in promiscuous mode. |
|
|
| Author |
RE: VirtualBox Bridged Adapter - runs LAT/DECnet but not SCS? |
malmberg
Moderator
Posts: 530
Joined: 15.04.08 |
| Posted on February 17 2013 12:45 |
|
|
I have FreeAXP running on a Windows 7 64 bit, and also a SimH system running on a Linux VM on the same host.
I have documented this in the FreeAXP forum. Some versions back, the Paravirtualized network drivers stopped working for SCS and other traffic loads under Virtualbox. Switching to emulated drivers allows full functionality.
|
|
|
| Author |
RE: VirtualBox Bridged Adapter - runs LAT/DECnet but not SCS? |
etmsreec
Member
Posts: 18
Joined: 15.02.07 |
| Posted on February 27 2013 04:32 |
|
|
I think I'm being a bit slow today, John. Are the emulated drivers on the FreeAXP/GnuVM side or on the VirtualBox or somewhere else entirely?
I've clicked onto using the real ethernet on the laptop today. Again, no SCS seems to pass and the config stays as two separate one-node clusters.  |
|
|
| Author |
RE: VirtualBox Bridged Adapter - runs LAT/DECnet but not SCS? |
malmberg
Moderator
Posts: 530
Joined: 15.04.08 |
| Posted on February 28 2013 03:04 |
|
|
To be more clear, for the Windows VM, I told virtual box to emulate a set of real physical adapters for the "Network interfaces" dedicated to the FreeVMS instance. This is more CPU overhead than using the paravirtualized I/O drivers. The paravirtualized drivers for Windows need to be downloaded from the Windows side.
With VMs you will always get the best performance with enabling any paravirtualization that you can.
Unfortunately the later versions of Virtualbox, W7, and FreeAXP, and the paravirtualized driver are not compatible.
I am not having any problem with Virtualbox, Ubuntu Linux, SimH, and the paravirtualized driver.
I have 4 network adapters set up for each VM. 2 for the OS on the VM, and 2 for the emulated VAX or Alpha running on the VM.
So each VM OS and each emulated VMS system has one network adapter on a private network and one bridged to the physical network adapter. So the host system, the VMs, and the emulators have both a private network to communicate on and a public network. SCS, LAT, DECNET IV, all work on both networks.
I think that you have to set the promiscuous mode to allow VMs or allow ALL for non TCP/IP traffic to be passed. The default setting is to deny it. |
|
|
