Among the changes in the main #kvm merge[1] for #Linux kernel 6.8 was the "guest-first memory subsystem" and new functionality based on it.
Guest_memfd allows kvm to provide features, enhancements, and optimizations that are kludgly or outright impossible to implement in a generic memory subsystem – and also protect a guest system's memory from access by actors outside of the guest itself.
Been banging my head on the keyboard for a few days trying to set up a virtualized #kvm supporting a #debian#armhf system on an #arm64 host machine... I have several machines set up with this working.
Finally had a breakthrough...
Debian does not support #secureboot on armhf. Disabled secure boot and yay, it boots the debian-installer mini.iso just fine!
Now if I could just figure out why #macvtap does not work... it would be all set to crank through lots of builds!
Fun fact: you can make your PiKVM multiport by just hooking it up to a cheap four ports HDMI kvm and hooking up the control serial port to the rpi hub, and setting up macros in kvmd to make it switch ports from the Web UI.
it's everything I ever wanted and the Redfish BCMs in my SuperMicro stuff are starting to feel primitive and clumsy in comparison.
I dared switching from #Windows to #Linux on my work computer yesterday. This...is going to be somewhat a challenging switch, even for a Linux enthusiast such as myself. 🫣 There is already #KVM and #Wine involved, but we will see about that as time goes on.
I never thought about this before, really for a monitor. I’ve heard about them being used as standalone switches, and still think that may be more flexible.
However, if you have one ultra-wide monitor, maybe it would make sense to split that display into t ...continues
:boost_requested: :boost_animated: :boost_ok: #FollowerPower: Anyone with #Linux - #boot|ing #KnowHow able and willing to take a look why my current build of OS/1337 doesn't boot?
It's a 1440kB 3,5" #Floppy image and should work just fine in #VirtualBox / #QEMU / #KVM / #vmware but it's stuck after loading #Linux (bzImage) and the remaining files (rootfs.cpio.xz)...
Sur des machines de gamme professionnelle, on utilise généralement iDRAC ou bien IPMI, une interface graphique qui permet d'avoir un visuel sur le matériel et le BIOS , le tout sur un réseau dédié. Sur une machine grand public, ce genre d'interface n'existe pas. Pour pallier ce problème, il existe une solution : un KVM sur IP.
Ce genre d'équipement est en général assez cher, mais il existe 2 solutions : PIKVM et Tinypilot.
@tayledras@noiq And yes, I think a lot of that stuff is extremely #bloated because if we need #Virtualization for seperation, there are many other options ranging from #BSD#jails to user privilegues usually [#Apache2 / #httpd runs as daemon/service under it's own user with near-zero privilegues!] and even #VMs can be done with #QEMU / #KVM more elegantly...
Seperating #Compute and #Storage does make sense - but only for medium to big businesses with their own Systems.
On a Linux 6.4 kernel I managed to break #qemu with #kvm, in such a way that booting several OS fails with page mapping errors. Nothing in dmesg. Reboot fixes it, merely reloading kvm_intel didn't help. Anyone heard of this before?
Anyone running #Xen or #KVM with #Glusterfs as a backing infrastructure for virtualized #kubernetes? Planning a small #homelab and looking for ideas/gotchas. (For instance, I'm not married to GlusterFS. I may end up going a different route if something better exists).
While I'm asking, anyone running #HomeAssistant on #k8s? Thoughts or suggestions there? (I'm currently running HA on a dedicated desktop machine, but considering repurposing that machine as a k8s worker, assuming migrating HA into k8s isn't crazy painful).