Native virtualization for macOS • Hacker News Board

Re: Native virtualization for macOS

#61

Post by pmarreck » Wed, Nov 09, 2016, 7:18 PM UTC

nailer wrote: post #25

mrweasel wrote: post #19

Earlier quoted context omitted.

VMware Fusion isn't discontinued. I might be wrong, but wasn't the last update in September? And you can still buy it from VMware.

http://www.theregister.co.uk/2016/01/27/vmware_fusion_and_wo... Entire team got fired, but yes still being maintained from a new team of outsourced devs.

oh jesus. somehow this flew under my radar. this isn't good

Re: Native virtualization for macOS

#62

Post by blacksmith_tb » Wed, Nov 09, 2016, 7:25 PM UTC

izik_e wrote: post #51

riobard wrote: post #49

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.

We now support usb, try it. Note that we have a bug that make it work only with mass stirage device, but we will release fix soon.

Are you intending to offer a shared clipboard? That is quite useful for running a guest OS with a GUI...

Re: Native virtualization for macOS

#63

Post by izik_e2 » Wed, Nov 09, 2016, 7:26 PM UTC

blacksmith_tb wrote: post #62

izik_e wrote: post #51

Earlier quoted context omitted.

We now support usb, try it. Note that we have a bug that make it work only with mass stirage device, but we will release fix soon.

Are you intending to offer a shared clipboard? That is quite useful for running a guest OS with a GUI...

There is copy paste tools both for windows and linux

Re: Native virtualization for macOS

#64

Post by oddevan » Wed, Nov 09, 2016, 7:54 PM UTC

Graphon1 wrote: post #43

Why would I switch from VirtualBox ?

In theory? Veertu uses the built-in Hypervisor.framework from macOS, so it can run without installing a kernel extension. I think they're still working on building out features, but for my basic needs I prefer it on that basis alone.

Re: Native virtualization for macOS

#65

Post by blacksmith_tb » Wed, Nov 09, 2016, 8:06 PM UTC

izik_e2 wrote: post #63

blacksmith_tb wrote: post #62

Earlier quoted context omitted.

Are you intending to offer a shared clipboard? That is quite useful for running a guest OS with a GUI...

There is copy paste tools both for windows and linux

Ah, I see the option now, which appears to be on by default. The test VM I just set up (a clean install from ubuntu-gnome-16.04-desktop-amd64.iso) doesn't copy or paste from host to guest or vice versa. I would be happy to log an issue in Github, is there any debug info I should provide?

Re: Native virtualization for macOS

#66

Post by shykes » Wed, Nov 09, 2016, 8:47 PM UTC

izik_e2 wrote: post #42

rcarmo wrote: post #41

Anyone know if this interacts OK with Docker beta? that uses xhyve as well, so before I install both I'd like to make sure nothing breaks.

yea, it is working togather

If you hit any issues on the Docker side, let us know on the support forums and we'll fix it.

Re: Native virtualization for macOS

#67

Post by fensipens » Wed, Nov 09, 2016, 8:50 PM UTC

george4n wrote: post #59

oneplane wrote: post #54

Earlier quoted context omitted.

Makes sense, 802.11 isn't Ethernet.

So how is VirtualBox able to bridge over Wi-Fi?

Bridging to a wireless interface is done differently from bridging to a wired interface, because most wireless adapters do not support promiscuous mode. All traffic has to use the MAC address of the host's wireless adapter, and therefore VirtualBox needs to replace the source MAC address in the Ethernet header of an outgoing packet to make sure the reply will be sent to the host interface. When VirtualBox sees an incoming packet with a destination IP address that belongs to one of the virtual machine adapters it replaces the destination MAC address in the Ethernet header with the VM adapter's MAC address and passes it on. VirtualBox examines ARP and DHCP packets in order to learn the IP addresses of virtual machines.

https://www.virtualbox.org/manual/ch06.html#network_bridged

Re: Native virtualization for macOS

#68

Post by bonzini » Wed, Nov 09, 2016, 8:56 PM UTC

izik_e wrote: post #48

stephenr wrote: post #47

Earlier quoted context omitted.

Yeah that part threw me too, but their website does say: "We are making Veertu Desktop Open source. It will be available on https://github.com/veertuinc/vdhh and will continue to be developed and maintained." Maybe a wording issue in the README, and the desktop app is intended to be open source and built from (the|another) repo too?

Hi, currently the hupervisor was opensourced, we are looking to open the ui and the vagrant plugin as well, the reason we didnt put the ui in that project was that wr beleived ot would be cleaner for the opensource community to have cli hypervisor project. the only part we might have issue to opensource is our windows drivers

Izik, now that you open-sourced it, why don't you say that it is based on QEMU? Everybody knew it was, and anybody could have asked Apple to pull your app from the store. It would be nice if you guys showed some appreciation for the fact that QEMU developers didn't do that right away.

Re: Native virtualization for macOS

#69

Post by FireBeyond » Wed, Nov 09, 2016, 9:02 PM UTC

stephenr wrote: post #23

rvanmil wrote: post #16

Earlier quoted context omitted.

That's the free version, not the business edition which I paid for in the app store.

The free version has all the paid features now. I asked the authors on Twitter about this, they said they will be releasing related products soon that will cover their revenue stream.

And of course they'll grandfather in the people who paid for the now free product less than 6 months ago, right?

Re: Native virtualization for macOS

#70

Post by izik_e2 » Wed, Nov 09, 2016, 9:05 PM UTC

bonzini wrote: post #68

izik_e wrote: post #48

Earlier quoted context omitted.

Hi, currently the hupervisor was opensourced, we are looking to open the ui and the vagrant plugin as well, the reason we didnt put the ui in that project was that wr beleived ot would be cleaner for the opensource community to have cli hypervisor project. the only part we might have issue to opensource is our windows drivers

Izik, now that you open-sourced it, why don't you say that it is based on QEMU? Everybody knew it was, and anybody could have asked Apple to pull your app from the store. It would be nice if you guys showed some appreciation for the fact that QEMU developers didn't do that right away.

We will be happy to give credit, let me contact you to see how to do this the best