Maybe it works on mac or windows, but on linux-2.6.22 with VirtualBox 1.5.6_OSE and an older processor without hardware support for virtualization such as amd athon xp 2100+ it still crashes(This is the latest alpha image) and BTW, I was talking about the host os kernel component (hence linux/windows). The point is, if you cannot run Haiku under VirtualBox, run it under qemu without the kqemu.ko linux kernel module and it works. To check once again I downloaded the latest VirtualBox from my Distro’s repos, created a .vdi image from the latest alpha and it crashed. Last time I checked the bug ticket was still open in trac.
I even tried to boot into safe mode with everything disabled that Haiku can disable with no luck.
Acknowledged, It can work for someone, but on this hardware/OS VirtualBox with haiku is a no-op. Only VM’s that can boot haiku reliably are vmware and qemu (and they are almost quaranteed to work).
Yeah, the lack of virtualization may in fact be the problem in this case.
AFAIK, Haiku never did run properly with VBox from the start unless you enabled the hardware virtualization features. I had never personally tried it (and have yet to do so), but a similar issue was reported with kqemu as well (again, I never personally tried it).
Since there have been many other people reporting success with Haiku in VirtualBox, I had assumed that something got fixed, but perhaps the original problem is still there.
I just tried a similar thing on openSUSE with VirtualBox from the distro’s repo, it crashed as well. The problem seems to be with the older version of VirtualBox. After I uninstalled the disto’s old version and installed the latest version from virtualbox.org it worked just fine.
I think a lot of distro’s have out of date versions. Just download the evaluation version or get the latest OSE version and build from source.
The latest version is 2.0.6, but I’m using 2.0.4 on my Mac and on Linux.
I’m currently running haiku latest build r28846 in VBox and it works great. I am using latest VBox version 2.1.0, with Vt-x enabled (when disabled, Haiku VM stops after splash screen). I’m on Mac OS X Leopard and I didn’t even have to convert the image vdi, since VBox supports VMWare images natively. All seems fine after minutes of testing.
edit: For Macbook Pro airport internet, in Network settings, choose Intel PRO 1000 MT Desktop, using Host Interface option and select en1: Airport.
If only VirtualBox supported raw hdd images it would be perfect. I tested the 2.x series and haiku ran just fine. I just wish there would be a way to avoid going to console and use vditool to convert raw images to .vdi like a graphical converter or just support for raw images…
In that case, why not use the VMware images? I use the .vmdk VMware images in Virtual Box all the time. You just have to download them, its that simple.
I tried the VMWare images on VirtualBox 3.0.10 on an OS X host with no VT-X enabled. No go. But I was able to install it off CD iso via VirtualBox just fine.
I had no problem loading the VMDK in Virtualbox 3.1.6 on Windows XP. Just add it in the Virtual Disk Manager, create a new VM with “Other/Unknown” as the operating system and set its hard disk to the VMDK.
The most recent Windows build of VirtualBox supports the alpha of Haiku with the following caveats:
The Guest Additions (naturally) don’t work.
The AMD PCnet adapter setting won’t work, either; however, the Intel PRO1000MT Desktop adapter option works just fine.
I am, in fact, posting this from Haiku alpha 1 installed in the current (3.1.6) Windows build of VirtualBox. (Though installed on Windows 7 Ultimate x64, x32 versions of VirtualBox, including those for Linux, should also work.)
[quote=skoe]Haiku has worked just fine in VirtualBox for quite some time for me. In fact, i have been compiling under Cygwin and using VirtualBox to test the images.
But the thing is: You need to enable VT-x/AMD-V emulation. Otherwise it wont boot.
Settings -> General -> Advanced -> tick Enable VT-x/AMD-V
Edit:
Oh, and if your PC doesn’t support this you might just be out of luck :(. For now at least, anyway.[/quote]
Don’t tell my Celeron DC E1200 (no VT-x support whatever) that.
I’ve got Haiku alpha 1 running just fine in the current (3.1.6) Windows version of VB (installed from ISO); in fact, I’m posting this from it.
While there are Celeron DCs that do support VT-x (the E3x00 series), my E1200 predates them.
While that is no longer an issue (with either Haiku or even XP Mode in Windows Virtual PC, as Microsoft has killed the VT-x/AMD-V requirement there also), there are other reasons to seriously consider the E3x00 series if you are running E1x00 now.
Hi, I am using VirtualBox 3.2.4 r62467 under Windows Vista 32bits, and Haiku R1 Alpha2 ISO.
I configured a VM with 64MB of RAM, 1 processor, no HD, CD/DVD-ROM, 6MB of VRAM, default sound and network card, and no serial ports neither USB ports.
It boots the system from the ISO image, asking me for my language, keyboard layout, and if I want to install it or just test the live CD version.
Because I didn’t set up any hard disk, I just wanted to test it, after I pressed “Desktop (Live-CD)”, there was some CD activity, and nothing else it showing blue background and the mouse. Finally, the mouse hangs.
Give it more RAM. Just because haiku technically can run in 64MB RAM doesn’t mean it will like it. 128MB should be enough. I personally run it in a VBox image with 1024MB RAM.
If that doesn’t work, try using VT-X if your processor has it.