Hi, You may want to follow this thread for the VDI not visible issue. Dan

Version 1.4.0 is released: https://codeberg.org/NiXOA/system/releases/tag/v1.4.0 It includes significant changes and improvements, including: dedicated getting started section, migration to valkey, only needing to clone system, and helper scripts. the xen-orchestra-ce nixpkg now references the libvhdi nixpkg, and the core flake now references and pulls from the xen-orchestra-ce repo as an overlay. System (the user input flake) now uses the Core repo as an overlay, reducing the need to clone both locally AND allowing system to pull new updates and releases from core. XO, and libvhdi as needed. The next goal is: Make an xsconsole-like TUI Automate package updates for libvhdi and xen-orchestra-ce using CI/CD pipelines Submit libvhdi and xen-orchestra-ce as official nixpkgs

@benapetr said in New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client: @Pilow I know them a little bit, I will have a look, but I am now working on another new cool thing! It's called xen_exporter: https://github.com/benapetr/xen_exporter It's a prometheus exporter that hooks directly to xen kernel via xenctrl library from dom0 and extract all low-level metrics from the host, allowing very detailed graphs with very low granularity with stuff I always missed in both XenOrchestra and XenAdmin: ... We have a similar project : https://github.com/xcp-ng/xcp-metrics, but unfortunately it's not used as of today (though it could get revived as Rust for Xen matures, i.e easier to build). There is also Xen Orchestra OpenMetrics support but it's not on XCP-ng itself.

That's a very good question, let me ask internally. Ping @pdonias he might know the answer

@vanny you can say you are working for Vinchin, I prefer when it's clearly told

That's very interesting, let me make sure @florent got this

I know it's actively worked as we speak (ACLv2). So I would say this year at least It's in our (soon published) roadmap in the "Next" section, just after the "now".

@DustyArmstrong The only GPU I've ever tried was nvidia quadro series, and that was probably under 8.2.

@TeddyAstie Thanks for that - I was going off of other old XCP hosts I have had running that did show IOMMU info there, so I figured it wasn't working on these particular machines. I also had the the Intel GPU working on those hosts, which further supported my theory. I do have a USB controller passed through to the same VM and that works perfectly, basically native functionality, but from the research I was doing it was suggested USB controllers are way less bothered about imperfect passthrough. I was able to find a ROM for my particular GPU, but I don't know what - if anything - I can do with it in XCP. I've found lots of info for QEMU and Proxmox, but I'm not sure they directly translate. If there's nothing I can do for the moment then I can live without the GPU, running decode on the CPU isn't really taxing it that much. Appreciate you looking into it.

Update 4: Hello, After a few tries, i reattempted to re-add the host to the pool, this time capturing the logs in another terminal and this time it seems to have worked. I think i followed the same steps the previous time, but maybe i did something different, like using pif-scan to introduce the reordered interfaces. This is how I've managed to get it to work: All hosts on version 8.2.1 all up to date. On the new host disconnected the management, remove pif, reorder the interfaces, reboot, add interfaces manually (used pif-introduce, not pif-scan), reboot, re-enable management, join pool. ifconfig eth2 down ifconfig eth3 down xe pif-list device=eth2 xe pif-list device=eth3 xe pif-forget uuid=9104e54c-6c82-5d83-b9fc-1d2b73d5d6f1 xe pif-forget uuid=27abec81-6861-796e-9abe-3b2653444c8f interface-rename --update eth6=14:23:f2:24:5a:80 eth7=14:23:f2:24:5a:81 reboot now interface-rename --list ifconfig eth6 up ifconfig eth7 up xe host-list xe pif-introduce device=eth6 host-uuid=edfaf68e-2c28-4486-8939-723bf2c72820 mac=14:23:f2:24:5a:80 xe pif-introduce device=eth7 host-uuid=edfaf68e-2c28-4486-8939-723bf2c72820 mac=14:23:f2:24:5a:81 reboot now I'm still baffled why it worked now, I've tried a few time with all the host up to date, and was planning to source a dual nic pcie card, to solve this issue. However on this host the the bond id doesnt match the pool ... on poll: [image: 1772217597892-f68e687e-5896-459f-9463-8806ffe4bb63-image.png] on the new host: [image: 1772217689154-b58bac6f-f7fa-484e-be30-de2c4d4304bc-image.png] xensource_error_log.txt xensource.log also presents lots of errors, so I'm going to leave it running over the weekend, and will try to add the necessary data for our SR on monday. what is the best way to send the full log file?

@MajorP93 we have almost same size 30 backup jobs (mixed delta/cr/repl/dr) for 95+ VMs [image: 1772211113722-42570f88-2792-4954-8315-b9fa92aa9047-image.png] but these are not operated by XOA but dispatched in 4 XO Proxies and still XOA get OOM killed

@florent root@xo-server:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm root@xo-server:~# dpkg -l | grep gnutls ii libcurl3-gnutls:amd64 7.88.1-10+deb12u12 amd64 easy-to-use client-side URL transfer library (GnuTLS flavour) ii libgnutls30:amd64 3.7.9-2 amd64 GNU TLS library - main runtime library ii libsrt1.5-gnutls:amd64 1.5.1-1 amd64 Secure Reliable Transport UDP streaming library (GnuTLS flavour)

@bleader thanks for the tip. You see my knowledge in redhat based systems is almost non existant. Think I'm almost 99% debian and 1% ubuntu (and that not by choice) So I will take care of redeploying the script as soon as I upgrade, should be easily noticeable since monitoring will loose access and yell at me.

@florent Awesome, i have patched a second location's XOA and am not experiencing the issue anymore there either.

@olivierlambert said in Rust-based guest-tools... How are things going?: The thing is that it works very well and doesn't need fixes… I know, not usual right? It was so stable that we left it like that waiting for people coming for bugs and nothing happened… We'll cut a 1.0 in the next weeks/months. I have indeed seen the stability of it myself. But the lack of updates made me worry anyway. But I'm really looking forward to the promotion to 1.0 as well. Thanks!

@rniesen Do you mean occasional hangs? Yes, Server 2025 is known to hang if these options are not present.

Hello, I have hardware issues, specially on the disks. Unfortunately I don't have fully access to the machine to be able to confirm if is effectively disks( more likely ) or back-plane. Interestingly some of those VMs does work, I can boot them and work with them but cannot copy the disks. Since those are Windows server VM I have also tried the Windows backup tool and this failed as well to perform to finish the backup. So I'm closing this investigation as hardware issue.

Just go to Settings > Servers tab in XO and remove the entry associated with this pool.