Mac os x virt manager

Is there a virt-manager alternative for Mac OS X? [closed]

Want to improve this question? Update the question so it’s on-topic for Stack Overflow.

Closed 3 years ago .

Here at work, we use a virtual infrastructure. We use virt-manager a lot, but I’m on a Mac and can’t get it to work.

Is there a way to make it work or an alternative ?

4 Answers 4

There’s now a brew formula homebrew-virt-manager which I’ve used to successfully connect to a CentOS 5 box running qemu+kvm.

sadly no, you can however install virt-manager on a linux box and run it on your mac desktop through vnc and X11.

what you need to do is start X11, open xterm (command + N), type ssh -X user@linux-box, then type virt-manager once logged on.

Same problem here, tried several solutions and workarounds, and found that for managing virtual machines on a remote Qemu/KVM server nothing is as reliable and comfortable than a GNU/Linux system running virt-manager .

Our best solution so far is to install Virtualbox in MacOS to run a Lubuntu LTS system with virt-manager .

We found Lubuntu excellent for this purpose: it just works, it’s easy to use and requires few resources to run (it can use less than 300 MB of RAM to run virt-manager and 3-4 SPICE clients). You can save this Virtualbox machine state when you don’t need it, and restore it in a few seconds when needed.

Moreover, there’s irony in running a virtual machine locally to manage remote virtual machines! 🙂

Update

Someone prepared a vagrantfile to quickly setup an Ubuntu virtual machine and run virt-manager via ssh. See:

Источник

Mac os x virt manager

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

A set of homebrew formulae to install virt-manager and virt-viewer on Mac OSX.

Why can’t I connect to a remote URI?

When connecting to remote URIs, you probably need to override the libvirt socket location, see www.jedi.be.

I still can’t connect to a remote URI, why?

This formula for virt-manager does not include the openssh-askpass dependency and does not prompt for passwords in a popup window. Here are two workarounds:

Run virt-manager with either the —debug or —no-fork option to get password prompt via the CLI.

Set up SSH keys between your local and remote system to avoid the prompt.

Why can’t I connect to a local URI (e.g., qemu:///system)?

I’ve not yet tested virt-manager against any local URIs/hypervisors. If you get virt-manager working with a local hypervisor and needed to take any special steps, feel free to share the details.

Everything was working yesterday, but it’s not working today, can you help?

If virt-manager or its dependencies have been upgraded recently ( brew upgrade ), it’s possible that a reinstall may fix the issue (see #39).

About

A set of homebrew formulae to install virt-manager and virt-viewer on MAC OSX

Источник

holms / virt-manager-osx

This comment has been minimized.

Copy link Quote reply

Toasty27 commented Aug 11, 2014

Doesn’t work in OSX 10.9

Even after symlinking /usr/bin/pythonw2.7 to /usr/bin/python2 and installing py27-gobject (and py27-gobject3 ), I still get the following error:

This comment has been minimized.

Copy link Quote reply

jaccoh commented Nov 11, 2014

I fixed that by doing:

now for the next error.

This comment has been minimized.

Copy link Quote reply

jamesooden commented Nov 21, 2014

I am experiencing the same problem, and got as far as you did (though I am using brew). libvirt-glib is separate library and it looks like the version of of gi.repository that you and I both have does not support it. I haven’t figured out much more than that.

This comment has been minimized.

Copy link Quote reply

jamesooden commented Nov 21, 2014

I found from another place that you need to tell gobject-inspector (that is the gi, part of gi.repository) where to find its type libs by using an environment variable GI_TYPELIB_PATH. In my case that would have been:

The problem was the particular gi typelib in question, LibvirtGlib did not exist. I could not find a brew package for this library so I built it myself pulling it from here:

Sadly after figuring out how to make it build (I had to patch the make files to remove an unsupported link option), it did not seem to product the typelib library, so I’m stuck again.

This comment has been minimized.

Copy link Quote reply

jamesooden commented Nov 21, 2014

OK, there is an —enable-introspection on the configure for libvirt-glib, however it does not detect the gobject-introspection library (which it is doing via a package tool). Anyway I bet if I could ever git this LibvirtGlib.typelib file built virt-manager would run.

This comment has been minimized.

Copy link Quote reply

jeffreywildman commented Dec 23, 2014

There are also a couple of other dependencies that need to be satisfied after libvirt-glib. I managed to get virt-manager installed and running using homebrew, albeit it is missing a few features. I’ve created a homebrew tap for others to check out and experiment with:

Источник

Steffen Gebert

Virt-Manager is a graphical user interface for libvirt, a popular toolset for managing virtual machines provided by KVM. Unfortunately, it does not work well on MacOS.

The MacOS port did not work for me, as I was not able to connect to the socket on the remote host even after changing adding the socket=/var/run/libvirt/libvirt-sock parameter. The same holds for its command-line pendant virsh .

So the idea to let it natively run on Linux inside a Vagrant VM came up.

Running Virt-Manager in Vagrant

On that path, I had to overcome the following two challenges:

• to run a window manager inside the VirtualBox GUI
• copying over my SSH private key into the VM

# After digging into Vagrant’s configuration options, I found solutions for both of these issues.

• SSH agent forwarding allows to use the private key located on my Mac
• X11 forwarding allows to run graphical applications inside the VM and display them using XQuartz as a normal program window on my Mac.

Ready-to-Go Vagrantfile

I’ve put the complete Vagrantfile on Github: StephenKing/vagrant-virt-manager.

After cloning the repository, the VM can be created using

and virt-manager can be started using

SSH Host Key Verification

The only issue that remains for me is the acknowledgement of the KVM host’s SSH fingerprint. The solution instead was to once connect to the server from the command line:

By Steffen Gebert

Steffen is a software engineer (mobile core) at EMnify, helping to provide connectivity for the Internet of Things. During night, he takes care of the TYPO3 open source project infrastructure.

Источник

Mac os x virt manager

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

This README.md documents the process of creating a Virtual Hackintosh system.

Note: All blobs and resources included in this repository are re-derivable (all instructions are included!).

💚 Looking for commercial support with this stuff? I am available over email for a chat for commercial support options only.

Looking for Big Sur support? See these notes.

This project can always use your help, time and attention. I am looking for help (pull-requests!) with the following work items:

Create full installation (ISO) image without requiring an existing macOS physical/virtual installation.

An Ansible playbook to automate all-the-things!

Documentation around running macOS on popular cloud providers (GCP, AWS). See the Is This Legal? section and associated references.

Test accel=hvf flag on QEMU + macOS Mojave on MacBook Pro.

Document (share) how you use this project to build + test open-source projects / get your stuff done.

Document how to use this project for iOS development.

Document how to use this project for XNU kernel debugging and development.

Document the process to create and reuse VM snapshots. Instantaneous macOS boots would be nice this way.

Document the process to launch a bunch of headless macOS VMs (build farm).

Document usage of munki to deploy software to such a build farm .

Enable SSH support out of the box or more easily.

Better support + docs for AMD Ryzen.

Patches to unify the various scripts we have. Robustness improvements.

A modern Linux distribution. E.g. Ubuntu 20.04 LTS 64-bit or later.

A CPU with Intel VT-x / AMD SVM support is required

A CPU with SSE4.1 support is required for >= macOS Sierra

A CPU with AVX2 support is required for >= macOS Mojave

Note: Older AMD CPU(s) are known to be problematic. AMD FX-8350 works but Phenom II X3 720 does not. Ryzen processors work just fine.

KVM may need the following tweak on the host machine to work.

To make this change permanent, you may use the following command.

Install QEMU and other packages.

This step may need to be adapted for your Linux distribution.

Clone this repository on your QEMU system. Files from this repository are used in the following steps.

Fetch macOS installer.

You can choose your desired macOS version here. After executing this step, you should have the BaseSystem.dmg file in the current folder.

Attention: Modern NVIDIA GPUs are supported on HighSierra but not on later versions (yet).

Next, convert this file into a usable format.

Create a virtual HDD image where macOS will be installed. If you change the name of the disk image from mac_hdd.img to something else, the boot scripts will need updating to point to the new image name.

Setup quick networking by running the following commands.

Note: If virbr0 network interface is not present on your system, it may have been deactivated. Try enabling it by using the following commands,

Now you are ready to install macOS 🚀

CLI method (primary). Just run the OpenCore-Boot.sh script to start the installation proces.

Note: This same script works for Big Sur, Catalina, Mojave, and High Sierra.

If you are new to installing macOS, see the older README for help.

(OPTIONAL) Use this macOS VM disk with libvirt (virt-manager / virsh stuff).

Edit macOS-libvirt-Catalina.xml file and change the various file paths (search for CHANGEME strings in that file). The following command should do the trick usually.

Create a VM by running the following command.

Launch virt-manager and start the macOS virtual machine.

Note: You may need to run sudo ip link delete tap0 command before virt-manager is able to start the macOS VM.

See networking notes to setup guest networking.

I have the following commands present in /etc/rc.local .

This has been enough for me so far.

To get sound on your virtual Mac, see the «Virtual Sound Device» in notes.

To passthrough GPUs and other devices, see these notes.

Need a different resolution? Check out the notes included in this repository.

To generate your own SMBIOS, use GenSMBIOS.

The «secret» Apple OSK string is widely available on the Internet. It is also included in a public court document available here. I am not a lawyer but it seems that Apple’s attempt(s) to get the OSK string treated as a trade secret did not work out. Due to these reasons, the OSK string is freely included in this repository.

Gabriel Somlo also has some thoughts on the legal aspects involved in running macOS under QEMU/KVM.

My aim is to enable macOS based builds + testing, kernel debugging, reversing, and security tasks in an easy, reproducible manner without needing to invest in Apple’s closed ecosystem (too heavily).

Backstory: I was a (poor) student in Canada once and Apple made my work on cracking Apple Keychains a lot harder than it needed to be.

About

Run macOS on QEMU/KVM. Only commercial support is available. With OpenCore + Big Sur support now!

Источник