Has anyone had any joy using OpenStep 4.2 under VMware Fusion 2.0.5 on Mac OS X.5/Intel on a long term basis? I can install it successfully, but after a short period of use (minutes) inevitably get the following kernel trap. I've tried all sorts of combinations of drivers and emulated hardware settings but can't pin it down:
Huh ... I get the exact same kernel trap when running in Parallels Desktop 2.5 build 3224.
All I do is:
- create a fresh install of OpenStep 4.2 User, OpenStep 4.2 Developer, EOF 2.1, patch4, drivers
- mount the NextStep 3.0 CD-ROM (ISO image)
- run in Terminal.app:
cd /tmp
gnutar cfps 3.0-M.tar /NeXTSTEP_3.0
Presumably this is not actually a bug in OpenStep 4.2, since I've never seen it triggered on a real NeXT system (Intel or Motorola), but OpenStep 4.2 executing some instruction which none of these virtualizers can handle?
It seems hard to imagine there would be a 486 instruction that the Intel Core 2 Duo cannot execute correctly.
You have to try Sun's VirtualBox. It is great, free and works.
I have been using Suns Virtualbox on Snow leopard. Ver 3.0.12.
All works well, including the networking (with the same instructions noted here on another thread), but modified to be more "netinfo" correct, which happened by way of installing and going through the DHCP client install. No kernel failures or ATAPI error traps.
All works, and my Debian "Lenny" and GNUstep dev environment as well on same box!!!
Dump the price and go free and with the Sun offering. Works great.
Quote from: "jaallen"You have to try Sun's VirtualBox. It is great, free and works.
VirtualBox works great in a Windows environment too. I've had issues running OPENSTEP on VirtualPC and on VMWare, but have not encountered any with VirtualBox.
Thanks for that tip. I have indeed tried VirtualBox. It looks nice and I have not run into any problems (yet), but it does run ridiculously slowly - more than an order of magnitude, perhaps two orders of magnitude, slower than Parallels or VMware. I haven't yet managed to get through a complete installation, because it ran so slowly.
Am I using some setting incorrectly?
Quote from: "tomaz"Thanks for that tip. I have indeed tried VirtualBox. It looks nice and I have not run into any problems (yet), but it does run ridiculously slowly - more than an order of magnitude, perhaps two orders of magnitude, slower than Parallels or VMware. I haven't yet managed to get through a complete installation, because it ran so slowly.
Am I using some setting incorrectly?
You must have something wrong. What version of VirtualBox and OSX are you running?
Once you give me that, ill run down what I have mine set for. No performance issues here for VirtualBox, actually, I have tried them all, and the statement that VirtualBox is slower than those two at Unix/Linux variants is NOT TRUE.
Maybe for windows, which Parallels is tweaked for, but then, who cares...
VirtualBox 3.1.0, OS X.5.8/Intel. It was running very slow when I was installing OpenStep 4.2.
I use VirtualBox 3.1 on top of OS X.6 Intel to run all kinds of VMs... from Windows XP through to various flavors of Unix and since 2.x have rarely had any issues. I tend to use fixed-sized disk images, but even without, it has been fast.
If you have a lot of snapshots, things will slow down significantly in older versions.
I don't have any snapshots. And the difference in speed between VMware/Parallels on the one hand and VirtualBox is palpable.
E.g. when booting from OpenStep 4.2 boot floppy in console mode, VMware/Parallels rush through the entire screen in an instant, whereas VirtualBox prints out characters character by character at the rate of about 300 baud.
Even when clearing the screen, I can see it clearing it scan line by scan line where as VMware/Parallels is instantaneous.
The difference is at least one order of magnitude, if not two.
As said in the other thread, VirtualBox 1.6.0 works fine for me, and there is now no kernel trap: tar now just fails with a Segmentation fault.
All running fine here except I cant get the vmware driver to display higher than 1024x768 on vmware fusion 3
