@olivierlambert I am open to building stuff into XCP-ng if my knowledge was there to do it.

@olivierlambert said in Dell cancels VMWare contract after Broadcom purchase: Time to make a phone call to Dell Yes sir do it. I hopefully a contract between you / Vates and Dell is on the horizen. Really hope XCP-ng comes as the standard for Virtualization just like ESXi once was.

@olivierlambert Good vacation and rest well ️

@Sergiu Good job! Hard to tell what was wrong, but Im happy you resolved it.

@grapesmc at one point I had the idea to set up a xcp-ng build environment and build netdata in there, then simply copy it over to the xcp-ng hosts. Unfortunately I was not able to dedicate the time to this so far.

@john-c @stormi @olivierlambert All, given the complexities involved in providing an automated solution for this issue, it may make the most sense at this time to mitigate any negative outcomes using an installation/update warning. For instance, throw a message dialog issued by both the ISO installer and the pool update feature in XO such as: WARNING: One or more of the pending updates may alter your VM's firmware. If you are using Microsoft BitLocker to encrypt virtual drives, you should exit now and suspend BitLocker prior to performing this update. (Provide customer with Exit or Continue buttons with Exit selected by default.)

@gskger https://xcp-ng.org/forum/topic/8202/eol-xcp-ng-center-has-come-to-an-end

@Danp Yes I did that and it looks good now.

Thanks for your feedback @loopway ! Happy to make your home lab running

just a personal opinion I'm leaving here, no follow-up needed. If I want to run containers I use OKD. I've always seen all the comments about keeping the dom0 controller to a minimum, docker alone adds a 2GB overhead to it, no more problems in adding stuff to it.

Thanks! Don't miss Daniel Stenberg stories, they are gold (eg: being insulted because someone found some curl sources in a bigger software). Some gems with the right tag in his blog: https://daniel.haxx.se/blog/tag/funny/

As I already explained in different places, what matters is the hypervisor, kernel, OVS and such important packages. We can still backport security fixes ourselves on various packages inside the OS. XCP-ng is only partially based on CentOS, only using non-critical CentOS packages (NOT the kernel, NOT Xen, NOT OVS, SMAPI/XAPI aren't packaged in CentOS etc.). XCP-ng is NOT your regular distro, it's an appliance where we backport relevant security fixes. Be sure that next major version won't even have SSH access enabled by default.

We are very well aware about all of this. But we are not a distro entirely based on RHEL at all (again, all the network, kernel, storage and compute plus many other things are NOT coming from RHEL). On a personal point of view, I'm a strong proponent of Copyleft licenses and the greater good, in the original spirit of free software. To me, there's a real moral contract between the software editors and the users. You can read my detailed opinion in this blog post: https://virtualize.sh/blog/the-moral-contract/ Due to those personal opinions, I'm really unhappy with RedHat move (and behind Alma and Rocky), but this is NOT clashing with our position for the next major release. So no, we won't be directly disrupted by this move.

@ryzen3 feel free to open a feature request on XO GH repository with many details as you can, so we can create the feature

We just released XCP-ng 8.3 beta 1 ! I opened a new thread for us to discuss it and for you to provide feedback: https://xcp-ng.org/forum/topic/7464/xcp-ng-8-3-beta Thanks for all the feedback already provided here, and see you on this new thread! In order not to miss anything (and, let's be honest, for me to be sure that messages on the new thread reach you all), the best course of action is: open the new thread right now and use the "watch" button. [image: 1687457779384-53fac025-6e0c-465b-97ab-5ca73a97bd93-image.png] And let's answer this common and legitimate question: how to upgrade from alpha to beta ? Well, there's nothing to do, just update as usual. In fact, you might already be in beta state. However, as indicated in the blog post, we need a lot of testing of the installer, so it's also an option to start from the installation ISO again.

Great news! Thanks for the feedback

Good news!!

@stormi @stormi said in New patch - sudo: Better not install security patches that require a reboot without rebooting. All you create is a discrepancy between what resides in memory and what is on disk, and in rare cases things may break, for no added security. Isn't this only true with specific patches? I'm no expert here so really just curious. Regardless I ALWAYS plan to reboot with ANY patches coming out and think others should do the same. @stormi said in New patch - sudo: We want to provide better metadata associated with updates, for XO to display. This is not ready yet, so for the time being, check the instructions for each update on the official blog. The update tag will list only update announcement: https://xcp-ng.org/blog/tag/update/ This is great news, love to see it!