Linux Kernel Virtual Machines With QEMU/KVM

https://video.fosshq.org/w/r86Y26VzUW4m5htntP41Sx

My best "rubber duck" is whatever public support fora exist for whatever I'm bloodying my forehead on. I rarely actually get useful responses, but just asking does something, sometimes.

e.g. https://forum.opennebula.io/t/debugging-domain-creation/14158/1

I'd been fighting this problem for many weeks, making little progress, largely because I didn't have decent time focusing on it. This morning I hit on the right places to look and found a huge mess underneath, but at least I fixed it.

#ProxmoxVE 9.0 has been released (#Proxmox / #VirtualEnvironment / #Virtualization / #VirtualMachine / #VM / #Linux / #Debian / #Trixie / #DebianTrixie / #QEMU / #LXC / #KVM / #ZFS / #OpenZFS / #Ceph) https://proxmox.com/

For anyone still using or considering the free #oVirt as virtualization management platform: Please don't. It is a broken nightmare on community life support.

After #RedHat has ended support for its commercial spin Red Hat Virtualization (RHV) last year the development of oVirt practically came to a halt.

There hasn't been an official stable release for over a year despite security issues, and numerous bugs. The official recommendation is to use nightly releases to get the latest fixes. Too bad you won't be able to roll back via DNF if an update fails because older nightly releases are gone from the repo.

And yes, nightly releases do break oVirt at times. The latest nightly causes updates to fail because of incomplete dependency changes.

The web interface of the official mailing list is offline most of the time, the documentation is a confusing and outdated mess.

Upgrades to newer Linux distribution releases such as RHEL 9 or even 10 based systems are extremely painful and not officially supported.

Move your VMs to #ProxmoxVE or any other actively maintained KVM based solution.

Decided to blog what I learned about Ubuntu multipass MicroVMs. Enjoy.

https://blog.faucher.net/2025/08/ubuntu-multipass-microvms.html

How would you enable #clipboard sharing from a physical remote IP KVM (like #JetKVM) to the local device?
Specifically: how can clipboard content (like copied text) from the remote machine be transferred back to your local system while using the KVM?

Pssssst - ProxLB 1.1.5 for your Proxmox Clusters has been released!

Just one small new feature:
* You can now use custom ports for the API request

This becomes handy when using additional/external load balancers on different ports than tcp/8006. Have fun :)

I finally received my JetKVM! I’m 6 years old and it’s Christmas!

Vermutlich ein Long-Shot, aber ich versuche es trotzdem:

Kennt sich hier jemand ein bisschen mit KVM Switches aus und kann mir einen für 2 Monitore + USB-Devices an 2 PCs empfehlen?
(Edit/Addendum: Ich will keine Monitore tauschen, Monitore mit integriertem KVM sind daher keine Option)

Ich weiß, dass Level1Techs eigene baut, die sind aber ziemlich teuer und dann kommt Zoll noch drauf:
https://www.store.level1techs.com/products/p/14-kvm-switch-dual-monitor-2computer-z5erd-n6mbj

Ich hab auch andere gefunden, aber die kommen mit eher scammy vor. Dieser Onlineshop z.B. der kein Impressum hat und in Wahrheit (anscheinend) aus China versendet?
https://tesmart.de/collections/dual-monitor-kvm-switch/products/dks202-m24?_pos=2&_fid=53164e3e5&_ss=c

Anyone got #jetkvm working on #tailscale so you can use the machine to which the #kvm is attached from outside your local area home #lan network? i.e. when on the road. I am nearly there but get connection failure every time.

Strato mailte vor ner Woche, das man V-Server jetzt per Klick von Virtuozzo zu KVM konvertieren kann. Klingt gut - im Gegensatz zu den Mails früher á la "mach doch mal neu".

Leider scheinen dann die inklusiven Snapshots wegzufallen und man muss sich selber ums Backup kümmern. Wenn ich das richtig verstehe. Hm,.wäre nen Grund den Wechsel weiter zu verzögern.

Here's the customary #introduction: i'm into #C and tolerate C++ on a daily basis at work, i've also used others like java, kotlin, python, PHP, etc and am curious about #COBOL, #AdaLanguage and #erlang.

My dislike of jenkins is only surpassed by my hate of githubactions and everything MS-related. AI is not I, only A. I'm interested in #selfhosted stuff but atm that's a VPS with some sites, which doesn't really count. For now #syncthing is quite useful and #wireguard is on the horizon once i reformat/reinstall my current #gentoo (i'll keep the root #ZFS aproach and am on the fence regarding #XFCE or #KDE), would be interesting to have a barebones #KVM/#QEMU running all the stuff and i digress.

kthxbai\0

Wonder if i'll ever discover why #QuickEMU 100% fails for me, on any pooter i install it?

#kvm This #glinet product is available here https://amzn.eu/d/6d2x2sj
and loosely reviewed here https://youtu.be/L_P1d89U8sc
but the comments to the video are super suspicious of the way it works and whether your computer can be hacked by their app. Not sure if open source, but seems to be, nor sure if it can run on linux. A comparison with #jetkvm would be interesting.

Please read the screen cap closely and also read the Alt text & realize how much boxyBSD has blown up

600 plus VMS!!!

An insightful article was written by @gyptazy
If this is of your interest, and you take the time to read, analyze between the lines what has been said, you will learn a lot from this

If you are passionate about Proxmox like I am, you will love to read these kind of posts, because they've been systematically, logically and relatively simply formulated, so that it's digestible for the end user of proxmox all the way up to the diehard programmer who hacks in Proxmox code

@deadbeefdotmonster Last time [not recently, maybe a year'ish ago] that i tried enabling 3D Accel [is that what you mean by "hardware accel"?] it seemed to work well, but it broke the ability for me to Suspend [aka Save] my VMs each time, ie, i had to fully SD them, then cold SU them next time. That was a bigger PITA for me than the hitherto lack of accel, so i disabled it again ever since. Ofc #QEMU / #KVM / #libvirt / #VirtManager have had many updates since then. Maybe it's better now?