@danp
I was having a similar issue with OVA imports (using Chrome), tried a different browser (Firefox) and was able to import the OVA.

Went back to the reverse proxy and tried in Firefox, I currently have two VMs importing directly from VMware 😀

We just released XCP-ng 8.3 beta 1 !

I opened a new thread for us to discuss it and for you to provide feedback: https://xcp-ng.org/forum/topic/7464/xcp-ng-8-3-beta

Thanks for all the feedback already provided here, and see you on this new thread!

In order not to miss anything (and, let's be honest, for me to be sure that messages on the new thread reach you all), the best course of action is: open the new thread right now and use the "watch" button.
53fac025-6e0c-465b-97ab-5ca73a97bd93-image.png

And let's answer this common and legitimate question: how to upgrade from alpha to beta ? Well, there's nothing to do, just update as usual. In fact, you might already be in beta state. However, as indicated in the blog post, we need a lot of testing of the installer, so it's also an option to start from the installation ISO again.

For those who have AMD EPYC 7003 (Zen 3 EPYCs), you may find in Processor settings in firmware

Which is apparently disabled by default.
It could be interesting to enable them and see if it changes anything performance-wise. I am not sure if it's just for showing a flag, or if it changes anything in the CPU behavior though.

You can also try REP-MOV/STOS Streaming to see it changes anything too.

Its not solving it, but you can run

echo 3 > /proc/sys/vm/drop_caches

to release some of the cache again, without interfering with running processes.

[root@host2 ~]# free -m
total used free shared buff/cache available
Mem: 15958 3308 158 8 12491 2355
Swap: 1023 177 846
[root@host2 ~]# echo 3 > /proc/sys/vm/drop_caches
[root@host2 ~]# free -m
total used free shared buff/cache available
Mem: 15958 3308 2598 10 10051 2751
Swap: 1023 177 846

@yann Thanks for the fast reply ❤

Ok, I am opening a ticket, and providing a simple support script.

@grapesmc at one point I had the idea to set up a xcp-ng build environment and build netdata in there, then simply copy it over to the xcp-ng hosts. Unfortunately I was not able to dedicate the time to this so far.

When you boot in UEFI mode, press "e" to edit the boot command line, you have a line to change the memory for dom0.

Largely depends on your homelab. I'm currently in my homelab using a 3970X Threadripper 😉 But, I got that board/chip free after we did a client upgrade to the new Threadrippers, and there isn't a single amount of money I could save on energy to match that savings.

That said, think about what you need to use your homelab configuration for; I often find that the availability of RAM and total available cores. But I guess different needs matter too..

@stormi said in Nested Virtualization of Windows Hyper-V on XCP-ng:

Actually, Xen never officially supported Nested Virtualization. It was experimental, and broke when other needed changes were made to Xen. Now there's work to be done to make it fully supported, and this won't happen before the final release of XCP-ng 8.3. This will be documented in the release notes.

This is also an issue for us internally as we create a lot of virtual pools for our tests.

I read through a lot of the earlier posts and finally started scrolling to find this, which is the answer I was looking for. Why do I care? There is a Microsoft evaluation learning lab for things like Intune that runs in Hyper-V, basically a bunch of VHD (x) that get spawned as needed. Applications I need to teach myself. Running XCP-NG 8.3 current updates for this lab.

If it doesn't happen, then I'll just need to throw an eval version of Windows Server on something else like an HP T740 to run these labs, not the biggest issue for me.

Link for the labs if anyone is curious (free with an email registration like all the evals):

https://www.microsoft.com/en-us/evalcenter/evaluate-mem-evaluation-lab-kit

I'd think direct Docker support would be a higher priority than nested virtualization with a focus on Hyper-V. But that's just me.

I did the manual installation via the XVA. It worked for me.

Yaaay!!! Nice catch!

@gduperrey (unrelated to this fan issue) I loaded the new standard 8.2 testing kernel on my NUC11 and it seems to boot a little faster and also no longer complains about some APIC devices.

@steff22 said in Gpu passthrough on Asrock rack B650D4U3-2L2Q will not work:

@ravenet Ok I think the pro gpu's work better without so many bugs.

I switched to Nvidia RTX 4070. With the Nvidia gpu and this works as it should and gets an image on the screen on the first try.

So there must be something wrong with the amd drivers plus that error with the amd reset bug

I've setup a test system with a ryzen 7700x and a regular radeon 7600xt, non-pro gpu. Will let you know results. Shouldn't be an issue, it's same hardware and even the drivers work across them. Though they do have different bios on cards

I've acctually got a PR to help solve the documentation regarding the yarn forever part. Since I never could get that to work, I implemented a systemd variant instead.

#7848

Ping @olivierlambert for visibility 🙂

Hi,

No, because XenCenter use XAPI LDAP configuration, which is removed in XCP-ng, it won't work. For user access with LDAP/SSO, you must use XO.