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

[Antediluvian]

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

[AVCESAR]

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?

[AVCESAR]

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?

[tha76]

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?

[xaol]

@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.

[Eadwine Rose]

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

Please stick to only one topic.


This one now closed.