Seems like the recent problems with device detection have been fixed,
and a current build boots. This is nice.
So, here is how my simulated 8650 appears right now:
============
sim> boot rq/r5:8
Loading boot code from vmb.exe
>> NetBSD/vax boot [1.11 Mon Apr 27 08:07:57 UTC 2009] <<
>> Press any key to abort autoboot 5
nfs_open: must mount first.
open netbsd.vax: Device not configured
> boot netbsd
2674084+172684 [212768+204148]=0x31cfc8
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013
The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
NetBSD 6.99.18 (Puff) #5: Fri Mar 29 04:10:49 CET 2013
root%GW.SoftJAR.SE@localhost:/usr/obj/sys/arch/vax/compile/Puff
VAX 8650
total memory = 65532 KB
avail memory = 59700 KB
mainbus0 (root)
cpu0 at mainbus0: KA865, S/N 1234, Rev. G, manufactured in simh.
cpu0: no FPA
...
NetBSD/vax (Puff.BQTnet.SE) (console)
login:
==========
There are a couple of problems right now, that I have not even started
looking at, but maybe someone already have an idea.
The system does not boot if I configure more than 64 Mbyte of memory.
If I configure more, it fails to detect my disk controller, and fails
to come past the initial setup. It asks for the root device, but since
it didn't even detect the controller, of course no possible answer can
be given.
With NetBSD 5.0, the same problem existed, but the limit then was 128
Mbyte. Anything more than that, and failure.
But now it is 64 Mbyte. I think I've also tested the 11/780 emulation,
with the same issue. However, it do work just fine with a 3900, which
I've ran with 512 Mbyte without problems.
(Actually booting the same image.)
Anyone who might know what that is about?