MX Linux Forum

Posted: **Sun Mar 06, 2022 3:59 pm**

Hi all,

I am new in MXLinux. I just got a new computer that I will use as a VM server. So I tried to get virt-manager to work but there is no qemu connection.
Apparently I have to install qemu-kvm but it's not in the repositories.

I know about this post:
viewtopic.php?p=673067&hilit=qemu+kvm#p673067

But I don't find the packet.
How can I do? Any idea?

Also, is there a server edition of MXLinux?
What is ddm-mx? An nvidia driver manager only? WHat is it's equivalent for the other dirvers? Ryzen, motherboard...

I am on Distro: MX-21_x64 Wildflower October 20 2021

Ty,

Posted: **Sun Mar 06, 2022 5:38 pm**

it looks like qemu-kvm for debian 11 (which mx 21 is based on) is a virtual package: https://packages.debian.org/bullseye/qemu-kvm

the debian wiki for kvm suggests installing qemu-system (among other packages): https://wiki.debian.org/KVM

it looks like qemu-system should bring in all of the packages (as dependencies) listed as providing qemu-kvm (qemu-system-{arm,ppc,x86}: https://packages.debian.org/bullseye/qemu-system

also the debian wiki page for qemu in case that might be of help: https://wiki.debian.org/QEMU

note: i haven't upgraded to 21 myself so can't confirm the above. i am just sharing what i could find from the sources listed.

Posted: **Mon Mar 07, 2022 3:04 pm**

I dont find the qemu-kvm in the packets installer. but the sudo apt-get seems to find it.
Why is that? Am I not supposed to find al available packages in the GUI packets installer?

Also, I already used CLI to install it before but my VM was very unstable, so I wonder if the apt-get did not install a qemu-kvm it was not supposed to.

Posted: **Mon Mar 07, 2022 5:08 pm**

what output do you get for

Code: Select all

apt show qemu-kvm

?

did you install all of the packages recommended in the wiki pages linked above?

Posted: **Tue Mar 08, 2022 1:53 pm**

I installed it the first time by following this guide: https://computingforgeeks.com/how-to-in ... on-debian/

But then I had the snapshot MXLinux, so I installed the stable version now. I didn't reinstall qemu-kvm in the new MXlinux system.

So I get:

Code: Select all

$ apt show qemu-kvm
Package: qemu-kvm
State: pas un véritable paquet (virtuel)
N: Impossible de choisir une version candidate du paquet « qemu-kvm » qui n'en n'a pas
N: Impossible de choisir les versions du paquet « qemu-kvm » qui n'est qu'un paquet virtuel
N: Aucun paquet n'a été trouvé

Posted: **Wed Mar 09, 2022 5:58 pm**

After a retry and by noticing the messages it actually says:

Code: Select all

Note : sélection de « qemu-system-x86 » au lieu de « qemu-kvm »

Which basically means it's selecting qemu-system-x86 instead of kvm-qemu.

Posted: **Wed Mar 09, 2022 6:09 pm**

are your vm's working correctly for you with what you have installed?

Posted: **Wed Mar 09, 2022 6:23 pm**

Nope, still having problems:

Code: Select all

Unable to connect to libvirt qemu:///system.

Vérifiez que le démon « libvirtd » est en cours d’exécution.

Libvirt URI is: qemu:///system

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 922, in _do_open
    self._backend.open(cb, data)
  File "/usr/share/virt-manager/virtinst/connection.py", line 153, in open
    conn = libvirt.openAuth(self._open_uri,
  File "/usr/lib/python3/dist-packages/libvirt.py", line 148, in openAuth
    raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Aucun fichier ou dossier de ce type

Waiting for a final stable solution to put the topic as closed and puting my findings here.

Posted: **Wed Mar 09, 2022 6:57 pm**

can you check the status of the libvirtd service? on sysv i checked all my services with

Code: Select all

service --status-all

i can see libvirt-guests and libvirtd both listed with [+] to the right. the + is an indication of running services according to

Code: Select all

man service

i checked the status of libvirtd with

Code: Select all

service libvirtd status

i used the same for libvirt-guests just in case.

if you are using systemd,

Code: Select all

systemctl status libvirtd

should hopefully work.

Posted: **Wed Mar 09, 2022 7:35 pm**

Here is a video on installing and getting QEMU up and running:
https://vid.puffyan.us/watch?v=wxxP39cNJOs 13m long
The guy is using arch but with a little savvy shouldn't be too difficult in MX.
He also explains on getting a win10 iso installed which includes the required virtio ones, including network, user, etc..
I'm still waiting on my new minipc as I want to run a win10 iso in qemu on top of AV-Linux.
Search utube for "Ditch Virtualbox, Get QEMU/Virt Manager" on Mental Outlaw's channel.
There are others of course but this one seemed to be quite thorough. Highly recommended.

Posted: **Fri Mar 11, 2022 2:42 am**

I know next to nothing about Virtualbox, much less QEMU-KVM. That said, if I made an attempt to get QEMU-KVM running on MX21 would the following "how to" written for Debian 11 work and is it sufficient? Thanks.

How to Install and Configure KVM on Debian 11 Bullseye Linux
Published in Linux Shout by Heyan Maurya
Last update: December 2, 2021

Posted: **Wed Mar 16, 2022 11:14 am**

I finally followed this guide and it worked: https://computingforgeeks.com/how-to-in ... on-debian/

- At first I thought I didn't install the good packet but it selected « qemu-system-x86 » instead of « qemu-kvm » by itself. The "virt-top" package was not found.
- After that I installed the latest SpiceClientGTK (careful to not install spice-client-gtk that do not work) with the GUI packages installer.
- I also added my user to the KVM and libvirt groups as I found on internet. Not sure this part is necessary.

I got a stable linux install but windows still has CPU and GPU management problems.

However now, I am trying to redo a final clean and stable install of MX_linux on a VM but I loop on the logging page. With the stable XFCE MX_linux ISO. I enter the demo password for the demo user but it loops me back to the logging page.
Any idea?

Posted: **Wed Mar 16, 2022 12:02 pm**

Just found a solution. I used the root root user instead to log in the live sessions.

Now that my problem is "solved". Should I keep this conversation here or delete it and put comments in the two other that treat the two parts of my same problems?

Posted: **Sat Apr 09, 2022 4:52 am**

I started following the following guide and I'm stuck at a certain step:

https://www.how2shout.com/linux/how-to- ... eye-linux/

---
To list the available network to use in KVM virtual machines, run the following command:

Code: Select all

sudo virsh net-list --all

However, in the output, you will see the default network is not active and also not set to start automatically with a system reboot. Therefore, to make it active and autostart run the following commands:

Code: Select all

sudo virsh net-start default
sudo virsh net-autostart default

---

These are the outputs I get for the above commands:

Code: Select all

error: failed to connect to the hypervisor
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

Code: Select all

error: failed to connect to the hypervisor
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

error: failed to connect to the hypervisor
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

This command resulted in the following warning, perhaps that's the problem: sudo apt install qemu-kvm libvirt-clients libvirt-daemon-system bridge-utils virtinst libvirt-daemon

Code: Select all

dpkg: sysvinit-core: dependency problems, but removing anyway as you requested:
 init depends on systemd-sysv | sysvinit-core; however:
  Package systemd-sysv is not installed.
  Package sysvinit-core is to be removed.

(Reading database ... 319215 files and directories currently installed.)
Removing sysvinit-core (2.96-7+deb11u1) ...
dpkg: systemd-shim: dependency problems, but removing anyway as you requested:
 libpam-systemd:amd64 depends on systemd-shim (>= 10-4~) | systemd-sysv; however:
  Package systemd-shim is to be removed.
  Package systemd-sysv is not installed.

Is this guide not compatible with MX Linux?

Posted: **Sat Apr 09, 2022 2:25 pm**

@tha76 in general it is a better idea to start a new topic for your specific circumstance since this topic has been marked as solved by the person who posted it. you may not get the help you want or need here. in a new post you should add your Quick System Info so others can know what the system you are trying to work on looks like.

Posted: **Wed Apr 13, 2022 4:10 am**

Tha76 topic here: https://forum.mxlinux.org/viewtopic.php?t=69729

Please stick to only one topic.

This one now closed.

MX Linux Forum

Qemu-kvm not present in software installer and new guy questions

Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions [Solved]

Re: Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions

Re: Qemu-kvm not present in software installer and new guy questions