@olivierlambert I understand and I thank you for at least hearing me out. If I go with KVM, I know that I’m not going to have all the fancy bells and whistles that XCP-NG offers. Believe me I know, I used your product and loved it. However, I will be able to operate and have an enterprise level backup fully supported via BDR Suite for $3 per VM. I can have as many hypervisors and file servers as my heart desires and never pay a penny more. It’s all based around the VM count and it’s all paid monthly. I can scale up or down as needed and only pay for the Qty that’s used during that month. Again, I would prefer to use XCP-NG but many of my customers require that I use a fully supported enterprise backup system. The only way I could afford to do it under your current model would be if your $1000 plan (pro) was $500 per hypervisor and that’s still almost double of what I’d be paying if I went with KVM and BDR Suite and never pay more when adding additional servers. I completely get your point about making enough but I wonder If you wouldn’t get a lot more people in my boat if you did come down or offer an MSP per month model that we could afford. Again, I thank you for at least hearing me out. Thank you.

It's very likely in Xen itself since a part of the power management is done there. Another topic to bring during the Xen Winter Meetup @TeddyAstie

@gudge25 ...forget about it... Mikrotik won't fix v6 and they have a proprietary OS, so you can't install normal stuff.

Great news

@Tristis-Oris sharing my google drive link via chat... should be easy to upload it there

@knightjoel I have not but glad you found something and I wasn't (at least then) crazy.

@jasonnix Yes, a vCPU means a virtual CPU, which is the assignment of a VM to a physical CPU core. Servers have sockets that contain physical CPUs, so it sounds like your system has four sockets, holding four physical CPUs. Each physical CPU can have multiple cores and in some cases, one thread per core or in others, two threads per core, but let's stick to the simpler case here. A configuration of 4 cores with 1 core per socket means each of the 4 vCPUs will reside on a core on four separate physical CPU sockets, so all four physical CPUs are accessed. This is in most cases not ldeal as in many servers with 4 physical CPUs, the memory banks are split between pairs of CPUs, two on one bank, two on the other. Having VMs cross over physical CPU memory bank boundaries is generally inefficient and should be avoided if possible. This is why NUMA (Non-Uniform Memory Access) and vNUMA become important in the configuration. And @gskger is correct that licensing can sometimes depend on the configuration. I should add that under some circumstances, configuring the CPUs for turbo mode can be an advantage. Suggested reading: my article on the effects of vCPU and GPU allocations in a three-part set of articles. In particular, Part 3 addresses NUMA and configuration issues and Part 2 discusses turbo mode. I hope this helps as it is initially quite confusing. https://community.citrix.com/citrix-community-articles/a-tale-of-two-servers-how-bios-settings-can-affect-your-apps-and-gpu-performance/ https://community.citrix.com/citrix-community-articles/a-tale-of-two-servers-part-2-how-not-only-bios-settings-but-also-gpu-settings-can-affect-your-apps-and-gpu-performance/ https://community.citrix.com/citrix-community-articles/a-tale-of-two-servers-part-3-the-influence-of-numa-cpus-and-sockets-cores-persocket-plus-other-vm-settings-on-apps-and-gpu-performance/

@olivierlambert Will do... that VM is running a massive rsync job at the moment, but once it's finished I'll be able to shut it down.

IIRC, just remove it (small cross) so it should use something default

@mattnj Thanks for the update, I didn't realize you could select the kernel in the ipxe boot, this might help me down the road.

@MathieuRA It does indeed Sir. Thank you very much!

For those who have AMD EPYC 7003 (Zen 3 EPYCs), you may find in Processor settings in firmware Enhanced REP MOVSB/STOSB (ERMS) Fast Short REP MOVSB (FSRM) 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.

@nomad What do you mean by the grand reconfiguration? Is there a new version that changes how things work?

@flakpyro Thanks, that will probably save me an hour this summer if I decide to upgrade my production system. By then it might all be fixed.

@StormMaster Thank you for sharing your findings! @stephane-m-dev Thank you for the update! Looking forward to testing the fix just not sure how to replicate other than what @StormMaster found.

@TeddyAstie thank you for investigating.

I don't think you need the --unit declaration. Try serial --port=pci,0b:00.0 perhaps?