VirtualBox

Ticket #7214 (new defect)

Opened 4 years ago

Last modified 19 months ago

[PATCH] Add BeOS and Haiku to the (Other) guest OS list

Reported by: mmu_man Owned by:
Priority: minor Component: other
Version: VirtualBox 3.2.6 Keywords: beos, haiku
Cc: Guest type: other
Host type: other

Description (last modified by ramshankar) (diff)

This patch adds BeOS and Haiku to the Other guest OS list, and selects the correct NIC. Both require the use of the Intel PRO/1000 MT Desktop NIC due to missing driver for the default one.

VBOXOSTYPE_Haiku is defined as a subtype for VBOXOSTYPE_BeOS though technically it is a reimplementation, so maybe 0xD0000 would fit better. A 64bit port of Haiku has been started but is not ready yet. 2GB is suggested for the disk, which should be enough for default installs. 256MB of RAM is enough for simple use.

Also added simple png files for the GUI, someone can probably do better.

This patch is under MIT license.

Attachments

os_beos.png Download (2.1 KB) - added by mmu_man 4 years ago.
os_haiku.png Download (2.1 KB) - added by mmu_man 4 years ago.
virtualbox-beos-haiku-ostypes.diff Download (5.7 KB) - added by mmu_man 3 years ago.
Diff against r35998

Change History

Changed 4 years ago by mmu_man

Changed 4 years ago by mmu_man

comment:1 follow-up: ↓ 2 Changed 4 years ago by mmu_man

It seems a new field was added to Global::OSType which breaks this patch... I'm not sure which chipset is best yet. All my Haiku VMs seem to be set to PIIX4 though I don't remember if PIIX3 was causing any trouble, will have to test.

comment:2 in reply to: ↑ 1 Changed 4 years ago by mmu_man

Oh, it seems it's a different flag than the IDE controller, which is already set to PIIX4. I guess the default should do then.

comment:3 Changed 3 years ago by mmu_man

It seems r34661 broke this patch again...

comment:4 Changed 3 years ago by mmu_man

r35368 Broke it again...

comment:5 Changed 3 years ago by kallisti5

could this get checked in? This is a valid addition and would make sense in my virtual environment.

Changed 3 years ago by mmu_man

Diff against r35998

comment:6 Changed 3 years ago by Technologov

Added myself as CC.

NOTE: I was unable to run BeOS 5 in VirtualBox v4.0.0.

Does it work for you ?

Which audio controller works ? AC'97 ?

-Technologov

comment:7 Changed 3 years ago by kallisti5

I know in qemu, BeOS Dano (5.1) will boot reliably if you emulate a P3 CPU...  https://picasaweb.google.com/kallisti05/BeOSDano#

As VirtualBox was based on qemu long ago... this may still be possible.

Booting the old BeOS can be tricky, it doesn't handle modern hardware (even emulated) well.

BeOS 5.1 should support AC'97

Haiku will boot well under most emulated configurations. You can use the VBoxManager tool to convertdd the raw nightly Haiku image into a virtualbox disk image.

comment:8 Changed 3 years ago by mmu_man

Actually I finally managed to make BeOS to boot. Unlike Haiku it doesn't like the filesystem being alone in the disk without a partition table.

An option is to prepend a partition table (the type should be 0xeb), but it's not easy to know how many sectors to prepend to end on a cylinder boundary.

Making use of the IMAGE.BE trick one can create a FAT partition in a file and copy it inside, something like (requires sfdisk and mtools):

#!/bin/sh

img=$PWD/beosdos.img
vdi=$PWD/beosdos.vdi

dd if=/dev/zero  bs=1M count=550 of=$img

sfdisk -f -D -H 255 -S 63 -uM /mnt/tera/public/beosdos.img << EOF
0,,0c,-



EOF

cat > tmp.mtools << EOF
drive i: file="$img" partition=1
EOF

MTOOLSRC=tmp.mtools mformat -v "BeOS" i:
MTOOLSRC=tmp.mtools mmd i:/BEOS
MTOOLSRC=tmp.mtools mcopy image.be i:/BEOS/IMAGE.BE

VBoxManage internalcommands converthd -srcformat RAW $img $vdi

Then booting from the floppy.img with beosdos.vdi attached to an IDE drive works. One must force a fail-safe video mode in the bootloader to avoid the grey screen (then one should be able to force the vesa config in the driver settings). Audio even seems to work.

comment:9 Changed 3 years ago by richienyhus

Any updates here?

Also to the Haiku devs, isn't it better to focus on getting Haiku running on VirtualBox rather than BeOS? The network problem is a major turn off to new users.

comment:10 Changed 3 years ago by kallisti5

Haiku is sponsoring a Google Summer of code student who is creating guest additions for the Haiku operating system. These guest additions are being added to the VirtualBox code base and can be compiled under Haiku.

As we are making progress getting Haiku native Virtual Box support, it would seem relevant to add Haiku as a supported OS (even if it is under "other operating systems"

You can view the students work here:  https://github.com/scgtrp/vbox-haiku

comment:11 Changed 3 years ago by ModeenF

Any news? I would rather use VB than VMWare ;)

comment:12 Changed 19 months ago by ramshankar

  • Description modified (diff)

A little late but nonethless, the Haiku additions should now be part of the VirtualBox tree. The base PCI VMMDev driver along with mouse integration has been tested personally by me and known to work. Currently there is no binary packaging for the additions that allows for easy installation. This will be done as follow up work along with fixing bugs and general cleanup.

Version 0, edited 19 months ago by ramshankar (next)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use