OneClick-macOS-Simple-KVM VS virt-manager

This works pretty well for running macOS on Linux:

https://github.com/notAperson535/OneClick-macOS-Simple-KVM/

Mostly used it when trying to track down reported macOS bugs in stuff for an OSS project, so maybe once every few months. But it's worked quite well at those times. :)

I have a MacOS Ventura VM up and running under Linux KVM/QEMU using Virtual Machine Manager. When I installed, I added a bridge network like I always do for VMs and I may have removed the previous NIC installed by this method: https://github.com/notAperson535/OneClick-macOS-Simple-KVM. I am now researching what it takes to get Apple Services working. One thing I'm unclear about is does the network type matter for this?

Hi all. Been getting a weird error the last week or so. I've noticed I'd lose connection and when I check my macos vm, it says "failed to prepare port" even though it had been running the whole time. I'm running airmessage inside of a VM inside of xubuntu. Specifically this OSX KVM solution . I haven't had any issues with running it this way until last week or so. The only way to fix seemed to be quit and restart airmessage. I do not want to use a Google account, so please do not suggest that as the solution. Thank you.

https://github.com/notAperson535/OneClick-macOS-Simple-KVM And disabled read-only

i was following a guide to get a macos kvm on wsl but when I'm trying to install it I get an error saying that my cpu does not support kvm extensions. I have used the same machine on linux to easily run the same kvm without any problems so I don't know why this is happening. I'm also using the latest wsl2 kernel package. Guide

This is the SIMPLEST one: https://github.com/foxlet/macOS-Simple-KVM sadly is not getting updates, but you can use it and upgrade after installation or use a fork: https://github.com/notAperson535/OneClick-macOS-Simple-KVM

I had Montery running on Xubuntu 20.04 a month ago, but something happened recently to bork it. I could not boot into it this morning. I think it had something to do with improperly shutting down the machine as I was messing with the breakers in my house. I thought a fresh install might fix it but that doesn't seem to be the case. I made a new folder for all the files and downloaded the KVM set up that I used before, but I get the error above. I'm guessing it's an issue with libvirtd but my home assistant VM seems to have no issues. If anyone has any idea how to fix this (without doing a nuke) that would be appreciated.

I followed this guide that I found here, it's the same as the macOS simple KVM but simpler to set up. I got the VM to boot and logged into my Apple ID with no problems. But the VM doesn't show up as a separate device on my router so I can forward the port that I need to to the VM. I tried using the bridged network instructions that guide has but it didn't work. Should I just use something like nginx proxy manager for it?

It's still being updated. I don't see anything on the virt-manager homepage or GitHub that would suggest it is deprecated.

https://virt-manager.org/

https://github.com/virt-manager/virt-manager

It can't do literally everything Qemu/libvirt can do using only the UI, but given that it has escape hatches to directly edit libvirt configurations, and libvirt has escape hatches to directly pass arguments to Qemu, there's very little you can't do with it.

I would love to see a serious comparison (features & performance) between VMWare ESXi, Proxmox VE and let's say a more stock RHEL or Ubuntu. And maybe even include FreeBSD/bhyve.

Because yes, in terms of core functionality it should be in the same ballpark. And in terms of UI, Virtual Machine Manager [0] was not that bad.

[0] https://virt-manager.org/

Shout out to https://virt-manager.org/ - works much better for me, supports running qemu on remote systems via ssh. I used to use this all the time for managing bunches of disparate vm hosts and local vms.

If not, I would just run a CentOS Stream 8 virtual machine using either GNOME Boxes or virt-manager, and set up networking and ssh so you can access the database from the host.

https://virt-manager.org/ <- Recommend this as Front-end

I'd say it is half-baked webmin. You can only use it with NetworkManager, and if you have an even remotely complex network setup for VMs, NetworkManager usually must be turned off, which makes Cockpit practically unusable. virt-manager [1] is way more powerful for those who like managing VMs with GUI.

[1] https://virt-manager.org/

$ apt build-dep libvirt $ git clone https://github.com/libvirt/libvirt.git Cloning into 'libvirt'... $ cd libvirt $ meson setup build $ ninja -C build $ ninja -C build install $ which virsh /usr/local/bin/virsh $ which libvirtd /usr/local/sbin/libvirtd $ apt install libgtk-3-dev libpulse-dev libgbm-dev libspice-protocol-dev \ libspice-server-dev libusb-1.0-0-dev libepoxy-dev libfdt-dev $ git clone -b v5.1.0 http://git.qemu.org/qemu.git $ cd qemu-v5.1.0 $ git submodule add -f https://git.kernel.org/pub/scm/utils/dtc/dtc.git dtc $ ./configure --disable-werror --target-list=arm-softmmu \ --enable-opengl --enable-gtk --enable-kvm --enable-guest-agent \ --enable-spice --audio-drv-list="oss pa" --enable-libusb \ --enable-trace-backend=simple --enable-debug $ make $ make install $ git clone https://github.com/virt-manager/virt-manager.git $ apt install gobject-introspection libosinfo-1.0-0 libosinfo-1.0-dev \ gir1.2-libosinfo-1.0 libvirt-glib-1.0-dev $ cd virt-manager $ ./setup.py configure --prefix=/usr/local $ sudo ./setup.py install $ sudo usermod -a -G libvirt root $ sudo usermod -a -G libvirtd root $ sudo usermod -a -G libvirt-qemu libvirt-qemu $ sudo usermod -a -G libvirt marietto $ sudo adduser libvirt-qemu $ sudo groupadd --system libvirt $ sudo groupadd --system libvirt-qemu $ sudo newgrp libvirt-qemu $ newgrp libvirt $ /usr/local/sbin# libvirtd & [1] 2875 $ /usr/local/sbin# virtqemud & info : libvirt version: 9.7.0 info : hostname: chromarietto error : virPidFileAcquirePathFull:409 Failed to acquire pid file : /var/local/run/libvirt/qemu/driver.pid Resource temporarily unavailable error : virStateInitialize:672 : Initialization of QEMU state driver failed Failed to acquire pid file : /var/local/run/libvirt/qemu/driver.pid Resource temporarily unavailable error : daemonRunStateInit:617 : Driver state initialization failed $ /usr/local/sbin# ps ax | grep libvirt 2875 pts/0 Sl 0:00 libvirtd $ /usr/local/sbin# ps ax | grep virtqemu nothing If I do the opposite way : $ /usr/local/sbin# virtqemud & $ /usr/local/sbin# ps ax | grep virtqemu 3041 pts/0 Sl 0:00 virtqemud $ /usr/local/sbin# libvirtd & info : libvirt version: 9.7.0 info : hostname: chromarietto error : virPidFileAcquirePathFull:409 Failed to acquire pid file : /var/local/run/libvirt/qemu/driver.pid Resource temporarily unavailable virStateInitialize:672 : Initialization of QEMU state driver failed Failed to acquire pid file : /var/local/run/libvirt/qemu/driver.pid Resource temporarily unavailable daemon RunStateInit:617 : Driver state initialization failed $ /usr/local/sbin# ps ax | grep virtqemu 3041 pts/0 Sl 0:00 virtqemud $ /usr/local/sbin# ps ax | grep libvirt nothing

I want to test Hyprland with NixOS in a VM using Virt-Manager (https://virt-manager.org/) on Arch Linux host before installing it on my machine.