Tired of Running Haiku Under VMs
I'm a Linux user and quite interested in taking a *real* look at Haiku. Unfortunately I can only run from a VM. The forums tell me that SATA is not supported in Haiku/BeOS Max yet, so installing to a HDD is probably out of the equation already (is it so?).
Is there a way to put Haiku onto a CD/DVD or even a USB drive? My computer supports booting from USB and, as far as I know, Haiku can now support USB drives. Any ideas?
Another question : what is dd? I've been reading that "installing through dd might also be possible", but with a name so general, even Google wasn't able to pinpoint it. [EDIT : okay, "man dd" did the trick. How could I be so stupid?]
I'm ready to build from source, too, although I might need some guidance.
Frankly speaking, I'm tired of running Haiku from QEMU. It's really slow and I can't install anything since de-compressing files makes the CPU usage 100% on the host machine, and the process gets stuck (although Haiku itself keeps running normally).
I would be glad of *any* kind of assistance. I've been following this project for the last year or so, and realizing that I *still* can't *really* use the system makes me itchy :-(
GM
Comments
Re: Tired of Running Haiku Under VMs
Well if you are ready to build Haiku from the source then you might want to try to build it directly to the USB drive. I don't have any experience building Haiku from source (in the process of setting up a machine to do so) but it sounds to me like it might work (no research done on this).
Here is Ryan's doc on how to build in case you run into problems. http://haiku-os.org/documents/dev/building_haiku_on_ubuntu_linux_step_by...
You might want to try #haiku on freenode IRC network. There was a good discussion going on there last night about building Haiku (to the folks in there... yes I was lurking :)). The folks who hang out there will probably be able to give you better instructions.
Re: Tired of Running Haiku Under VMs
I'm a Linux user and quite interested in taking a *real* look at Haiku. Unfortunately I can only run from a VM. The forums tell me that SATA is not supported in Haiku/BeOS Max yet, so installing to a HDD is probably out of the equation already (is it so?).
Some legacy SATA drivers are now in the tree - but I'm not certain if they're built as part of the image by default yet (a quick check in the HaikuImage jam rules would be in order). These should allow Haiku to boot on a decent number of existing SATA controllers without AHCI support (still in development) being necessary I think.
Is there a way to put Haiku onto a CD/DVD or even a USB drive? My computer supports booting from USB and, as far as I know, Haiku can now support USB drives. Any ideas?
A LiveCD can be created - but it's not easy. I think the only way to create your own LiveCD now is from a BeOS/Zeta install. I don't think booting from a USB disk will work yet. You can try, but last I heard it was still a "no".
Another question : what is dd? I've been reading that "installing through dd might also be possible", but with a name so general, even Google wasn't able to pinpoint it. [EDIT : okay, "man dd" did the trick. How could I be so stupid?]
You can dd a raw image onto a partition, but you will subsequently have to run makebootable on it. makebootable is a build tool that is built from the Haiku repository (not in the buildtools branch) that is used to write the bootloader to a partition and set the proper offset. The offset can be altered manually, but it's not much fun ;) If you don't run makebootable, it will start booting from grub and then complain that it can't find the volume.
I'm ready to build from source, too, although I might need some guidance.
This is probably the easier method. There is a way to have the image built directly to a partition by changing some values in the UserBuildConfig. It was just discussed in #haiku yesterday even - and I grabbed some of that info. I can write up some steps, but it's a little sketchy. Once you are able to build an image, the next step would be to build it onto a partition - so first get to the point where you can create an image with the build system.
Frankly speaking, I'm tired of running Haiku from QEMU. It's really slow and I can't install anything since de-compressing files makes the CPU usage 100% on the host machine, and the process gets stuck (although Haiku itself keeps running normally).
VMWare provides a much better experience IMO - you should try it out.
I would be glad of *any* kind of assistance. I've been following this project for the last year or so, and realizing that I *still* can't *really* use the system makes me itchy :-(
It sounds like you're ready to make the leap from testing pre-built images to building your own... warning: it can be a bumpy ride, rife with possible disappointments - hope you're prepared ;)
Hope my reply is helpful - you can always pop into #haiku on irc.freenode.net if you need some assistance. There's usually a couple people hanging out there who can help, but if not, you can try again later.
- Urias
Re: Tired of Running Haiku Under VMs
I've made the leap as well. Unfortunately my hardware is not very compatible with Haiku and it freezes on boot. I suppose I could do a serial dump but I don't know what's involved in setting that up. Hopefully I can eventually find a cheap hardware config that works.
Re: Tired of Running Haiku Under VMs
Okay, I've just grabbed all the tools required to build Haiku off the PCLinux repos. I'm following this tutorial : http://haiku-os.org/documents/dev/building_haiku_on_ubuntu_linux_step_by...
The step mentions running an install script for the Haiku Jam (./jam0 install). I want to know whether it's possible for me to remove Jam cleanly from my system when I'm done (I just don't prefer to have any stuff on my system that I don't use much :)).
@Urias
Building seems easy, but I seriously don't have any clue about putting it on a partition and making it bootable. And what about making it play nice with GRUB? A write up, a tutorial, a nudge in the right direction ... you get the picture :)
By the way, I just got VMWare. It's working way better than QEMU, but the network doesn't seem to work well at the moment. wget-ing stuff from BeBits doesn't work (stuff built for BeOS R5 *will* work on Haiku, right?).
Re: Tired of Running Haiku Under VMs
The step mentions running an install script for the Haiku Jam (./jam0 install). I want to know whether it's possible for me to remove Jam cleanly from my system when I'm done (I just don't prefer to have any stuff on my system that I don't use much :)).
All that does really is copy jam0 to /usr/local/bin/jam IIRC... If you already have jam installed (which is a tool that is not specific to Haiku) - you may want to simply copy it there with a different name. Some people call it hjam instead to differentiate it from the standard jam they have installed.
I'll get some info posted here on how to jam it directly to a partition, or how to dd an image there and makebootable on it as an option.
When you setup VMWare, I recommend leaving it in NAT configuration (as opposed to bridged) - as there are still apparently some issues with the DHCP client that prevent it from working with all servers out there. If you do this, you should *not* have to mess with the network settings whatsoever, it will just work from a clean image after boot - in fact I believe the new netprefs panel might actually prevent DHCP from working properly as others have reported issues after messing with the settings there. Also, I've read that there can be some problems getting VMWare's network interfaces working under Linux - you might want to check that.
Re: Tired of Running Haiku Under VMs
Make sure VMWare is emulating a card Haiku supports - add ethernet0.virtualDev="e1000" in your .vmx file.
Re: Tired of Running Haiku Under VMs
Oh - good point - I sometimes forget about this. I think the .vmx file in the haiku repo, and on haikuhost.com both are set this way - hopefully!
Re: Tired of Running Haiku Under VMs
Okay, the network works under VMWare now. Switching to NAT made it work.
Compiling was easy. But I'm putting off dd-ing the image to a partition unless SATA drivers become usable. Looking out for that announcement :)
Looks like it's VMWare for now. But somebody please do that write up on how to dd the image to a partition, make it bootable and make it play nice with GRUB. It'll be useful for future reference (if Haiku doesn't change much), and for those who still have their old HDDs around.
(Me still itching to get my hands on R1...)
Re: Tired of Running Haiku Under VMs
I'll volunteer to write this up as I have been able to get it to work. The only thing I am not sure of is the makebootable. I have been able to accomplish that by booting from a BeOS MAX live cd but I've been told that it may be possible to run it from Linux somehow (??). If someone can explain to me how this works I can add it to my writeup. Otherwise I'll explain how to do it with the BeOS Max CD.
Also, If I write up something like this where would I post it? Should I tack it on as a comment to Ryan's Ubuntu tutorial or somewhere else?
Re: Tired of Running Haiku Under VMs
Some pointers,
I can run Haiku on my sata drive, if I enable "Legacy Emulation" in the Bios. Have a look for this setting in your bios. You might be lucky.
The haiku version of Jam is mandatory, and you can't use any other version.
You might have some problems running makebootable. If you do copy libbe_build.so, and libroot_build.so as root to "/lib". That was the easist way to fix it that i found.
As far as I know booting from USB will not work, as there is no handover from the bootloader to the kernel for USB. Here is a conversation on the mailing list regarding the situation at present: http://www.freelists.org/archives/openbeos/07-2007/msg00103.html
The Linux version of makebootable is located at .../haiku/haiku/generated/objects/linux/x86/release/tools/makebootable/platform/bios_ia32
Re: Tired of Running Haiku Under VMs
The Linux version of makebootable is located at .../haiku/haiku/generated/objects/linux/x86/release/tools/makebootable/platform/bios_ia32
Thanks. Looks like it will be next week before I can try that out and do a write up. I have one more weekend away before things slow down for the fall/winter season.
Re: Tired of Running Haiku Under VMs
Looks like Fredrik Ekdahl beat you to it:
http://haiku-os.org/community/forum/installing_haiku_to_a_partition_from...
It demonstrates how to build directly to a partition so you don't need to use dd and makebootable.
Re: Tired of Running Haiku Under VMs
Guess he did. I need to speed up on those things I guess. Thanks to Frederik for that! :)
Re: Tired of Running Haiku Under VMs
I just did it. I had a spare partition (1GB) which used to be a swap partition for Ubuntu in the days of yore. Everything went smoothly, but once the Haiku bootscreen came up, Haiku went into kernel debugland.
"No boot partitions found.", it said.
fdisk tells me that the partition I installed to is *still* swap. Shouldn't I be using something like EXT or BeFS? How to format to BeFS from Linux?
Re: Tired of Running Haiku Under VMs
I don't know why no one ever fixes that. It seems pretty dumb to put BFS on a partition and leave it marked as being FAT32, Swap, or whatever. Worst case, you can change that from parted or gparted. IIRC, the hex value for a BFS partition is 0xEB.
Re: Tired of Running Haiku Under VMs
I did that from fdisk. It still doesn't boot. Same error.
Now what? Is my hardware causing any conflicts? I have a Seagate SATA drive, but somebody previously mentioned that SATA works okay. I also happen to have a gig of RAM. Does Haiku support it, or does it have the same limitation as BeOS?
Should I make the disk bootable? Will that help at all?
Re: Tired of Running Haiku Under VMs
Very possibly your SATA controller isn't supported...
Once the kernel takes over from the bootloader, it will stop using the BIOS to access the disk and start using its own drivers - if there's no driver to support the controller that the disk was booted from, you get nothin' basically :(
What controller/mobo is it? Maybe we can figure out if it's supported that way. Keep in mind - I'm not sure the SATA drivers in the repo are even compiled into the image yet - you might have to add them to the jam rules manually.
Also a serial debug output log of the entire boot is useful for debugging these kinds of issues.
Also, are you installing it to an extended partition? I've not tried this myself, I assume it works, but I usually install to a primary partition on my systems.
Finally, try running makebootable on it again - this sets the offset in the bootloader to point to the physical location on the disk where the partition starts - I believe based on where you landed, this is already correct - as it would seem the kernel loaded ok.
Re: Tired of Running Haiku Under VMs
I have an Asus A8N-E mobo and a Seagate HDD - not sure about the model, because I've lost the box, but KInfoCenter tells me the model number is ST3250824AS.
How do I get a debug log of all this, as you said? And also tell me about the jam rules to compile SATA drivers into the kernel (if they aren't already compiled).
I've run makebootable on the partition. I suppose the bootscreen wouldn't have come up if I hadn't done that, right?
(Yay! For the first time in my life, I'm an "early adopter" :))
Re: Tired of Running Haiku Under VMs
Starting with your last question:
I've run makebootable on the partition. I suppose the bootscreen wouldn't have come up if I hadn't done that, right?
Actually, the reason I was suggesting this is in case the partition offset is wrong - for example, if you moved Haiku to another partition, it would still show the splash screen (I believe), but fail to boot properly. In any case, I suspect you're running into a SATA driver issue, so let's assume that first and see what we can do.
How do I get a debug log of all this, as you said?
This requires a second machine, both need serial ports, and a null-modem serial cable connecting them together... if you don't have those, then it's gonna be hard ;) But if you have them, this would be an excellent way to trace what's going on during boot. For example, there's an entire section of debug text dumped out that lists all the PCI devices in your machine - it also shows any debug info spit out as drivers are loaded. Exceptionally useful stuff for non-booting systems.
And also tell me about the jam rules to compile SATA drivers into the kernel (if they aren't already compiled).
So here's where things start getting a little bit technical - the haiku-image (and thus haiku-vmware-image) jam targets only build the targets listed in the build/jam/HaikuImage file. Now, i'm looking in there, and I see a legacy_sata driver being installed. When I go look at this driver, it has a whole list of PCI ids that it supports.
I looked up your motherboard, and it appears to have an nforce4 chipset - the legacy_sata driver only supports a few NF2/3 chips - so I have a feeling you're out of luck until the AHCI driver is completed :( It's always hard to get modern hardware working with alternative OSes :( I'm not entirely sure though - so if you can get the vendor/device IDs for your SATA controller, you can verify them against the list in src/add-ons/kernel/busses/ide/legacy_sata/legacy_sata.c
You can try and see if there's a "legacy mode" on your SATA controller in the BIOS - but I kind of doubt it.
Re: Tired of Running Haiku Under VMs
Starting with your last question:
Now, i'm looking in there, and I see a legacy_sata driver being installed. When I go look at this driver, it has a whole list of PCI ids that it supports.
I looked up your motherboard, and it appears to have an nforce4 chipset - the legacy_sata driver only supports a few NF2/3 chips - so I have a feeling you're out of luck until the AHCI driver is completed :( It's always hard to get modern hardware working with alternative OSes :( I'm not entirely sure though - so if you can get the vendor/device IDs for your SATA controller, you can verify them against the list in src/add-ons/kernel/busses/ide/legacy_sata/legacy_sata.c
I have a MSI K9NGM2 (http://global.msi.com.tw/index.php?func=proddesc&prod_no=257&maincat_no=1) which has a NVIDIA nForce 430 southbridge and that works very well with the legacy_sata driver. nForce 4 and 5 (and the earlier ones also of course) doesn't support AHCI and should use the legacy_sata driver, I'm not sure about the 6 series.
Re: Tired of Running Haiku Under VMs
Oh well. I don't have another machine, so I can't get a logfile, and my BIOS has no legacy_mode. Looks like I'm out of luck.
I've seen some progress on the AHCI driver on the frontpage of this website. I can only hope it gets done ASAP so that I can finally use the OS.
Re: Tired of Running Haiku Under VMs
Your hardware is not AHCI compliant. You need the legacy_sata driver, which is already included in the image. You don't need to use legacy mode, as the driver should support your sata controller.
Re: Tired of Running Haiku Under VMs
AHCI works only on many ( but not all ) "newer" sata controllers.
Normally your motherboard manual would say if your board supports AHCI. I *believe* that AHCI is not supported by your motherboard.
You're stuck with getting the legacy_sata driver working for you.
Only certain legacy ( Nvidia ) sata controllers are supported with legacy sata driver. To see if yours is, do the following ( in Windows XP ):
Getting the Vendor & Device ID ( for Sata Controller ):
1) Start->Control Panel->System
2) Click "Hardware" Tab, click "Device Manager"
3) Double Click "SCSI & RAID Controllers"
4) Double Click on your SATA Controller
5) Click "Details" Tab
6) Provide the info you get here
ie: PCI\VEN_1095&DEV_3112
Silicon Image 3112 SATA Controller
From above: Vendor id=0x1095, Device id=0x3112
Device & vendor ids can be used to verify if legacy sata driver supports your sata controller.
Fredrik, would you mind giving your vendor & device ids for your sata controller also, for comparison?
PS, you can also get vendor & device ids from Linux too.
Re: Tired of Running Haiku Under VMs
Sure, my vendor id is of course 0x10de since it's nvidia, and the device id is 0x0266. You can see that it's supported in http://svn.berlios.de/viewcvs/haiku/haiku/trunk/src/add-ons/kernel/busse...
Re: Tired of Running Haiku Under VMs
My apologies, I haven't done much research on nForce SATA controllers... (which is ironic since I have two different mobos with this).
I just looked up my Gigabyte GA-M55plus-S3G board and it also has the nvidia 0x0266/0x0267 (MCP51) devid controller...
My ECS GeForce6100SM-M board (currently in RAID configuration) has 0x03F6 (MCP61)
Unfortunately I can't test either of these soon :(
Re: Tired of Running Haiku Under VMs
Cool guys.
It looks like your sata controllers are supported ( or should be ) by the legacy sata driver.
Urias, hopefully you can test out one of those motherboards. The one of interest would be the ECS board. Because it has newer (MCP61) controller?
Ankur, if you could give your vendor id ( should be 0x10de for Nvidia ) & device id then we can find out if your sata controller is supported.
The best way to know if your hardware works, in Haiku, is always to give the brand, model, vendor id and device id. This way it can be matched up to Haiku source code.
Later,
Re: Tired of Running Haiku Under VMs
I've got the ECS GeForce6100SM-M myself, and it's able to boot Haiku fine. Though so far not much else works other than the video.
Vendor ID?
How do I get the vendor ID and stuff under Linux? KInfoCenter doesn't help much.
EDIT : I just heard about some 137gig limit. I have a 250GB HDD with Haiku on (Linux name) sda9 (total 10 partitions, 25gigs each). Can this be a problem?
Re: Vendor ID?
Thanks Michael. Good to hear that sata & video are working for you.
Ankur,
Ok, under Linux ( I had to boot into Fedora to check this ):
Type ( easy way ):
"lspci -nn | grep -i SATA "
My result ( copy yours like I've done below ):
01:0d.0 Mass storage controller [0180]: Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] Serial ATA Controller [1095:3112] (rev 02)
Notice at the end it says: " [1095:3112] ", 1095 is the Vendor ID, 3112 is the Device ID.
Your Vendor id should be 10de because that identifies Nvidia
OR you can do ( hard way ):
"lspci -nn" and search through to find your SATA controller.
BeOS had the hard drive limit because at the time Be Inc. did not realize that drive sizes would get bigger than 137GB in the future. Haiku does not have drive limit issue.
Re: Vendor ID?
BeOS had the hard drive limit because at the time Be Inc. did not realize that drive sizes would get bigger than 137GB in the future. Haiku does not have drive limit issue.
You know this for sure? Haiku uses the same boot block as R5 did - and this boot block has the offset to the partition start in it... I speculate that possibly a partition starting above the 137gb limit may actually be unable to boot.
Now, on the other hand, Haiku probably supports accessing a disk beyond 137gb, but booting from a partition starting beyond 137gb is a different issue.
Please let us know if you've successfully booted haiku from a partition beyond the first 137gb of the disk - I'd like to know for sure that this works... and I haven't had time to test it myself :(
Re: Vendor ID?
Now, on the other hand, Haiku probably supports accessing a disk beyond 137gb, but booting from a partition starting beyond 137gb is a different issue.
Good call Urias. I was thinking about Haiku supporting a drive bigger than 137GB in size ( which it should ). I can not say if Haiku will boot a partition that is over the 137GB limit - may or may not.
So, that could be an issue. But first thing is to find out the hardware Ankur has to see if it is even supported by Haiku. If so, then can move onto the other issues like this, etc.
Re: Vendor ID?
Correct, but I think he was referencing another forum post - I just wanted to make sure it wasn't being discounted here ;)
http://haiku-os.org/community/forum/installing_haiku_to_a_partition_from...
Actually, I just realized my statement that "Haiku uses the same boot block as R5" may be inaccurate... perhaps it appears that way because I formatted the specific partition from R5 rather than using the tools provided in the Haiku repository... I will check this.
Re: Tired of Running Haiku Under VMs
Here's the SATA stuff :
Did I mention that my sda9 is actually is under an extended partition? Is that a problem?
Re: Tired of Running Haiku Under VMs
Your device ids 0x0054, 0x0055 should both be supported by the legacy sata controller because they are both listed in there.
from legacy sata driver:
#define PCI_vendor_NVIDIA 0x10de
[snip]
#define PCI_device_CK804S1 0x0054
#define PCI_device_CK804S2 0x0055
[snip]
Sata driver is unlikely to be the problem. Some other things to check out:
1) Could be because your partition is over 137GB mark or
2) Partition is extended instead of primary or
3) Is your partition bfs formatted?
Try hitting [SPACEBAR] quickly when booting & it'll take you to safe mode. Check Console Debugging & that'll make the booting more verbose & you can see what error you are given.
Re: Tired of Running Haiku Under VMs
Here's the SATA stuff :
Did I mention that my sda9 is actually is under an extended partition? Is that a problem?
I boot Haiku from an extended partition, but it is a PATA system. The legacy_sata driver is very new, so it is possible your system shows up a bug in it. If you file a bug at http://dev.haiku-os.org with any information you can get then it will be seen by the people who may be able to help.
Re: Tired of Running Haiku Under VMs
I got the new Image.
Installed it from zeta onto a bootable partition using cp -a * /HaikuTest
Boot goes fine but I only see a blank blue screen with cursor.
When try safe mode with console output and safe video mode, I get in the haiku shell successfully.
Commands seem to work fine.
/var/log has no log file in it, So I cannot see what is the problem.
I have a Sata drive, but obviously shell works.
I usually use a usb mouse, but I have problem with a PS2 mouse also.
4 months ago I did have tacker up.
Any ideas?
Re: Tired of Running Haiku Under VMs
I haven't tried a recent build in some weeks - so maybe some recent changes have rendered something "unstable"...
I assume that since you are running Zeta on this same machine, you have a decent amount of RAM... (at least 128mb)
Perhaps some of the new VM changes are causing an issue with app_server, Tracker, etc?
Re: Tired of Running Haiku Under VMs
In today's xxx66/67 revisions I have the same phenomenon on a PATA system that previously worked fine. Either everything looks normal but I cannot launch any preferences or applications, or I see only the Terminal window and the blue background (no desktop icons, no menu/tracker). RAM is 512 MB. Shutting down or restarting doesn't work either.
Re: Tired of Running Haiku Under VMs
Yes, I have a giga byte of memory. :-)
Re: Tired of Running Haiku Under VMs
Hi Lengyel,
If an older version of Haiku worked for you ( ie: you had tracker up ). Then the code was changed & now not working for you. You should bring this up in the mailing list because that is where you'll get responses from the Haiku coders.
Without log file it'll be harder to figure out what is going wrong.
I have to test the newer Haiku & see if it gives me any problems. So, I can see if it affects me also or isolated to only "some" people having issues.
For diagnosis; you need to provide more information:
1) Motherboard chipset?
2) Processor?
3) RAM Total? ( you said 1GB RAM )
4) SATA or PATA? ( you said SATA )
5) Video Card?
Example:
1) Nvidia Nforce2 chipset 2) Athlon XP 3) 1GB RAM 4) PATA 5) ATI Radeon 8500 6) ps2 keyboard & mouse
Try selecting all the safe mode options & see if that works out.
And best to use ps2 mouse & keyboard which work better.
Also, if you have ( wait till I test latest Haiku image first ):
1) pata drive, try installing & using that
2) older video card; give that a try too
In BIOS, disable Plug & Play OS ( maybe go through & disable some other things too; ie: onboard sound, onboard network, usb, acpi - use apm, etc. ).
Re: Tired of Running Haiku Under VMs
I just tested newer Haiku image, version 22380.
1st Boot
Deskbar & Tracker crashed. I only had a blue background and a terminal window.
2nd Boot
Everything started up fine ( tracker, deskbar & terminal ), blue background with HAIKU logo & 3 desktop icons. Ran a few programs without issues.
3rd Boot
Tracker crashed on me.
I'd say newer Haiku is not that stable anymore ( too many changes going on to the code ). Anyone else want to confirm; boot Haiku a couple of times & see if deskbar &/or tracker crash?
Edit:
I re-copied the files to my partition & tried again & Tracker was crashing on start up.
A quick fix; in Terminal. type "cd /boot/beos/system", "./Tracker &"
and that should start up tracker for you.
Re: Tired of Running Haiku Under VMs
Could you please post a bug report at http://dev.haiku-os.org about this issues with back trace output (type "bt" in debug window).
This should help improving stability of Tracker/Deskbar a lot!
Thanks!
Re: Tired of Running Haiku Under VMs
Sure Diver. Done.
Funny thing is that I restarted my computer and it took a few boots to get Tracker to crash ( about eight boots and it crashed twice ).
Anyone else having a similar issue should add their comment ( & attach back trace info ) to the bug report I filed here:
http://dev.haiku-os.org/ticket/1509
Re: Tired of Running Haiku Under VMs
Dual-core or Dual-proc?
Sounds like the kind of flakiness you might experience with multi-threading and race conditions on an SMP machine...
Re: Tired of Running Haiku Under VMs
For me, it is single core Athlon XP 2400+ processor on Nforce2 chipset board.
But I believe those with multi core are experiencing Tracker crashing more frequently or all the time.
Looks like Marcus might have the same problem.
"The blue desktop appears, and I can enter Team Monitor using Ctrl+Alt+Del, but Tracker doesn't seem to work."
http://www.freelists.org/archives/haiku-development/09-2007/msg00112.html
Re: Tired of Running Haiku Under VMs
Yes, and it appears it was fixed:
http://www.freelists.org/archives/haiku-development/09-2007/msg00113.html
:)
Re: Tired of Running Haiku Under VMs
Sounds like this is a bigger issue somewhere.
Please add any additional comments you can provide to this bug:
http://dev.haiku-os.org/ticket/1512
It might be helpful if each person who experiences this issue were to list their hardware configuration, and where they got the haiku build they're testing (not to mention which rev works/doesn't work).