- This topic has 23 replies, 6 voices, and was last updated Oct 19-7:21 pm by olsztyn.
-
Posts
-
anticapitalista
I have managed to build systemd/elogind -free debs of brltty (this is where libbrlapi0.8 comes from).
I have no idea if qemeu will work without elogind/systemd so testers are needed.All debs here: https://download.tuxfamily.org/antix/Testing/
You probably only need to install the libbrlapi0.8 deb before trying to install the ‘entire kaboodle of KVM/QEMU’
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
olsztyn
I have managed to build systemd/elogind -free debs of brltty (this is where libbrlapi0.8 comes from).
I have no idea if qemeu will work without elogind/systemd so testers are needed.Great news… Thank you…
I want to participate in testing.Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersI have no idea if qemeu will work without elogind/systemd so testers are needed.
Just to report initial results:
– The libbrlapi0.8 from Testing installed fine – no *elogind* installed.
– Installed the entire KVM/QEMU bunch as previously quoted – appears to have worked fine and still no *elogind*.
– After reboot the Virtual machine manager starts but with the following error:“Unable to connect to libvirt qemu:///system.”
Looks like libvirt service may have not started. I will try to figure out how to start…
It appears to me that with the new *elogind*-free libbrlapi0.8 the KVM/QEMU is in fact working fine and the above issue is not related to it.- This reply was modified 6 months, 3 weeks ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersI have no idea if qemeu will work without elogind/systemd so testers are needed.
Update:
I was able to resolve the ‘Unable to connect’ error on KVM/QEMU start.
At this point KVM/QEMU starts connected when under sudo authority and not connected under user authority. I will need to figure out how these entitlements work but one way or the other KVM/QEMU appears to work correctly, as *elogind*-free, allowing to install operating systems from their ISO images, at least as root.
My conclusion is that the libbrlapi0.8 from Testing is working fine and the entire KVM/QEMU so installed does work fine, just I need to figure out these entitlements to operate it as user not as root.To emphasize – this is not any issue with the software or *elogind*-free config by anticapitalista but just my lack of adequate familiarity with KVM/QEMU. This my limited familiarity ended with successful install, and resulted in what appears a correctly working KVM/QEMU. How to operate it remains a learning process for me.
Looking forward to have the libbrlapi0.8 from Testing moved to general repo…
- This reply was modified 6 months, 3 weeks ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
techore
I think I remember it was insisting on installation of libelogind0, if I am not mistaken.
You are not mistaken.
No trace of elogind
I reported this fairly recently for I use virt-manager and do not want libelogind0 on my assets. Let me see if I can find the post and package.
techore
Here is the post:
https://www.antixforum.com/forums/topic/antix-22-being-worked-on/page/6/#post-87656
The package is:
https://packages.debian.org/bullseye/qemu-system-x86.
It provides both i386 and x86_64 emulation.
- This reply was modified 6 months, 3 weeks ago by techore.
Hi techore…
In that statement anticapitalista was referring to virt-manager alone, not the entire QEMU/KVM set.
The new libbrlapi0.8 (as compiled by anticapitalista for our testing) no longer requires libelogind0 and the entire QEMU/KVM is *elogind*-free, therefore compaatible with antiX 22, which is great news. According to my testing QEMU/KVM installs just fine, using the new libbrlapi0.8.However (unrelated to the above testing and confirmation of *elogind*-free QEMU/KVM):
My QEMU/KVM appears to run as expected while under root authority, however when starting as user I am seeing message ‘QEMU/KVM – Not Connected’.
The user has been added to libvirt group.
I am running out of ideas and will appreciate advice how to resolve this…P.S: antiX contributor rayluo has put together an excellent QEMU/KVM howto for antiX, which can be found in this forum…
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameterstechore
Gotcha. I may need to slow my roll. Thank you, @anticapitalista!
My QEMU/KVM appears to run as expected while under root authority, however when starting as user I am seeing message ‘QEMU/KVM – Not Connected’.
Yeah. I am having the same issue and spent a couple hours thrashing before I added it to my “to do” list. It is an oddity for I don’t have the issue when launching as root. Another item you may run into is not being able to bridge the network interface. Another item on my “to do” list. So many tasks and not enough time.. 🙁
I am excited about antiX 22.
I am having the same issue and spent a couple hours thrashing before I added it to my “to do” list. It is an oddity for I don’t have the issue when launching as root. Another item you may run into is not being able to bridge the network interface.
Complexities like these make QEMU/KVM not that simple for mainstream users, unless there is a solid process that can be followed to successfully install it.
Those who invested effort to master these complexities may consider themselves as elite, setting them apart from ordinary people…
I typically prefer simplicity accessible to ordinary masses and not requiring IT gurus to operate though…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
- You must be logged in to reply to this topic.
