4 ms·

Possibly it was needed for no-driver virtualization while preserving the same functionally of https://blogs.vmware.com/teamfusion/2020/07/fusion-big-sur-tech-pr

Possibly it was needed for no-driver virtualization while preserving the same functionally of https://blogs.vmware.com/teamfusion/2020/07/fusion-big-sur-tech-preview.html https://blogs.vmware.com/teamfusion/2020/07/fusion-big-sur-t... — note there’s a newer beta if you view the community link, I think, and I can’t find an equivalent public beta from Parallels yet but presumably they’re working hard on it...

pilif 6y ago
That VMWare tech preview ran in Beta 2 already which didn’t have this framework yet. No kernel extension required
- lstamour 6y ago
  I’ll admit though I ran it in Beta 2, I’m not aware of the details of which release had which API or which features VMware is using or not. It’s possible VMWare, having inside access to Apple docs, started working with private APIs that Apple has now made public? I really don’t know the details, I’d be happy if others chimed in, though. :)
saagarjha 6y ago
If by “no-driver” you mean “no kernel extensions”, that’s just part of Hypervisor.framework which shipped years ago. Perhaps they just added support for that?
- lstamour 6y ago
  My understanding is the Hypervisor framework didn’t easily support file system connectivity like fuse or different networking scenarios with virtio but perhaps the new, linked, APIs here in Big Sur now offer that? I presume Apple asked VMWare and Parallels why neither used the new Hypervisor framework and this was the resulting collaboration, but it might also have come about simply because Apple wanted to demo virtualization on ARM, of course...
  - kergonath 6y ago
    Parallels have been able to use Hypervisor.framework already since version 12, AFAIK. that was not yesterday.
    - lstamour 6y ago
      And it reportedly had limitations, including performance: https://communities.vmware.com/thread/551842 https://communities.vmware.com/thread/551842 This is something Apple and VMware are now obviously working on together for Big Sur.
stephenr 6y ago
Parallels has had a shipping product that uses Hypervisor.framework for a couple of years - its how they ship Parllels Lite (or whatever it's called) in the MAS. In the non-MAS version there's a per-VM option to use either Parallels' or Apples' Hypervisor.

pilif 6y ago

That VMWare tech preview ran in Beta 2 already which didn’t have this framework yet. No kernel extension required

lstamour 6y ago
I’ll admit though I ran it in Beta 2, I’m not aware of the details of which release had which API or which features VMware is using or not. It’s possible VMWare, having inside access to Apple docs, started working with private APIs that Apple has now made public? I really don’t know the details, I’d be happy if others chimed in, though. :)

saagarjha 6y ago

If by “no-driver” you mean “no kernel extensions”, that’s just part of Hypervisor.framework which shipped years ago. Perhaps they just added support for that?

lstamour 6y ago
My understanding is the Hypervisor framework didn’t easily support file system connectivity like fuse or different networking scenarios with virtio but perhaps the new, linked, APIs here in Big Sur now offer that? I presume Apple asked VMWare and Parallels why neither used the new Hypervisor framework and this was the resulting collaboration, but it might also have come about simply because Apple wanted to demo virtualization on ARM, of course...
- kergonath 6y ago
  Parallels have been able to use Hypervisor.framework already since version 12, AFAIK. that was not yesterday.
  - lstamour 6y ago
    And it reportedly had limitations, including performance: https://communities.vmware.com/thread/551842 https://communities.vmware.com/thread/551842 This is something Apple and VMware are now obviously working on together for Big Sur.

stephenr 6y ago

Parallels has had a shipping product that uses Hypervisor.framework for a couple of years - its how they ship Parllels Lite (or whatever it's called) in the MAS. In the non-MAS version there's a per-VM option to use either Parallels' or Apples' Hypervisor.