XCP-ng 8.3 betas and RCs feedback 🚀

ThierryC01

@ThierryC01 said in XCP-ng 8.3 beta :

For your information, the connection error icon in "Settings"-->"Remotes" that appears when entering a wrong password once, then connecting anyway afterwards with the correct password is still present after all the 8.3 updates.

Is this an XCP-ng issue?

After the latest XOA update, the annoying error icon is gone! So it was an XOA issue

rmaclachlan

Not sure if this is a known issue, I couldn't find it on Github but maybe I was looking in the wrong spot. Is anyone else's network Bond speeds 0? I thought I had seen a fix a month ago for this in a release but now I can't find that changelog

stormi

@jivanpal If it persists, please open a new thread in the Xen Orchestra section of the forum.

stormi

I just pushed a few updates to the xcp-ng-base repository for XCP-ng 8.3. Nothing really worth mentioning from the user point of view, so what matters is as usual to ensure no regressions are seen.

flakpyro

After installing all the latest patches from this week my XOA and xe pif-param-list are both still showing network bonds linking at 0 b/s just like @rmaclachlan pointed out above.

ph7

@stormi
In XO updated yesterday, it says: 6 missing patches. but in the patches tab i got no missing pathes ???

stormi

@ph7 This happens when not all hosts in the pool are up to date. Could it be the case?

ph7

@stormi No, they are on the same patchlevel. Exept these released just resently.

ph7

@ph7
Eureka. I can see them now !!!

ph7

@ph7 Running rolling pool update.
This is really fun.
Love this project

laurentm

XenOrchestra (from source) update failed with the latest updates of XCP-NG 8.3.
I opened a topic in XOA forum, but I succeeded to update in XCP-NG 8.2, so the
error is coming from 8.3.

fatal: unable to access 'https://github.com/vatesfr/xen-orchestra/': server certificate verification failed. CAfile: none CRLfile: none

Finally, I have bypassed the PFBlocker module during the update and no more error happened.

lethedata

ISO NFS can't seem to mount with an IPv6 address as it leads to a "DNS Error."

Error code: SR_BACKEND_FAILURE_140
Error parameters: , Incorrect DNS name, unable to resolve.,

sr-probe is able to find the target/paths and VDI SR NFS is able to mount using the same path. Tried with and without brackets but no success on the NFS ISO side

stormi

@laurentm What's the dedicated topic? We can discuss there.

BenjiReis

@lethedata Can you share the command you're running and the corresponding SMlog?

Thanks

laurentm

@stormi

https://xcp-ng.org/forum/topic/8527/fatal-error-while-updating-xoa-installed-from-source/7

cunrun

Just providing feedback:

Love the XO interface at the start, very helpful. Also, I do like the colour scheme. It turned a few heads in the datacentre the other day.

Using a Dell R740xd with 2 GPU's to pass through - Works fine and given the GPU's to a VM each (for 3D mapping).

After watching Lawrence Systems device passthrough vid, I managed to view a PUSB in the XOA via the host. I managed to pass it through to a Windows 10 VM but cannot see if in the device manager. Assuming that this still in beta stages so will try a different set of USB devices for testing but so far the Seagate RSS LLC_00000000NAB7AQ06 doesn't show in Windows.

Happy to test further

john.c

@cunrun said in XCP-ng 8.3 beta :

Just providing feedback:

Love the XO interface at the start, very helpful. Also, I do like the colour scheme. It turned a few heads in the datacentre the other day.

Using a Dell R740xd with 2 GPU's to pass through - Works fine and given the GPU's to a VM each (for 3D mapping).

After watching Lawrence Systems device passthrough vid, I managed to view a PUSB in the XOA via the host. I managed to pass it through to a Windows 10 VM but cannot see if in the device manager. Assuming that this still in beta stages so will try a different set of USB devices for testing but so far the Seagate RSS LLC_00000000NAB7AQ06 doesn't show in Windows.

Happy to test further

Did you run a scan for changes (the icon of a monitor with a magnifying glass) in that Device Manager window? It will then check for new drivers to install and prepare for use. Prompting for device driver installation if required.

ravenet

@Andrew said in XCP-ng 8.3 beta :

@ravenet I did not have any problems with my Mellanox Connect-4 Lx card during upgrades from 8.2.1 (5.0 driver), to 8.3 (5.4 driver), then update to current 8.3 (5.9 driver), and then update to Xen 4.17.3. My card has the 14.32.1010 firmware. It is not used for the management interface. It is used by VMs and continued to keep the same ethernet name and function for the VMs.

Thanks for testing

I finally got around to updating the firmware on this Mellanox connectx-4 LX adapter. Bit of jumping through hoops to install tools, find proper firmware, but went from FW version14.18.1000 to New FW version: 14.32.1010. Had to do an emergency network reset again, but it's back.

Obviously an incompatibility with the new 5.9 driver with much older mellanox firmware.

Anonabhar

@ravenet This worries me because I use the Connectx-3 cards in my setup. I wonder if I am going to run into the same problem or is it only a Connectx-4 problem.

Andrew

@Anonabhar I don't think so as the ConnectX-3 is supported only in the older 4.9 drivers and not the newer versions (5.0 or 5.9 or newer). As all of these cards are old and EOL, it would be good to have the latest/last firmware installed anyway.