XCP-ng 8.3 betas and RCs feedback 🚀

Andrew

@steff22 I tested the stock 8125 driver again on my ASRock AMD system and I have full read and write speed at 1G and 2.5G with native access and VLANs... I'll still try a driver update.

gsrfan01

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.

steff22

@Andrew now see that I also get 118MBytes/sec (connected to 1G switch.

But I don't have a dedicated 2.5 switch. So it is connected to a 10G switch with rj45 sfp+ module which steps down to 2.5g. This solution worked perfectly in windows 10 with full 2.5G both directions on the same Asus pn52 with CrystalDiskMark over smb I got Sequential reed 0.42 MB/s and Write 292.80 MB/s with Xcp-ng win 10 vm

steff22

@steff22 is one of these in the Asus pn52 RTL8125B-CG or Realtek RTL8125BG-CG, by the way. is it standard RTL8125 even if it is B-CG or BG-CG

steff22

By the way, is there a built-in driver for the Dell S140 in Xcp-ng?

Too bad write speed on a Dell poweredge R440 with Samsung 860 evo ssd all the way down to 150MB/s write speed. The same ssd in a regular PC with Xcp-ng gave 560MB/s

Andrew

@steff22 Let's continue the 8125 issue on your other network thread as it not directly a 8.3 beta problem.

gsrfan01

@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.

rRobbie

Hello there

Just updated from 8.3 alpha (updated to the latest patches) to 8.3 beta using XOA on a Intel NUC11ATKC4 and a Intel NUC8i5BEH.

All went well, great job and so far super stable.

Thank You
RP

rRobbie

@rRobbie

I quote myself to report a small issue, after the reboot following the upgrade to beta one VM did not auto power on-
When I realized some services were not available I went and started the VM myself.

The other two VM with auto power on switch did power on without issues.

Let me know if I can provide any other info.
RP

olivierlambert

@rRobbie can you disable/re-enable the "Auto power on" toggle, reboot and see if it works?

If it doesn't, if the problematic VM is hosted on a storage repository that's inside a VM on the same host? (could be a "dependency" auto boot issue)

stormi

@gsrfan01 said in XCP-ng 8.3 beta :

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.

It is definitely an interesting finding. It would be worth testing whether this will happen in final release when upgrading a 8.2 pool to 8.3 (will this flip the setting to True automatically or keep as False?) and then trying to add a freshly installed 8.3 member to the existing pool.

If the tests show users of the final release, upgrading from 8.2 and then adding new hosts, may encounter the same issue, we'll have document this clearly in the 8.3 release notes.

By the way, was your pool initially ugraded from 8.2 to 8.3 alpha, or was it directly installed with 8.3 alpha?

Many thanks for your investigation and feedback! I'm creating a card in our kanban to keep track of this.

@gsrfan01 said in XCP-ng 8.3 beta :

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.

This is indeed a pending task: documenting the new TLS verification feature. Citrix Hypervisor Cloud (8.3) once had a pre-release documentation available, then it was taken down when they canceled the Citrix Hypervisor Cloud preview and renamed it XenServer 8 Stream.

gsrfan01

@stormi I was originally fairly confident it was fresh from 8.3 Alpha but can't recall with 100% certainty if it wasn't an in-place upgrade from 8.2.

Is there anything in the file system I can check to see if it was a fresh install or an upgrade?

moussa854

How to add vTPM in Xen Orchestra?

I have XCP-ng 8.3 beta and XOA 5.83.3

olivierlambert

It's not exposed yet in the web UI.

stormi

@moussa854 You can create a vTPM with xe vtpm-create vm-uuid=UUID_OF_YOUR_VM.

cocoon

@moussa854
And after adding it you might need some more prep? I have had no time to try more:

https://xcp-ng.org/forum/topic/6578/xcp-ng-8-3-public-alpha/121?_=1687790268385

moussa854

xe vtpm-create vm-uuid=UUID_OF_YOUR_VM

was enough to enable the vTPM in my case. Thank you so much.

rRobbie

This post is deleted!

rRobbie

@olivierlambert said in XCP-ng 8.3 beta :

@rRobbie can you disable/re-enable the "Auto power on" toggle, reboot and see if it works?

If it doesn't, if the problematic VM is hosted on a storage repository that's inside a VM on the same host? (could be a "dependency" auto boot issue)

I disabled / enabled the auto power on option, then rebooted the host and it worked fine. The vm started automatically along with the other vms with auto power on which started regularry the first time after upgrade to beta.

Btw, the vm is running on local storage.

Thanks
RP

olivierlambert

I think the upgrade disable auto power on at the pool level (so even when your VM got it, disabling and then re-enabling will also re-enable it on the pool).

I'm not sure there's an ideal solution, except maybe display if there's a discrepancy visible in XO when you have VM with auto power on enable while the pool doesn't.