To those who believe #Firecracker is a good idea for running #containers in another protective layer, should just migrate to #QEMU #microvms on #SmartOS, which will protect the #VM within a container.

Hey @dexter@bsd.network, when will #bhyve support microvms (https://www.qemu.org/docs/master/system/i386/microvm.html) ? I am curious to see if @cperciva@mastodon.social 's #FreeBSD kernel work allowing it to boot in ~20ms, works over there, and gets carried over into #OmniOS.

* Used Resources: Rebalances VMs for the optimal resource usage by their currently used resources for efficiency

* Assigned Resources: Rebalances VMs by their max. assigned resources to guarantee the resources (avoid overprovisioning)

#proxmox #virtualmachines #hosting #kvm #qemu #esx #esxi #drs #cluster #vm #vms #virtualisation #virtualization #virtualisierung #opensource

https://github.com/gyptazy/ProxLB

#kvm #qemu #vmware #virt #vm #virtualization #virtualisation #virtualisierung #opensource

trying to debug the pkg: Fail to chown /usr/local/lib/.pkgtemp.libpkg.so.2vn5iQkf2Ggn:Message too long stuff with the #FreeBSD 9p client under #qemu and it's feeling like an endless tower of cursed…

first of all it's not EMSGSIZE, it's errno 40 from Linux which is ELOOP (great, so the 9p protocol does not standardize error codes haha)

so it seemed to be that ELOOP which

FIXME: this should be handled with fchmodat(AT_SYMLINK_NOFOLLOW). Unfortunately, the linux kernel doesn't implement it yet.

which actually since 6.6 it does and musl libc does support it…

so I modified my local qemu to use it…

and the call succeeds in various cases but still not in this exact moment in the pkg installation process!

fchmodat2(655, ".pkgtemp.libpkg.so.2vn5iQkf2Ggn", 0120777, AT_SYMLINK_NOFOLLOW) = -1 EOPNOTSUPP (Not supported)

…what even!!

Today I quickly refreshed the differences between #KVM, #QEMU, and #libvirt, essential tools for virtualization on #Linux.

#KVM (Kernel-based Virtual Machine) is a component of the #Linux #kernel that turns it into a #hypervisor, allowing you to run multiple virtual machines (#VMs) on a #Linux host with hardware acceleration.

#QEMU is a user-space #emulator that works with #KVM to provide #hardware emulation. This means it offers the virtual #hardware that #VMs need to run various operating systems as if they were on a physical machine.

#libvirt is a toolkit that makes managing virtualization platforms like #KVM and #QEMU easier. It offers a consistent #API, command-line tools (virsh), and a graphical interface (virt-manager) to help create and manage #VMs.

In summary, KVM provides the core virtualization capabilities, QEMU offers the hardware emulation, and libvirt simplifies VM management with easy-to-use tools. These components together make Linux virtualization powerful and accessible!

#Virtualization #TIL

https://gyptazy.ch/blog/proxlb-rebalance-vm-workloads-across-nodes-in-proxmox-clusters/

#opensource #vm #virtualmachine #automation #ci #cicd #esx #esxi #drs #kvm #qemu #management

Great news, really great.

I played Baldurs gate 3 for a while in my Mint vm (LMDE).

I do not feel any difference in comparison to playing on my gentoo host machine ... REALLY.

IDK why i noticed moments of shuttering in system shock remake but You know what?
Maybe installing system on additional and passed SSD would help a lot ... I do not see a need to do CPU pinning. So i will stay with just plain QEMU script.

I just want to say i'm done with gaming vm, and i need to review my FreeBSD learning notes and make desktop vm.

I can safely rate my experience with BG3 in vm as 10/10 ...
This game is programmed so well ... Damn Larian, You are the best!

Small update, 2nd time i saw some shutterings but ... i can live with that for now. Maybe real SSD will help with loadings textures and stuff.

It's not the worst, no the best - but i have what i needed.

#qemu #passthrough #learning #virtualization #linuxgaming

Okay. I played for a while, and there's little noticeable "stuttering" but idk, maybe this is because CPU, maybe because my qcow2 img is on Iron wolf ...
Maybe i should pass SSD?
Then check ...
if this will not help ...
Maybe CPU pinning?

But hey, it's not that bad! it's playable.

With just plain QEMU 😎

I need something more demanding, maybe i should buy Phantom liberty and play cyberpunk? Baldurs gate 3 could be great for checking because i played unhealthy amounts of time and i remember this game.

For now, it's 50% of success.
Currently i should worry more about my desktop vm and on this one... i want FreeBSD.

#passthrough #learning #qemu

passthrough werks as intended!

a small thing i noticed ...
You need to have yubikey plugged if you use option u2f-passthrough!

I'm sorry for look but i didn't even started to make gaming vm, and ... idk in vm i don't care much how my system looks.

I need to install lutris now, access my gog and i will see how gaming is going without cpu pinning etc.

if i will get any performance issues i will reinstall libvirt and virt-manager ... (i hope not)

#qemu #passthrough

I passed yubikey to guest!

no hidraw{x,y,z} is needed.

just added -device usb-host,vendorid=0x0000,productid=0x0000

ofc vendorid, productid i provided from lsusb output, 0x0000 is just example.

after that (idk if this do anything) i added -device u2f-passthru

When i booted vm i had error like this (but yubikey was recognized etc)
"usb-x-y-z: can't set config #1, error -32"

I unplugged, plugged device like few times, and imagine that i opened keepassxc ...
during db creation, my yubikey was properly recognized so ...

it's time to build desktop vm! with gpu passthrough ... In plain qemu!

I get my script to work so... idk if i will need libvirt or virt-manager anymore ...

Just for tests, i think about trying uninstall libvirt+virt-manager.

#qemu #virtualization #learning

Surprisingly... #qemu 9.0.0 seems to compile just fine on #Slackware 15! Yay! 🤓

This being said, I am only on:

[2407/9553] Compiling C object libqemu-aarch64_be-linux-user.fa.p/linux-user_uname.c.o

So there is still plenty of time to mess things up. Let's see how it goes, and if the end result is usable.

And I am pleased to report that #qemu 9.0.0 compiles straight on #slackware 15 with almost no fiddling at all!

Took a while on my little server, but:

$ qemu-system-x86_64 --version

QEMU emulator version 9.0.0
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers

$ ls /usr/local/bin/qemu-sys* | wc -l
31

Ooooh yeah! 🤓

#QEMU 9.0 Released with #RaspberryPi 4 Support, LoongArch #KVM Acceleration Support, and New #RISCV Features https://9to5linux.com/qemu-9-0-released-with-raspberry-pi-4-support-loongarch-kvm-acceleration

#Linux #OpenSource

Small article about #Debian with #Docker and #KVM / #QEMU
#IPTables can sure be fun sometimes 😎 (Or I should rather say using a #bridge device under #KVM )

#Debian #KVM #QEMU #VM #Bridge

https://jhx7.de/blog/debian-kvm-bridge/

#amd64 offers the best support and is fast.
#arm64 is very efficient and also very fast.
#riscv is amazing & exciting (but slow with my current hw, but I can deal with it)

While amd64 & ARM64 work perfectly fine with #FreeBSD, the #RISCV hardware support (beside #qemu stuff) is still very limited. Currently, #Ubuntu and #OpenBSD work very well there.

mmdebstrap --architectures=riscv64 --aptopt='Acquire::Check-Valid-Until "false"' --include="debian-ports-archive-keyring" sid /srv/riscv64-chroot "deb [trusted=yes] https://snapshot.debian.org/archive/debian-ports/20220616T194833Z unstable main"

cp /usr/bin/qemu-riscv64-static /srv/riscv64-chroot/usr/bin/

chroot /srv/riscv64-chroot/ qemu-riscv64-static /bin/bash

Tags:
#risc #riscv #risc64 #riscv64 #starfive #vision #packages #crosscompile #foss