@olivierlambert said in XCP-ng Center 20.03.00 released: why it's not the opposite (XenCenter should change this) This would be the logical change, which would allow all existing snapshots to work as designed. Making the change in XO would require maintenance on all existing XO-created snapshots.

Just to know the headline and interesting points, not to make a copy here

@Appollonius @borzel They've been saying that it'll be relevant for 20 years, though.

Yes, it will mean that we'll work very closely with Xen Project, and this is great for both Xen AND XCP-ng!

@olivierlambert Awesome and thank you for the follow-up.

Guys, you really deserve it! Congratulations!!

Yeah but it's not the case here, at all. They have absolutely 0 technical knowledge (a task force was created to "judge" the technical aspect, and it was only non-gov experts). So the goal for the gov is to select carefully some project to help with innovation, to: 1. keep startups here 2. create high skilled jobs "locally".

This is what we use (xenstore) for XOA deploy. However, Cloudinit is almost a de facto standard, so we think it's better to use it than custom scripts.

@FMaster007 Not if you do it correctly. See here -- https://github.com/xcp-ng/xcp/wiki/Upgrade-Howto

Issue is now fixed. You can clearly see IOwait exploding during the storage network issue: [image: 1570954346736-iowait.png]

[image: tenor.gif]

Cert is renewed... the proxy didn't reload after cert renewal...

Always

When you boot in UEFI mode, press "e" to edit the boot command line, you have a line to change the memory for dom0.