This config works under 3.9-0 The 3900 config is:
set console brk=4 load -r /simh/vax/ka655x.bin set cpu 256m set dz enable set dz lines=4 attach dz 5104 att nvr /simh/vax/nvr.img set rq0 rauser=4096 attach rq0 /simh/vax/rq0.dsk set rq1 disable set rq2 disable set rq3 disable set rl disable set ry disable set ts disable set tq disable set xq enable set xq mac=08-00-11-C3-56-39 set xq type=delqa att xq0 eth0 set cpu conhalt set cpu idle d wru 6 d bdr 0 b cpu MicroVAX 3900 simulator V4.0-0 Beta git commit id: 4a1cf358 Listening on port 5104 NVR: buffering file in memory ./vax3900.cfg-14> set ry disable Non-existent device Eth: Must specify actual tap device name (i.e. tap:tap0) KA655X-B V5.3, VMB 2.7 Performing normal system tests. 40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25.. 24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09.. 08..07..06..05..04..03.. Tests completed. Loading system software. (BOOT/R5:10000000 DUA0 The 780 config is: VAX 11/780 simulator V4.0-0 Beta git commit id: 4a1cf358 Listening on port 5100 Eth: Must specify actual tap device name (i.e. tap:tap0) Loading boot code from internal vmb.exe set cpu 128M set dz lines=8 attach dz 5100 set rq0 rauser=4096 attach rq0 /simh/vax/rq0.dsk set rq1 disable set rq2 disable set rq3 disable set hk disable set rl disable set rp disable set ry disable set ts disable set tq disable set tu disable set xu enable set xu mac=08-00-11-C3-56-B4 set xu type=delua att xu0 eth0 set cpu conhalt set cpu idle d wru 6 b rq0 %SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk %SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped %SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk %SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0 The systems crash when trying to start LAST. Changing the eth device to tap:tap0 allows a system to boot but the second system gives the message: Eth: open error - Device or resource busy on boot. However the booted system cannot contact the Alpha system on the same Linux system and can only be connected to from a remote system _______________________________________________ Simh mailing list [email protected] http://mailman.trailing-edge.com/mailman/listinfo/simh
