From gregg.drwho8 at gmail.com Thu Dec 5 23:03:22 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Thu, 5 Dec 2013 23:03:22 -0500 Subject: [Simh] Networking and SIMH Message-ID: Hello! Okay so I've managed to install the VDE components and the PCAP development components on my Raspberry Pi. Invoking make caused the build system to "choose" the VDE components. Why? When both are present I figured it would chose both rather then the one I'm not familiar with. In any case I know I can work with what the methods chose and eventually accomplish what I am planning on doing with the appropriate simulators. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From Mark at infocomm.com Fri Dec 6 05:21:35 2013 From: Mark at infocomm.com (Mark Pizzolato - Info Comm) Date: Fri, 6 Dec 2013 02:21:35 -0800 Subject: [Simh] Networking and SIMH In-Reply-To: References: Message-ID: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> Hi Gregg, On Thursday, December 05, 2013 at 8:03 PM, Gregg Levine wrote: > Okay so I've managed to install the VDE components and the PCAP > development components on my Raspberry Pi. Invoking make caused the > build system to "choose" the VDE components. Why? When both are > present I figured it would chose both rather then the one I'm not familiar > with. > > In any case I know I can work with what the methods chose and eventually > accomplish what I am planning on doing with the appropriate simulators. The build It is not an either or process. It will build using whatever Ethernet transports methods are available on the local environment when the build is done and each of those may be available when running with the simulator you built. As I recall, when I did this on the Raspberry Pi, I didn't have to look for libpcap-dev for that platform, I believe it was packaged with the OS. If /usr/include/pcap.h exists AND libpcap's shared object is available on the system (i.e. if tcpdump works) that is sufficient to build (and later use at runtime) with libpcap support. You don't explain how you think it chose just VDE rather than both. If you provide the output that make produced while building the simulator it will be more clear what capabilities are being built in. Meanwhile, to use one Ethernet transport method over another at run time will depend on several different goals. You need to be running as root on any Linux platform in order to inject packets into the network using libpcap. On the other hand, using VDE you can run as a normal unprivileged user as long as the VDE environment is already setup by some components running as root (maybe startup scripts, etc...). The simulator's "show xq ether" command will list the Ethernet transports which can be used by the process issuing that command. You would see different output if you were running as root. Additionally, you may or may not desire to have the simulated system actually be able to speak (exchange IP packets) with the host it is running on. If that is a goal, then on Linux you can't do that directly with libpcap. If that is a goal, then VDE can help you or you can build your own internal bridge with kernel bridging and tun/tap network interfaces. - Mark From dundas at caltech.edu Fri Dec 6 11:17:48 2013 From: dundas at caltech.edu (John A. Dundas III) Date: Fri, 6 Dec 2013 08:17:48 -0800 Subject: [Simh] PDP-11: CSM bug and fix Message-ID: Bob and all, I ran across what I believe to be a bug in the CSM code: case 070: /* CSM */ if (CPUT (HAS_CSM) && (MMR3 & MMR3_CSM) || (cm != MD_KER)) { According to the Architecture Handbook, CSM may be executed only if the MMR3 bit is set AND the mode is not Kernel. Changing the code to: case 070: /* CSM */ if (CPUT (HAS_CSM) && (MMR3 & MMR3_CSM) && (cm != MD_KER)) { also has the effect of making the ZKDKB0 diagnostic much happier. Thanks, John -- John A. Dundas III Director, IMSS Voice & Data Networks, Caltech Mail Code: 1-10, Pasadena, CA 91125 Phone: 626.395.3392 FAX: 626.395.2122 From bqt at softjar.se Fri Dec 6 11:55:16 2013 From: bqt at softjar.se (Johnny Billquist) Date: Fri, 06 Dec 2013 17:55:16 +0100 Subject: [Simh] Networking and SIMH In-Reply-To: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> References: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> Message-ID: <52A20174.4070302@softjar.se> On 2013-12-06 11:21, Mark Pizzolato - Info Comm wrote: > Hi Gregg, > > On Thursday, December 05, 2013 at 8:03 PM, Gregg Levine wrote: >> Okay so I've managed to install the VDE components and the PCAP >> development components on my Raspberry Pi. Invoking make caused the >> build system to "choose" the VDE components. Why? When both are >> present I figured it would chose both rather then the one I'm not familiar >> with. >> >> In any case I know I can work with what the methods chose and eventually >> accomplish what I am planning on doing with the appropriate simulators. > > The build It is not an either or process. It will build using whatever Ethernet transports methods are available on the local environment when the build is done and each of those may be available when running with the simulator you built. > > As I recall, when I did this on the Raspberry Pi, I didn't have to look for libpcap-dev for that platform, I believe it was packaged with the OS. If /usr/include/pcap.h exists AND libpcap's shared object is available on the system (i.e. if tcpdump works) that is sufficient to build (and later use at runtime) with libpcap support. > > You don't explain how you think it chose just VDE rather than both. If you provide the output that make produced while building the simulator it will be more clear what capabilities are being built in. > > Meanwhile, to use one Ethernet transport method over another at run time will depend on several different goals. You need to be running as root on any Linux platform in order to inject packets into the network using libpcap. You need to be running as root to even sniff packets with pcap. Johnny From gregg.drwho8 at gmail.com Fri Dec 6 12:13:57 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Fri, 6 Dec 2013 12:13:57 -0500 Subject: [Simh] Networking and SIMH In-Reply-To: <52A20174.4070302@softjar.se> References: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> <52A20174.4070302@softjar.se> Message-ID: Hello! Correct on that point Johnny. Mark, where do you want the build activity posted? Here? To the Git server's pages? I'll rebuild everything, and this time with the script mechanism writing down what happened. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." On Fri, Dec 6, 2013 at 11:55 AM, Johnny Billquist wrote: > On 2013-12-06 11:21, Mark Pizzolato - Info Comm wrote: >> >> Hi Gregg, >> >> On Thursday, December 05, 2013 at 8:03 PM, Gregg Levine wrote: >>> >>> Okay so I've managed to install the VDE components and the PCAP >>> development components on my Raspberry Pi. Invoking make caused the >>> build system to "choose" the VDE components. Why? When both are >>> present I figured it would chose both rather then the one I'm not >>> familiar >>> with. >>> >>> In any case I know I can work with what the methods chose and eventually >>> accomplish what I am planning on doing with the appropriate simulators. >> >> >> The build It is not an either or process. It will build using whatever >> Ethernet transports methods are available on the local environment when the >> build is done and each of those may be available when running with the >> simulator you built. >> >> As I recall, when I did this on the Raspberry Pi, I didn't have to look >> for libpcap-dev for that platform, I believe it was packaged with the OS. >> If /usr/include/pcap.h exists AND libpcap's shared object is available on >> the system (i.e. if tcpdump works) that is sufficient to build (and later >> use at runtime) with libpcap support. >> >> You don't explain how you think it chose just VDE rather than both. If >> you provide the output that make produced while building the simulator it >> will be more clear what capabilities are being built in. >> >> Meanwhile, to use one Ethernet transport method over another at run time >> will depend on several different goals. You need to be running as root on >> any Linux platform in order to inject packets into the network using >> libpcap. > > > You need to be running as root to even sniff packets with pcap. > > Johnny > > _______________________________________________ > Simh mailing list > Simh at trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh From Mark at infocomm.com Fri Dec 6 12:26:18 2013 From: Mark at infocomm.com (Mark Pizzolato - Info Comm) Date: Fri, 6 Dec 2013 09:26:18 -0800 Subject: [Simh] Networking and SIMH In-Reply-To: References: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> <52A20174.4070302@softjar.se> Message-ID: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1B2@REDROOF2.alohasunset.com> On Friday, December 06, 2013 at 9:14 AM, Gregg Levine wrote: > Mark, where do you want the build activity posted? Here? To the Git server's > pages? I'll rebuild everything, and this time with the script mechanism writing > down what happened. Hi Gregg, Please create an issue at https://github.com/simh/simh/issues to contain the build activity and any further discussion on this problem. Please restate what you've already said while creating that issue. Thanks. - Mark From aek at bitsavers.org Fri Dec 6 12:30:03 2013 From: aek at bitsavers.org (Al Kossow) Date: Fri, 06 Dec 2013 09:30:03 -0800 Subject: [Simh] Networking and SIMH In-Reply-To: References: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> <52A20174.4070302@softjar.se> Message-ID: <52A2099B.5070003@bitsavers.org> On 12/6/13 9:13 AM, Gregg Levine wrote: > Mark, where do you want the build activity posted? I had been wondering about this for a while. Is most of the SIMH development discussion done off-list? There seems to be very few posts here, and nothing at all on simh-dev (unless I'm looking in the wrong place). One of the things I like to do is monitor mailing lists watching for people asking about documentation, since I have lots of it queued up, but prioritize based on what people seem to be looking for. "Marty" looking for better copies of the 11/40 print set on the vcforum is an example. I've been trying to clear my backlog of PDP-10 and 11 datacomm stuff recently. I just put the AN10 drawings up this morning. Best way to see what's new is to look at http://user.xmission.com/~legalize/vintage/bitsavers-pdf.xml to see when the uploads make it out to the mirrors. From Mark at infocomm.com Fri Dec 6 12:45:27 2013 From: Mark at infocomm.com (Mark Pizzolato - Info Comm) Date: Fri, 6 Dec 2013 09:45:27 -0800 Subject: [Simh] Networking and SIMH In-Reply-To: <52A2099B.5070003@bitsavers.org> References: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> <52A20174.4070302@softjar.se> <52A2099B.5070003@bitsavers.org> Message-ID: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1B4@REDROOF2.alohasunset.com> On Friday, December 06, 2013 at 9:30 AM, Al Kossow wrote: > On 12/6/13 9:13 AM, Gregg Levine wrote: > > > Mark, where do you want the build activity posted? > > I had been wondering about this for a while. Is most of the SIMH > development discussion done off-list? There seems to be very few posts > here, and nothing at all on simh-dev (unless I'm looking in the wrong place). Well, I'm looking for bug reports and/or enhancement requests to be tracked and discussed proximate to the repository containing the source. When folks ask questions on the simh list which potentially need code changes, I try to encourage that to create issues in the github repository issue system. I qualify this statement to exclude issues which are obviously going to solicit an answer from Bob (John Dundas's message today "[Simh] PDP-11: CSM bug and fix" is an example of that). If any issues are create on the github issue system which Bob would be the obvious authority for, or if his input would be valuable, I point him at the issue. Anyone can subscribe to get updates from the github system via an RSS feed. > One of the things I like to do is monitor mailing lists watching for people > asking about documentation, since I have lots of it queued up, but prioritize > based on what people seem to be looking for. "Marty" looking for better > copies of the 11/40 print set on the vcforum is an example. No issues have been raised on the issue system about documentation. If there were, I'd redirect those issues to the simh list. - Mark From j_hoppe at t-online.de Tue Dec 17 15:28:32 2013 From: j_hoppe at t-online.de (=?ISO-8859-15?Q?J=F6rg_Hoppe?=) Date: Tue, 17 Dec 2013 21:28:32 +0100 Subject: [Simh] Database of PDP-11 diagnostics Message-ID: <52B0B3F0.1070504@t-online.de> Hi all, a new database about all PDP-11 diagnostics went online this week: http://www.retrocmp.com/tools/pdp-11-diagnostic-database The database contains - a list of all known PDP-11 / MAINDEC / X11 / XXDP diagnostic modules - links to all kind of bitsavers files: manual pages, binary files, media images, listing scans, file images, and indexes - a list of all tested devices All in all there are several thousand data items, and all are linked with each other. Enjoy! Joerg From frisbie at flying-disk.com Tue Dec 17 16:16:12 2013 From: frisbie at flying-disk.com (Alan Frisbie) Date: Tue, 17 Dec 2013 13:16:12 -0800 (PST) Subject: [Simh] Database of PDP-11 diagnostics Message-ID: <13121713161240_448@slug.flying-disk.com> > a new database about all PDP-11 diagnostics went online this week: > http://www.retrocmp.com/tools/pdp-11-diagnostic-database > > The database contains > - a list of all known PDP-11 / MAINDEC / X11 / XXDP diagnostic modules > - links to all kind of bitsavers files: manual pages, binary files, > media images, listing scans, file images, and indexes > - a list of all tested devices Wow! This is fantastic. Thank you (and everyone else who made this possible) very much. It is a valuable resource. Alan Frisbie From aek at bitsavers.org Tue Dec 17 17:10:55 2013 From: aek at bitsavers.org (Al Kossow) Date: Tue, 17 Dec 2013 14:10:55 -0800 Subject: [Simh] Database of PDP-11 diagnostics In-Reply-To: <13121713161240_448@slug.flying-disk.com> References: <13121713161240_448@slug.flying-disk.com> Message-ID: <52B0CBEF.2080008@bitsavers.org> On 12/17/13 1:16 PM, Alan Frisbie wrote: > Wow! This is fantastic. Thank you (and everyone else who > made this possible) very much. It is a valuable resource. > If anyone turns up any other listings that haven't been scanned, I would like to add them to bitsavers. TM03 diags will be doing up soon, but I would like to find the writeups for the Massbus disks as well. From frisbie at flying-disk.com Tue Dec 17 19:52:57 2013 From: frisbie at flying-disk.com (Alan Frisbie) Date: Tue, 17 Dec 2013 16:52:57 -0800 (PST) Subject: [Simh] Database of PDP-11 diagnostics Message-ID: <13121716525743_448@slug.flying-disk.com> > If anyone turns up any other listings that haven't been scanned, > I would like to add them to bitsavers. I just acquired a bunch of Q-bus related XXDP listings from the family of a deceased friend. Actually, I acquired two storage units full of "stuff". I'll be going through it over the next few months to make sure it all goes to a good home. The guy liked to make copies of every manual he owned, so there are lots to go around. I'll post a list to the SIMH mailing list, but would appreciate other suggestions. There is lots of hardware too. Anyone need DHV11 cabinet kits? There must be at least 30 Q-bus cards in nice anti-static boxes. Alan Frisbie From priyachinc at gmail.com Wed Dec 18 06:27:37 2013 From: priyachinc at gmail.com (Priya Chincholikar) Date: Wed, 18 Dec 2013 16:57:37 +0530 Subject: [Simh] Ethernet connection problems Message-ID: Hi, I'm installing SIMH on RedHat VM. I seem to have Ethernet connection problems. # usr/local/vax/bin/vax MicroVAX 3900 simulator V4.0-0 Beta git commit id: 25a62c28 NVR: buffering file in memory usr/local/vax/bin/vax.ini-34> attach XQ eth0 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. >>>usr/local/vax/bin/vax.ini-47> boot cpu *I did ^E here* Simulation stopped, PC: 20043601 (BSBW 2004367B) sim> sh ver MicroVAX 3900 simulator V4.0-0 Beta Simulator Framework Capabilities: 64b data 64b addresses no Ethernet Idle/Throttling support is available Virtual Hard Disk (VHD) support RAW disk and CD/DVD ROM support Asynchronous I/O support Host Platform: Compiler: GCC 4.1.1 20070105 (Red Hat 4.1.1-52) Simulator Compiled: Dec 12 2013 at 00:20:12 Memory Access: Little Endian Memory Pointer Size: 32 bits Large File (>2GB) support OS clock tick size: 2ms OS: Linux dt558.**.com 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:21 EST 2007 i686 i686 i386 GNU/Linux git commit id: 25a62c28 sim> show ethernet ETH devices: network support not available in simulator sim> quit Goodbye NVR: writing buffer to file The host is : # cat /proc/version Linux version 2.6.18-8.el5 (brewbuilder at ls20-bc2-14.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP Fri Jan 26 14:15:21 EST 2007 VAX.INI ; ; 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 rauser=10240 set rq2 rauser=10240 set rq3 cdrom ; ; Attach defined drives to local files attach rq0 /mnt/simh-disks/d0.dsk attach rq1 /mnt/simh-disks/d1.dsk attach rq2 /mnt/simh-disks/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 eth0 ; ;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 ~ The steps I followed for installing of the emulator are: $ wget *https://github.com/simh/simh/archive/master.zip* $ unzip simh-master.zip $ cd simh-master $ make vax -------------- next part -------------- An HTML attachment was scrubbed... URL: From Mark at infocomm.com Wed Dec 18 06:41:39 2013 From: Mark at infocomm.com (Mark Pizzolato - Info Comm) Date: Wed, 18 Dec 2013 03:41:39 -0800 Subject: [Simh] Ethernet connection problems In-Reply-To: References: Message-ID: <0CC6789C1C831B4C8CCFF49D45D7010F0127D51050E3@REDROOF2.alohasunset.com> Hi Priya, Hmmm... There was a fix checked into the github repository about 21 hours ago which fixed an Ethernet issue and which the version you've built does not contain. You will definitely need the latest code, However, that doesn't seem to be the issue you are encountering. It seems you've built a simulator without support for libpcap. The output produced when you performed 'make vax' would be more informative regarding this. It probably suggests that you need to install the libpcap-dev package for your simulator to have Ethernet support... If after considering this, you still have a problem, please open an issue at https://github.com/simh/simh/issues. - Mark From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-edge.com] On Behalf Of Priya Chincholikar Sent: Wednesday, December 18, 2013 3:28 AM To: simh at trailing-edge.com Subject: [Simh] Ethernet connection problems Hi, I'm installing SIMH on RedHat VM. I seem to have Ethernet connection problems. # usr/local/vax/bin/vax MicroVAX 3900 simulator V4.0-0 Beta git commit id: 25a62c28 NVR: buffering file in memory usr/local/vax/bin/vax.ini-34> attach XQ eth0 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. >>>usr/local/vax/bin/vax.ini-47> boot cpu *I did ^E here* Simulation stopped, PC: 20043601 (BSBW 2004367B) sim> sh ver MicroVAX 3900 simulator V4.0-0 Beta Simulator Framework Capabilities: 64b data 64b addresses no Ethernet Idle/Throttling support is available Virtual Hard Disk (VHD) support RAW disk and CD/DVD ROM support Asynchronous I/O support Host Platform: Compiler: GCC 4.1.1 20070105 (Red Hat 4.1.1-52) Simulator Compiled: Dec 12 2013 at 00:20:12 Memory Access: Little Endian Memory Pointer Size: 32 bits Large File (>2GB) support OS clock tick size: 2ms OS: Linux dt558.**.com 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:21 EST 2007 i686 i686 i386 GNU/Linux git commit id: 25a62c28 sim> show ethernet ETH devices: network support not available in simulator sim> quit Goodbye NVR: writing buffer to file The host is : # cat /proc/version Linux version 2.6.18-8.el5 (brewbuilder at ls20-bc2-14.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP Fri Jan 26 14:15:21 EST 2007 VAX.INI ; ; 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 rauser=10240 set rq2 rauser=10240 set rq3 cdrom ; ; Attach defined drives to local files attach rq0 /mnt/simh-disks/d0.dsk attach rq1 /mnt/simh-disks/d1.dsk attach rq2 /mnt/simh-disks/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 eth0 ; ;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 ~ The steps I followed for installing of the emulator are: $ wget https://github.com/simh/simh/archive/master.zip $ unzip simh-master.zip $ cd simh-master $ make vax -------------- next part -------------- An HTML attachment was scrubbed... URL: From bqt at softjar.se Wed Dec 18 06:42:59 2013 From: bqt at softjar.se (Johnny Billquist) Date: Wed, 18 Dec 2013 12:42:59 +0100 Subject: [Simh] Ethernet connection problems In-Reply-To: References: Message-ID: <52B18A43.1000800@softjar.se> Hi. On 2013-12-18 12:27, Priya Chincholikar wrote: > Hi, > > I'm installing SIMH on RedHat VM. I seem to have Ethernet connection > problems. > > > # usr/local/vax/bin/vax > > MicroVAX 3900 simulator V4.0-0 Beta git commit id: 25a62c28 > NVR: buffering file in memory > usr/local/vax/bin/vax.ini-34> attach XQ eth0 > Command not allowed ^^^^^^^^ This is your obvious problem. Others might have more useful comments here, but looking at the config file: > ; Attach Ethernet to a network interface > set XQ mac=08-00-2B-AC-AC-B1 > set XQ type=DELQA > attach XQ eth0 I'm not sure if XQ is enabled by default or not. You could try adding set XQ enable. Other than that, I would possibly suspect that it didn't manage to build with ethernet support. Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol From priyachinc at gmail.com Tue Dec 31 07:52:53 2013 From: priyachinc at gmail.com (Priya Chincholikar) Date: Tue, 31 Dec 2013 18:22:53 +0530 Subject: [Simh] Network Problem Message-ID: Hi, I am trying boot a vax disk on SIMH and it keeps getting hung while starting network like TCP/IP. I have the required lipcap packages. My host is RedHat VM. The simulator was built with network support. *******INTERnet Started************** %UCX-I-DEFINTE, Defining interfaces %UCX-E-INVINTER, Error defining interface: SE0 -UCX-I-ACPQIO, Failure on Internet ACP QIO -SYSTEM-W-NOSUCHDEV, no such device available -SYSTEM-W-NOSUCHDEV, no such device available %UCX-E-INVINTERNAM, Invalid interface name -UCX-I-DRIVERQIO, Failure on Internet driver QIO -UCX-E-INVNETMASK, Invalid network mask %UCX-E-DELINTER, Error deleting interface: SE0 -UCX-I-ACPQIO, Failure on Internet ACP QIO ----> gets hung here usr/local/vax/bin/vax.ini-47> boot cpuname Simulation stopped, PC: 8358DF47 (BBC #3,26C(R3),8358DF9B) sim> *This is the build*: root at dt558 simh-master]# make vax lib paths are: /lib/ /usr/lib/ /usr/lib/qt-3.3/lib/ /usr/lib/sse2/ using libm: /usr/lib//libm.so using librt: /usr/lib//librt.so using libpthread: /usr/lib//libpthread.so /usr/include/pthread.h using libdl: /usr/lib//libdl.so /usr/include/dlfcn.h using libpcap: /usr/local/lib/libpcap.a /usr/local/include/pcap.h *** Warning *** *** Warning *** vax Simulator being built with networking support using *** Warning *** libpcap components from www.tcpdump.org. *** Warning *** Some users have had problems using the www.tcpdump.orglibpcap *** Warning *** components for simh networking. For best results, with *** Warning *** simh networking, it is recommended that you install the *** Warning *** libpcap-dev package from your Linux distribution *** Warning *** *** Warning *** Building with the components manually installed from www.tcpdump.org *** Warning *** is officially deprecated. Attempting to do so is unsupported. *** Warning *** *** Warning *** *** Warning *** vax Simulator are being built with *** Warning *** minimal libpcap networking support *** Warning *** *** Warning *** Simulators on your Linux platform can also be built with *** Warning *** extended Ethernet networking support by using VDE Ethernet. *** Warning *** *** Warning *** To build simulator(s) with extended networking support you *** Warning *** should read 0readme_ethernet.txt and follow the instructions *** Warning *** regarding the needed libvdeplug components for your Linux *** Warning *** platform *** Warning *** *** *** vax Simulator being built with: *** - compiler optimizations and no debugging support. GCC Version: 4.1.2. *** - networking support using libpcap components from www.tcpdump.org. *** - Local LAN packet transports: PCAP TAP *** *** git commit id is 86e342501deaec3df79b31c13dd6d622938176e2. *** mkdir -p BIN gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fno-unsafe-loop-optimizations -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB sim_BuildROMs.c -o BIN/BuildROMs BIN/BuildROMs rm -f BIN/BuildROMs mkdir -p BIN gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fno-unsafe-loop-optimizations -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB VAX/vax_cpu.c VAX/vax_cpu1.c VAX/vax_fpa.c VAX/vax_io.c VAX/vax_cis.c VAX/vax_octa.c VAX/vax_cmode.c VAX/vax_mmu.c VAX/vax_stddev.c VAX/vax_sysdev.c VAX/vax_sys.c VAX/vax_syscm.c VAX/vax_syslist.c PDP11/pdp11_rl.c PDP11/pdp11_rq.c PDP11/pdp11_ts.c PDP11/pdp11_dz.c PDP11/pdp11_lp.c PDP11/pdp11_tq.c PDP11/pdp11_xq.c PDP11/pdp11_vh.c PDP11/pdp11_cr.c PDP11/pdp11_io_lib.c scp.c sim_console.c sim_fio.c sim_timer.c sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c sim_disk.c sim_serial.c sim_video.c -DVM_VAX -DUSE_INT64 -DUSE_ADDR64 -I VAX -I PDP11 -DUSE_NETWORK -DHAVE_PCAP_NETWORK -isystem -I/usr/local/include/ /usr/local/lib/libpcap.a -DHAVE_TAP_NETWORK -o BIN/microvax3900 -lm -lrt -lpthread -ldl cp BIN/microvax3900 BIN/vax *Show version and show ethernet :* 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. >>>usr/local/vax/bin/vax.ini-47> boot cpu Simulation stopped, PC: 20043601 (BSBW 2004367B) sim> sh ver MicroVAX 3900 simulator V4.0-0 Beta Simulator Framework Capabilities: 64b data 64b addresses Ethernet Packet transport:PCAP:TAP:UDP Idle/Throttling support is available Virtual Hard Disk (VHD) support RAW disk and CD/DVD ROM support Asynchronous I/O support Host Platform: Compiler: GCC 4.1.2 20080704 (Red Hat 4.1.2-46) Simulator Compiled: Dec 30 2013 at 17:52:32 Memory Access: Little Endian Memory Pointer Size: 32 bits Large File (>2GB) support OS clock tick size: 3ms OS: Linux dt558.***.com 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:54 EDT 2009 i686 i686 i386 GNU/Linux git commit id: 86e34250 sim> sh eth ETH devices: eth0 eth0 (No description available) eth1 tap:tapN (Integrated Tun/Tap support) eth2 udp:sourceport:remotehost:remoteport (Integrated UDP bridge support) Open ETH Devices: XQ eth0 (No description available) Ethernet Device: Name: eth0 Reflections: 0 Self Loopbacks Sent: 2 Self Loopbacks Rcvd: 0 Host NIC Address: 00:0C:29:59:50:83 Packets Sent: 4 Asynch Interrupts: Disabled Read Queue: Count: 0 Read Queue: High: 0 Read Queue: Loss: 0 Peak Write Queue Size: 1 sim> quit Goodbye NVR: writing buffer to file Eth: closed eth0 [root at dt558 /]# cat proc/version Linux version 2.6.18-164.el5 (mockbuild at x86-002.build.bos.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Aug 18 15:51:54 EDT 2009 *Vax.ini :* ; ;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 rauser=10240 set rq2 rauser=10240 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=00:1D:D8:B7:1C:00 set XQ type=DELQA attach XQ eth0 ; ;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 -Priya -------------- next part -------------- An HTML attachment was scrubbed... URL: From johnsong at gregjohnson.org Tue Dec 31 09:59:53 2013 From: johnsong at gregjohnson.org (Greg Johnson) Date: Tue, 31 Dec 2013 06:59:53 -0800 Subject: [Simh] Network Problem In-Reply-To: References: Message-ID: <52C2DBE9.6060802@gregjohnson.org> Are you running it as 'root'? I believe that under Linux you need to run simh as root to place the network connection in the right mode for networking. On 12/31/2013 4:52 AM, Priya Chincholikar wrote: > > > Hi, > > I am trying boot a vax disk on SIMH and it keeps getting hung while > starting network like TCP/IP. > I have the required lipcap packages. My host is RedHat VM. The > simulator was built with network support. > > *******INTERnet Started************** > > %UCX-I-DEFINTE, Defining interfaces > %UCX-E-INVINTER, Error defining interface: SE0 > -UCX-I-ACPQIO, Failure on Internet ACP QIO > -SYSTEM-W-NOSUCHDEV, no such device available > -SYSTEM-W-NOSUCHDEV, no such device available > %UCX-E-INVINTERNAM, Invalid interface name > -UCX-I-DRIVERQIO, Failure on Internet driver QIO > -UCX-E-INVNETMASK, Invalid network mask > %UCX-E-DELINTER, Error deleting interface: SE0 > -UCX-I-ACPQIO, Failure on Internet ACP QIO ---->gets hung here > usr/local/vax/bin/vax.ini-47> boot cpuname > > Simulation stopped, PC: 8358DF47 (BBC #3,26C(R3),8358DF9B) > sim> > > *This is the build*: > > root at dt558 simh-master]# make vax > lib paths are: /lib/ /usr/lib/ /usr/lib/qt-3.3/lib/ /usr/lib/sse2/ > using libm: /usr/lib//libm.so > using librt: /usr/lib//librt.so > using libpthread: /usr/lib//libpthread.so /usr/include/pthread.h > using libdl: /usr/lib//libdl.so /usr/include/dlfcn.h > using libpcap: /usr/local/lib/libpcap.a /usr/local/include/pcap.h > *** Warning *** > *** Warning *** vax Simulator being built with networking support using > *** Warning *** libpcap components from www.tcpdump.org > . > *** Warning *** Some users have had problems using the www.tcpdump.org > libpcap > *** Warning *** components for simh networking. For best results, with > *** Warning *** simh networking, it is recommended that you install the > *** Warning *** libpcap-dev package from your Linux distribution > *** Warning *** > *** Warning *** Building with the components manually installed from > www.tcpdump.org > *** Warning *** is officially deprecated. Attempting to do so is > unsupported. > *** Warning *** > *** Warning *** > *** Warning *** vax Simulator are being built with > *** Warning *** minimal libpcap networking support > *** Warning *** > *** Warning *** Simulators on your Linux platform can also be built with > *** Warning *** extended Ethernet networking support by using VDE > Ethernet. > *** Warning *** > *** Warning *** To build simulator(s) with extended networking support you > *** Warning *** should read 0readme_ethernet.txt and follow the > instructions > *** Warning *** regarding the needed libvdeplug components for your Linux > *** Warning *** platform > *** Warning *** > *** > *** vax Simulator being built with: > *** - compiler optimizations and no debugging support. GCC Version: 4.1.2. > *** - networking support using libpcap components from www.tcpdump.org > . > *** - Local LAN packet transports: PCAP TAP > *** > *** git commit id is 86e342501deaec3df79b31c13dd6d622938176e2. > *** > mkdir -p BIN > gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions > -fgcse-after-reload -fno-unsafe-loop-optimizations > -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 > -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE > -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB > sim_BuildROMs.c -o BIN/BuildROMs > BIN/BuildROMs > rm -f BIN/BuildROMs > mkdir -p BIN > gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions > -fgcse-after-reload -fno-unsafe-loop-optimizations > -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 > -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE > -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB > VAX/vax_cpu.c VAX/vax_cpu1.c VAX/vax_fpa.c VAX/vax_io.c VAX/vax_cis.c > VAX/vax_octa.c VAX/vax_cmode.c VAX/vax_mmu.c VAX/vax_stddev.c > VAX/vax_sysdev.c VAX/vax_sys.c VAX/vax_syscm.c VAX/vax_syslist.c > PDP11/pdp11_rl.c PDP11/pdp11_rq.c PDP11/pdp11_ts.c PDP11/pdp11_dz.c > PDP11/pdp11_lp.c PDP11/pdp11_tq.c PDP11/pdp11_xq.c PDP11/pdp11_vh.c > PDP11/pdp11_cr.c PDP11/pdp11_io_lib.c scp.c sim_console.c sim_fio.c > sim_timer.c sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c sim_disk.c > sim_serial.c sim_video.c -DVM_VAX -DUSE_INT64 -DUSE_ADDR64 -I VAX -I > PDP11 -DUSE_NETWORK -DHAVE_PCAP_NETWORK -isystem -I/usr/local/include/ > /usr/local/lib/libpcap.a -DHAVE_TAP_NETWORK -o BIN/microvax3900 -lm > -lrt -lpthread -ldl > cp BIN/microvax3900 BIN/vax > > > *Show version and show ethernet :* > > 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. > >>>usr/local/vax/bin/vax.ini-47> boot cpu > > Simulation stopped, PC: 20043601 (BSBW 2004367B) > sim> sh ver > MicroVAX 3900 simulator V4.0-0 Beta > Simulator Framework Capabilities: > 64b data > 64b addresses > Ethernet Packet transport:PCAP:TAP:UDP > Idle/Throttling support is available > Virtual Hard Disk (VHD) support > RAW disk and CD/DVD ROM support > Asynchronous I/O support > Host Platform: > Compiler: GCC 4.1.2 20080704 (Red Hat 4.1.2-46) > Simulator Compiled: Dec 30 2013 at 17:52:32 > Memory Access: Little Endian > Memory Pointer Size: 32 bits > Large File (>2GB) support > OS clock tick size: 3ms > OS: Linux dt558.***.com 2.6.18-164.el5 #1 SMP Tue Aug > 18 15:51:54 EDT 2009 i686 i686 i386 GNU/Linux > > git commit id: 86e34250 > sim> sh eth > ETH devices: > eth0 eth0 (No description available) > eth1 tap:tapN (Integrated Tun/Tap support) > eth2 udp:sourceport:remotehost:remoteport (Integrated UDP bridge support) > Open ETH Devices: > XQ eth0 (No description available) > Ethernet Device: > Name: eth0 > Reflections: 0 > Self Loopbacks Sent: 2 > Self Loopbacks Rcvd: 0 > Host NIC Address: 00:0C:29:59:50:83 > Packets Sent: 4 > Asynch Interrupts: Disabled > Read Queue: Count: 0 > Read Queue: High: 0 > Read Queue: Loss: 0 > Peak Write Queue Size: 1 > sim> quit > Goodbye > NVR: writing buffer to file > Eth: closed eth0 > > [root at dt558 /]# cat proc/version > Linux version 2.6.18-164.el5 (mockbuild at x86-002.build.bos.redhat.com > ) (gcc version 4.1.2 > 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Aug 18 15:51:54 EDT 2009 > > *Vax.ini :* > ; > ;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 rauser=10240 > set rq2 rauser=10240 > 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=00:1D:D8:B7:1C:00 > set XQ type=DELQA > attach XQ eth0 > ; > ;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 > > -Priya > > > _______________________________________________ > Simh mailing list > Simh at trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.hittner at ngc.com Tue Dec 31 11:10:45 2013 From: david.hittner at ngc.com (Hittner, David T (IS)) Date: Tue, 31 Dec 2013 16:10:45 +0000 Subject: [Simh] EXT : Network Problem In-Reply-To: References: Message-ID: <9C9FDA2BCCFB5E4098DEB87AC47B94503E268384@XMBVAG73.northgrum.com> Rerun @SYS$MANAGER:TCPIP$CONFIG to fix your TCPIP hardware interface definitions. The error is telling you that it can't find the VAX hardware device (no such device SE0) to attach (on the 4th line). The MicroVAX 3900 in the SIMH VAX does not have an SE0 interface, it has a QNA interface. I think SE0 was the built-in MicroVAX/VAXstation 3100 interface. Was this system disk originally used by a different VAX emulator (like Charon/SRI) or a different model of real VAX? Dave From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-edge.com] On Behalf Of Priya Chincholikar Sent: Tuesday, December 31, 2013 7:53 AM To: simh at trailing-edge.com Subject: EXT :[Simh] Network Problem Hi, I am trying boot a vax disk on SIMH and it keeps getting hung while starting network like TCP/IP. I have the required lipcap packages. My host is RedHat VM. The simulator was built with network support. *******INTERnet Started************** %UCX-I-DEFINTE, Defining interfaces %UCX-E-INVINTER, Error defining interface: SE0 -UCX-I-ACPQIO, Failure on Internet ACP QIO -SYSTEM-W-NOSUCHDEV, no such device available -SYSTEM-W-NOSUCHDEV, no such device available %UCX-E-INVINTERNAM, Invalid interface name -UCX-I-DRIVERQIO, Failure on Internet driver QIO -UCX-E-INVNETMASK, Invalid network mask %UCX-E-DELINTER, Error deleting interface: SE0 -UCX-I-ACPQIO, Failure on Internet ACP QIO ----> gets hung here usr/local/vax/bin/vax.ini-47> boot cpuname Simulation stopped, PC: 8358DF47 (BBC #3,26C(R3),8358DF9B) sim> This is the build: root at dt558 simh-master]# make vax lib paths are: /lib/ /usr/lib/ /usr/lib/qt-3.3/lib/ /usr/lib/sse2/ using libm: /usr/lib//libm.so using librt: /usr/lib//librt.so using libpthread: /usr/lib//libpthread.so /usr/include/pthread.h using libdl: /usr/lib//libdl.so /usr/include/dlfcn.h using libpcap: /usr/local/lib/libpcap.a /usr/local/include/pcap.h *** Warning *** *** Warning *** vax Simulator being built with networking support using *** Warning *** libpcap components from www.tcpdump.org. *** Warning *** Some users have had problems using the www.tcpdump.org libpcap *** Warning *** components for simh networking. For best results, with *** Warning *** simh networking, it is recommended that you install the *** Warning *** libpcap-dev package from your Linux distribution *** Warning *** *** Warning *** Building with the components manually installed from www.tcpdump.org *** Warning *** is officially deprecated. Attempting to do so is unsupported. *** Warning *** *** Warning *** *** Warning *** vax Simulator are being built with *** Warning *** minimal libpcap networking support *** Warning *** *** Warning *** Simulators on your Linux platform can also be built with *** Warning *** extended Ethernet networking support by using VDE Ethernet. *** Warning *** *** Warning *** To build simulator(s) with extended networking support you *** Warning *** should read 0readme_ethernet.txt and follow the instructions *** Warning *** regarding the needed libvdeplug components for your Linux *** Warning *** platform *** Warning *** *** *** vax Simulator being built with: *** - compiler optimizations and no debugging support. GCC Version: 4.1.2. *** - networking support using libpcap components from www.tcpdump.org. *** - Local LAN packet transports: PCAP TAP *** *** git commit id is 86e342501deaec3df79b31c13dd6d622938176e2. *** mkdir -p BIN gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fno-unsafe-loop-optimizations -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB sim_BuildROMs.c -o BIN/BuildROMs BIN/BuildROMs rm -f BIN/BuildROMs mkdir -p BIN gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fno-unsafe-loop-optimizations -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB VAX/vax_cpu.c VAX/vax_cpu1.c VAX/vax_fpa.c VAX/vax_io.c VAX/vax_cis.c VAX/vax_octa.c VAX/vax_cmode.c VAX/vax_mmu.c VAX/vax_stddev.c VAX/vax_sysdev.c VAX/vax_sys.c VAX/vax_syscm.c VAX/vax_syslist.c PDP11/pdp11_rl.c PDP11/pdp11_rq.c PDP11/pdp11_ts.c PDP11/pdp11_dz.c PDP11/pdp11_lp.c PDP11/pdp11_tq.c PDP11/pdp11_xq.c PDP11/pdp11_vh.c PDP11/pdp11_cr.c PDP11/pdp11_io_lib.c scp.c sim_console.c sim_fio.c sim_timer.c sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c sim_disk.c sim_serial.c sim_video.c -DVM_VAX -DUSE_INT64 -DUSE_ADDR64 -I VAX -I PDP11 -DUSE_NETWORK -DHAVE_PCAP_NETWORK -isystem -I/usr/local/include/ /usr/local/lib/libpcap.a -DHAVE_TAP_NETWORK -o BIN/microvax3900 -lm -lrt -lpthread -ldl cp BIN/microvax3900 BIN/vax Show version and show ethernet : 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. >>>usr/local/vax/bin/vax.ini-47> boot cpu Simulation stopped, PC: 20043601 (BSBW 2004367B) sim> sh ver MicroVAX 3900 simulator V4.0-0 Beta Simulator Framework Capabilities: 64b data 64b addresses Ethernet Packet transport:PCAP:TAP:UDP Idle/Throttling support is available Virtual Hard Disk (VHD) support RAW disk and CD/DVD ROM support Asynchronous I/O support Host Platform: Compiler: GCC 4.1.2 20080704 (Red Hat 4.1.2-46) Simulator Compiled: Dec 30 2013 at 17:52:32 Memory Access: Little Endian Memory Pointer Size: 32 bits Large File (>2GB) support OS clock tick size: 3ms OS: Linux dt558.***.com 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:54 EDT 2009 i686 i686 i386 GNU/Linux git commit id: 86e34250 sim> sh eth ETH devices: eth0 eth0 (No description available) eth1 tap:tapN (Integrated Tun/Tap support) eth2 udp:sourceport:remotehost:remoteport (Integrated UDP bridge support) Open ETH Devices: XQ eth0 (No description available) Ethernet Device: Name: eth0 Reflections: 0 Self Loopbacks Sent: 2 Self Loopbacks Rcvd: 0 Host NIC Address: 00:0C:29:59:50:83 Packets Sent: 4 Asynch Interrupts: Disabled Read Queue: Count: 0 Read Queue: High: 0 Read Queue: Loss: 0 Peak Write Queue Size: 1 sim> quit Goodbye NVR: writing buffer to file Eth: closed eth0 [root at dt558 /]# cat proc/version Linux version 2.6.18-164.el5 (mockbuild at x86-002.build.bos.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Aug 18 15:51:54 EDT 2009 Vax.ini : ; ;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 rauser=10240 set rq2 rauser=10240 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=00:1D:D8:B7:1C:00 set XQ type=DELQA attach XQ eth0 ; ;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 -Priya -------------- next part -------------- An HTML attachment was scrubbed... URL: From Mark at infocomm.com Tue Dec 31 18:19:47 2013 From: Mark at infocomm.com (Mark Pizzolato - Info Comm) Date: Tue, 31 Dec 2013 15:19:47 -0800 Subject: [Simh] EXT : Network Problem In-Reply-To: <9C9FDA2BCCFB5E4098DEB87AC47B94503E268384@XMBVAG73.northgrum.com> References: <9C9FDA2BCCFB5E4098DEB87AC47B94503E268384@XMBVAG73.northgrum.com> Message-ID: <0CC6789C1C831B4C8CCFF49D45D7010F0127D510517E@REDROOF2.alohasunset.com> Hi Priya, Dave may be right, BUT there still is something strange about your environment. Dave Johnson had suggested that you need to run as root. I don't think that your problem is due to the running as root issue since if that were the case "SHOW ETHERNET" usually wouldn't have mentioned eth0. The various attempts you made to install a libpcap development environment have left your system in a situation I'm explicitly removing support for going forward. The key information which is most likely the problem is: using libpcap: /usr/local/lib/libpcap.a /usr/local/include/pcap.h *** Warning *** *** Warning *** vax Simulator being built with networking support using *** Warning *** libpcap components from www.tcpdump.org. *** Warning *** Some users have had problems using the www.tcpdump.org libpcap *** Warning *** components for simh networking. For best results, with *** Warning *** simh networking, it is recommended that you install the *** Warning *** libpcap-dev package from your Linux distribution *** Warning *** *** Warning *** Building with the components manually installed from www.tcpdump.org *** Warning *** is officially deprecated. Attempting to do so is unsupported. It seems that the libpcap components you've built with were NOT directly provided by RedHat as part of their Linux distribution or it wouldn't have installed in /usr/local .... Some folks have mangled the working components of libpcap on their Linux systems by attempting to install various versions of non-OS-vendor supplied libpcap components. This mangling is why support for doing this that way has been officially deprecated. Your case has inspired me to take the time to completely remove this support for host platforms which have known good vendor supplied libpcap components (i.e. Linux). You should uninstall the package you found which dropped the libpcap pieces in /usr/local. I'm not a paid RedHat user and therefore don't have access to their customer portal to access their knowledgebase, however since you appear to be, you may want to look at the solution provided by: https://access.redhat.com/site/solutions/57913 Can you explicitly describe EXACTY what version of RedHat Linux you're working with and get back to me directly. I'll dig up libpcap directions for that platform and add it to the simh 0readme-ethernet.txt. Please get back to me. Thanks. - Mark Pizzolato From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-edge.com] On Behalf Of Hittner, David T (IS) Sent: Tuesday, December 31, 2013 8:11 AM To: Priya Chincholikar; simh at trailing-edge.com Subject: Re: [Simh] EXT : Network Problem Rerun @SYS$MANAGER:TCPIP$CONFIG to fix your TCPIP hardware interface definitions. The error is telling you that it can't find the VAX hardware device (no such device SE0) to attach (on the 4th line). The MicroVAX 3900 in the SIMH VAX does not have an SE0 interface, it has a QNA interface. I think SE0 was the built-in MicroVAX/VAXstation 3100 interface. Was this system disk originally used by a different VAX emulator (like Charon/SRI) or a different model of real VAX? Dave From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-edge.com] On Behalf Of Priya Chincholikar Sent: Tuesday, December 31, 2013 7:53 AM To: simh at trailing-edge.com Subject: EXT :[Simh] Network Problem Hi, I am trying boot a vax disk on SIMH and it keeps getting hung while starting network like TCP/IP. I have the required lipcap packages. My host is RedHat VM. The simulator was built with network support. *******INTERnet Started************** %UCX-I-DEFINTE, Defining interfaces %UCX-E-INVINTER, Error defining interface: SE0 -UCX-I-ACPQIO, Failure on Internet ACP QIO -SYSTEM-W-NOSUCHDEV, no such device available -SYSTEM-W-NOSUCHDEV, no such device available %UCX-E-INVINTERNAM, Invalid interface name -UCX-I-DRIVERQIO, Failure on Internet driver QIO -UCX-E-INVNETMASK, Invalid network mask %UCX-E-DELINTER, Error deleting interface: SE0 -UCX-I-ACPQIO, Failure on Internet ACP QIO ----> gets hung here usr/local/vax/bin/vax.ini-47> boot cpuname Simulation stopped, PC: 8358DF47 (BBC #3,26C(R3),8358DF9B) sim> This is the build: root at dt558 simh-master]# make vax lib paths are: /lib/ /usr/lib/ /usr/lib/qt-3.3/lib/ /usr/lib/sse2/ using libm: /usr/lib//libm.so using librt: /usr/lib//librt.so using libpthread: /usr/lib//libpthread.so /usr/include/pthread.h using libdl: /usr/lib//libdl.so /usr/include/dlfcn.h using libpcap: /usr/local/lib/libpcap.a /usr/local/include/pcap.h *** Warning *** *** Warning *** vax Simulator being built with networking support using *** Warning *** libpcap components from www.tcpdump.org. *** Warning *** Some users have had problems using the www.tcpdump.org libpcap *** Warning *** components for simh networking. For best results, with *** Warning *** simh networking, it is recommended that you install the *** Warning *** libpcap-dev package from your Linux distribution *** Warning *** *** Warning *** Building with the components manually installed from www.tcpdump.org *** Warning *** is officially deprecated. Attempting to do so is unsupported. *** Warning *** *** Warning *** *** Warning *** vax Simulator are being built with *** Warning *** minimal libpcap networking support *** Warning *** *** Warning *** Simulators on your Linux platform can also be built with *** Warning *** extended Ethernet networking support by using VDE Ethernet. *** Warning *** *** Warning *** To build simulator(s) with extended networking support you *** Warning *** should read 0readme_ethernet.txt and follow the instructions *** Warning *** regarding the needed libvdeplug components for your Linux *** Warning *** platform *** Warning *** *** *** vax Simulator being built with: *** - compiler optimizations and no debugging support. GCC Version: 4.1.2. *** - networking support using libpcap components from www.tcpdump.org. *** - Local LAN packet transports: PCAP TAP *** *** git commit id is 86e342501deaec3df79b31c13dd6d622938176e2. *** mkdir -p BIN gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fno-unsafe-loop-optimizations -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB sim_BuildROMs.c -o BIN/BuildROMs BIN/BuildROMs rm -f BIN/BuildROMs mkdir -p BIN gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fno-unsafe-loop-optimizations -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB VAX/vax_cpu.c VAX/vax_cpu1.c VAX/vax_fpa.c VAX/vax_io.c VAX/vax_cis.c VAX/vax_octa.c VAX/vax_cmode.c VAX/vax_mmu.c VAX/vax_stddev.c VAX/vax_sysdev.c VAX/vax_sys.c VAX/vax_syscm.c VAX/vax_syslist.c PDP11/pdp11_rl.c PDP11/pdp11_rq.c PDP11/pdp11_ts.c PDP11/pdp11_dz.c PDP11/pdp11_lp.c PDP11/pdp11_tq.c PDP11/pdp11_xq.c PDP11/pdp11_vh.c PDP11/pdp11_cr.c PDP11/pdp11_io_lib.c scp.c sim_console.c sim_fio.c sim_timer.c sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c sim_disk.c sim_serial.c sim_video.c -DVM_VAX -DUSE_INT64 -DUSE_ADDR64 -I VAX -I PDP11 -DUSE_NETWORK -DHAVE_PCAP_NETWORK -isystem -I/usr/local/include/ /usr/local/lib/libpcap.a -DHAVE_TAP_NETWORK -o BIN/microvax3900 -lm -lrt -lpthread -ldl cp BIN/microvax3900 BIN/vax Show version and show ethernet : 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. >>>usr/local/vax/bin/vax.ini-47> boot cpu Simulation stopped, PC: 20043601 (BSBW 2004367B) sim> sh ver MicroVAX 3900 simulator V4.0-0 Beta Simulator Framework Capabilities: 64b data 64b addresses Ethernet Packet transport:PCAP:TAP:UDP Idle/Throttling support is available Virtual Hard Disk (VHD) support RAW disk and CD/DVD ROM support Asynchronous I/O support Host Platform: Compiler: GCC 4.1.2 20080704 (Red Hat 4.1.2-46) Simulator Compiled: Dec 30 2013 at 17:52:32 Memory Access: Little Endian Memory Pointer Size: 32 bits Large File (>2GB) support OS clock tick size: 3ms OS: Linux dt558.***.com 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:54 EDT 2009 i686 i686 i386 GNU/Linux git commit id: 86e34250 sim> sh eth ETH devices: eth0 eth0 (No description available) eth1 tap:tapN (Integrated Tun/Tap support) eth2 udp:sourceport:remotehost:remoteport (Integrated UDP bridge support) Open ETH Devices: XQ eth0 (No description available) Ethernet Device: Name: eth0 Reflections: 0 Self Loopbacks Sent: 2 Self Loopbacks Rcvd: 0 Host NIC Address: 00:0C:29:59:50:83 Packets Sent: 4 Asynch Interrupts: Disabled Read Queue: Count: 0 Read Queue: High: 0 Read Queue: Loss: 0 Peak Write Queue Size: 1 sim> quit Goodbye NVR: writing buffer to file Eth: closed eth0 [root at dt558 /]# cat proc/version Linux version 2.6.18-164.el5 (mockbuild at x86-002.build.bos.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Aug 18 15:51:54 EDT 2009 Vax.ini : ; ;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 rauser=10240 set rq2 rauser=10240 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=00:1D:D8:B7:1C:00 set XQ type=DELQA attach XQ eth0 ; ;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 -Priya -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Thu Dec 5 23:03:22 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Thu, 5 Dec 2013 23:03:22 -0500 Subject: [Simh] Networking and SIMH Message-ID: Hello! Okay so I've managed to install the VDE components and the PCAP development components on my Raspberry Pi. Invoking make caused the build system to "choose" the VDE components. Why? When both are present I figured it would chose both rather then the one I'm not familiar with. In any case I know I can work with what the methods chose and eventually accomplish what I am planning on doing with the appropriate simulators. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From Mark at infocomm.com Fri Dec 6 05:21:35 2013 From: Mark at infocomm.com (Mark Pizzolato - Info Comm) Date: Fri, 6 Dec 2013 02:21:35 -0800 Subject: [Simh] Networking and SIMH In-Reply-To: References: Message-ID: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> Hi Gregg, On Thursday, December 05, 2013 at 8:03 PM, Gregg Levine wrote: > Okay so I've managed to install the VDE components and the PCAP > development components on my Raspberry Pi. Invoking make caused the > build system to "choose" the VDE components. Why? When both are > present I figured it would chose both rather then the one I'm not familiar > with. > > In any case I know I can work with what the methods chose and eventually > accomplish what I am planning on doing with the appropriate simulators. The build It is not an either or process. It will build using whatever Ethernet transports methods are available on the local environment when the build is done and each of those may be available when running with the simulator you built. As I recall, when I did this on the Raspberry Pi, I didn't have to look for libpcap-dev for that platform, I believe it was packaged with the OS. If /usr/include/pcap.h exists AND libpcap's shared object is available on the system (i.e. if tcpdump works) that is sufficient to build (and later use at runtime) with libpcap support. You don't explain how you think it chose just VDE rather than both. If you provide the output that make produced while building the simulator it will be more clear what capabilities are being built in. Meanwhile, to use one Ethernet transport method over another at run time will depend on several different goals. You need to be running as root on any Linux platform in order to inject packets into the network using libpcap. On the other hand, using VDE you can run as a normal unprivileged user as long as the VDE environment is already setup by some components running as root (maybe startup scripts, etc...). The simulator's "show xq ether" command will list the Ethernet transports which can be used by the process issuing that command. You would see different output if you were running as root. Additionally, you may or may not desire to have the simulated system actually be able to speak (exchange IP packets) with the host it is running on. If that is a goal, then on Linux you can't do that directly with libpcap. If that is a goal, then VDE can help you or you can build your own internal bridge with kernel bridging and tun/tap network interfaces. - Mark From dundas at caltech.edu Fri Dec 6 11:17:48 2013 From: dundas at caltech.edu (John A. Dundas III) Date: Fri, 6 Dec 2013 08:17:48 -0800 Subject: [Simh] PDP-11: CSM bug and fix Message-ID: Bob and all, I ran across what I believe to be a bug in the CSM code: case 070: /* CSM */ if (CPUT (HAS_CSM) && (MMR3 & MMR3_CSM) || (cm != MD_KER)) { According to the Architecture Handbook, CSM may be executed only if the MMR3 bit is set AND the mode is not Kernel. Changing the code to: case 070: /* CSM */ if (CPUT (HAS_CSM) && (MMR3 & MMR3_CSM) && (cm != MD_KER)) { also has the effect of making the ZKDKB0 diagnostic much happier. Thanks, John -- John A. Dundas III Director, IMSS Voice & Data Networks, Caltech Mail Code: 1-10, Pasadena, CA 91125 Phone: 626.395.3392 FAX: 626.395.2122 From bqt at softjar.se Fri Dec 6 11:55:16 2013 From: bqt at softjar.se (Johnny Billquist) Date: Fri, 06 Dec 2013 17:55:16 +0100 Subject: [Simh] Networking and SIMH In-Reply-To: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> References: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> Message-ID: <52A20174.4070302@softjar.se> On 2013-12-06 11:21, Mark Pizzolato - Info Comm wrote: > Hi Gregg, > > On Thursday, December 05, 2013 at 8:03 PM, Gregg Levine wrote: >> Okay so I've managed to install the VDE components and the PCAP >> development components on my Raspberry Pi. Invoking make caused the >> build system to "choose" the VDE components. Why? When both are >> present I figured it would chose both rather then the one I'm not familiar >> with. >> >> In any case I know I can work with what the methods chose and eventually >> accomplish what I am planning on doing with the appropriate simulators. > > The build It is not an either or process. It will build using whatever Ethernet transports methods are available on the local environment when the build is done and each of those may be available when running with the simulator you built. > > As I recall, when I did this on the Raspberry Pi, I didn't have to look for libpcap-dev for that platform, I believe it was packaged with the OS. If /usr/include/pcap.h exists AND libpcap's shared object is available on the system (i.e. if tcpdump works) that is sufficient to build (and later use at runtime) with libpcap support. > > You don't explain how you think it chose just VDE rather than both. If you provide the output that make produced while building the simulator it will be more clear what capabilities are being built in. > > Meanwhile, to use one Ethernet transport method over another at run time will depend on several different goals. You need to be running as root on any Linux platform in order to inject packets into the network using libpcap. You need to be running as root to even sniff packets with pcap. Johnny From gregg.drwho8 at gmail.com Fri Dec 6 12:13:57 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Fri, 6 Dec 2013 12:13:57 -0500 Subject: [Simh] Networking and SIMH In-Reply-To: <52A20174.4070302@softjar.se> References: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> <52A20174.4070302@softjar.se> Message-ID: Hello! Correct on that point Johnny. Mark, where do you want the build activity posted? Here? To the Git server's pages? I'll rebuild everything, and this time with the script mechanism writing down what happened. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." On Fri, Dec 6, 2013 at 11:55 AM, Johnny Billquist wrote: > On 2013-12-06 11:21, Mark Pizzolato - Info Comm wrote: >> >> Hi Gregg, >> >> On Thursday, December 05, 2013 at 8:03 PM, Gregg Levine wrote: >>> >>> Okay so I've managed to install the VDE components and the PCAP >>> development components on my Raspberry Pi. Invoking make caused the >>> build system to "choose" the VDE components. Why? When both are >>> present I figured it would chose both rather then the one I'm not >>> familiar >>> with. >>> >>> In any case I know I can work with what the methods chose and eventually >>> accomplish what I am planning on doing with the appropriate simulators. >> >> >> The build It is not an either or process. It will build using whatever >> Ethernet transports methods are available on the local environment when the >> build is done and each of those may be available when running with the >> simulator you built. >> >> As I recall, when I did this on the Raspberry Pi, I didn't have to look >> for libpcap-dev for that platform, I believe it was packaged with the OS. >> If /usr/include/pcap.h exists AND libpcap's shared object is available on >> the system (i.e. if tcpdump works) that is sufficient to build (and later >> use at runtime) with libpcap support. >> >> You don't explain how you think it chose just VDE rather than both. If >> you provide the output that make produced while building the simulator it >> will be more clear what capabilities are being built in. >> >> Meanwhile, to use one Ethernet transport method over another at run time >> will depend on several different goals. You need to be running as root on >> any Linux platform in order to inject packets into the network using >> libpcap. > > > You need to be running as root to even sniff packets with pcap. > > Johnny > > _______________________________________________ > Simh mailing list > Simh at trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh From Mark at infocomm.com Fri Dec 6 12:26:18 2013 From: Mark at infocomm.com (Mark Pizzolato - Info Comm) Date: Fri, 6 Dec 2013 09:26:18 -0800 Subject: [Simh] Networking and SIMH In-Reply-To: References: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> <52A20174.4070302@softjar.se> Message-ID: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1B2@REDROOF2.alohasunset.com> On Friday, December 06, 2013 at 9:14 AM, Gregg Levine wrote: > Mark, where do you want the build activity posted? Here? To the Git server's > pages? I'll rebuild everything, and this time with the script mechanism writing > down what happened. Hi Gregg, Please create an issue at https://github.com/simh/simh/issues to contain the build activity and any further discussion on this problem. Please restate what you've already said while creating that issue. Thanks. - Mark From aek at bitsavers.org Fri Dec 6 12:30:03 2013 From: aek at bitsavers.org (Al Kossow) Date: Fri, 06 Dec 2013 09:30:03 -0800 Subject: [Simh] Networking and SIMH In-Reply-To: References: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> <52A20174.4070302@softjar.se> Message-ID: <52A2099B.5070003@bitsavers.org> On 12/6/13 9:13 AM, Gregg Levine wrote: > Mark, where do you want the build activity posted? I had been wondering about this for a while. Is most of the SIMH development discussion done off-list? There seems to be very few posts here, and nothing at all on simh-dev (unless I'm looking in the wrong place). One of the things I like to do is monitor mailing lists watching for people asking about documentation, since I have lots of it queued up, but prioritize based on what people seem to be looking for. "Marty" looking for better copies of the 11/40 print set on the vcforum is an example. I've been trying to clear my backlog of PDP-10 and 11 datacomm stuff recently. I just put the AN10 drawings up this morning. Best way to see what's new is to look at http://user.xmission.com/~legalize/vintage/bitsavers-pdf.xml to see when the uploads make it out to the mirrors. From Mark at infocomm.com Fri Dec 6 12:45:27 2013 From: Mark at infocomm.com (Mark Pizzolato - Info Comm) Date: Fri, 6 Dec 2013 09:45:27 -0800 Subject: [Simh] Networking and SIMH In-Reply-To: <52A2099B.5070003@bitsavers.org> References: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1A3@REDROOF2.alohasunset.com> <52A20174.4070302@softjar.se> <52A2099B.5070003@bitsavers.org> Message-ID: <0CC6789C1C831B4C8CCFF49D45D7010FDF9890B1B4@REDROOF2.alohasunset.com> On Friday, December 06, 2013 at 9:30 AM, Al Kossow wrote: > On 12/6/13 9:13 AM, Gregg Levine wrote: > > > Mark, where do you want the build activity posted? > > I had been wondering about this for a while. Is most of the SIMH > development discussion done off-list? There seems to be very few posts > here, and nothing at all on simh-dev (unless I'm looking in the wrong place). Well, I'm looking for bug reports and/or enhancement requests to be tracked and discussed proximate to the repository containing the source. When folks ask questions on the simh list which potentially need code changes, I try to encourage that to create issues in the github repository issue system. I qualify this statement to exclude issues which are obviously going to solicit an answer from Bob (John Dundas's message today "[Simh] PDP-11: CSM bug and fix" is an example of that). If any issues are create on the github issue system which Bob would be the obvious authority for, or if his input would be valuable, I point him at the issue. Anyone can subscribe to get updates from the github system via an RSS feed. > One of the things I like to do is monitor mailing lists watching for people > asking about documentation, since I have lots of it queued up, but prioritize > based on what people seem to be looking for. "Marty" looking for better > copies of the 11/40 print set on the vcforum is an example. No issues have been raised on the issue system about documentation. If there were, I'd redirect those issues to the simh list. - Mark From j_hoppe at t-online.de Tue Dec 17 15:28:32 2013 From: j_hoppe at t-online.de (=?ISO-8859-15?Q?J=F6rg_Hoppe?=) Date: Tue, 17 Dec 2013 21:28:32 +0100 Subject: [Simh] Database of PDP-11 diagnostics Message-ID: <52B0B3F0.1070504@t-online.de> Hi all, a new database about all PDP-11 diagnostics went online this week: http://www.retrocmp.com/tools/pdp-11-diagnostic-database The database contains - a list of all known PDP-11 / MAINDEC / X11 / XXDP diagnostic modules - links to all kind of bitsavers files: manual pages, binary files, media images, listing scans, file images, and indexes - a list of all tested devices All in all there are several thousand data items, and all are linked with each other. Enjoy! Joerg From frisbie at flying-disk.com Tue Dec 17 16:16:12 2013 From: frisbie at flying-disk.com (Alan Frisbie) Date: Tue, 17 Dec 2013 13:16:12 -0800 (PST) Subject: [Simh] Database of PDP-11 diagnostics Message-ID: <13121713161240_448@slug.flying-disk.com> > a new database about all PDP-11 diagnostics went online this week: > http://www.retrocmp.com/tools/pdp-11-diagnostic-database > > The database contains > - a list of all known PDP-11 / MAINDEC / X11 / XXDP diagnostic modules > - links to all kind of bitsavers files: manual pages, binary files, > media images, listing scans, file images, and indexes > - a list of all tested devices Wow! This is fantastic. Thank you (and everyone else who made this possible) very much. It is a valuable resource. Alan Frisbie From aek at bitsavers.org Tue Dec 17 17:10:55 2013 From: aek at bitsavers.org (Al Kossow) Date: Tue, 17 Dec 2013 14:10:55 -0800 Subject: [Simh] Database of PDP-11 diagnostics In-Reply-To: <13121713161240_448@slug.flying-disk.com> References: <13121713161240_448@slug.flying-disk.com> Message-ID: <52B0CBEF.2080008@bitsavers.org> On 12/17/13 1:16 PM, Alan Frisbie wrote: > Wow! This is fantastic. Thank you (and everyone else who > made this possible) very much. It is a valuable resource. > If anyone turns up any other listings that haven't been scanned, I would like to add them to bitsavers. TM03 diags will be doing up soon, but I would like to find the writeups for the Massbus disks as well. From frisbie at flying-disk.com Tue Dec 17 19:52:57 2013 From: frisbie at flying-disk.com (Alan Frisbie) Date: Tue, 17 Dec 2013 16:52:57 -0800 (PST) Subject: [Simh] Database of PDP-11 diagnostics Message-ID: <13121716525743_448@slug.flying-disk.com> > If anyone turns up any other listings that haven't been scanned, > I would like to add them to bitsavers. I just acquired a bunch of Q-bus related XXDP listings from the family of a deceased friend. Actually, I acquired two storage units full of "stuff". I'll be going through it over the next few months to make sure it all goes to a good home. The guy liked to make copies of every manual he owned, so there are lots to go around. I'll post a list to the SIMH mailing list, but would appreciate other suggestions. There is lots of hardware too. Anyone need DHV11 cabinet kits? There must be at least 30 Q-bus cards in nice anti-static boxes. Alan Frisbie From priyachinc at gmail.com Wed Dec 18 06:27:37 2013 From: priyachinc at gmail.com (Priya Chincholikar) Date: Wed, 18 Dec 2013 16:57:37 +0530 Subject: [Simh] Ethernet connection problems Message-ID: Hi, I'm installing SIMH on RedHat VM. I seem to have Ethernet connection problems. # usr/local/vax/bin/vax MicroVAX 3900 simulator V4.0-0 Beta git commit id: 25a62c28 NVR: buffering file in memory usr/local/vax/bin/vax.ini-34> attach XQ eth0 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. >>>usr/local/vax/bin/vax.ini-47> boot cpu *I did ^E here* Simulation stopped, PC: 20043601 (BSBW 2004367B) sim> sh ver MicroVAX 3900 simulator V4.0-0 Beta Simulator Framework Capabilities: 64b data 64b addresses no Ethernet Idle/Throttling support is available Virtual Hard Disk (VHD) support RAW disk and CD/DVD ROM support Asynchronous I/O support Host Platform: Compiler: GCC 4.1.1 20070105 (Red Hat 4.1.1-52) Simulator Compiled: Dec 12 2013 at 00:20:12 Memory Access: Little Endian Memory Pointer Size: 32 bits Large File (>2GB) support OS clock tick size: 2ms OS: Linux dt558.**.com 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:21 EST 2007 i686 i686 i386 GNU/Linux git commit id: 25a62c28 sim> show ethernet ETH devices: network support not available in simulator sim> quit Goodbye NVR: writing buffer to file The host is : # cat /proc/version Linux version 2.6.18-8.el5 (brewbuilder at ls20-bc2-14.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP Fri Jan 26 14:15:21 EST 2007 VAX.INI ; ; 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 rauser=10240 set rq2 rauser=10240 set rq3 cdrom ; ; Attach defined drives to local files attach rq0 /mnt/simh-disks/d0.dsk attach rq1 /mnt/simh-disks/d1.dsk attach rq2 /mnt/simh-disks/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 eth0 ; ;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 ~ The steps I followed for installing of the emulator are: $ wget *https://github.com/simh/simh/archive/master.zip* $ unzip simh-master.zip $ cd simh-master $ make vax -------------- next part -------------- An HTML attachment was scrubbed... URL: From Mark at infocomm.com Wed Dec 18 06:41:39 2013 From: Mark at infocomm.com (Mark Pizzolato - Info Comm) Date: Wed, 18 Dec 2013 03:41:39 -0800 Subject: [Simh] Ethernet connection problems In-Reply-To: References: Message-ID: <0CC6789C1C831B4C8CCFF49D45D7010F0127D51050E3@REDROOF2.alohasunset.com> Hi Priya, Hmmm... There was a fix checked into the github repository about 21 hours ago which fixed an Ethernet issue and which the version you've built does not contain. You will definitely need the latest code, However, that doesn't seem to be the issue you are encountering. It seems you've built a simulator without support for libpcap. The output produced when you performed 'make vax' would be more informative regarding this. It probably suggests that you need to install the libpcap-dev package for your simulator to have Ethernet support... If after considering this, you still have a problem, please open an issue at https://github.com/simh/simh/issues. - Mark From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-edge.com] On Behalf Of Priya Chincholikar Sent: Wednesday, December 18, 2013 3:28 AM To: simh at trailing-edge.com Subject: [Simh] Ethernet connection problems Hi, I'm installing SIMH on RedHat VM. I seem to have Ethernet connection problems. # usr/local/vax/bin/vax MicroVAX 3900 simulator V4.0-0 Beta git commit id: 25a62c28 NVR: buffering file in memory usr/local/vax/bin/vax.ini-34> attach XQ eth0 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. >>>usr/local/vax/bin/vax.ini-47> boot cpu *I did ^E here* Simulation stopped, PC: 20043601 (BSBW 2004367B) sim> sh ver MicroVAX 3900 simulator V4.0-0 Beta Simulator Framework Capabilities: 64b data 64b addresses no Ethernet Idle/Throttling support is available Virtual Hard Disk (VHD) support RAW disk and CD/DVD ROM support Asynchronous I/O support Host Platform: Compiler: GCC 4.1.1 20070105 (Red Hat 4.1.1-52) Simulator Compiled: Dec 12 2013 at 00:20:12 Memory Access: Little Endian Memory Pointer Size: 32 bits Large File (>2GB) support OS clock tick size: 2ms OS: Linux dt558.**.com 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:21 EST 2007 i686 i686 i386 GNU/Linux git commit id: 25a62c28 sim> show ethernet ETH devices: network support not available in simulator sim> quit Goodbye NVR: writing buffer to file The host is : # cat /proc/version Linux version 2.6.18-8.el5 (brewbuilder at ls20-bc2-14.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP Fri Jan 26 14:15:21 EST 2007 VAX.INI ; ; 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 rauser=10240 set rq2 rauser=10240 set rq3 cdrom ; ; Attach defined drives to local files attach rq0 /mnt/simh-disks/d0.dsk attach rq1 /mnt/simh-disks/d1.dsk attach rq2 /mnt/simh-disks/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 eth0 ; ;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 ~ The steps I followed for installing of the emulator are: $ wget https://github.com/simh/simh/archive/master.zip $ unzip simh-master.zip $ cd simh-master $ make vax -------------- next part -------------- An HTML attachment was scrubbed... URL: From bqt at softjar.se Wed Dec 18 06:42:59 2013 From: bqt at softjar.se (Johnny Billquist) Date: Wed, 18 Dec 2013 12:42:59 +0100 Subject: [Simh] Ethernet connection problems In-Reply-To: References: Message-ID: <52B18A43.1000800@softjar.se> Hi. On 2013-12-18 12:27, Priya Chincholikar wrote: > Hi, > > I'm installing SIMH on RedHat VM. I seem to have Ethernet connection > problems. > > > # usr/local/vax/bin/vax > > MicroVAX 3900 simulator V4.0-0 Beta git commit id: 25a62c28 > NVR: buffering file in memory > usr/local/vax/bin/vax.ini-34> attach XQ eth0 > Command not allowed ^^^^^^^^ This is your obvious problem. Others might have more useful comments here, but looking at the config file: > ; Attach Ethernet to a network interface > set XQ mac=08-00-2B-AC-AC-B1 > set XQ type=DELQA > attach XQ eth0 I'm not sure if XQ is enabled by default or not. You could try adding set XQ enable. Other than that, I would possibly suspect that it didn't manage to build with ethernet support. Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol From priyachinc at gmail.com Tue Dec 31 07:52:53 2013 From: priyachinc at gmail.com (Priya Chincholikar) Date: Tue, 31 Dec 2013 18:22:53 +0530 Subject: [Simh] Network Problem Message-ID: Hi, I am trying boot a vax disk on SIMH and it keeps getting hung while starting network like TCP/IP. I have the required lipcap packages. My host is RedHat VM. The simulator was built with network support. *******INTERnet Started************** %UCX-I-DEFINTE, Defining interfaces %UCX-E-INVINTER, Error defining interface: SE0 -UCX-I-ACPQIO, Failure on Internet ACP QIO -SYSTEM-W-NOSUCHDEV, no such device available -SYSTEM-W-NOSUCHDEV, no such device available %UCX-E-INVINTERNAM, Invalid interface name -UCX-I-DRIVERQIO, Failure on Internet driver QIO -UCX-E-INVNETMASK, Invalid network mask %UCX-E-DELINTER, Error deleting interface: SE0 -UCX-I-ACPQIO, Failure on Internet ACP QIO ----> gets hung here usr/local/vax/bin/vax.ini-47> boot cpuname Simulation stopped, PC: 8358DF47 (BBC #3,26C(R3),8358DF9B) sim> *This is the build*: root at dt558 simh-master]# make vax lib paths are: /lib/ /usr/lib/ /usr/lib/qt-3.3/lib/ /usr/lib/sse2/ using libm: /usr/lib//libm.so using librt: /usr/lib//librt.so using libpthread: /usr/lib//libpthread.so /usr/include/pthread.h using libdl: /usr/lib//libdl.so /usr/include/dlfcn.h using libpcap: /usr/local/lib/libpcap.a /usr/local/include/pcap.h *** Warning *** *** Warning *** vax Simulator being built with networking support using *** Warning *** libpcap components from www.tcpdump.org. *** Warning *** Some users have had problems using the www.tcpdump.orglibpcap *** Warning *** components for simh networking. For best results, with *** Warning *** simh networking, it is recommended that you install the *** Warning *** libpcap-dev package from your Linux distribution *** Warning *** *** Warning *** Building with the components manually installed from www.tcpdump.org *** Warning *** is officially deprecated. Attempting to do so is unsupported. *** Warning *** *** Warning *** *** Warning *** vax Simulator are being built with *** Warning *** minimal libpcap networking support *** Warning *** *** Warning *** Simulators on your Linux platform can also be built with *** Warning *** extended Ethernet networking support by using VDE Ethernet. *** Warning *** *** Warning *** To build simulator(s) with extended networking support you *** Warning *** should read 0readme_ethernet.txt and follow the instructions *** Warning *** regarding the needed libvdeplug components for your Linux *** Warning *** platform *** Warning *** *** *** vax Simulator being built with: *** - compiler optimizations and no debugging support. GCC Version: 4.1.2. *** - networking support using libpcap components from www.tcpdump.org. *** - Local LAN packet transports: PCAP TAP *** *** git commit id is 86e342501deaec3df79b31c13dd6d622938176e2. *** mkdir -p BIN gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fno-unsafe-loop-optimizations -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB sim_BuildROMs.c -o BIN/BuildROMs BIN/BuildROMs rm -f BIN/BuildROMs mkdir -p BIN gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fno-unsafe-loop-optimizations -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB VAX/vax_cpu.c VAX/vax_cpu1.c VAX/vax_fpa.c VAX/vax_io.c VAX/vax_cis.c VAX/vax_octa.c VAX/vax_cmode.c VAX/vax_mmu.c VAX/vax_stddev.c VAX/vax_sysdev.c VAX/vax_sys.c VAX/vax_syscm.c VAX/vax_syslist.c PDP11/pdp11_rl.c PDP11/pdp11_rq.c PDP11/pdp11_ts.c PDP11/pdp11_dz.c PDP11/pdp11_lp.c PDP11/pdp11_tq.c PDP11/pdp11_xq.c PDP11/pdp11_vh.c PDP11/pdp11_cr.c PDP11/pdp11_io_lib.c scp.c sim_console.c sim_fio.c sim_timer.c sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c sim_disk.c sim_serial.c sim_video.c -DVM_VAX -DUSE_INT64 -DUSE_ADDR64 -I VAX -I PDP11 -DUSE_NETWORK -DHAVE_PCAP_NETWORK -isystem -I/usr/local/include/ /usr/local/lib/libpcap.a -DHAVE_TAP_NETWORK -o BIN/microvax3900 -lm -lrt -lpthread -ldl cp BIN/microvax3900 BIN/vax *Show version and show ethernet :* 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. >>>usr/local/vax/bin/vax.ini-47> boot cpu Simulation stopped, PC: 20043601 (BSBW 2004367B) sim> sh ver MicroVAX 3900 simulator V4.0-0 Beta Simulator Framework Capabilities: 64b data 64b addresses Ethernet Packet transport:PCAP:TAP:UDP Idle/Throttling support is available Virtual Hard Disk (VHD) support RAW disk and CD/DVD ROM support Asynchronous I/O support Host Platform: Compiler: GCC 4.1.2 20080704 (Red Hat 4.1.2-46) Simulator Compiled: Dec 30 2013 at 17:52:32 Memory Access: Little Endian Memory Pointer Size: 32 bits Large File (>2GB) support OS clock tick size: 3ms OS: Linux dt558.***.com 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:54 EDT 2009 i686 i686 i386 GNU/Linux git commit id: 86e34250 sim> sh eth ETH devices: eth0 eth0 (No description available) eth1 tap:tapN (Integrated Tun/Tap support) eth2 udp:sourceport:remotehost:remoteport (Integrated UDP bridge support) Open ETH Devices: XQ eth0 (No description available) Ethernet Device: Name: eth0 Reflections: 0 Self Loopbacks Sent: 2 Self Loopbacks Rcvd: 0 Host NIC Address: 00:0C:29:59:50:83 Packets Sent: 4 Asynch Interrupts: Disabled Read Queue: Count: 0 Read Queue: High: 0 Read Queue: Loss: 0 Peak Write Queue Size: 1 sim> quit Goodbye NVR: writing buffer to file Eth: closed eth0 [root at dt558 /]# cat proc/version Linux version 2.6.18-164.el5 (mockbuild at x86-002.build.bos.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Aug 18 15:51:54 EDT 2009 *Vax.ini :* ; ;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 rauser=10240 set rq2 rauser=10240 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=00:1D:D8:B7:1C:00 set XQ type=DELQA attach XQ eth0 ; ;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 -Priya -------------- next part -------------- An HTML attachment was scrubbed... URL: From johnsong at gregjohnson.org Tue Dec 31 09:59:53 2013 From: johnsong at gregjohnson.org (Greg Johnson) Date: Tue, 31 Dec 2013 06:59:53 -0800 Subject: [Simh] Network Problem In-Reply-To: References: Message-ID: <52C2DBE9.6060802@gregjohnson.org> Are you running it as 'root'? I believe that under Linux you need to run simh as root to place the network connection in the right mode for networking. On 12/31/2013 4:52 AM, Priya Chincholikar wrote: > > > Hi, > > I am trying boot a vax disk on SIMH and it keeps getting hung while > starting network like TCP/IP. > I have the required lipcap packages. My host is RedHat VM. The > simulator was built with network support. > > *******INTERnet Started************** > > %UCX-I-DEFINTE, Defining interfaces > %UCX-E-INVINTER, Error defining interface: SE0 > -UCX-I-ACPQIO, Failure on Internet ACP QIO > -SYSTEM-W-NOSUCHDEV, no such device available > -SYSTEM-W-NOSUCHDEV, no such device available > %UCX-E-INVINTERNAM, Invalid interface name > -UCX-I-DRIVERQIO, Failure on Internet driver QIO > -UCX-E-INVNETMASK, Invalid network mask > %UCX-E-DELINTER, Error deleting interface: SE0 > -UCX-I-ACPQIO, Failure on Internet ACP QIO ---->gets hung here > usr/local/vax/bin/vax.ini-47> boot cpuname > > Simulation stopped, PC: 8358DF47 (BBC #3,26C(R3),8358DF9B) > sim> > > *This is the build*: > > root at dt558 simh-master]# make vax > lib paths are: /lib/ /usr/lib/ /usr/lib/qt-3.3/lib/ /usr/lib/sse2/ > using libm: /usr/lib//libm.so > using librt: /usr/lib//librt.so > using libpthread: /usr/lib//libpthread.so /usr/include/pthread.h > using libdl: /usr/lib//libdl.so /usr/include/dlfcn.h > using libpcap: /usr/local/lib/libpcap.a /usr/local/include/pcap.h > *** Warning *** > *** Warning *** vax Simulator being built with networking support using > *** Warning *** libpcap components from www.tcpdump.org > . > *** Warning *** Some users have had problems using the www.tcpdump.org > libpcap > *** Warning *** components for simh networking. For best results, with > *** Warning *** simh networking, it is recommended that you install the > *** Warning *** libpcap-dev package from your Linux distribution > *** Warning *** > *** Warning *** Building with the components manually installed from > www.tcpdump.org > *** Warning *** is officially deprecated. Attempting to do so is > unsupported. > *** Warning *** > *** Warning *** > *** Warning *** vax Simulator are being built with > *** Warning *** minimal libpcap networking support > *** Warning *** > *** Warning *** Simulators on your Linux platform can also be built with > *** Warning *** extended Ethernet networking support by using VDE > Ethernet. > *** Warning *** > *** Warning *** To build simulator(s) with extended networking support you > *** Warning *** should read 0readme_ethernet.txt and follow the > instructions > *** Warning *** regarding the needed libvdeplug components for your Linux > *** Warning *** platform > *** Warning *** > *** > *** vax Simulator being built with: > *** - compiler optimizations and no debugging support. GCC Version: 4.1.2. > *** - networking support using libpcap components from www.tcpdump.org > . > *** - Local LAN packet transports: PCAP TAP > *** > *** git commit id is 86e342501deaec3df79b31c13dd6d622938176e2. > *** > mkdir -p BIN > gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions > -fgcse-after-reload -fno-unsafe-loop-optimizations > -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 > -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE > -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB > sim_BuildROMs.c -o BIN/BuildROMs > BIN/BuildROMs > rm -f BIN/BuildROMs > mkdir -p BIN > gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions > -fgcse-after-reload -fno-unsafe-loop-optimizations > -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 > -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE > -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB > VAX/vax_cpu.c VAX/vax_cpu1.c VAX/vax_fpa.c VAX/vax_io.c VAX/vax_cis.c > VAX/vax_octa.c VAX/vax_cmode.c VAX/vax_mmu.c VAX/vax_stddev.c > VAX/vax_sysdev.c VAX/vax_sys.c VAX/vax_syscm.c VAX/vax_syslist.c > PDP11/pdp11_rl.c PDP11/pdp11_rq.c PDP11/pdp11_ts.c PDP11/pdp11_dz.c > PDP11/pdp11_lp.c PDP11/pdp11_tq.c PDP11/pdp11_xq.c PDP11/pdp11_vh.c > PDP11/pdp11_cr.c PDP11/pdp11_io_lib.c scp.c sim_console.c sim_fio.c > sim_timer.c sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c sim_disk.c > sim_serial.c sim_video.c -DVM_VAX -DUSE_INT64 -DUSE_ADDR64 -I VAX -I > PDP11 -DUSE_NETWORK -DHAVE_PCAP_NETWORK -isystem -I/usr/local/include/ > /usr/local/lib/libpcap.a -DHAVE_TAP_NETWORK -o BIN/microvax3900 -lm > -lrt -lpthread -ldl > cp BIN/microvax3900 BIN/vax > > > *Show version and show ethernet :* > > 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. > >>>usr/local/vax/bin/vax.ini-47> boot cpu > > Simulation stopped, PC: 20043601 (BSBW 2004367B) > sim> sh ver > MicroVAX 3900 simulator V4.0-0 Beta > Simulator Framework Capabilities: > 64b data > 64b addresses > Ethernet Packet transport:PCAP:TAP:UDP > Idle/Throttling support is available > Virtual Hard Disk (VHD) support > RAW disk and CD/DVD ROM support > Asynchronous I/O support > Host Platform: > Compiler: GCC 4.1.2 20080704 (Red Hat 4.1.2-46) > Simulator Compiled: Dec 30 2013 at 17:52:32 > Memory Access: Little Endian > Memory Pointer Size: 32 bits > Large File (>2GB) support > OS clock tick size: 3ms > OS: Linux dt558.***.com 2.6.18-164.el5 #1 SMP Tue Aug > 18 15:51:54 EDT 2009 i686 i686 i386 GNU/Linux > > git commit id: 86e34250 > sim> sh eth > ETH devices: > eth0 eth0 (No description available) > eth1 tap:tapN (Integrated Tun/Tap support) > eth2 udp:sourceport:remotehost:remoteport (Integrated UDP bridge support) > Open ETH Devices: > XQ eth0 (No description available) > Ethernet Device: > Name: eth0 > Reflections: 0 > Self Loopbacks Sent: 2 > Self Loopbacks Rcvd: 0 > Host NIC Address: 00:0C:29:59:50:83 > Packets Sent: 4 > Asynch Interrupts: Disabled > Read Queue: Count: 0 > Read Queue: High: 0 > Read Queue: Loss: 0 > Peak Write Queue Size: 1 > sim> quit > Goodbye > NVR: writing buffer to file > Eth: closed eth0 > > [root at dt558 /]# cat proc/version > Linux version 2.6.18-164.el5 (mockbuild at x86-002.build.bos.redhat.com > ) (gcc version 4.1.2 > 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Aug 18 15:51:54 EDT 2009 > > *Vax.ini :* > ; > ;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 rauser=10240 > set rq2 rauser=10240 > 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=00:1D:D8:B7:1C:00 > set XQ type=DELQA > attach XQ eth0 > ; > ;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 > > -Priya > > > _______________________________________________ > Simh mailing list > Simh at trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.hittner at ngc.com Tue Dec 31 11:10:45 2013 From: david.hittner at ngc.com (Hittner, David T (IS)) Date: Tue, 31 Dec 2013 16:10:45 +0000 Subject: [Simh] EXT : Network Problem In-Reply-To: References: Message-ID: <9C9FDA2BCCFB5E4098DEB87AC47B94503E268384@XMBVAG73.northgrum.com> Rerun @SYS$MANAGER:TCPIP$CONFIG to fix your TCPIP hardware interface definitions. The error is telling you that it can't find the VAX hardware device (no such device SE0) to attach (on the 4th line). The MicroVAX 3900 in the SIMH VAX does not have an SE0 interface, it has a QNA interface. I think SE0 was the built-in MicroVAX/VAXstation 3100 interface. Was this system disk originally used by a different VAX emulator (like Charon/SRI) or a different model of real VAX? Dave From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-edge.com] On Behalf Of Priya Chincholikar Sent: Tuesday, December 31, 2013 7:53 AM To: simh at trailing-edge.com Subject: EXT :[Simh] Network Problem Hi, I am trying boot a vax disk on SIMH and it keeps getting hung while starting network like TCP/IP. I have the required lipcap packages. My host is RedHat VM. The simulator was built with network support. *******INTERnet Started************** %UCX-I-DEFINTE, Defining interfaces %UCX-E-INVINTER, Error defining interface: SE0 -UCX-I-ACPQIO, Failure on Internet ACP QIO -SYSTEM-W-NOSUCHDEV, no such device available -SYSTEM-W-NOSUCHDEV, no such device available %UCX-E-INVINTERNAM, Invalid interface name -UCX-I-DRIVERQIO, Failure on Internet driver QIO -UCX-E-INVNETMASK, Invalid network mask %UCX-E-DELINTER, Error deleting interface: SE0 -UCX-I-ACPQIO, Failure on Internet ACP QIO ----> gets hung here usr/local/vax/bin/vax.ini-47> boot cpuname Simulation stopped, PC: 8358DF47 (BBC #3,26C(R3),8358DF9B) sim> This is the build: root at dt558 simh-master]# make vax lib paths are: /lib/ /usr/lib/ /usr/lib/qt-3.3/lib/ /usr/lib/sse2/ using libm: /usr/lib//libm.so using librt: /usr/lib//librt.so using libpthread: /usr/lib//libpthread.so /usr/include/pthread.h using libdl: /usr/lib//libdl.so /usr/include/dlfcn.h using libpcap: /usr/local/lib/libpcap.a /usr/local/include/pcap.h *** Warning *** *** Warning *** vax Simulator being built with networking support using *** Warning *** libpcap components from www.tcpdump.org. *** Warning *** Some users have had problems using the www.tcpdump.org libpcap *** Warning *** components for simh networking. For best results, with *** Warning *** simh networking, it is recommended that you install the *** Warning *** libpcap-dev package from your Linux distribution *** Warning *** *** Warning *** Building with the components manually installed from www.tcpdump.org *** Warning *** is officially deprecated. Attempting to do so is unsupported. *** Warning *** *** Warning *** *** Warning *** vax Simulator are being built with *** Warning *** minimal libpcap networking support *** Warning *** *** Warning *** Simulators on your Linux platform can also be built with *** Warning *** extended Ethernet networking support by using VDE Ethernet. *** Warning *** *** Warning *** To build simulator(s) with extended networking support you *** Warning *** should read 0readme_ethernet.txt and follow the instructions *** Warning *** regarding the needed libvdeplug components for your Linux *** Warning *** platform *** Warning *** *** *** vax Simulator being built with: *** - compiler optimizations and no debugging support. GCC Version: 4.1.2. *** - networking support using libpcap components from www.tcpdump.org. *** - Local LAN packet transports: PCAP TAP *** *** git commit id is 86e342501deaec3df79b31c13dd6d622938176e2. *** mkdir -p BIN gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fno-unsafe-loop-optimizations -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB sim_BuildROMs.c -o BIN/BuildROMs BIN/BuildROMs rm -f BIN/BuildROMs mkdir -p BIN gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fno-unsafe-loop-optimizations -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB VAX/vax_cpu.c VAX/vax_cpu1.c VAX/vax_fpa.c VAX/vax_io.c VAX/vax_cis.c VAX/vax_octa.c VAX/vax_cmode.c VAX/vax_mmu.c VAX/vax_stddev.c VAX/vax_sysdev.c VAX/vax_sys.c VAX/vax_syscm.c VAX/vax_syslist.c PDP11/pdp11_rl.c PDP11/pdp11_rq.c PDP11/pdp11_ts.c PDP11/pdp11_dz.c PDP11/pdp11_lp.c PDP11/pdp11_tq.c PDP11/pdp11_xq.c PDP11/pdp11_vh.c PDP11/pdp11_cr.c PDP11/pdp11_io_lib.c scp.c sim_console.c sim_fio.c sim_timer.c sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c sim_disk.c sim_serial.c sim_video.c -DVM_VAX -DUSE_INT64 -DUSE_ADDR64 -I VAX -I PDP11 -DUSE_NETWORK -DHAVE_PCAP_NETWORK -isystem -I/usr/local/include/ /usr/local/lib/libpcap.a -DHAVE_TAP_NETWORK -o BIN/microvax3900 -lm -lrt -lpthread -ldl cp BIN/microvax3900 BIN/vax Show version and show ethernet : 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. >>>usr/local/vax/bin/vax.ini-47> boot cpu Simulation stopped, PC: 20043601 (BSBW 2004367B) sim> sh ver MicroVAX 3900 simulator V4.0-0 Beta Simulator Framework Capabilities: 64b data 64b addresses Ethernet Packet transport:PCAP:TAP:UDP Idle/Throttling support is available Virtual Hard Disk (VHD) support RAW disk and CD/DVD ROM support Asynchronous I/O support Host Platform: Compiler: GCC 4.1.2 20080704 (Red Hat 4.1.2-46) Simulator Compiled: Dec 30 2013 at 17:52:32 Memory Access: Little Endian Memory Pointer Size: 32 bits Large File (>2GB) support OS clock tick size: 3ms OS: Linux dt558.***.com 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:54 EDT 2009 i686 i686 i386 GNU/Linux git commit id: 86e34250 sim> sh eth ETH devices: eth0 eth0 (No description available) eth1 tap:tapN (Integrated Tun/Tap support) eth2 udp:sourceport:remotehost:remoteport (Integrated UDP bridge support) Open ETH Devices: XQ eth0 (No description available) Ethernet Device: Name: eth0 Reflections: 0 Self Loopbacks Sent: 2 Self Loopbacks Rcvd: 0 Host NIC Address: 00:0C:29:59:50:83 Packets Sent: 4 Asynch Interrupts: Disabled Read Queue: Count: 0 Read Queue: High: 0 Read Queue: Loss: 0 Peak Write Queue Size: 1 sim> quit Goodbye NVR: writing buffer to file Eth: closed eth0 [root at dt558 /]# cat proc/version Linux version 2.6.18-164.el5 (mockbuild at x86-002.build.bos.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Aug 18 15:51:54 EDT 2009 Vax.ini : ; ;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 rauser=10240 set rq2 rauser=10240 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=00:1D:D8:B7:1C:00 set XQ type=DELQA attach XQ eth0 ; ;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 -Priya -------------- next part -------------- An HTML attachment was scrubbed... URL: From Mark at infocomm.com Tue Dec 31 18:19:47 2013 From: Mark at infocomm.com (Mark Pizzolato - Info Comm) Date: Tue, 31 Dec 2013 15:19:47 -0800 Subject: [Simh] EXT : Network Problem In-Reply-To: <9C9FDA2BCCFB5E4098DEB87AC47B94503E268384@XMBVAG73.northgrum.com> References: <9C9FDA2BCCFB5E4098DEB87AC47B94503E268384@XMBVAG73.northgrum.com> Message-ID: <0CC6789C1C831B4C8CCFF49D45D7010F0127D510517E@REDROOF2.alohasunset.com> Hi Priya, Dave may be right, BUT there still is something strange about your environment. Dave Johnson had suggested that you need to run as root. I don't think that your problem is due to the running as root issue since if that were the case "SHOW ETHERNET" usually wouldn't have mentioned eth0. The various attempts you made to install a libpcap development environment have left your system in a situation I'm explicitly removing support for going forward. The key information which is most likely the problem is: using libpcap: /usr/local/lib/libpcap.a /usr/local/include/pcap.h *** Warning *** *** Warning *** vax Simulator being built with networking support using *** Warning *** libpcap components from www.tcpdump.org. *** Warning *** Some users have had problems using the www.tcpdump.org libpcap *** Warning *** components for simh networking. For best results, with *** Warning *** simh networking, it is recommended that you install the *** Warning *** libpcap-dev package from your Linux distribution *** Warning *** *** Warning *** Building with the components manually installed from www.tcpdump.org *** Warning *** is officially deprecated. Attempting to do so is unsupported. It seems that the libpcap components you've built with were NOT directly provided by RedHat as part of their Linux distribution or it wouldn't have installed in /usr/local .... Some folks have mangled the working components of libpcap on their Linux systems by attempting to install various versions of non-OS-vendor supplied libpcap components. This mangling is why support for doing this that way has been officially deprecated. Your case has inspired me to take the time to completely remove this support for host platforms which have known good vendor supplied libpcap components (i.e. Linux). You should uninstall the package you found which dropped the libpcap pieces in /usr/local. I'm not a paid RedHat user and therefore don't have access to their customer portal to access their knowledgebase, however since you appear to be, you may want to look at the solution provided by: https://access.redhat.com/site/solutions/57913 Can you explicitly describe EXACTY what version of RedHat Linux you're working with and get back to me directly. I'll dig up libpcap directions for that platform and add it to the simh 0readme-ethernet.txt. Please get back to me. Thanks. - Mark Pizzolato From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-edge.com] On Behalf Of Hittner, David T (IS) Sent: Tuesday, December 31, 2013 8:11 AM To: Priya Chincholikar; simh at trailing-edge.com Subject: Re: [Simh] EXT : Network Problem Rerun @SYS$MANAGER:TCPIP$CONFIG to fix your TCPIP hardware interface definitions. The error is telling you that it can't find the VAX hardware device (no such device SE0) to attach (on the 4th line). The MicroVAX 3900 in the SIMH VAX does not have an SE0 interface, it has a QNA interface. I think SE0 was the built-in MicroVAX/VAXstation 3100 interface. Was this system disk originally used by a different VAX emulator (like Charon/SRI) or a different model of real VAX? Dave From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-edge.com] On Behalf Of Priya Chincholikar Sent: Tuesday, December 31, 2013 7:53 AM To: simh at trailing-edge.com Subject: EXT :[Simh] Network Problem Hi, I am trying boot a vax disk on SIMH and it keeps getting hung while starting network like TCP/IP. I have the required lipcap packages. My host is RedHat VM. The simulator was built with network support. *******INTERnet Started************** %UCX-I-DEFINTE, Defining interfaces %UCX-E-INVINTER, Error defining interface: SE0 -UCX-I-ACPQIO, Failure on Internet ACP QIO -SYSTEM-W-NOSUCHDEV, no such device available -SYSTEM-W-NOSUCHDEV, no such device available %UCX-E-INVINTERNAM, Invalid interface name -UCX-I-DRIVERQIO, Failure on Internet driver QIO -UCX-E-INVNETMASK, Invalid network mask %UCX-E-DELINTER, Error deleting interface: SE0 -UCX-I-ACPQIO, Failure on Internet ACP QIO ----> gets hung here usr/local/vax/bin/vax.ini-47> boot cpuname Simulation stopped, PC: 8358DF47 (BBC #3,26C(R3),8358DF9B) sim> This is the build: root at dt558 simh-master]# make vax lib paths are: /lib/ /usr/lib/ /usr/lib/qt-3.3/lib/ /usr/lib/sse2/ using libm: /usr/lib//libm.so using librt: /usr/lib//librt.so using libpthread: /usr/lib//libpthread.so /usr/include/pthread.h using libdl: /usr/lib//libdl.so /usr/include/dlfcn.h using libpcap: /usr/local/lib/libpcap.a /usr/local/include/pcap.h *** Warning *** *** Warning *** vax Simulator being built with networking support using *** Warning *** libpcap components from www.tcpdump.org. *** Warning *** Some users have had problems using the www.tcpdump.org libpcap *** Warning *** components for simh networking. For best results, with *** Warning *** simh networking, it is recommended that you install the *** Warning *** libpcap-dev package from your Linux distribution *** Warning *** *** Warning *** Building with the components manually installed from www.tcpdump.org *** Warning *** is officially deprecated. Attempting to do so is unsupported. *** Warning *** *** Warning *** *** Warning *** vax Simulator are being built with *** Warning *** minimal libpcap networking support *** Warning *** *** Warning *** Simulators on your Linux platform can also be built with *** Warning *** extended Ethernet networking support by using VDE Ethernet. *** Warning *** *** Warning *** To build simulator(s) with extended networking support you *** Warning *** should read 0readme_ethernet.txt and follow the instructions *** Warning *** regarding the needed libvdeplug components for your Linux *** Warning *** platform *** Warning *** *** *** vax Simulator being built with: *** - compiler optimizations and no debugging support. GCC Version: 4.1.2. *** - networking support using libpcap components from www.tcpdump.org. *** - Local LAN packet transports: PCAP TAP *** *** git commit id is 86e342501deaec3df79b31c13dd6d622938176e2. *** mkdir -p BIN gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fno-unsafe-loop-optimizations -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB sim_BuildROMs.c -o BIN/BuildROMs BIN/BuildROMs rm -f BIN/BuildROMs mkdir -p BIN gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fno-unsafe-loop-optimizations -DSIM_GIT_COMMIT_ID=86e342501deaec3df79b31c13dd6d622938176e2 -DSIM_COMPILER="GCC Version: 4.1.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so -DHAVE_GLOB VAX/vax_cpu.c VAX/vax_cpu1.c VAX/vax_fpa.c VAX/vax_io.c VAX/vax_cis.c VAX/vax_octa.c VAX/vax_cmode.c VAX/vax_mmu.c VAX/vax_stddev.c VAX/vax_sysdev.c VAX/vax_sys.c VAX/vax_syscm.c VAX/vax_syslist.c PDP11/pdp11_rl.c PDP11/pdp11_rq.c PDP11/pdp11_ts.c PDP11/pdp11_dz.c PDP11/pdp11_lp.c PDP11/pdp11_tq.c PDP11/pdp11_xq.c PDP11/pdp11_vh.c PDP11/pdp11_cr.c PDP11/pdp11_io_lib.c scp.c sim_console.c sim_fio.c sim_timer.c sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c sim_disk.c sim_serial.c sim_video.c -DVM_VAX -DUSE_INT64 -DUSE_ADDR64 -I VAX -I PDP11 -DUSE_NETWORK -DHAVE_PCAP_NETWORK -isystem -I/usr/local/include/ /usr/local/lib/libpcap.a -DHAVE_TAP_NETWORK -o BIN/microvax3900 -lm -lrt -lpthread -ldl cp BIN/microvax3900 BIN/vax Show version and show ethernet : 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. >>>usr/local/vax/bin/vax.ini-47> boot cpu Simulation stopped, PC: 20043601 (BSBW 2004367B) sim> sh ver MicroVAX 3900 simulator V4.0-0 Beta Simulator Framework Capabilities: 64b data 64b addresses Ethernet Packet transport:PCAP:TAP:UDP Idle/Throttling support is available Virtual Hard Disk (VHD) support RAW disk and CD/DVD ROM support Asynchronous I/O support Host Platform: Compiler: GCC 4.1.2 20080704 (Red Hat 4.1.2-46) Simulator Compiled: Dec 30 2013 at 17:52:32 Memory Access: Little Endian Memory Pointer Size: 32 bits Large File (>2GB) support OS clock tick size: 3ms OS: Linux dt558.***.com 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:54 EDT 2009 i686 i686 i386 GNU/Linux git commit id: 86e34250 sim> sh eth ETH devices: eth0 eth0 (No description available) eth1 tap:tapN (Integrated Tun/Tap support) eth2 udp:sourceport:remotehost:remoteport (Integrated UDP bridge support) Open ETH Devices: XQ eth0 (No description available) Ethernet Device: Name: eth0 Reflections: 0 Self Loopbacks Sent: 2 Self Loopbacks Rcvd: 0 Host NIC Address: 00:0C:29:59:50:83 Packets Sent: 4 Asynch Interrupts: Disabled Read Queue: Count: 0 Read Queue: High: 0 Read Queue: Loss: 0 Peak Write Queue Size: 1 sim> quit Goodbye NVR: writing buffer to file Eth: closed eth0 [root at dt558 /]# cat proc/version Linux version 2.6.18-164.el5 (mockbuild at x86-002.build.bos.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Aug 18 15:51:54 EDT 2009 Vax.ini : ; ;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 rauser=10240 set rq2 rauser=10240 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=00:1D:D8:B7:1C:00 set XQ type=DELQA attach XQ eth0 ; ;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 -Priya -------------- next part -------------- An HTML attachment was scrubbed... URL: