XCP-ng 8.3 public alpha 🚀
-
@tjkreidl
Although it's my test lab, I have a backup of everything. I'm something of a burned child with many years of bad experience.
Unfortunately it would take a few days to play everything back.
But I'll get a new SSD and give it a try.
But first thanks for the help, I'll write if it worked.
Regards Joerg -
@stormi Finally updated my two host playlab from 8.2.0 fully patched to 8.3.0-alpha2 using the ISO method followed by installing available patches using XO from source.
As boring as it is, I have nothing to report other than that the update of my low-tech hosts has worked (Dell Optiplex 9010, Intel i5-3550 CPU, 32GB RAM, Intel S3700 100GB SSD for boot, Samsung 860 EVO 500GB SSD for local SR, Intel X520-DA1 10G). You wouldn't believe it, but sometimes boring is good
.I'll report back if anything comes up in day-to-day operations
. -
@jhansen said in XCP-ng 8.3 public alpha
:@tjkreidl
Although it's my test lab, I have a backup of everything. I'm something of a burned child with many years of bad experience.
Unfortunately it would take a few days to play everything back.
But I'll get a new SSD and give it a try.
But first thanks for the help, I'll write if it worked.
Regards JoergSounds good, Joerg. Good luck!
-
@olivierlambert
Hello
So now the 8.3 is running with all updates.
Where the old partition table came from is still a mystery to me but it could be something to do with Dell Utility as tjkreidl assumed.
No idea....
I took all disks out of the server and wiped the boot disk with zeros and then installed a new fresh 8.2.1. Now I also had the 18GB partitions.
I then did a metadata restore via XO. (the trick with renaming the backup folder from the old UUID to the UUID of the new installation)
All disks back in the server and then all VM and functions of the server checked, everything ok.
USB stick with the 8.3 version in - and the update ran without any problems. Then yum update, no problems here either.
All VMs are running.
I've only noticed one thing so far:
I set up one of my 10GBit network cards with SR-IOV, which no longer worked. I deleted it and created a new one, then it worked again. I have 2 Intel I350 gigabit adapters in the server, they can no longer do SR-IOV.
Now it's time to stress test the server with Windows, Linux, databases and video conversion. I'll let the CPU's run at 70-80% load for a week and also let the network cards and disk sweat. We'll see.Thanks again for the help.
Greetings JörgTest server:
Dell Poweredge R730
2 x Xenon E5-2698v4 (40 pyk+40 ht)
512GB RAM
2 x I350 Gigabit and 2 x X540 10 Gigabit adapters
1 x NVidia Gforce RTX 2070S for GPU support
1 x 512GB SSD for boot disk
2 x 512 SSD for dmcache
5 x 8 TB Harddisk in Raid5 for VM -
@tjkreidl
Hello again,
thanks for your help, you put me on the right path.
I wrote to Olivier what I dit.
Greetings Jörg -
@jhansen Great news! Maybe the SR-IOV issue is driver-related - is there a newer driver available or perhaps some setting in the BIOS?
And, yes, I bet wiping all the old partitions made a big difference.
-
@tjkreidl
Yes I believe that too -
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
