Document CPU limits and other limits of VMs in XCP-ng

[thomas-dkmt]

I’ve updated the Requirements page of the XCP-ng documentation, so that it includes the VM limits (CPU, Network, vGPU, etc.), and I improved the overall style and language.

Before submitting the pull request, you must agree with the following statements by checking both boxes with a 'x'.

• [x ] "I accept that my contribution is placed under the CC BY-SA 2.0 license [1]."
• [x ] "My contribution complies with the Developer Certificate of Origin [2]."

[1] https://creativecommons.org/licenses/by-sa/2.0/
[2] https://docs.xcp-ng.org/project/contributing/#developer-certificate-of-origin-dco

[nathanael-h]

Looks good, only 2 questions/suggestions.

[stormi]

Adding @olivierlambert and @julien-f to the reviewers as the topic of what we say we support or not is a product management topic IMO.

[stormi]

Why is there a modified version of my already merged "Add doc related to Nested Virtualization, and update 8.3 release notes" commit in this PR?

[julien-f]

@thomas-dkmt Ensure your master is up-to-date, rebase your branch on top of it and re-push 🙂

[stormi]

@thomas-dkmt Ensure your master is up-to-date, rebase your branch on top of it and re-push 🙂

There still is a problem with this branch. It looks like a rebase it still needed.

[stormi]

Nitpicking about the commit messages: the convention in commit messages is usually to use the imperative form rather than the past tense. For example "Improved the style and presentation across the whole page" would become "Improve the style and presentation across the whole page".

[thomas-dkmt]

@thomas-dkmt Ensure your master is up-to-date, rebase your branch on top of it and re-push 🙂

There still is a problem with this branch. It looks like a rebase it still needed.

Rebase done

[olivierlambert]

I am not sure at all with this entire section:

• we are very cautious and a quick overview isn't great for us by looking at the numbers
• We tested more than 64 vCPU with some Linux VMs IIRC, and topology will be one important work next year. So if we provide a limit, we should always put that in perspective with actual work
• it's even worse for the 2TiB limit, which isn't true for all VDI. Raw are not limited, SMAPIv3 current drivers neither and we aren't far to get qcow2 on tapdisk. So to me it's simply too negative to restrict too much by displaying those numbers without context.
• I'm not aware of a CD drive limit per VM, I remember some XS doc explaining how to add another one
• I'm not even sure about some limits (only one passed through GPU? never heard of it)

The rest of the PR is OK to me. Maybe we can start to merge everything except the VM limits which require more work to be suitable.

[stormi]

I tried to address all this in a new commit. We're not in a hurry to merge this PR so I think we can take the time to finalize it as a whole.

[stormi]

Ping @olivierlambert whenever you find time