@olivierlambert said in XCP-ng 7.5 net-install ISO: Sounds like something you wanted @maxcuttins You know already... to me what's matter is the level of engagement in the project. At the beginning is always everything awesome but in the long terms most of the project get low level of attention. So I need to be very very very very prudent in order to use something in production on my customers. But in this case I have to say: there is something new everyday. I'm exicted!

Note: even on XenServer, VSS still require to be enabled manually I'm so happy to NOT have Windows VMs into production… Far easier on Linux…

That's a possibility yes. I don't think it could happen fast however. And you can't close existing opened code, so it will be more proprietary additions in the end. That's why we are innovating directly in XCP-ng, and we'll continue that way!

Hello dear RC testers! We are releasing 7.5.0 final today, so here's how to go from 7.5.0RC to 7.5.0. Warning: this is only for people who installed the RC. Detailed procedure will be given in the release announcement for upgrading an XCP-ng 7.4 server Option 1, upgrade using the installation ISO Will work, although may be a little overkill since you already have a nearly-final 7.5.0. Option 2, update yum repository files and update the system # remove the RC-specific repository file if present rm /etc/yum.repos.d/xcp-ng-7.5.repo -f # install the 7.5 official repository file wget https://updates.xcp-ng.org/7/xcp-ng-7.5.repo -O /etc/yum.repos.d/xcp-ng.repo # update. If you had updated your RC regularly, this will install nothing, else you'll get a few packages yum update # if the kernel or xen-* packages got updated, reboot your server # that's it, you've got 7.5.0 final!

@olivierlambert Okej, its that part that's tricky Yea maybe so, but it's cool. And makes the uptime better even if it's just a lab. I've been using vmware for a while at my last work. But the licensing is not nice for a homelab. So this is my first time with xcp-ng (xenserver). I'll try updating tomorrow. Thanks.

Thanks for the tests. I have now moved the updates candidates to the updates repository, so everybody who installed 7.5RC1 should see the updates soon.

If someone fails to build, maybe the git-lfs in not properly initialised. To fetch the lfs-files after git clone you can do a git lfs fetch. weird ... after the second time installing git-lfs and again cloning the repo, it worked...

Hi, Since we do NOT use supplemental packs but directly RPMs, it's a bit different. We got a build env dedicated to that: https://github.com/xcp-ng/xcp-ng-build-env If you have questions, please ask @stormi

Updated: main renamed to base.

Document updated: new, simpler, branch structure for the repositories + section added to detail how we handle experimental changes to existing packages.

I'm not sure to understand your question. What do you mean?

@borzel The button seems like it was just randomly dropped on the page. I would suggest moving it directly below the checkbox group and the boot parameters entry field. My 2cts...

Now there is also a CHANGELOG.txt in nightly builds

@tzirechnoy Thats ok as it would work for you. And as @stormi mentioned, there is no difference in binaries except the ones he mentioned. So you would not see any execution differences.

@r1 Hi Thanks for that. Aimee

@maxcuttins There are two packages. User level blktap driver that you referred blktap and a builtin kernel driver blktap2. Said patch is against mainline kernel as additional driver. You still need to have user land blktap from https://github.com/xapi-project/blktap There are instructions lying around https://xcp-ng.org/forum/topic/122/how-to-build-blktap-from-sources/ to build user land blktap (its without patch).

No believe me. They don't have it. But they have a huge farm of test hardware. That's why they don't need an emulator…