Testing KLV-vmHost, Designed for Hosting VM's

[rockedge]

For an experiment I assembled a KLV-vmHost from a PLUG recipe and FirstRib build script. Then did some manual polish to work out some kinks.

This system is similar to KLV-Airedale but has less applications included and comes with no browser. It is designed to run as a virtual machine host system using QEMU-KVM and virt-manager which are built in and comes setup for immediate operation.

XFCE4 desktop, and has all of the Kennel Linux RAM modes. This distro is a proof-of-concept and for experimentation. If tests prove positive perhaps a production version could be produced.

Supplied with a Void Linux kernel 6.10.10_1

Link updated on 26Oct2024 20:12 EDT:
Download KLV-vmHost-rc4

[JusGellin]

@rockedge
Thanks, I'll try it out.

[JusGellin]

@rockedge
How can I make it save a session?
Other than that virt-manager comes up and I'm able to make a vm.
This is just what I've been looking for!!!

I still need to test it for memory usage.

Thanks

[JusGellin]

@rockedge
I found the Session and Startup app.
It is set to Prompt on logout, but doesn't do that.

Also, I couldn't find network connection for wifi.

Thanks

[rockedge]

@JusGellin

Let's look at the boot stanza's you are using to start the system. See what RAM mode you are operating in.

[JusGellin]

@rockedge

This is the one I added from running wd_grubconfig:

Code: Select all

#####grub.cfg (note the UUID or LABEL options below):
menuentry "KLV-vmHost-rc2" {
  insmod ext2
  search --no-floppy --label main --set
  linux /KLV-vmHost-rc2/vmlinuz w_bootfrom=LABEL=main=/KLV-vmHost-rc2 w_changes=RAM2
  initrd /KLV-vmHost-rc2/initrd.gz 
}
#############################OR uuid method:
menuentry "KLV-vmHost-rc2" {
  insmod ext2
  search --no-floppy --fs-uuid --set 0f8bf0f6-17fc-4973-a765-dcea642ca35c
  linux /KLV-vmHost-rc2/vmlinuz w_bootfrom=UUID=0f8bf0f6-17fc-4973-a765-dcea642ca35c=/KLV-vmHost-rc2 w_changes=RAM2
  initrd /KLV-vmHost-rc2/initrd.gz
}

Thanks

[JusGellin]

Also, I couldn't find network connection for wifi.

I found it in Advanced Network settings.
Once I figured out how to use it, it works.

[rockedge]

@JusGellin

Here is the modification in the grub.cfg that will allow direct session saving
The first selection will use the direct save mode:

Code: Select all

#####grub.cfg (note the UUID or LABEL options below):
menuentry "KLV-vmHost-rc2 normal" {
  insmod ext2
  search --no-floppy --label main --set
  linux /KLV-vmHost-rc2/vmlinuz w_bootfrom=LABEL=main=/KLV-vmHost-rc2 
  initrd /KLV-vmHost-rc2/initrd.gz 
}
#############################OR uuid method:
menuentry "KLV-vmHost-rc2" {
  insmod ext2
  search --no-floppy --fs-uuid --set 0f8bf0f6-17fc-4973-a765-dcea642ca35c
  linux /KLV-vmHost-rc2/vmlinuz w_bootfrom=UUID=0f8bf0f6-17fc-4973-a765-dcea642ca35c=/KLV-vmHost-rc2 w_changes=RAM2
  initrd /KLV-vmHost-rc2/initrd.gz
}

Also you can try to manually save in RAM2 mode by typing in a terminal:

Code: Select all

save2flash

[JusGellin]

@rockedge

I favor save2flash. Then I can save only when I want to.

Thanks

[JusGellin]

@rockedge
I'm able to make vm guest using virt-manager.
I can save the vm and restart virt-manager to bring up the guest vm again for the current session.

I can save2flash and still it works fine.

But after I do a complete reboot and try to bring the guest vm up again, it crashes and seems to try to reboot up to a place where it stops.
(See the attached to where it stops.)
I have to power down/up to run again, but trying to bring up the vm guest, crashes again.
It's like the save vm guest is corrupted.

Screenshot(2).jpg (163.04 KiB) Viewed 1992 times

[JusGellin]

@rockedge
I tried this on KLV-Airedale-sr15.
It didn't crash but wouldn't start the vm after a reboot and instead gave this error message:

Code: Select all

Error starting domain unable to open
/var/lib/libvirt/images/debian12.qcow2
No space left on device.

I'm not sure what it is referring to as being out of space and why this occurrs only after a host reboot.

So this isn't just a KLV-vmHost problem.

[JusGellin]

@rockedge
I'm still trying to figure the best way of not making the *.qcow2 vm images go to upper_changes for a save session.

But I did notice something a little peculiar.
Once in a while I see the display flicker a bit for the KLV-vmHost.
I've never had that happen for anything else I have installed on the Dell
Even installing KLV-Airedale-sr15 doesn't have that happen.

For the KLV-vmHost, I made sure the display was 60Hz and it was.
Could that be a display driver problem?

Thanks

[JusGellin]

@rockedge
I'm still trying to figure the best way of not making the *.qcow2 vm images go to upper_changes for a save session.

I opened up a topic for that specific thing called
Re: What Directory Areas are Not Saved in upper_changes?
viewtopic.php?p=132432#p132432
I think this will help me make progress here.

But I did notice something a little peculiar.
Once in a while I see the display flicker a bit for the KLV-vmHost.
I've never had that happen for anything else I have installed on the Dell
Even installing KLV-Airedale-sr15 doesn't have that happen.

For the KLV-vmHost, I made sure the display was 60Hz and it was.
Could that be a display driver problem?

Thanks

As for this part, I rebuilt this again and didn't seemed to have this problem.
It may have happened because of the vm image was hogging ram.

[rockedge]

@JusGellin

I am in Boston at the moment but will be home in several hours.

I have my qcow2 disk images on /mnt/sdc1

[JusGellin]

@rockedge

@wiak helped me understand to do that just a little while ago.
I put mine on my main partition at /mnt/sda2/vms
Then set my storage pool to that with a qcow2 volume. It works great.

I just needed to get over that hump to now make progress on this.

Thanks

[rockedge]

@JusGellin

Sounds like most of the system is working, which is good news.

What is the performance like and does it meet the RAM usage requirements?

[JusGellin]

@rockedge
I just did a rough comparison with Alpine Linux which has to be built up to use.
It looks like the KLV-vmHost is fairly comparable with Alpine

Comparing a base install of each on the same laptop:
Alpine memory usage: 564M / storage space: 1.6G
KLV-vmHost usage: 677M / storage space: 830M

Testing with a fully installed vm Guest - Bookwormpup64 on each
Alpine memory usage: 2.76G / storage space: 2.7G
KLV-vmHost usage: 2.9G / storage space: 1.8G

With this crude look, it seems KLV used slightly more memory and less storage than Alpine Linux - not significant
It also seemed that KLV was a bit less responsive than Alpine. The virt-manager was a bit slower.

But I really like the less complication of this being out of the box ready to run virt-manager compared with Alpine which has to be built from the ground up to do this.
To me, this is a better Virtualbox with its own OS.

I'll keep using this KLV to see more what it can do. I think it is good enough for me to keep using it.
I'm not sure if more improvements can be made for it. If it could be sped up would always help.

Also I was still getting a very few display flickerings when I put KLV on my Dell laptop. But on my HP laptop, I haven't seen any of this happening.

Thanks for making this.

[JusGellin]

@rockedge
I just noticed that when I have a vm built using virt-manager and reboot the host computer, it loses the vm.

Of course this is because the session needs to be saved, which I didn't do.

How can I make this ask to save session when I reboot or shut down?

Thanks

[rockedge]

@JusGellin You are booted in RAM2 mode and there is no prompt at reboot/shutdown for the option to save or not save?

There should be one when booting using w_changes=RAM2 in the boot stanza.

If it is in RAM0 mode w_changes=RAM0 there is no opportunity to save at all.

If in a terminal you can use manually:

Code: Select all

save2flash

then the system is in RAM2 the save on demand mode.

Please post what the boot stanza's look like that you are using.

Perhaps there is a problem with the RAM2 mode and the save2flash system.
Download and install this package and boot into RAM2 mode and manually in a terminal try save2flash. If it works, then reboot and see if the query appears to save or not save.

The boot stanza's you are using and the info about the partition this is all happening on will help fix this.

[JusGellin]

@rockedge

save2flash works fine and w_changes=RAM2.

But reboot doesn't ask to save.

Thanks

[JusGellin]

@rockedge

These are two things I'm asking for:
1. Can a save2flash button be made for on the desktop?
2. Can a Save Session prompt be made when rebooting/shutdown occurs?

Thanks

[Clarity]

Hello @rockedge

I'm just getting around to this on my list.

Went to download this interesting project but the link in the OP does not work. Has it been moved or is it on one of your sites?

A Virt-manager project is an excellent idea for any developer or user. I've considered this fro years in forum. This is similar in scope to Proxmox which I use. I like the idea you propose.

This offers some extended options beyond our usual QEMU stanzas: Especially for those of us who would want to virtually replicate a VM LAN network setup of several VMs connected on an internal virtual LAN for a closed loop test of several virtual PCs.

Thanks in advance if this is still publicly available

[rockedge]

These are two things I'm asking for:
1. Can a save2flash button be made for on the desktop?
2. Can a Save Session prompt be made when rebooting/shutdown occurs?

Thanks

Yes. Both possible. #2 should already be working but isn't so that needs to be fixed.

The button on the desktop is easy. A tiny Bash script set up with a Launcher for the desktop. Pick an icon.
I will set that up on a follow up version for KLV-vmHost.

Code: Select all

#!/bin/sh
save2flash

[JusGellin]

@rockedge

To add to the power of this host virt-manager, I have now figured out how to make clipboard copy work between guests and host
and between guests as well.
I've been wanting to do this with the puppy linux clients but haven't been able to until now. I was able to only with other linux before.

In order to accomplish clipboard copy/paste text you need to install spice-vdagent on the client.
The problem I had before was it was erring out. I found out why.

It was expecting to use the install at /run/ but the install went to /var/run/ instead.
So making a symlink from /var/run/spice-vdagentd to /run/ makes it start up the service on boot and allows the text clipboard copy.

Now they work like my other linux clients do.

Thanks

[rockedge]

@fredx181 seems like there is a small problem with save2flash showing the save or not save question during reboot/shutdown.

I have installed save2flash-1.9_0. Otherwise it all works as expected. I've run across it before but forgot what I did to fix it, it was so long ago!

[fredx181]

@fredx181 seems like there is a small problem with save2flash showing the save or not save question during reboot/shutdown.

I have installed save2flash-1.9_0. Otherwise it all works as expected. I've run across it before but forgot what I did to fix it, it was so long ago!

Tested KLV-vmHost and found that installing dialog fixes it.

edit: btw, strange, I don't understand why dialog is not installed, the save2flash-1.9_0 xbps package has it as dependency AFAIK.

[rockedge]

I just uploaded an ISO image of KLV-vmHost-rc3 to a Mega.nz cloud drive! A Link for download is in the first post of this topic.

• KLV-vmHost-rc3 has libvirt clipboard functionality between guest and host, provided by spice-vdagentd added in by @JusGellin

• Diagnosed by @fredx181, we added the missing dependency package dialog needed for save2flash notification windows.

• Complete rolling update done as indicated by the upload date.

[Sofiya]

[JusGellin]

I just uploaded an ISO image of KLV-vmHost-rc3 to a Mega.nz cloud drive! A Link for download is in the first post of this topic.

• KLV-vmHost-rc3 has libvirt clipboard functionality between guest and host, provided by spice-vdagentd added in by @JusGellin

• Diagnosed by @fredx181, we added the missing dependency package dialog needed for save2flash notification windows.

• Complete rolling update done as indicated by the upload date.

This makes using virt-manager so easy! Thanks for this and the improvements.
As I use this I have become more familiar using it.
I really like the prompt that comes up on a reboot asking if I want to save to save folder. If I don't do that after making a vm, I lose the vm!

Here's some things I now noticed as I'm becoming more familiar with it that should be noted:
For installing this on a computer, I noticed that if I run this as an iso from Ventoy in order to copy the extracted iso to partition 2 ,
and then using this iso's menu selection of Grub2 bootloader config for making partition 1 bootable, that it isn't bootable.
The grub.cfg it makes doesn't seem to be complete enough for the menu item.
So I use the structure that this makes for the efi partition 1 and then run the script from the iso called wd_grubconfig to get the proper
menu items to make it work and copy those menu items into the grub.cfg.

The first item you mentioned above isn't quite what I meant for the clipboard copy using spice-vdagent.
This has to be installed on a vm that was built to make this work. The host doesn't need it.
But the install, which goes to /var/usr/spice-vdagentd has to be symlinked to /run/spice-vdagentd to make this work.

I think this will be valuable for how I work with trying different linux/puppy distributions.
I especially like that, even though I can make individual save folder backups of the puppy/kl distributions, with this, I can make snapshots of them
to go back to as well. This gives me a lot of freedom to go back when something happens to go wrong (which does).

Thank you for making this.

[rockedge]

I noticed that if I run this as an iso from Ventoy in order to copy the extracted iso to partition 2 ,
and then using this iso's menu selection of Grub2 bootloader config for making partition 1 bootable, that it isn't bootable.
The grub.cfg it makes doesn't seem to be complete enough for the menu item.
So I use the structure that this makes for the efi partition 1 and then run the script from the iso called wd_grubconfig to get the proper
menu items to make it work and copy those menu items into the grub.cfg.

The problem is Grub2config and Grub4Dos used in KLV's where designed with Puppy Linux in mind so the boot stanza's the programs will construct use kernel command line parameters and options for Puppy Linux. This is still a work in progress getting these two programs modified to generate Kennel Linux boot stanza syntax.

@JusGellin you did the right thing by running the included script wd_grubconfig to generate the correct boot stanza's.

A possible solution would be to have Grub2config call wd_grubconfig as a function so it can generate both Puppy Linux and Kennel Linux boot stanza's.

The first item you mentioned above isn't quite what I meant for the clipboard copy using spice-vdagent.
This has to be installed on a vm that was built to make this work. The host doesn't need it.
But the install, which goes to /var/usr/spice-vdagentd has to be symlinked to /run/spice-vdagentd to make this work.

Would it be a good idea to remove it from the KLV-vmHost rootfs or has it a use when it remains included?