What Can Host QEMU Virt-Manager?

[JusGellin]

There seems to be hardly any activity in this section, but I thought this would still be the right place for my question.

Can any Puppy Linux, KL, or EasyOS be used as a QEMU host that can use virt-manager?

Virt-Manager for QEMU is such an easy way to manage this simply and effectively without making it too complicated.
It just seems like there could be some version of OS around here that could do this. So I thought I would ask.

Thanks

[rockedge]

Yes it can.

I most use a QEMU portable at the moment but also on some F96-CE_4 systems QEMU is installed.

On a NoblePup64 both a stock and a FirstRibIt'ed version have QEMU installed but still can run the portable version.

I tend to set up new QEMU machines using AQEMU.

[JusGellin]

@rockedge
Thanks.

I was thinking more about using virt-manager to manage the QEMU.
Can any of those run virt-manager?

[rockedge]

@JusGellin I think so. I have not used it for sometime but it should work......

[JusGellin]

@rockedge
Thanks, I'll try them out.

[JusGellin]

I installed F96-CE_4 and installed virt-manager using the Package manager, successfully.
When I ran virt-manager, it indicated that I needed libvirtd service.
This wasn't in the Package manager, but I found Libvirt-9.4.0.pet which I installed. I couldn't find any instructions once I did for how to use it though.
So virt-manager still gives that error for it missing libvirtd.
I also installed qemu_4.2 using the Package manager that didn't help. I wasn't sure if I should do anything after I downloaded qemu.

Then I saw another reference about a qemu pet called qemu-ready-0.3.1-x86_64.pet which I also loaded, but again didn't know what to do once I installed it.
So still virt-manager says it needs libvirtd.

But this sounds hopeful that there must be a few that have run the virt-manager successful using puppy linux.

I wonder what I am doing wrong. Is there any more specific instructions to make it work?

Thanks

[rockedge]

try in a terminal:

Code: Select all

ldconfig

now see if it will recognize the libvirtd. Otherwise where is it located? Perhaps it installed outside of the library path and needs a symlink......

[JusGellin]

When I run ldconfig, it comes back to the prompt.
But still virt-manager says it's missing libvirtd

Searching the drive to libvirtd only gives a reference to a man page.
Searching for libvirt gives a lot of finds.

Installing Libvirt-9.4.0.pet evidently didn't load libvirtd.

[JusGellin]

I looked at my backup before installing Libvirt-9.4.0.pet.
I'm not sure that the pet did anything because there were a lot of libvirt references before installing the pet.

[JusGellin]

try in a terminal:

Code: Select all

ldconfig

now see if it will recognize the libvirtd. Otherwise where is it located? Perhaps it installed outside of the library path and needs a symlink......

I used the Legacy Package Manager to Install:
Libvirt Daemon
virt-manager
qemu kvm

Then I ran ldconfig.
When virt-manager came up, it still said it was missing libvirtd

This time I found libvirtd at /usr/sbin/libvirtd
How do I symlink it to the library path?

Thanks

[JusGellin]

I did the install on a fresh BookwormPup64_10.0.7.
When I run virt-manager it doesn't give the error that it can't find libvirtd.
But instead, gives this:
Unable to connect to libvirt qemu:///system
Verify that the 'libvirtd' daemon is running

How can I start libvirtd?

After seeing this, I installed Libvirt-9.4.0.pet which didn't help any either.

I also ran ldconfig without any errors.
I found that libvirtd has been installed.

It must be that the service needs to be started.
I don't know how to do this.

Thanks

[rockedge]

I have been fooling around with this right now to see how to get it going. I installed the package ebtables which showed up as missing and some other fiddling I got libvirtd apparently running.

I managed to start the daemon in a terminal with:

Code: Select all

libvirtd

Screenshot.jpg (46.11 KiB) Viewed 1889 times

you can start it as daemon but I did it in a terminal to see if any output messages showed up.

I started the virt-manager which gives me the GUI but claims that libvirtd is not connecting

Screenshot(1).jpg (18.38 KiB) Viewed 1889 times

[JusGellin]

Before doing anything I look at htop.
It showed the processes running like yours but listing it as /usr/sbin/libvirtd -d

I tried running libvirtd directly from the terminal. This is what I got:

Code: Select all

# libvirtd
2024-09-04 14:44:04.047+0000: 14943: info : libvirt version: 9.0.0, package: 9.0.0-4+deb12u1 (Debian)
2024-09-04 14:44:04.047+0000: 14943: info : hostname: puppypc2581
2024-09-04 14:44:04.047+0000: 14943: error : virPidFileAcquirePath:401 : Failed to acquire pid file '/run/libvirtd.pid': Resource temporarily unavailable
# 

Then when I run it says:
Unable to connect to libvirt qemu:///system

This is with BookwormPup.
Should I reinstall F96-CE_4 and try it again?

Thanks

[JusGellin]

It didn't bring up libvirtd in htop like Bookworm did.
When I brought up virt-manager, it indicated that it couldn't find libvirtd service

[JusGellin]

It looks like I got as far as you have.
I can see libvirtd running in htop like you.
When I run virt-manager I get the same as you.
If I click and open the connection that comes up, it says this:
Unable to connect to libvirt qemu:///system.
Verify that the 'libvirtd' daemon is running
But htop shows it to be running.

So it works up to this point but doesn't connect to the libvirtd service to run.
I hope you or someone can figure this out.

Thanks for helping me see some things to check to see if they are running.

[JusGellin]

Hey @rockedge ,
I got virt-manager to connect!!

Like in yours, virt-manager said it couldn't find libvirtd service.
So I looked at another computer I'm using with PopOS linux to host virt-manager.
I noticed that all the libvirt stuff it was using was at /var/run/libvirt.
Where puppy linux installed all of this at /run/libvirt instead.
So I placed the puppy /run/libvirt as a symlink into /var/run.
This made it connect.

Please look over what I did to see if I did it properly or if there would be a better way.

I haven't made any virtual machines yet, but I will and report back.

[JusGellin]

@rockedge
When I make a symlink like this, it loses it even if I save it before a reboot.
How can I do this without losing the symlink?

[rockedge]

I set the symlink from /run to /var/run and I also have virt-manager connecting.....but then an error not finding usb.ids which I fixed in a terminal with:

Code: Select all

update-usbids

Now with the symlink in place (we'll figure out how to make this more permanent ) and the file usb.ids created I am about to attempt setting up a virtual machine.

Screenshot(2).jpg (24.08 KiB) Viewed 1763 times

Screenshot(3).jpg (11.23 KiB) Viewed 1763 times

[rockedge]

@JusGellin I got a virtual machine started!

I did a bunch of things so I'll have to retrace but make sure you have libvirtd and virtlogd started and running.

[JusGellin]

@rockedge
I almost got BookwormPup running virt-manager, but not quite.
I didn't understand how you:

I set the symlink from /run to /var/run

Mine worked when I placed the puppy /run/libvirt as a symlink into /var/run like a shortcut. How did you do yours?
It was giving me an error so I decided to try to go back and use it on F96-CE_4.
I couldn't get libvirtd service to run.

So I was wondering how you set up your kvm qemu installs.
I installed each of the following using the Package Manager in F96-CE_4:

qemu-kvm libvirt-clients libvirt-daemon-system bridge-utils virtinst libvirt-daemon virt-manager

Is that how you installed yours?

Thanks

[rockedge]

@JusGellin,

Using the F96-CE_4 package manager PPM I have the following:

• gir1.2-spiceclientgtk-3.0_0.37-2fakesync1

• libvirt-daemon-driver-qemu_6.0.0

• qemu-system-x86_4.2

• qemu-system-common_4.2

• qemu-utils_4.2

• libqcow-utils_20181227-1.1

• libqcow1_20181227-1.1

• libvirt-clients_6.0.0

• libvirt-daemon_6.0.0

• libvirt-daemon-driver-qemu_6.0.0

• libvirt-daemon-system_6.0.0

• libvirt0_6.0.0

• python3-libvirt_6.1.0-1

• gir1.2-libvirt-glib-1.0_3.0.0-1

• libnss-libvirt_6.0.0

• libvirt-dbus_1.3.0-1

• libvirt-glib-1.0-0_3.0.0-1

• virt-manager_2.2.1

• ebtables_2.0.11

I had to add users and a group with:

Code: Select all

adduser libvirt-dnsmasq
adduser libvirt-qemu
addgroup libvirt

In a terminals I start:

Code: Select all

libvirtd
virtlogd

then create a symlink from /var/run/libvirt to the target /run/libvirt
this can be achieved manually or with a script that starts both daemons and creates the symlink.

Or might be possible with creating service files and pretending systemd and using service. Then it would be possible go into the Puppy settings and select them to start at boot,

Code: Select all

service libvirtd start
service virtlogd start

I started with an ISO of KLV-Boxer-rc4

Screenshot(5).jpg (52.07 KiB) Viewed 1724 times

[rockedge]

I forgot to mention I needed to run this in a terminal:

Code: Select all

update-usbids

Update your USB IDs

The USB ID database is stored in a file called usb.ids. This location may vary depending on the Linux distribution.

On Ubuntu 18.04, this file is located in /var/lib/usbutils. To update the database, use the command update-usbids, which you need to run with root privileges or with sudo

libvirt and virt-manager otherwise refused to start without this file.

[JusGellin]

@rockedge
Thank you very much. This is great!
I really appreciate this.