I'm using fedora 18 as the host.
*This is the message i get when i run the simulator :*
VAX simulator V3.9-0
NVR: buffering file in memory
RQ: unit is read only
/usr/local/vax/bin/vax.ini> attach XQ em1
Command not allowed
KA655-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:0 EXIT
2..
?41 DEVASSIGN, EXIT
?06 HLT INST
PC = 00000C1A
Failure.
>>>show version
KA655-B V5.3, VMB 2.7
*This is the vax.ini file :*
;
; Load CPU microcode
load -r /usr/local/vax/data/ka655x.bin
;
; Attach non-volatile RAM to a file
attach nvr /usr/local/vax/data/nvram.bin
;
; This virtual machine has 64M memory
set cpu 64m
;
; Define disk drive types. RA92 is largest-supported VAX drive.
set rq0 ra92
set rq1 ra92
set rq2 ra92
set rq3 cdrom
;
; Attach defined drives to local files
attach rq0 /usr/local/vax/data/d0.dsk
attach rq1 /usr/local/vax/data/d1.dsk
attach rq2 /usr/local/vax/data/d2.dsk
;
; Attach the CD-ROM to its file (read-only)
attach -r rq3 /usr/local/vax/data/cd.iso
;
; Disable unused devices. It's also possible to disable individual devices,
; using a construction like "set rq2 disable" if desired.
;
set rl disable
set ts disable
;
; Attach Ethernet to a network interface
set XQ mac=08-00-2B-AC-AC-B1
set XQ type=DELQA
attach XQ em1
;
;Uncomment the line below to enable auto-boot
dep bdr 0
;
;Choose one of the following lines.SET CPU CONHALT returns control to the
; VAX console monitor on a halt event (where behavior will be further
; determined by whether auto-boot is set--see above. SET CPU SIMHALT will
; cause the simulator to get control instead.
set cpu conhalt
;set cpu simhalt
;
;Now start the emulator
boot cpu
;
; Exit the simulator
exit
Regards,
Priya
On Mon, Nov 4, 2013 at 6:02 PM, Mark Pizzolato - Info Comm <
[email protected]> wrote:
> On Monday, November 04, 2013 at 4:29 AM, Lennert Van Alboom wrote:
> > The output you sent seems to indicate that your problem isn't with
> telnet,
> > but with the guest not having networking at all (configuring the network
> > inside simh alone doesn't do much).
> >
> > What host OS are you doing this on?
> > What does your host networking stack look like?
> > Can you show your simh configuration file?
>
> Also include the output of SHOW VERSION from within the simulator you are
> using...
>
> > Regards,
> >
> >
> > Lennert
> >
> >
> > On Mon, Nov 04, 2013 at 05:20:34PM +0530, priya chincholikar wrote:
> > > Hi,
> > > I'm new to openvms and simh. I installed open vms 7.3 and have
> > configured
> > > tcpip too.
> > > I want to connect to other hosts to test my tcpip.
> > > $ telnet 192.168.0.37
> > > %TELNET-E-IVHOST, Invalid or unknown host 192.168.0.37
> > > -TCPIP-E-NO_RECOVERY, unexpected name server failure
> > > $ ucx
> > > TCPIP> ping 192.168.0.37
> > > PING 192.168.0.37 (192.168.0.37): 56 data bytes
> > > ----192.168.0.37 PING Statistics----
> > > 4 packets transmitted, 0 packets received, 100% packet loss
> > > %SYSTEM-F-TIMEOUT, device timeout
> > > I'm not able to understand where I went wrong.
> > > Thanks,
> > > Priya
> >
> > > _______________________________________________
> > > Simh mailing list
> > > [email protected]
> > > http://mailman.trailing-edge.com/mailman/listinfo/simh
>
>
>
_______________________________________________
Simh mailing list
[email protected]
http://mailman.trailing-edge.com/mailman/listinfo/simh
