@olivierlambert I think some kind of registration would be a great idea. I'd also love some kind of way to kick back to you guys for the excellent work you've put into these products that's not a subscription. XCP-NG + XO have let me span my home lab from my basement into a rented office space and into a dedicated box.

I don't generate revenue so a subscription for this would be out of budget, I'd love to kick back something for the work you guys have put in. While not a perfect example, something like Untangle's home license at $50 / $150 per year depending on features would help fill in the gap.

Keeping a registration option to remove the nag in lab environments would still be a nice have

@gsrfan01 Follow up to this

Turns out the existing pool has it sent to false while the new one was set to new

New

[17:06 prod-hv-xcpng02]# xe host-param-list uuid= 
...
tls-verification-enabled ( RO): true
[17:06 prod-hv-xcpng02]# xe host-param-list uuid= 
tls-verification-enabled ( RO): true

Old

[17:06 prod-hv-xcpng02]# xe host-param-list uuid= 
tls-verification-enabled ( RO): false
[17:07 prod-hv-xcpng01]# xe pool-param-list uuid= 
tls-verification-enabled ( RO): false

Solution

Ended up running xe pool-enable-tls-verification and xe host-emergency-reenable-tls-verification on the existing server and was then able to get the new server added to the pool.

I was able to find very little documentation on these commands so I'm crossing fingers emergency-reenable-tls-verification doesn't cause any issues down the line but all seems good so far.

Not sure if this is related to 8.3 quite yet, but having trouble joining a newly installed 8.3 beta server into a pool that was started from 8.3 alpha and updated.

Attempting to add the new host generates this error POOL_JOINING_HOST_TLS_VERIFICATION_MISMATCH which I only see a single other reference to mentioning CPU settings which as far as I can tell match between the 2 hosts.

Intel Xeon CPU E5-1620 v4 on a
Supermicro SYS-5018R-WR

/xtf-runner selftest -q --host
Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS

./xtf-runner -aqq --host
Combined test results:
test-hvm32-umip                          SKIP
test-hvm64-umip                          SKIP
test-pv64-xsa-167                        SKIP
test-pv64-xsa-182                        SKIP

/usr/libexec/xen/bin/test-cpu-policy
CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:
Done: all ok

@vsaad that might be your limit. Those old PERC cards aren't particularly performant unfortunately.

You could try passing the whole device through to the VM: https://forums.lawrencesystems.com/t/xenserver-hard-drive-whole-disk-passthrough-with-xcp-ng/3433

That might help, but I'm not sure if that method still works.

You should be able to go to the network tab for the VM, click the network it's currently connected to, and then change it to the new one. If you have the management tools installed this can be done live, otherwise you'd need to shut the VM down.

I've been running TrueNAS for hypervisor storage since version 9, it has been rock solid since. I cannot say quite the same about SCALE (though this was alpha).

If you just want storage and no extra services, go core, it'll do everything you need it to do. If you decide you need more, it's easier to go from Core -> Scale than the other way around.

@encryptblockr

The issue with tools right now is dependent on the version of Ubuntu you use. My cloud-init uses Ubuntu's cloud image, but it's 20.04 so I can apt-get the tools. Once the tools hit the repos you can simply add this to your cloud-init template on Xen Orchestra and they install.

package_update: true
packages:
  - xe-guest-utilities
package_upgrade: true

Echoing Oliver's statement, my basic cloud-init took me probably a full week on and off to get exactly how I wanted it to, but has worked flawlessly sense.

If you want to delve into a DIY cloud-init image, this was useful for me when fixing my template and may be of use:

https://www.youtube.com/watch?v=exeuvgPxd-E