Hello, We tried the compression feature. You "can see" a benefit only if you have a shared storage. ( and again, the migration between 2 nodes is already very fast, we don't see major difference, but maybe a VM will a lot of ram ( >32GB ) can see a difference. If you don't have a shared storage ( like XOSTOR, NFS, ISCSI ), then you will not see any difference because there is a limitation of 30MB/s-40MB/s ( see here: https://xcp-ng.org/forum/topic/9389/backup-migration-performance ) Best regards,

@JL457 a coworker was telling me about Intune, if you run Config Manager, there are some settings to let them work together. Not sure exactly what needed to be done, but apparently ours is fixed and ready for someone to learn what's what. Our contract allows some stupidly larger number of clients to be using Intune.

OK so potentially a vCPU topology issue

@KPS Glad to hear

Hello, We've added a card to our backlog to investigate this topic.

@markr All, I am currently running Windows 11 24H2 on an Intel Haswell i7-4700HQ laptop and it runs fine. What's more, it was in-place upgraded from Windows 11 23H2 using the (still working) setup.exe /product server switch compatibility bypass. (Simpler than all the LabConfig registry tweaks.) The only change I know of that simply won't run due to 24H2 is that it requires a processor capability that has been available since first generation Intel Core processors. It should run on your hardware in a VM. Seems like something else is going on.

@DustinB That pic was taken from the host tab. But yes I removed from the settings tab and host 2 still shows under pool 1 and all looks ok. Thank you.

@olivierlambert said in Can't boot a VM with 1TB memory / 128 CPUs: We are testing some machines with 6TiB RAM My god

Thanks for your feedback, @TeddyAstie and @gecant . From your answers and the discussion in Non-server CPU compatibility - Ryzen and Intel I conclude, that the benefits of the 8 V-cache cores vs. the 8 turbo cores are just irrelevant. For XEN they are transparent and not really different in terms of performance. Hence, in a typical server environment we just let XEN randomly choose the cores and don't think about different "performance cores" that COULD be faster in specific applications like games.

@pierrebrunet fixed now, thanks.

@deefdragon said in VM UUID via dmidecode does not match VM ID in xen-orchestra: Out of curiosity, I dumped the DMI into a bin and opened it up in a hex editor. I am seeing ASCII of the ID, but also a variant encoded in binary. In both cases, its formatted as 0b08f477-491a-a982-23c4-d224723624ea. I believe the ASCII version is the one that gets populated into the serial number as it comes after ASCII encoded versions of the 3 lines above it in the decode. In SMBIOS 2.8, the UUID is supposed to be encoded in little endian (i.e Microsoft GUID). Yet it is put as big endian instead. So when Linux generates the UUID string from the SMBIOS table, it is considered as little endian which causes this mismatch. SMBIOS 2.4 is supposed to be used (which appears to be using big endian UUIDs), but for some reason, something in XCP-ng UEFI supports forces it to be SMBIOS 2.8. So the binary UUID is the same, just that it is interpreted with a different endianness due to accidental format change.

Hey @olivierlambert and @andyhhp , thanks for your quick reply. That means it's not a problem at all. But we can't use all of the CPU's performance features either. However, these would only be used for specific computing operations (e.g., games) and would have little to no relevance for standard server applications, right?

@CodeMercenary Glad it worked! I just noticed that in the couple weeks since this happened, a new set of Pool Patches was available, so I ran through the usual process to update those and had no issues at all. This time, everything went smoothly, just as it has for the entire time I've had this lab up and running. So, chalk this up to one of those weird glitches you're bound to see when you use any technology long enough. As far as I'm concerned, the issue has been resolved. Please feel free to close out the issue.

@olivierlambert said in Limiting access to xo-lite to a specific IP address or ssubnet: About iptables, there's /etc/sysconfig/iptables but I'm not sure it's the right place to put manual modification, that's why I pinged the @Team-OS-Platform-Release In a way that's the right place, but one needs to be careful with modifications there.

@acebmxer good news! XO Team is totally aware of these "loading in progress" issues, and it will be fixed in the next release which will be released very soon. Don't hesitate to inform us if you see another UI issues. Have a good day!

Hi, It goes via XOA, which is piping the export of host A to host B import.

Question for @pdonias

@florent mmm. Sounds good dns_interno2 (ctx3.tosnet.it) Wasabi transfer Start: 2025-07-27 06:02 End: 2025-07-27 06:15 Duration: 13 minutes Size: 14.21 GiB Speed: 18.73 MiB/s transfer Start: 2025-07-27 06:15 End: 2025-07-27 06:16 Duration: a few seconds Size: 314 MiB Speed: 12.17 MiB/s Start: 2025-07-27 06:02 End: 2025-07-27 06:19 Duration: 16 minutes Wasabi Start: 2025-07-27 06:15 End: 2025-07-27 06:19 Duration: 3 minutes Start: 2025-07-27 06:02 End: 2025-07-27 06:19 Duration: 16 minutes dns_interno1 (ctx1.tosnet.it) Wasabi transfer Start: 2025-07-27 06:02 End: 2025-07-27 06:20 Duration: 17 minutes Size: 25.03 GiB Speed: 24.84 MiB/s transfer Start: 2025-07-27 06:20 End: 2025-07-27 06:20 Duration: a few seconds Size: 506 MiB Speed: 16.66 MiB/s Start: 2025-07-27 06:02 End: 2025-07-27 06:23 Duration: 21 minutes Wasabi Start: 2025-07-27 06:20 End: 2025-07-27 06:23 Duration: 3 minutes Start: 2025-07-27 06:02 End: 2025-07-27 06:23 Duration: 21 minutes FtpA TEST (ctx1.tosnet.it) Wasabi transfer Start: 2025-07-27 06:19 End: 2025-07-27 07:40 Duration: an hour Size: 164.59 GiB Speed: 34.67 MiB/s transfer Start: 2025-07-27 07:40 End: 2025-07-27 07:41 Duration: a few seconds Size: 804 MiB Speed: 52.72 MiB/s Start: 2025-07-27 06:19 End: 2025-07-27 07:42 Duration: an hour Wasabi Start: 2025-07-27 07:40 End: 2025-07-27 07:42 Duration: 2 minutes Start: 2025-07-27 06:19 End: 2025-07-27 07:42 Duration: an hour

Yes, you can install Windows Server 2022 Essentials as a VM on XCP-ng, but the issue is likely due to using a DELL ROK DVD. ROK media checks for DELL hardware during setup and won’t work properly in a virtual environment like XCP-ng. Instead, download the standard Microsoft ISO for Server 2022 Essentials and install that. If your DELL key doesn’t work or you need a new one, you can get a genuine key from Noxkeys.com for around $20 worked perfectly for me. Activation was smooth after that.