101–110 of 178 posts
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?
If you want to virtualize something with good performance on desktop windows you use Hyper-V; if you want to do it on mac you use Apple's Virtualization Framework; if you want to do it on Linux you use KVM. Desktop virtualization products used to bring the secret sauce with them; now that every OS ships with a well-integrated and well supported type 1 hypervisor they have lost much of the reason for existing. There's…
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 performance (and occasional flaky issues with drivers and whatnots).
Am I the only grouchy geezer here?:-)
Now go try to download it. All links are broken. https://knowledge.broadcom.com/external/article?articleNumbe... https://www.vmware.com/content/vmware/vmware-published-sites... https://customerconnect.vmware.com/web/vmware/downloads/info...
Another broken link...
Earlier quoted context omitted.
If you want to virtualize something with good performance on desktop windows you use Hyper-V; if you want to do it on mac you use Apple's Virtualization Framework; if you want to do it on Linux you use KVM. Desktop virtualization products used to bring the secret sauce with them; now that every OS ships with a well-integrated and well supported type 1 hypervisor they have lost much of the reason for existing. There's…
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…
Did you measure the performance hit? How often did you encounter driver trouble?
Earlier quoted context omitted.
Fortunately the open-source VM space is the best it has ever been these days. No reason at all to use proprietary crap anymore.
What open source options would you recommend for running Linux and Windows VM's on Windows? I've been unhappy with Virtualbox because the audio quality is abysmal which is an issue since I use screen reading software. I'm interested to try out VMWare Workstation since it's audio support was pretty good many years ago when I used it at a prior job.
Have been a happy Fusion Pro customer for years, including buying upgrades. A user can install 5 seats which includes both Workstation and Fusion, so I could have it on my Mac desktop, iMac, and Linux desktop. The licence was very clear it is kosher for commercial use. And it was perpetual, no worrying about annual renewals. Beware the new “free” licence, which is emphatically not for commercial use. Get caught accid…
Open-source would help if there's any desire to keep it alive, otherwise this is a nice gesture but I would read this as a signal that I should stick away from it because it's dead or a trap.
Pro free for now, or Pro is free abandonware. Both cases discourage adoption. Open-source would help if there's any desire to keep it alive, otherwise this is a nice gesture but I would read this as a signal that I should stick away from it because it's dead or a trap.
My VMs are doing pretty well if they last the quarter.
Earlier quoted context omitted.
Today this is mostly implemented by having a guest driver pass calls through to a layer on the host that does the actual rendering. While I agree that there is a lot of magic to making such an arrangement work, it's a terrible awful idea to suggest that relying on a vendor's emulation layer is how things should be done today. Proper GPU virtualization and/or partitioning is the right way to do it and the vendors need…
So you say having a decoupled arrangement in software (which happens to be a de facto open standard) is a "terrible awful idea" and that instead you should just rely on whatever your proprietary hardware graphics vendor proposes to you? Why? And that's assuming they propose anything at all. Even GVT-g breaks every other Linux release, is at risk of being abandoned by Intel (e.g. how they already abandoned the Xen ver…
Sandboxing, and resource quotas / allocations / reservations.
By itself, a paravirtualized GPU just treats each userland workload launched by any given guest onto the GPU, as all being siblings — exactly as if there was no virtualization and you were just running multiple workloads on one host.
And so, just like multiple GPU-using apps on a single non-virtualized host, these workloads will get "thin-provisioned" the resources they need, as they ask for them, with no advance reservation; and workloads may very well end up fighting over those resources, if they attempt to use a lot of them. You're just not supposed to run two things that attempt to use "as much VRAM as possible" at once.
This means that, on a multi-tenant hypervisor host (e.g. the "with GPU" compute machines in most clouds), a paravirtualized GPU would give no protection at all from one tenant using all of a host GPU's resources, leaving none left over for the other guests sharing that host GPU. The cloud vendor would have guaranteed each tenant so much GPU capacity — but that guarantee would be empty!
To enforce multi-tenant QoS, you need hardware-supported virtualization — i.e. the ability to make "all of the GPU" actually mean "some of the GPU", defining how much GPU that is on a per-guest basis.
(And even in PC use-cases, you don't want a guest to be able to starve the host! Especially if you might be running untrusted workloads inside the guest, for e.g. forensic analysis!)