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.

anyone can request a change in https://github.com/xcp-ng/xenadmin/issues 🙂

@stormi Yes, it's present in both. That's what drew me to the 8.0.1 release - I hopping this was fixed from version 8.
I will go ahead and open an issue on github.

https://nakedsecurity.sophos.com/2019/06/19/netflix-researcher-spots-tcp-sack-flaws-in-linux-and-freebsd/

Testhost at home updated

XCP-ng 8.0 beta CPU: i5-4430 (Haswell) https://ark.intel.com/content/www/de/de/ark/products/75036/intel-core-i5-4430-processor-6m-cache-up-to-3-20-ghz.html (XEN) [ 0.000000] Hardware features: IBRS/IBPB STIBP L1D_FLUSH SSBD MD_CLEAR

Host started just fine, Win10 VM startetd also.

@stormi dd stands for disk dump and does exactly that: Copy a stream of data.
Fio however can be configured for precise workloads and read/write mixes, parallel workloads etc.

So the first thing will only give you streamline benchmarks, what almost nobody cares about.
The second can simulate realworld (VM/database...) workloads, where (controller) Caches and non magnetic storage (Flash, Optane, MRAM...) makes the real difference.
Also use big amount of data, since caches can impact small ones extremely. Don't get me wrong: We need them and they can make huge differences, but as long as your benchmarks fully fit into them, it gives your nonsense/fake results. Also (consumer) SSDs start throttling after some 10 to a very few 100 GB of data written. Their caches fill up and they 'overheat'.

You can spend days on benchmarks and how to do what. 😉

Good news, the vote are closed and the Public Center for Social Welfare's case study is first as we hoped!
https://a.cstmapp.com/voteme/31130/633291567

Thank you everyone!

Thanks for your input!

I think it might be the one then 🙂 Also, if there is a big problem with it, we can always update the package!

@Kalloritis I'm not sure about that. You see a stack of "unknown" functions because the tapdisk binary was not compiled with all debug symbols, contrary to qemu-dp.

And I'm waiting for the next XenServer release before continuing this diary. 😉

Nicely done!

I don't know what's xo-updater, maybe an external script, but it's not the upstream one from XOA or XO project.

And yes, there is some patches sometime (for xo-server, which is one package of Xen Orchestra).

For example, xo-server in 5.38.0 never landed in XOA, because we did some QA before and found some issues. We patched it, and then we've done some QA again, and then we decided to release Xen Orchestra 5.33. That's why you can have sometimes some surprises from the sources, because it's not officially tested (unlike in XOA)