171–178 of 178 posts
Orbstack now serves 100% of my virtualization and docker needs on macOS. Hopefully I'll never feel the need to install virtualbox or fusion or parallels ever again.
Orbstack is really nice on an M1. But occasionally I run into the need for a GUI application and then I'm stuck. Is it possible to use Orbstack for that?
Earlier quoted context omitted.
> bringing back ESXI for homelab users would be a good step too. It would be interesting if they did. So many have now tried Proxmox and liked it.
Yeah. Once the Proxmox team fixed the recent kernel bug that caused migration hangs with Ryzen/EPYC hardware (~20% of migrations just hung), things have been pretty great. Presently trialling a HA cluster with it, and likely to deploy that to a local data centre in the next few weeks.
Toggled back and forth maybe 5-6 times. Finally settled on Parallels and stopped upgrading Fusion. Haven't had problems since.
Glad it's free now, but that sometimes means the company is going to stop investing in it.
Earlier quoted context omitted.
Orbstack is really nice on an M1. But occasionally I run into the need for a GUI application and then I'm stuck. Is it possible to use Orbstack for that?
I haven't had that need, sorry. What applications?
Earlier quoted context omitted.
Am I the only one who explicitly does not want type 1 hyper visor on my desktop? Am I out dated? I like workstation and virtualbox because they're controllable and minimally impactful when I'm not using them. Installing hyper v (and historically even WSL - not sure if it's still the case but it was never sufficiently explicit) now makes my primary OS a guest, with potential impact on my gaming, multimedia, and other…
I used to worry about this overhead too but this appears to be nothing on modern CPUs. I had minuscule differences here-and-there on Intel 9th gen (9900K) but my current Intel 13th gen (13900K) has zero performance decrease with HV enabled. (At least on any perceptible level)
Note, I'm less worried about percentage performance, as some things just not working well at all, because of assumptions of direct hardware access vs reality of running under hyper v. I.e. Are ALL hardware calls and capabilities 100% absolutely completely available once your main Windows install is running as a VM? Not most, majority, should be good; but actually, seamlessly all? My understanding was No, but things may have changed for the better.
Given that this is owned Broadcom now, and they are going all in with squeezing every last drop from ESXi and similar offerings, I wonder what's gonna happen with Fusion in the future; while now you only pay for commercial usage, maybe they are going to let it rot over the years until it's no longer cutting edge software? Would they keep it as a loss-leader?
Fusion became basically worthless when you couldn't easily run Intel Windows on a Mac anymore because the underlying processor changed.
Earlier quoted context omitted.
The use case is mainly interoperability with VirtualBox; they can still keep thier own disk/vm formats, guest tools, etc. and use HyperV as the 'virtualization engine'. Users that have workflows that call out to VirtualBox can continue to work; a lot of vm image tools (vagrant, packer) continue to work, etc. But yes, of course you can also change your tools to use HyperV directly. "Having to use HyperV" is not actual…
> "Having to use HyperV" is not actually anything nefarious as the other comment seems to imply. You can't have two type 1 hypervisors running cooperatively on the bare metal and you cant implement your type 2 hypervisor hooks if you have a type 1 hypervisor running. The nefarious part is that Windows enables Hyper-V even if you don't actually use Hyper-V VMs and never will. KVM doesn't take exclusive control of VMX…
It does not actually enable it by default but there are many settings or apps that can cause it to become enabled. Virtualization-based-security, WSL, container tools, etc. Providing a hypervisor and related functionality is part of what a modern OS kernel should do! It's not nefarious!