4 ms·

Does this have to be this complex? Can't I just fire up a VirualBox as I do on Linux and Windows and go ahead?

by qwerty456127 4y ago

naikrovek 4y ago
github.com/cirruslabs/tart is what I use, because it is a command-line tool. also, death to oracle.
CharlesW 4y ago
You sure can. This is developer sample code, rather than something a typical user would use.
mmis1000 4y ago
I think this code is for who make VirualBox or similiar management software instead of end user. It basically demonstrate how to use macos's api to launch a virtual machine.
philipkglass 4y ago
You can, but running Linux with a graphical desktop on VirtualBox under MacOS has become extremely sluggish in my experience. I don't know whether newer releases of MacOS or VirtualBox itself are to blame. It was much snappier 8 years ago even though I had a significantly slower laptop then.
- coldtea 4y ago
  >You can, but running Linux with a graphical desktop on VirtualBox under MacOS has become extremely sluggish in my experience. Huh? It's actually faster than ever, and near native experience. And the post is not about "how to run" a virtual machine as an end user or dev (for that the way the parent describes is still the suggested way). It's about how to program running it under the hood if you're a developer who wants to develop something like a program that manages virtual machines or that hosts and runs one.
  - philipkglass 4y ago
    I'm only referring to the VirtualBox experience asked about by qwerty456127. Running e.g. Debian with Gnome under MacOS became extremely sluggish for me. The screen re-renders slowly, like running a remote desktop over a slow network link. I did a lot of searching and setting-tweaking when I encountered the problem earlier this year. I never found a satisfactory resolution. I tried this fix: https://mkyong.com/mac/virtualbox-running-slow-and-lag-on-macos-macbook-pro/ https://mkyong.com/mac/virtualbox-running-slow-and-lag-on-ma... as well as others suggested on the VirtualBox forums, but couldn't get it running smoothly. I didn't have any trouble with a similar setup several years ago.
    - coldtea 4y ago
      Ah, sorry, glossed over the Virtualbox part - thought it was about generally about running a VM on a Mac. I used to use Virtuabox on x86 Mac until 3-4 years ago, don't know if it was changed - but then again, I used it for headless Linux only.
  - qwerty456127 4y ago
    > It's about how to program running it under the hood if you're a developer who wants to develop something like a program that manages virtual machines Has somebody already done that perhaps? Is there a reasonable alternative to VirtualBox/WMWare using the optimal way to run a VM on a Mac? I don't mind paying if it's worth it. I have zero experience of Mac development but I am going to need to run Windows 7 (to use IE6 with old crypto to access an outdated state-ran system) on an M2 MacBook next week. What's the best way to achieve that?
    - kergonath 4y ago
      > Has somebody already done that perhaps? Yes. And there have been several examples of small or independent developers cobbling together VM applications based on Apple’s frameworks in the last year or so. I do my know how many will actually survive but there is quite a bit of developer interest. > Is there a reasonable alternative to VirtualBox/WMWare using the optimal way to run a VM on a Mac? I don't mind paying if it's worth it. I don’t know about VMWare, but Parallels does this (for money, I am not a fan of their subscription model). AFAIK the best free equivalent is UTM, which can use either Apple’s frameworks or QEMU: https://mac.getutm.app/ https://mac.getutm.app/ . > I have zero experience of Mac development but I am going to need to run Windows 7 (to use IE6 with old crypto to access an outdated state-ran system) on an M2 MacBook next week. What's the best way to achieve that? I would try UTM, personally.
0x0 4y ago
Not on Apple Silicon arm64 macs
- deleted 4y ago
  [deleted]
olliej 4y ago
This documentation is more for the people who make virtualbox, rather than end users. All this is stuff that VirtualBox, etc already do on intel, you just don’t see it because you’re the end user.

Does this have to be this complex? Can't I just fire up a VirualBox as I do on Linux and Windows and go ahead?

naikrovek 4y ago

github.com/cirruslabs/tart is what I use, because it is a command-line tool. also, death to oracle.

CharlesW 4y ago

You sure can. This is developer sample code, rather than something a typical user would use.

mmis1000 4y ago

I think this code is for who make VirualBox or similiar management software instead of end user. It basically demonstrate how to use macos's api to launch a virtual machine.

philipkglass 4y ago

You can, but running Linux with a graphical desktop on VirtualBox under MacOS has become extremely sluggish in my experience. I don't know whether newer releases of MacOS or VirtualBox itself are to blame. It was much snappier 8 years ago even though I had a significantly slower laptop then.

coldtea 4y ago
>You can, but running Linux with a graphical desktop on VirtualBox under MacOS has become extremely sluggish in my experience. Huh? It's actually faster than ever, and near native experience. And the post is not about "how to run" a virtual machine as an end user or dev (for that the way the parent describes is still the suggested way). It's about how to program running it under the hood if you're a developer who wants to develop something like a program that manages virtual machines or that hosts and runs one.
- philipkglass 4y ago
  I'm only referring to the VirtualBox experience asked about by qwerty456127. Running e.g. Debian with Gnome under MacOS became extremely sluggish for me. The screen re-renders slowly, like running a remote desktop over a slow network link. I did a lot of searching and setting-tweaking when I encountered the problem earlier this year. I never found a satisfactory resolution. I tried this fix: https://mkyong.com/mac/virtualbox-running-slow-and-lag-on-macos-macbook-pro/ https://mkyong.com/mac/virtualbox-running-slow-and-lag-on-ma... as well as others suggested on the VirtualBox forums, but couldn't get it running smoothly. I didn't have any trouble with a similar setup several years ago.
  - coldtea 4y ago
    Ah, sorry, glossed over the Virtualbox part - thought it was about generally about running a VM on a Mac. I used to use Virtuabox on x86 Mac until 3-4 years ago, don't know if it was changed - but then again, I used it for headless Linux only.
- qwerty456127 4y ago
  > It's about how to program running it under the hood if you're a developer who wants to develop something like a program that manages virtual machines Has somebody already done that perhaps? Is there a reasonable alternative to VirtualBox/WMWare using the optimal way to run a VM on a Mac? I don't mind paying if it's worth it. I have zero experience of Mac development but I am going to need to run Windows 7 (to use IE6 with old crypto to access an outdated state-ran system) on an M2 MacBook next week. What's the best way to achieve that?
  - kergonath 4y ago
    > Has somebody already done that perhaps? Yes. And there have been several examples of small or independent developers cobbling together VM applications based on Apple’s frameworks in the last year or so. I do my know how many will actually survive but there is quite a bit of developer interest. > Is there a reasonable alternative to VirtualBox/WMWare using the optimal way to run a VM on a Mac? I don't mind paying if it's worth it. I don’t know about VMWare, but Parallels does this (for money, I am not a fan of their subscription model). AFAIK the best free equivalent is UTM, which can use either Apple’s frameworks or QEMU: https://mac.getutm.app/ https://mac.getutm.app/ . > I have zero experience of Mac development but I am going to need to run Windows 7 (to use IE6 with old crypto to access an outdated state-ran system) on an M2 MacBook next week. What's the best way to achieve that? I would try UTM, personally.

0x0 4y ago

Not on Apple Silicon arm64 macs

deleted 4y ago
[deleted]

olliej 4y ago

This documentation is more for the people who make virtualbox, rather than end users. All this is stuff that VirtualBox, etc already do on intel, you just don’t see it because you’re the end user.