This is very nice! HiDPI mode works perfectly for Windows 10 guest (unlike VirtualBox, which has weird graphic issues). Unfortunately macOS Hypervisor.Framework does not support USB devices ( https://veertu.com/knowledgebase/usb-support/ ), which makes Veertu useless to me, as the only reason I use Windows VM is to attach stupid USB tokens for certain banking use cases.
Native virtualization for macOS
51–60 of 103 posts
Re: Native virtualization for macOS
#52Re: Native virtualization for macOS
#53I tried converting a linux vm I frequently use via vagrant just now, and it seems to work well except for network bridging: You can't bridge over wifi. Kindof a deal-breaker.
The relevant page[1] explains it thus: "Due to features of wireless protocol, level 2 bridges don’t work over Wi-Fi, and so you can’t use wireless interface of your Mac to route bridge traffic to external network – only among VMs and host."
[1] https://veertu.com/knowledgebase/vagrant-setup-instructions/
Re: Native virtualization for macOS
#54Well, I'm excited by the potential of having something better than Virtualbox available for free. I tried converting a linux vm I frequently use via vagrant just now, and it seems to work well except for network bridging: You can't bridge over wifi. Kindof a deal-breaker. The relevant page[1] explains it thus: "Due to features of wireless protocol, level 2 bridges don’t work over Wi-Fi, and so you can’t use wireless…
Re: Native virtualization for macOS
#55I've tried this as I was really excited after hearing about fusions discontinuation and how incredibly poorly performing virtualbox IO and network is. I found it to be even slower than virtualbox which I have no idea how this is possible. Tested on a late 2015 5k iMac top specced and a late 2015 MacBook top specced both running OSX 10.11 at the time. I will re-test the latest version with MacOS 10.12.
Totally different results here. I use a Surface Book now but on my Mac (2013 MBA) Veertu destroyed VMware and VirtualBox for interactive latency. Ie, VirtualBox and VMware were slow to the point I'd consider them unusable (I'm latency sensitive, eg, I consider Eclipse to the be same and other people think it's fine). Veertu made me actually test in Edge again. Did you still have VMware or VirtualBox drivers installed…
Re: Native virtualization for macOS
#56I'm always leery of adopting a technology which will be fundamental to my work environment when I don't know how long it will be supported, or if I will have to change my use of it due to licensing issues.
Re: Native virtualization for macOS
#57How is support for this going to be funded? Will there be a commercial license which will pop up later? Paid features? It would be great to have some information. I'm always leery of adopting a technology which will be fundamental to my work environment when I don't know how long it will be supported, or if I will have to change my use of it due to licensing issues.
Re: Native virtualization for macOS
#58How is support for this going to be funded? Will there be a commercial license which will pop up later? Paid features? It would be great to have some information. I'm always leery of adopting a technology which will be fundamental to my work environment when I don't know how long it will be supported, or if I will have to change my use of it due to licensing issues.
The version that can run only images from their library is free-as-in-beer. The version that you can create your own VMs with, is paid.
Re: Native virtualization for macOS
#59Well, I'm excited by the potential of having something better than Virtualbox available for free. I tried converting a linux vm I frequently use via vagrant just now, and it seems to work well except for network bridging: You can't bridge over wifi. Kindof a deal-breaker. The relevant page[1] explains it thus: "Due to features of wireless protocol, level 2 bridges don’t work over Wi-Fi, and so you can’t use wireless…
Makes sense, 802.11 isn't Ethernet.
Re: Native virtualization for macOS
#60No support for storing VMs on an external drive? Not even symlinking seems to work (VMs don't get saved to the list).