NFS through SLiRP with Rhapsody DR2 x86

I'm using Qemu 0.90 with the Busmouse patch from a decade ago...


With all the kernel excitement I thought I'd like to try to do something so I installed this as kernel 5.1 is pretty close to 5.3

I've already installed, and I guess I can give more detail if needed but 0.90 will install NeXTSTEP just fine, and I'm pretty sure OPENSTEP, must as Rhapsody DR2 installs just fine.  I used the NE2K_0.91beta (http://www.nextcomputers.org/NeXTfiles/Software/OPENSTEP/Drivers/Third_Party/i386/network/) driver from here, and configured it manually for 10.0.2.15/24 with a 10.0.2.2 gateway as it doesn't like SLiRP or DHCP, it's still BOOTP!!

qemu -L . -hda rhap.raw -net nic,model=ne2k_pci -net user -serial none -parallel none -m 64  -redir tcp:42323::23

I've also disarmed /etc/ttys so I can telnet in as root.  I know, evil!

I have a Synology Diskstation that I've setup as my NFS server.  In Rhapody if I mount the NFS directly it'll hang if I do anything with it.  However by dropping the timeouts, and shrinking the buffers it'll work!

/sbin/mount_nfs -a 1 -D 1 -R 1 -r 512 -t 1 -w 512 192.168.1.3:/volume1/Data /mnt



rhapsody:77# /sbin/mount_nfs -a 1 -D 1 -R 1 -r 512 -t 1 -w 512 192.168.1.3:/volume1/Data /mnt
rhapsody:78# df
Filesystem                512-blocks     Used    Avail Capacity  Mounted on
/dev/hd0a                    3960076   740052  3022020    20%    /
fdesc                              2        2        0   100%    /private/dev
automount -fstab [214]             0        0        0   100%    /Net
192.168.1.3:/volume1/Data 1445681456 881259968 564216688    61%    /mnt
rhapsody:79#


You get the idea....  SLiRP from 0.90 is crazy old, and with all kinds of subtle bugs!  but I've mounted and been able to read and write.

Also this works on NeXTSTEP 3.3!

mount -t nfs -o fs,mnttimeout=1,retry=1,rsize=512,wsize=512,retrans=1 192.168.1.3:/volume1/Data /mnt/data


Thanks, neozeed, for posting this excellent info.  It goes nicely with my howto on using the NFS automounter.: http://www.nextcomputers.org/forums/viewtopic.php?t=3598

Like you, I have a Synology; mine is a DS415+.  Since most of my systems are laptops, I use the automounter rather than static mounts, and to keep uniformity, I use the same setup on my NeXTs.

Quote from: "eagle"Thanks, neozeed, for posting this excellent info.  It goes nicely with my howto on using the NFS automounter.: http://www.nextcomputers.org/forums/viewtopic.php?t=3598

Like you, I have a Synology; mine is a DS415+.  Since most of my systems are laptops, I use the automounter rather than static mounts, and to keep uniformity, I use the same setup on my NeXTs.

Sure thing!  I think the one big issue I had with the default stuff is that I would constantly get timeouts, and errors that would hang the VM.  I've also been messing around with ancient SUNOS 2.0, and as part of it's readme it mentions that the updated SUN-1U hardware that the early Ethernet boards could only reliably transmit a single frame at a time, and that NFS would want to queue so much data it would flood the driver.  The fix was to force SUNOS to use small windows.. So taking that bit of useless knowledge out of context, and now I can mount my Synology from Qemu 0.9.0!