Here's how to get Haiku to work in Parallels:
Software always changes :) So if you want haiku to work with the newer version of Parallels (in this case version 3) you need to do the following steps:
- Get the nightly build
- Extract the tar.bz2 file
- Move the extracted haiku.image file to a directory
- Open terminal and go to the directory
- and run the following step in the terminal:
dd if=/dev/zero of=haiku.image bs=1024 count=1 conv=notrunc seek=204800
- Then rename the haiku.image to haiku.hdd
- Create the nieuwe virtual machine in Parallels, choose windows xp and choose to use an existing disk image
- Disable network in parallels! If enabled it will cause haiku to stop at boot time.
If you use the old steps you will get stuck at the ImageTool because I could not find image to in the new Parallels Desktop.
Speaking of changing software - I hear that the etherpci driver might work now (after a lot of stability fixes in Haiku)...
Can you confirm whether or not you need to disable the network still?
It still doesnt work, not even one of the 3 options.
At least not with the nightly build of 2 days ago, and having no network is a bit sucky because I cant download tools for development. Why isn that included in the nightly build?
By the way parallels emulates the realtek 8029(AS) network card. Maybe a driver port of bsd/linux? :)
The closest i have got it working is enabling the adapter, but setting its state to "unplugged", thus ensuring that the adapter is present but as soon as i set it to "plugged in" whilst haiku is running, it hangs.
The only other solution to networking in Parallels is perhaps you could add a serial port and point it to a socket with PPP running on the end - that's if haiku has any dial-up support in it.
Hm, is there some new trick to getting the disk image to work in Parallels? The last time I fired it up, all I had to do was download the latest disk image, run the Parallels Image Tool to "convert from plain virtual hard disk to expanding one", and then use that for the VM image. Networking had to be disabled, but I'm not even getting to that point this time. The boot screen pops up with the logo and after a few seconds it drops to the kernel debugger prompt saying "could not mount boot device".
The serial log from my last boot is available here: http://bzflag.bz/~sean/haiku/serial_r22554_20071014.txt
I've also tried various contortions including unmodified haiku.image, using the dd mentioned above that zeros out 1k part-way in (what is that supposed to do??), using a disk converted to expanding and non-expanding for all of these, and pulling the image from two separate places (haiku build factory and haikuhost). This used to work without a hitch, but now apparently needs some different encouragement. Can anyone shed some light on something I can try? Thanks.
From http://forum.parallels.com/showthread.php?t=13431
bunzip2 haiku.image.bz2
dd if=/dev/zero of=haiku.image bs=1024 count=1 conv=notrunc seek=408600
mv haiku.image haiku.hdd
And then run a vm, with the newly created image. Networking may still be an issue, though!
Rich
Some have reported that Haiku hangs when booting unless you disable the Parallels network interface. Looks like some issue with the etherpci driver maybe.