Günter Born#Xen jetzt mit 5 Jahren Sicherheitssupport
gyptazy#PegaProx for#Proxmox only? Nah, now you can also manage #XCPng!
XCP-ng support is still in tech preview but alread comes with:
Blogpost: https://gyptazy.com/blog/pegaprox-with-xcpng-support/
PegaProx 0.9.1 Release: https://github.com/PegaProx/project-pegaprox/releases/tag/v0.9.1
#homelab #virtualization #pve #proxmox #xen #xcp #xcpng #pegaprox #enterprise #vmware
XCP-ng support is still in tech preview but alread comes with:
- XCP-ng Pool Support — Connect XCP-ng / Xen hypervisor pools alongside Proxmox clusters
- VM Power Actions — Start, stop, shutdown, reboot, suspend/resume for XCP-ng VMs
- VNC Console — Remote console access via XAPI RFB
- Disk Management — Add, resize, remove, move virtual disks on XCP-ng VMs
- Network Management — Add, update, remove virtual network interfaces
- CD-ROM — Mount/unmount ISOs from XCP-ng storage repositories
- Node Details & Maintenance — View node info, enter/exit maintenance mode with VM evacuation
- Storage Uploads — Upload ISOs and templates to XCP-ng storage
Blogpost: https://gyptazy.com/blog/pegaprox-with-xcpng-support/
PegaProx 0.9.1 Release: https://github.com/PegaProx/project-pegaprox/releases/tag/v0.9.1
#homelab #virtualization #pve #proxmox #xen #xcp #xcpng #pegaprox #enterprise #vmware
nrbAt @bawuenet we're in the process of upgrading our #Xen #xcpng hypervisors to #uefi boot. Of course, we automate things and want to be able to reinstall our hypervisors from network boot. Our EFI netboot system is based on #ipxe which means it can only load EFI binaries. But xcp-ng ships the Xen kernel as a multiboot2 based image.
As probably one of the most weird ways to solve this problem, I've decided to chainload #grub2 from iPXE and learned a bit! 🧵
As probably one of the most weird ways to solve this problem, I've decided to chainload #grub2 from iPXE and learned a bit! 🧵
Echo NarI wish this post by the Xen Project existed years ago when I was trying to understand the differences between Xen and KVM. Would have been a great jumping point to dig deeper.
https://xenproject.org/blog/xen-at-fosdem-real-world-conversations-about-xen-and-kvm/
Xen at FOSDEM: Real-World Conversations About Xen and KVM
We just wrapped up a weekend at FOSDEM 2026 where Xen and XCP-ng both had dedicated booths. This was my first time at FOSDEM and the legend lived up to the hype. It was an insightful weekend full of interesting folks who were genuinely interested in the Xen Project. Everything
https://purl.org/rzr#https://vates.tech/blog/fosdem-2026/# #vates staff ask us for demos featuring #xen #xcpng #xenorchestra #waydroid #linageos #netbootxyz and more and follow @vates
xyhhx 🔻til alpine has setup-xen-dom0
Klaus FrankSo back on #QubesOS / #Xen. There is definitely something wrong with how it forwards the A380 into the #windows VM.
Now that I've remote desktop enabled (and can conenct with the A380 disconnected just fine) I now can also see a black screen via RDP when the A380 is passed into it.
(Note: passing the two end devices, aka the one for the video and the one for the audio of the A380 worked just fine in KVM on #NixOS. So it is something Xen/QubesOS does that breaks it...
So rebooted into NixOS and after having compiled some food I've tried passing through the end devices using KVM. And well it works with KVM. So what is wrong with my #QubesOS aka. #Xen config then?
Also because I thought it was funny I also tried attaching the Intel A380 to a windows XP VM.
The generic driver for the video card doesn't work.
It has a generic audio driver that almost works. It matches the device but fails to start :p
Sooo are we just going to ignore the vulnerability qsb-091-2023 "Xen Security Notice 1: winpvdrvbuild.xenproject.org potentially compromised"?
I do not see any more recent build of the XEN Windows PV Drivers.
Even the ones linked on the website https://xenproject.org/resources/downloads/ right now are only from 2023-07-13. Which is 11 days before that vulnerability was published.
Also the part that they replaced the executables with a warning text doesn't seem to apply to that website either...