Neat, but this looks very specialized for a single person's config. I wouldn't want to run this on my machine seeing as it removes apt sources and does a bunch of other system changes unrelated to installing a macOS guest.
Despite these being optional tweaks in the menu, I'm also surprised by how this is the default. I guess the options are for PVE updates.
"Disclaimer for dev/student/test purposes only."
Shouldn't be used with enterprise license, which may be against ToS.
The original intent is to avoid custom hardware configurations by using PVE as a layer. Hackintosh on bare metal can take days to figure out on new hardware.
Yes, this is correct. There seem to be a lot of people confused about the benefit of this in the thread, but it’s very simple: This tool exists essentially as a replacement for doing a full Hackintosh build of a system. You install Proxmox on a machine with a GPU, set this up, pass through the GPU and any other PCIe cards you want to run, and you’re in business.
It turns a days-long process into something that you can be up and running within like an hour. With OSX-KVM you have to set up the machine to be ready to do all the stuff like passthrough. This leverages the fact that Proxmox makes all that stuff super-simple.
It has to be AMD specifically, with some cards working better than others. Really old Nvidia cards work if you’re willing to go all the way back to High Sierra, though I haven’t tested it with this specific setup.
Intel iGPUs work on bare metal up until about tenth gen Core series, but I don’t know if you can pass them through with Proxmox.
I don't know why you got downvoted, because you are right. There is no problem with keeping the Ceph repos, and you can use it with the community repos.
How is this easier than OSX-KVM? I can't imagine how proxmox is easier (or better for most use-cases I can think of) than qemu.
EDIT: Script just immediately tries to apt-get stuff. Nah. Oh lord and then helps itself to editting your apt sources. (All just to get git? How odd.) Before downloading another un-tagged/un-versioned link and excuting it. Nah nah nah.
I don't like the untagged/unversioned script either but...
Proxmox is easy. To me Proxmox is not just a bit but much easier than "directly running QEMU". It's also got ZFS for free working out of the box. I'm not saying it's secure. I'm not saying it's giving you the utmost control. I'm saying Proxmox is the definition of easy.
Because I can manage it in a relatively understandable web interface and not have to deal with a bunch of config files. It's also significantly easier than Hackintoshing the machine, which is what I did previously.
I see you're a nixos enthusiast, so I take it you enjoy config files. I just like having a machine I don't have to think about.
I use this script on my Z420 with a Xeon and RX570 GPU (which I use to access Mac-specific apps remotely). It works really well. Excellent script, though I can’t go above Monterey with it, because of CPU limitations on the Xeon.
On top of the GPU, I pass through a USB-C card. I did have some problems with getting the WiFi card I have working but I have it plugged in via Ethernet anyway so not much of a problem.
My main reason for this is to have an easy way to access graphics software in the relatively rare cases I need access to Photoshop, Illustrator, or InDesign specifically.
Even if it did dial home, do you think Apple is going to come after you, single human being, running BS-tier workloads on a VM you're technically not licensed to run? They are a $1T company or thereabouts, they literally do not care about you.
curling some random install script from some domain I've never heard of and is possibly unrelated to this GitHub repo? great! what could possibly go wrong?
Always review scripts before running, regardless of origin, Github isn't always safe.
The domain redirects to github due to the changing commit hash raw URL.
You also have to cross-check the 4 kexts checksum with the origin in the OpenCore ISO, including binaries in other projects like OSX-KVM. Thankfully there are no binaries that require reproducible build setup.
I always try to read the source script before running it, unless it’s something I trust highly (brew, for example or tteck scripts in the case of PVE). Even then, I read some of them just to see what it does under the hood.
Almost totally OT, but since this is fundamentally about QEMU ...
... yesterday I needed to access data in a MySQL database that was shutdown in 2022. At that time, it had been managed by MySQL 5.5.62. On my current Debian system, we are at 10.X (MariaDB). I had a backup of the entire DB folder and tried to get MySQL/MariaDB to read it. Tried a couple of different things. Failure.
Then ... grab Ubuntu 14.04 ISO ... type virt-manager in a terminal ... less than 15 minutes later I'm in the MySQL shell running queries on the old DB.
The Linux kernel's "don't break user space" motto probably means that you don't need a full VM, just a container that has that old version of MySQL and you probably can run it just fine with docker or podman.
I recently tried to run a CentOS 7 container (LXC) on ProxMox 8 and it didn't work because CentOS 7 uses cgroup v1 which is not supported anymore by most recent distros (they are all on cgroups v2).
This appears to be under a _very_ restrictive license, from the file `setup`:
All rights reserved - You may not copy, reproduce, distribute, publish, display, perform, modify, create derivative works, transmit, or in any way exploit any such content, nor may you distribute any part of this content over any network, including a local area network, sell or offer it for sale, or use such content to construct any kind of database.
it's removing the enterprise and ceph repos from proxmox. i can take a screenshot to show you what it's removing.
Basically if you're not paying for proxmox, and you're running a single node, there's absolutely no reason to have either of those apt sources in the config.
I don't remove them, and it does pollute the log at the bottom of proxmox interface with apt errors, so i could see why someone would just disable them as a matter of course.
whenever i release stuff on github it's kinda in this sort of state, "it works on my setup." i'm not a software developer or publisher and TBQH i'd be shocked if anyone ran my code other than me.
Neat, but this looks very specialized for a single person's config. I wouldn't want to run this on my machine seeing as it removes apt sources and does a bunch of other system changes unrelated to installing a macOS guest.
https://github.com/luchina-gabriel/OSX-PROXMOX/blob/7ca3dc81... https://github.com/luchina-gabriel/OSX-PROXMOX/blob/7ca3dc81... https://github.com/luchina-gabriel/OSX-PROXMOX/blob/7ca3dc81...
Despite these being optional tweaks in the menu, I'm also surprised by how this is the default. I guess the options are for PVE updates.
"Disclaimer for dev/student/test purposes only." Shouldn't be used with enterprise license, which may be against ToS.
The original intent is to avoid custom hardware configurations by using PVE as a layer. Hackintosh on bare metal can take days to figure out on new hardware.
Yes, this is correct. There seem to be a lot of people confused about the benefit of this in the thread, but it’s very simple: This tool exists essentially as a replacement for doing a full Hackintosh build of a system. You install Proxmox on a machine with a GPU, set this up, pass through the GPU and any other PCIe cards you want to run, and you’re in business.
It turns a days-long process into something that you can be up and running within like an hour. With OSX-KVM you have to set up the machine to be ready to do all the stuff like passthrough. This leverages the fact that Proxmox makes all that stuff super-simple.
> ... pass through the GPU
I've got GPU passthrough working under Proxmox but not for Hackintosh. Will a Hackintosh work with most GPUs or only with certain brands/models?
It has to be AMD specifically, with some cards working better than others. Really old Nvidia cards work if you’re willing to go all the way back to High Sierra, though I haven’t tested it with this specific setup.
Intel iGPUs work on bare metal up until about tenth gen Core series, but I don’t know if you can pass them through with Proxmox.
This list is a good place to start: https://dortania.github.io/GPU-Buyers-Guide/modern-gpus/amd-...
If you just want to mess around, RX 580s are pretty cheap on eBay these days and are fast enough to handle most tasks on a Mac.
This is all standard proxmox setup and is step 1 for anyone running the free version
> This is all standard proxmox setup and is step 1 for anyone running the free version
I run the free version and do not delete the Ceph repos (especially since I'm using Ceph amongst my storage options):
At the very least run a sed command to just comment out any/all lines in the files instead of nuking them.Or change the file extension to anything else than .list
I don't know why you got downvoted, because you are right. There is no problem with keeping the Ceph repos, and you can use it with the community repos.
How is this easier than OSX-KVM? I can't imagine how proxmox is easier (or better for most use-cases I can think of) than qemu.
EDIT: Script just immediately tries to apt-get stuff. Nah. Oh lord and then helps itself to editting your apt sources. (All just to get git? How odd.) Before downloading another un-tagged/un-versioned link and excuting it. Nah nah nah.
I don't like the untagged/unversioned script either but...
Proxmox is easy. To me Proxmox is not just a bit but much easier than "directly running QEMU". It's also got ZFS for free working out of the box. I'm not saying it's secure. I'm not saying it's giving you the utmost control. I'm saying Proxmox is the definition of easy.
Proxmox is QEMU, but with GUI and lot of infra stuff.
It’s much less of a pain when passthrough is involved, FWIW.
Why? How? Especially if Proxmox is just using qemu under the hood?
Because I can manage it in a relatively understandable web interface and not have to deal with a bunch of config files. It's also significantly easier than Hackintoshing the machine, which is what I did previously.
I see you're a nixos enthusiast, so I take it you enjoy config files. I just like having a machine I don't have to think about.
Lol but qemu doesn't use config files.
> I just like having a machine I don't have to think about.
After a crack about NixOS? Funny times tonight.
Just because you don't know what the hell you're talking about doesn't mean you have to take it out on me.
Virsh does.
Proxmox uses qemu for vm’s.
Semi-related: Windows or macOS in a Docker Container
https://github.com/dockur
This is a great thanks for sharing.
I'm used to physical hackintosh & OS-KVM; how does docker macOS compare to them in terms of user experience? Is it usable for xcode development?
I use this script on my Z420 with a Xeon and RX570 GPU (which I use to access Mac-specific apps remotely). It works really well. Excellent script, though I can’t go above Monterey with it, because of CPU limitations on the Xeon.
Oh, almost forgot, I actually wrote about my process getting this set up about six months ago:
https://tedium.co/2024/04/08/hackintosh-proxmox-vm-experienc...
On top of the GPU, I pass through a USB-C card. I did have some problems with getting the WiFi card I have working but I have it plugged in via Ethernet anyway so not much of a problem.
My main reason for this is to have an easy way to access graphics software in the relatively rare cases I need access to Photoshop, Illustrator, or InDesign specifically.
There is also Docker OSX https://github.com/sickcodes/Docker-OSX
one problem I found was you need to be connected to the internet to install MacOSX?
also apparently its a violation of Apple license if you run OSX on a non-Apple hardware?
so im concerned if I connect my VM to the internet and install OSX on my proxmox it will dial home to Apple :/
Even if it did dial home, do you think Apple is going to come after you, single human being, running BS-tier workloads on a VM you're technically not licensed to run? They are a $1T company or thereabouts, they literally do not care about you.
Top tip: don’t sign into iCloud.
I did this once on a hackintosh got locked out. Watching my various services stop working was rather distressing.
Yes!!! This happened to me also. It took me a day to get my account working on all devices again.
I never had any issues with being signed into iCloud and Hackintosh.
curling some random install script from some domain I've never heard of and is possibly unrelated to this GitHub repo? great! what could possibly go wrong?
That's the first thing that's ever gone wring!
>What could possibly go wring?
No such domain ( ͡° ͜ʖ ͡°)
a flannel after a bath
The author really hates the Proxmox enterprise repo sources.list.d file, he deletes it several times ('rm -rf') at least in 2 files
Always review scripts before running, regardless of origin, Github isn't always safe.
The domain redirects to github due to the changing commit hash raw URL.
You also have to cross-check the 4 kexts checksum with the origin in the OpenCore ISO, including binaries in other projects like OSX-KVM. Thankfully there are no binaries that require reproducible build setup.
I always try to read the source script before running it, unless it’s something I trust highly (brew, for example or tteck scripts in the case of PVE). Even then, I read some of them just to see what it does under the hood.
Almost totally OT, but since this is fundamentally about QEMU ...
... yesterday I needed to access data in a MySQL database that was shutdown in 2022. At that time, it had been managed by MySQL 5.5.62. On my current Debian system, we are at 10.X (MariaDB). I had a backup of the entire DB folder and tried to get MySQL/MariaDB to read it. Tried a couple of different things. Failure.
Then ... grab Ubuntu 14.04 ISO ... type virt-manager in a terminal ... less than 15 minutes later I'm in the MySQL shell running queries on the old DB.
Modern VM stuff is just fucking amazing.
The Linux kernel's "don't break user space" motto probably means that you don't need a full VM, just a container that has that old version of MySQL and you probably can run it just fine with docker or podman.
I recently tried to run a CentOS 7 container (LXC) on ProxMox 8 and it didn't work because CentOS 7 uses cgroup v1 which is not supported anymore by most recent distros (they are all on cgroups v2).
So your container might or might not work.
This appears to be under a _very_ restrictive license, from the file `setup`:
All rights reserved - You may not copy, reproduce, distribute, publish, display, perform, modify, create derivative works, transmit, or in any way exploit any such content, nor may you distribute any part of this content over any network, including a local area network, sell or offer it for sale, or use such content to construct any kind of database.
Perhaps by having such a restrictive licensing scheme, they are hoping to avoid any sort of liability: "I told them they couldn't do that thing!"
IANAL, but I don't think responsibility or liability issues work like that.
I've come across this one before, but the script is doing apt stuff which is really odd so I didn't use it.
it's removing the enterprise and ceph repos from proxmox. i can take a screenshot to show you what it's removing.
Basically if you're not paying for proxmox, and you're running a single node, there's absolutely no reason to have either of those apt sources in the config.
I don't remove them, and it does pollute the log at the bottom of proxmox interface with apt errors, so i could see why someone would just disable them as a matter of course.
Yeah but I've already done that, it's just odd that something to set up an OSX VM is for some reason deciding to help me with my OS config too.
whenever i release stuff on github it's kinda in this sort of state, "it works on my setup." i'm not a software developer or publisher and TBQH i'd be shocked if anyone ran my code other than me.
Yeah fair enough!
From the About: "This is really and magic easiest way!" - not confidence-inspiring.
There are a number of fair criticisms of this project in this thread. Criticising the grammar of a non-native english speaker is not one of them.
[dead]