XCP-ng 8.3 public alpha 🚀
-
Great news!
-
I just upgraded a virtual Test-Cluster from 8.2 to 8.3-Alpha and afterwards had on one console that it told me that I don't have a management Interface and even no network interfaces. Am "Emergency Network Reset" did not change anything .
After checking everything, network was working, even ping was working ... I remembered my problem with the certificates I mentioned here already in November and yes, it was just the same problem with the old too short certificate
But this leads me to the new "problem":
Couldn't the xsconsole be improved to give a better hint than "no network interfaces"?
Because it really means something like: Could't establish a connection to the master.Oh and one more thing:
Is it by design that I cannot login to XO Light on the VM that is not the master?
It just tells me "An error has occured"
... Ah just check the return value and it says error: "HOST_IS_SLAVE"
This could also be improved or automatically redirect to the master as it contains the IP of the master in the response ... or in the end it might be good to be able to login if the master is not available for troubleshooting -
Adding @pdonias for the XO Light question, however and FYI, you can't do anything without a master, that's the only place where you can call the XAPI. If you lose your master for good, you need to promote a slave to master so you can get back querying the XAPI.
-
@olivierlambert said in XCP-ng 8.3 public alpha
:you need to promote a slave to master so you can get back querying the XAPI.
Yes I know, I mean a limited access mode or as you said, to make it master would be one task for troubleshooting that could be done if you could login (with warnings), generate/checking/exporting logfiles etc ... (and all you can do on xsconsole, see MAC addresses etc ...)
-
It's not possible, you can't speak to a slave at all via XAPI, so there's no limited mode possible. You must login and run a dedicated command to transform the node into a new master.
-
Oh I see, you don't plan to add more system near features?
All is just around xapi, even the login system. I thougt it would be more like on ESXi systems where you can manage the whole server from a web ui and will get features like the ones you can do from the local console screen.
-
@olivierlambert
The first overnight tests went well.
Performens and stability are good.
I have a question.
Do you recommend any specific Xen-Tools version for Windows and Linux on XCP-NG 8.3?
Currently have a mix of old and new versions on the various VM's.
The XO-Lite version doesn't have the big scope yet, but it looks very promising
-
Quick post to report that my home lab Intel NUC 11 N5105 is working without any issue since day one of the alpha release (not sure why you call it alpha then
).Running VMs are: 1xWin10, 1xFedora, 2xUbuntu and XOA from source.
Thank you for supporting latest intel nuc!
-
It's an alpha not because it's unstable
Just that we can make some updates before the official release. Happy to see it works well! -
Any updates in regards to getting nested Hyper-V working for WSL2?
-
This is more a Xen question, if you want progress, you need to pressure create a very precise report on xen-devel. Easier to be fixed in upstream, faster it will be backported to Xen running in XCP-ng
-
@jhansen said in XCP-ng 8.3 public alpha
:Do you recommend any specific Xen-Tools version for Windows and Linux on XCP-NG 8.3?
On Linux, you can simply install/update the tools from the guest tools ISO that is included in XCP-ng. If you already have tools working, there's no emergency: they haven't changed much in a while, and the part that affects performance and drivers is directly included in your distro's Linux kernel already.
On Windows, use Citrix tools if you plan to enable Secure Boot. Otherwise, ours generally work well (except for Secure Boot due to an expired signature key), but haven't been updated in a while and may have some shortcomings on newer Windows. We're still in the process of searching for a developer to improve them.
-
@stormi
Thank you.
At the moment all VMs are running with XCP-NG tools, including Windows (Win 10 and Server 2019)
I'm looking for the latest tools from Citrix and will then set up a 2022 Server. Should I enable "receive updates from Windows Update" or rather disable it ?
In the past, I often had problems that the Windows server no longer wanted to boot after some updates and then had to remove the updates manually.
It's only a test environment, but it should work after reboot -
@jhansen If you want to use Citrix tools, you can enable it. This will only install the drivers, not the management agent, though.
-
@stormi
Okay, I try
Thanks -
Something I've noticed when trying Citrix Tools up to 9.2.2 that it breaks some parts of the network connections.
On xcp-ng 8.2 (not tested on 8.3) I've tried multiple times, Active Directory goes out of sync due to network issues and Windows 10 and 11 can no longer connect to truenas SMB shares.
I've not been able to pin point the root causes of the issue but it goes away when you uninstall the network driver.
I'm really hoping this sort of issues will be resolved in drivers provided by you guys. -
@JurgenDM if you have an active XCP-ng subscription, please create a ticket so we can prioritize some requests
-
I'm just an home/hobby enthusiast who likes to play/test and learn these sorts of things.
So I cannot open a ticket, however if there is something I can contribute in the effort to be able to reproduce and solve the issue i'm happy to help. -
Stay tuned then, we'll publish a more recent version of the drivers at some point. We might have a dedicated profile this year (but this cost a lot, and it's hard to prioritize everything). Hope the best for us in terms of growth and we could deliver in every part of XCP-ng/XO
-
I just pushed a batch of updates to the
8.3/baserepository.You can update your 8.3 testing hosts with
yum update, and reboot.There isn't much on the side of user-visible changes, but this catches up with several months of changes made by both the XenServer team and us. Things are mostly evolving under the hood, so at this stage what matters is that the changes did not cause any regressions. Our internal test suite passed successfully.
Let's mention a few key changes from a very long changelog, though:
- All latest security fixes
- Performance optimizations in XAPI components. This means better performance for dom0 in various situations. This doesn't change the performance of VMs themselves, unless they are in situations where their performance was impacted by XAPI.
- Basic vTPM support (no snapshots, no migration, no HA...). We haven't tested it yet so I can't guide you towards testing it yet.
- Various fixes, as always.
- Work on HTTPS support for all operations (for example storage migration) so that port 80 can be eventually closed. A lot was done, but I'm not sure it's complete yet.
- Beginning of transition from python2 to python3: a few scripts ported to python3, and so python3 is now installed alongside python2 in dom0, and code will be ported progressively.
- Various driver updates
