-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Biu Sur - the fight goes on without success :( #159
Comments
Can confirm, Big Sur isn't working anymore. I got the following error, when I tried a clean install:
|
Might be related to the issue and solution in #142 |
@theranger Thank you! That fixed the install problem. Now Python 3/Virt-Manager crashes when I do a right click. |
Hi all, FWIW got some success (on Big Sur / 11.1) by basically updated everything to current versions. just check here. YMMV All the best António |
Confirming this worked for me on my M1 MacBook Air; thanks! brew tap AntonioMeireles/homebrew-virt-manager
arch -x86_64 brew install virt-manager virt-viewer |
I'm also on M1 MacBook Air, and virt-manager itself is working per your instructions (thank you!), and I made a working formula for qemu (heavily influenced by this) which installs via
However, I cannot get virt-manager (or virsh) to connect to qemu:///system
Anyone else have luck with this? Is is strictly necessary for libvirt and qemu to be compiled for the same architecture? I did try building libvirt for aarch64 with
|
@m-bers The connection to system didn't work for me either, I had to use session: |
@arthurk are you on a Mac with the M1 chip? I'm still not able to connect even via qemu:///session |
@m-bers My hosts are running on a remote linux machine which needs the libvirt package installed & the libvirtd daemon running as virt-manager connects to a unix socket. Spitballing here but can you install libvirt on your Mac & get a daemon running? Here's the Libvirt Documentation to the connection URIs Here is my Connection URI for my remote host
|
@m-bers I'm not on the M1, I guess it will be related to that. Quick google showed that qemu has problems running on the M1, I found some info on https://gist.github.com/niw/e4313b9c14e968764a52375da41b4278#running-ubuntu-server-for-arm64 with possible fixes I've updated the formula with the latest virt-manager (from 2.2 to 3.2) because it had problems with Python 3.9. I've also merged @AntonioMeireles commit that updates all other deps https://github.com/arthurk/homebrew-virt-manager brew tap arthurk/homebrew-virt-manager
brew install virt-manager virt-viewer Only thing I didn't know how to fix is the patch that sets --no-fork default to true: https://github.com/jeffreywildman/homebrew-virt-manager/blob/master/virt-manager.rb#L97 (the changes are the same, it has just moved to a different file). Result is that qemu bin will keep running in the background when virt-manager is closed and needs to be killed manually. Not sure if we should patch it and change default behaviour in the first place. Workaround is to use |
@pahansen95 Yep, libvirtd is running, and qemu-system-aarch64 is in my path (and works without a hitch by itself)
My guess is that libvirt has to be compiled for the architecture it targets, but sys/auxv.h doesn't exist within the libc that ships with Darwin. I had hoped that since libvirt uses qemu commands under the hood, it would recognize the qemu-system-aarch64 binary that does successfully compile and run on M1 Macs. The only clue I've found that might suggest a path forward for libvirt (and by extension virt-manager) natively on the M1 chip is this thread regarding building Firefox from source on FreeBSD aarch64, where both read_cpu_features and elf_aux_info functions are discussed as ways to query for CPU features on arm64 chips. I don't see references to either of those functions in Apple's public documentation, and I'm not sure the consequences of getting rid of all references to auxv.h and the function getauxval in libvirt's source code, if it'd even compile at all. |
Update, I got libvirt's compilation to go further by applying this patch which I adapted from this libvirt patch for openbsd. Now the compilation is hanging on virfilewrapper.c with the following output:
|
Submitted my patch to homebrew/homebrew-core on this PR. This isn't directly related to virt-manager on Big Sur specifically (though successful compilation of libvirt on the Apple M1 is required for virt-manager to work properly). I will continue working through this on the PR instead of here |
In Big Sur, after the update brew, the virt-manager started to launch.
But virt-viewer flies with such errors and locks the whole virt-maneger I fell: /
Invalid operand Traceback (most recent call last): File "/usr/local/Cellar/virt-manager/2.2.1_3/libexec/share/virt-manager/virtManager/manager.py", line 489, in row_activated self.show_vm(_src) File "/usr/local/Cellar/virt-manager/2.2.1_3/libexec/share/virt-manager/virtManager/manager.py", line 474, in show_vm vmmenu.VMActionUI.show(self, self.current_vm()) File "/usr/local/Cellar/virt-manager/2.2.1_3/libexec/share/virt-manager/virtManager/vmmenu.py", line 330, in show vmmVMWindow.get_instance(src, vm).show() AttributeError: 'NoneType' object has no attribute 'show' zsh: segmentation fault virt-manager
anyone have any idea?
Torin
The text was updated successfully, but these errors were encountered: