@cg Those HDD's will take their fair time to rebuild.
Always stressful looking how far along it is while crossing your fingers that another drive wont pop during the process.

@wtdrisco Chicken-egg thing: you need a program to listen in the VM to "get the order from XO" to install the tools. By default, there's no way to tell a VM doing something without any permission or specific program to listen to commands (which tools are doing partially, but since you haven't got them in the first place…).

For Linux, the best approach is indeed some automation in your templates (eg with Packer) or manual templates with tools already installed. Or Cloudinit to install them on first boot (but when you have a VM that's cloudinit ready, you also have the opportunity to install the tools so…)

@julien-f
I can confirm that the fix worked! Snapshots are back and working.

I am impressed at how quick you managed to fix it too.
Thanks!

@wolfmon You have this documentation https://xenbits.xen.org/docs/unstable/man/xl.1.html
But be careful, most operations of xl are not officially supported in XCP-ng.

@john-c Nice to see progress there, I did not update to that version yet. Did you already check if the shown USB devices are independent of the usb-policy.conf (so that you see really all devices there)? The blogpost did not get specific about this detail. As @stormi stated above, controlling the usb-policy is not available via XAPI for now.

@CJ yum update from 8.3 beta to 8.3 will be possible, but I still recommend using the ISO. In a perfect world, yum update would give you exactly the same result, but in reality there are always corner cases where files or packages are left behind (we have no sane way to tell yum/rpm to remove an installed RPM, unless making another RPM obsolete it and thus make it impossible to reinstall later if someone needs it for a good reason).

@mohammadm i think for nfs you should handle that from the kubernetes side. i.e. use an nfs-provisioner or the built-in nfs storageclass

@thepro101

i would install the guest-tools right from the start after base install of the os.

create min 3 nodes, install them as you like with guest-tools and then install the first rke2-node. read the docs how to config metallb on rke2. you have to do a small config tweak in the nginx ingress controller config

then add the other nodes.

to manage rke2 i would use openlens.

you can use democtratic-csi but be aware that you completely trust truenas and this opensource-project for your data. i dont think that i would go this route when i am not expirienced with k8s.

i would use the nfs-provisioner and when everything works fine and you have a solid csi-enabled backup you can add democratic-csi in the mix.

for us, backup and restore was the biggest problem. in theory everything seebs easy with k10 or velero but if you completely shoot your cluster you will have a very hard time.

to be honest, after 6 month and some installations we gave up on k8s and migrated our customers and our internal IT to a setup where we use openSuse MicroOS VMs for every docker-compose project. We now have approximately the same amount of VMs which we had as namespace but with the benefit of complete control over resources with very little overhead. And we have the benefit of an optimal backup and restore.

K8S bite me quite a bit too often 😉

@Nux rebuilding the dom0 kernel is quite tricky, and I am not sure it is going to help your usecase, if you really want, you may want to look on xcp-ng-rpms and the related linux rpm
Regarding nested Hyper-V in Xen, gen2 support was considered in the past, but it never got fully implemented, see https://lore.kernel.org/xen-devel/20191130115737.15752-1-liuwe@microsoft.com/
and https://lore.kernel.org/xen-devel/20190923100931.29670-1-liuwe@microsoft.com/ for related discussion on the Xen mailing list.
So as it is now, Xen in Hyper-V gen2 vm is not supported.
Only gen1 is supported on a best-effort basis.

Gen1 use realistic-behaving emulated devices, thus there is no Hyper-V specific driver that may improve performance.

@jasonnix depends on what PV driver you want to implement.
But such place would be the Xen MiniOS repo (tiny PV kernel project that serves as a base for Unikraft among others) : http://xenbits.xen.org/gitweb/?p=mini-os.git;a=tree

Also give a look at https://wiki.xenproject.org/wiki/Unikernels

@psafont said in Stunnel - Future plans to use something else?:

@nikade We've already fixed some issues to start using ocaml 5 regarding the C interfaces. Handling threading in ocaml 5 is still an open problem that the ecosystem has not yet solved (there are many libraries competing now). We still need to create a credible strategy to port xapi to the new model, and don't have any timelines yet

Yea porting it is probably not a bad idea, but I guess that involves the biggest tasks as well 🙂
All tho if you port it there might be opportunities to re-do a lot of things that you have been looking to fix for ages.

Crossing my fingers that this is something that you get time to do in the near future, there is a real chance here to take a big part of the esxi market as a lot of ppl are migrating.

@olivierlambert I think so. ceph.ko anyway isn't a core module for XCP-ng, so I don't think there's a high risk in patching it, especially with patches coming from upstream kernel.org.

Regarding the initial question, XCP-ng 8.3 will also have a newer kernel-alt. However, I don't recommend it for production, because it is a lot less tested in the context of XCP-ng.

@TheiLLeniumStudios I'm trying to do something similar with Talos, were you able to find a workflow that worked for you since this post?

Hi,

It depends on your Windows version (eg > 2019 : go for XenServer drivers). Those PV drivers are pretty stable and works. Alternatively, you can use https://www.xenserver.com/downloads

Our latest update train should provide full vTPM support or close to that (even for migration/snapshot). It's 8.3 beta 2. See https://xcp-ng.org/forum/post/68789

Yes, we are considering OpenELA for many reasons. It's backed by big companies with a common goal, so it's probably less risky than other choices (but Alma is also an interesting choice anyway).

As usual, it will be loosely based too: it's relatively impossible to "transform" a regular distro to XCP-ng, but it is very helpful to re-use many packages as possible for reducing the burden of maintaining them all 🙂

Well, it's not really possible to answer with a short answer. Globally, for the whole platform, we are talking about hard in a way that it takes time.