4 ms·

On macOS nothing works better for vm audio than Parallels. Never experienced latency with it. However, I would never use Parallels with Vagrant. I do all my dev

by teilo 10y ago

On macOS nothing works better for vm audio than Parallels. Never experienced latency with it. However, I would never use Parallels with Vagrant. I do all my dev using VMWare.

colordrops 10y ago
What are the downsides to using it with vagrant?
- brazzledazzle 10y ago
  Not who you were asking but personally I'd be apprehensive about going off the beaten path with my tools. Less community support and effective Google searches.
- teilo 10y ago
  A few reasons: The VMWare Vagrant provider is a core provider, well maintained, and supported. The Parallels provider, by contrast, is third-party and rarely updated. Further, it does not even work unless you have a Parallels Professional subscription. Second: Stability. This is more historical, but Parallels has a bad history of being a poor citizen, eating up CPU power for no apparent reason (even when a VM is not running). Truth be told, I have not seen this issue in the last couple of major releases, but it happened so often in the past that I used VMWare exclusively for my Windows VM because I could rely on it not to trounce my CPU. I now use Parallels again for Windows, but only for Windows. Third: OS Support. Parallels is so tuned to specific OSes that if you try to use anything out of the ordinary, like OpenBSD, you will struggle. VMWare, by contrast, will even work with completely fringe OSes, such as Haiku (a beOS fork), which Parallels won't even boot. Finally, image portability: I can use the same base image for development and deployment to ESX. And speaking of ESX, VMWare Fusion can connect to ESX hosts and manage / pull up a console / upload and download to data stores. On a Mac this is invaluable because the vCenter plugins just do not work right on anything but Windows. For instance, I have never managed to upload an OVA or ISO to ESX using the vSphere Web Client on a Mac. It always fails.

by teilo 10y ago

On macOS nothing works better for vm audio than Parallels. Never experienced latency with it. However, I would never use Parallels with Vagrant. I do all my dev using VMWare.

colordrops 10y ago

What are the downsides to using it with vagrant?

brazzledazzle 10y ago
Not who you were asking but personally I'd be apprehensive about going off the beaten path with my tools. Less community support and effective Google searches.
teilo 10y ago
A few reasons: The VMWare Vagrant provider is a core provider, well maintained, and supported. The Parallels provider, by contrast, is third-party and rarely updated. Further, it does not even work unless you have a Parallels Professional subscription. Second: Stability. This is more historical, but Parallels has a bad history of being a poor citizen, eating up CPU power for no apparent reason (even when a VM is not running). Truth be told, I have not seen this issue in the last couple of major releases, but it happened so often in the past that I used VMWare exclusively for my Windows VM because I could rely on it not to trounce my CPU. I now use Parallels again for Windows, but only for Windows. Third: OS Support. Parallels is so tuned to specific OSes that if you try to use anything out of the ordinary, like OpenBSD, you will struggle. VMWare, by contrast, will even work with completely fringe OSes, such as Haiku (a beOS fork), which Parallels won't even boot. Finally, image portability: I can use the same base image for development and deployment to ESX. And speaking of ESX, VMWare Fusion can connect to ESX hosts and manage / pull up a console / upload and download to data stores. On a Mac this is invaluable because the vCenter plugins just do not work right on anything but Windows. For instance, I have never managed to upload an OVA or ISO to ESX using the vSphere Web Client on a Mac. It always fails.