XCP-ng 8.3 betas and RCs feedback 🚀
-
@stormi
OmniOS guest fails to boot in xcp-ng on version 8.3.Installation is fine: create a new vm, set viridian=false and installation progress smoothly. I've noticed that installation seem to lack PV-drivers.
When booting from freshly installed disk it panics with:
panic[cpu0]/thread=ffffffffffbc490c0: unable to configure /xpvd nexusI've tried several version of OmniOS (and latest OpenIndiana), I also tried Solaris 11.4, tried disabling apix with apix_enable=0 in /etc/system and all without success.
The same setup in xcp-ng 8.0 works like a charm with working PV-drivers (but no tools).Anyone with an idea of a workaround or even better, a resolution to this.
-
If you have the same problem in 8.2, then it's not 8.3 related.
-
@olivierlambert oh, sorry, got too carried away and did not notice this is 8.3 beta.
-
can confirm the stats/true granulrity issue as well
-
No stats :o(
but netdata seems to work -
So we are working on this issue. The format of the JSON output changed, which explains why it doesn't work in XO anymore. We'll fix it either in XCP-ng or in XO, depending on what is the best thing to do.
-
@stormi
No stats in XO-lite v0.1.7 (0d127) , as you probably already know -
@ph7 Indeed, we know about XO lite too. Thanks
-
And XCP-ng 8.3 Beta 2 finally released!
https://xcp-ng.org/blog/2024/02/15/xcp-ng-8-3-beta-2/
Fixes are on the way for the stats issue. It involves both XCP-ng and Xen-Orchestra, so this will take a few more days.
-
Good news. Release at this year possible?
What xapi version now at 8.2.1? dunno how to check it. -
@stormi I assume you had issue so took file down as link is giving a 404 page not found? lol
-
8.3 will be obviously released this year @Tristis-Oris
-
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.
-
Has the emergency network reset and xe been updated to handle IPv6 only configurations with patches after Beta2 ISO or is there something special that needs to be done?
I'm not able to pull patches atm and after running the resets it didn't seem to like the v6 addressing and xe refused to set the management interface without v4 set. Couldn't drop the temporary v4 address either.
Looks like the answer is yes but only at boot? "The only way to enable IPv6 for the management interface is at boot time. It's something that can't be modified afterwards in XAPI."
-
This update broke my mellanox network drivers for connectx-4 / 4 LX
Seems this latest patches included update from mennalox-mlnxen 5.4 to 5.9I have no networking, and after an emergency network reset, eth0 and eth1 disappeared.
update1: used yum downgrade mellanox-mlnxen-5.4_1.0.3.0-4.xcpng8.3.x86_64
this didn't fix until I did another emergency network reset.Looks like I'm back up and running.
Anyone else able to confirm this bug or am I alone in this hiccup? -
Thanks for your feedback @ravenet !
-
@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?
-
@olivierlambert said in XCP-ng 8.3 beta
:Thanks for your feedback @ravenet !
ill do firther testing later, in case issue is out-of-date firmware on the adapter itself being incompatible with the new driver. ill try and check the mellanox 5.9 changelog for firmware version requirements.
-
@ravenet @olivierlambert I have a 4Lx card on the way for testing...
-
One thing i have learned from testing various different 10G nics with XCP-NG that may be somewhat related to this is if you remove (or if a driver fails to load properly perhaps) a NIC that has the management interface assigned to it from a host, upon reboot the host will come up with no NICs present in XO or via xe pif-list, an emergency network rest will not restore them either, my only fix has been to re-install XCP-NG.
If you however first move the management interface to a different NIC before removing said NIC then everything will come up fine and if you have installed a different NIC it will be discovered no problem. I have tested this going from a Qlogic NIC to an Intel X520 and from an Intel X520 to an Intel X710.
