Either I’m just too used to slow machines, or my Phenom II X4 (and previously my Athlon II X2) has no real issues running Haiku on VirtualBox (6.1.14, 6.1.40, and now 7.0.2).
I’m using real HDD/Partitions as storage… the rest of my VBox settings are pretty straight forward:
4 Cores, 2048 MB of RAM, 32 VRAM, VT-x/AMD-v, Nested Pagination, PAE/NX, KVM paravirtualization (that’s due to using the same VM to access a Linux install on that HDD).
VMSVGA graphics (as recomended by VBox), installed vmware_addons on Haiku to make use of that graphics driver.
ICH97 for audio, Intel PRO/1000MT Desktop for LAN (bridged).
My only complain, performance wise, is with large filesystem operations (deleting/stating big repo trees),but that also happens when running on bare metal, and only under Haiku, so, not a VBox issue.
Edit: just to clarify… I use VBox 7.02 on Win 10 LTSC 2021 (Hyper-V or WSL not even installed) most of the times with no real performance issues. Not much different from my old Linux install with 6.x there.
It seems in Windows you can only use one type of virtualisation. So indeed if you activate Hyper-V you will get virtualbox to use it’s slower emulation mode instead of virtualization. This should be visible in virtualbox settings then.
I can second this on macOS after upgrading to VirtualBox 7. The window rendering and window movement both jump and lag behind,; I’ve never had this problem in Haiku or VirtualBox, so I wonder why it’s doing this. I’ll try to think of a solution because I’d like to review beta4 when it comes out…
In replying to my last VBox post (and the host is macOS on Intel), I’ve tried turning paravirtualization off completely, turning nested paging on and off, changing the disk configuration, giving the VM more graphics memory, and the tearing and lagging window bug is still there. To test this out yourself, open the Leaf menu and open the About box or any basic app. Haiku will slowly draw the window when opening it and draw it when closing it, and dragging isn’t smooth either.
I’ll see if another VM works better and post again but yeah, VirtualBox 7 does not seem to like Haiku so far; 6 worked fine.
A shot in the dark here but… as mentioned, Haiku on VBox works really OK even on my Phenom II X4 on Win10… EXCEPT… when using the “Power Saver” power-plan. In that case, booting up the VM IS slow, and the GUI redraws gets slower.
But switching to “Balanced” makes it snappy again.
I switch between them as needed to save some watts.
Maybe this could be what’s causing (or worsening) the slowdowns for other people?
So I tried the advice from @Lrrr and played with the number of cores, it didn’t make any difference. I tried the advice from @Diver and set the NSHighResolutionCapable XML key inside /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/Info.plist to false.
Then I went back to try to start the Haiku VM. That gave me a signal 9 error when I tried to start Haiku, which was really strange…
So I then tried to start other VMs and found the error didn’t just happen to only the Haiku VM, but affected all machines, which all ended in this:
Far as I could tell on looking at the details, the reason is that somehow editing that file tripped something with the VirtualBox app far as I can tell with an ‘invalid signature’ in the app now (freaking security on macOS 12.6) Putting the ‘corrupt’ VirtualBox.app in the trash and reinstalling 7.0.4 fixed the problem. But now Haiku is the way it was again…
It might be the future or rather a solid alternative to VirtualBox or VMWare if supported.
I’m just trying to find the latest version of UTM which works in OSX 10.15.7 (Catalina) and found this on GitHub “Frontend designed from scratch for macOS 11 and iOS 11+ using the latest and greatest APIs”