101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

503
active users

#kvm

3 posts3 participants0 posts today

Want to get rid of license costs of your #VMware environment? Switching to #Proxmox & looking for enterprise features like DRS? #ProxLB (opensource) has you covered!

With ProxLB you extend the features of your Proxmox cluster with DRS alike features including affinity & anti-affinity support, maintenance mode and soon also power management (DPM alike) and automated security patching!

github.com/gyptazy/ProxLB

GitHubGitHub - gyptazy/ProxLB: ProxLB - (Re)Balance VM Workloads Across Nodes in Proxmox Clusters. A Load Balancer for Proxmox - and more!ProxLB - (Re)Balance VM Workloads Across Nodes in Proxmox Clusters. A Load Balancer for Proxmox - and more! - gyptazy/ProxLB

I've gotten so used to running my everyday Unix system as a VM on top of various host systems that I notice myself hesitating to install it on bare metal. It feels unsafe. With a VM, I can back up the disk image(es) in various ways (wholesale or incremental snapshots), move it to new hardware, transfer it to a completely different environment and have it up and running in no time. On a bare metal machine, I feel "stuck". Does that make sense to anyone out there? #virtualmachine #vm #kvm #unix

Schwarm zuhülf!

Mein debian (12) will keine VMs starten.
Habe mir (mit Cockpit) einen Storagepool im Standardpfad (/var/lib/libvirt/images) eingerichtet & da ein qcow2 abgelegt. Versuche ich jetzt eine VM mit dem Image zu starten, verweigert AppArmor den Zugriff auf das Image.
Jemensch hier eine Idee für einen (möglichst frickelarmen/korrekten) Lösungsansatz?
Da unten gibt’s nochn paar Details.👇
#linux #kvm #debian #libvirt #qemu

Look at this gem I just found:

Using WinDbg Over KDNet on QEMU-KVM

https://www.osr.com/blog/2021/10/05/using-windbg-over-kdnet-on-qemu-kvm/

"The enlightenments that are enabled by default include setting the hypervisor ID to the same ID that’s reported by Microsoft Hyper-V (which is “Microsoft Hv”). [...] when the KDNet transport initializes, it checks the hypervisor ID, and if it discovers it is running under Microsoft Hyper-V [...] it attempts to open a debugger connection using an undocumented protocol over a synthetic hypervisor-owned debug device that Hyper-V provides."

I'll give this a shot tomorrow on Proxmox and I'll drink something strong if modifying the hypervisor ID actually solves my issues! :D

#windbg #reverseengineering #proxmox #kvm
OSR · Using WinDbg Over KDNet on QEMU-KVMWe spent several months working on a very intensive (and very interesting) project that required a writing a driver that was specifically intended to run on a Windows system running under QEMU-KVM …