XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Epyc VM to VM networking slow

    Scheduled Pinned Locked Moved Compute
    260 Posts 28 Posters 171.1k Views 29 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by olivierlambert

      XOA's kernel should have the capability already, as it's a Debian 12 with stock kernel. Also, the bottleneck is ONLY between VMs on the same host.

      ForzaF 1 Reply Last reply Reply Quote 0
      • ForzaF Offline
        Forza @olivierlambert
        last edited by Forza

        @olivierlambert said in Epyc VM to VM networking slow:

        XOA's kernel should have the capability already, as it's a Debian 12 with stock kernel. Also, the bottleneck is ONLY between VMs on the same host.

        OK, but then I do not understand the huge difference.

        Tested some VM-VM traffic on the same host:

        Ubuntu (kernel 6.8) -> Alpine (kernel 6.12): 13.7Gbit/s, P4 = 23.8 Gbit/s
        XOA (kernel 6.1) -> Ubuntu (kernel 6.8) : 5.5 Gbit/s, P4 = 17.5 Gbit/s
        XOA (kernel 6.1) -> Alpine (kernel 6.12): 11.9 Gbit/s, P4 = 13.6 Gbit/s

        And for measure against the bare metal NFS server:
        Alpine -> NFS SR (kernel 6.12): 13.7 Gbit/s, P4 = 23.4 Gbit/s

        bleaderB 1 Reply Last reply Reply Quote 0
        • bleaderB Offline
          bleader Vates 🪐 XCP-ng Team @Forza
          last edited by

          @Forza By default XOA VM has 2 vcpus, how many vcpus do your ubuntu have? Althrough iperf isn't running multithreaded in your test, there is one queue on the kernel side of the VM per vcpu to process packets.

          ForzaF 1 Reply Last reply Reply Quote 0
          • ForzaF Offline
            Forza @bleader
            last edited by Forza

            @bleader said in Epyc VM to VM networking slow:

            @Forza By default XOA VM has 2 vcpus, how many vcpus do your ubuntu have? Althrough iperf isn't running multithreaded in your test, there is one queue on the kernel side of the VM per vcpu to process packets.

            I have 8 CPUS on XOA, 4 CPUs in the Alpine VM and 6 in the Ubuntu VM

            P4 uses 4 threads with iperf3.

            @bleader Are you saying you do not see any performance differences between XOA and VMs with more recent kernels?

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Offline
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              If you want to compare perf between kernels, do that with the same number of vCPUs ideally (and also the same env, ie different kernel versions with the same iperf version)

              ForzaF 1 Reply Last reply Reply Quote 0
              • ForzaF Offline
                Forza @olivierlambert
                last edited by Forza

                @olivierlambert said in Epyc VM to VM networking slow:

                If you want to compare perf between kernels, do that with the same number of vCPUs ideally (and also the same env, ie different kernel versions with the same iperf version)

                Sure. but in this context it is not that relevant as all other VMs got a boost while XOA didnt as much.

                Does the Debian 6.1 kernel that XOA uses have the backported fixes mentioned in https://xcp-ng.org/blog/2025/09/01/september-2025-maintenance-update-for-xcp-ng-8-3/

                Even if it has, it is clear that more resent kernels are much faster. Why not release a XOA with more recent kernels?

                1 Reply Last reply Reply Quote 0
                • olivierlambertO Offline
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by olivierlambert

                  Kernel version could have an impact and being unrelated to the fix we provided. Get an even more recent kernel on your XOA to test (eg one from testing)

                  ForzaF 1 Reply Last reply Reply Quote 0
                  • ForzaF Offline
                    Forza @olivierlambert
                    last edited by Forza

                    @olivierlambert said in Epyc VM to VM networking slow:

                    Kernel version could have an impact and being unrelated to the fix we provided. Get an even more recent kernel on your XOA to test (eg one from testing)

                    I was not able to update the kernel due to some issue in XOA installation. I commented on this at https://xcp-ng.org/forum/post/97522

                    But to clarify — my goal is to reach the same performance in XOA as with our other VMs. I had assumed it lacked the kernel support, and that led to the confusion. Sorry for that.

                    D 1 Reply Last reply Reply Quote 0
                    • D Offline
                      dinhngtu Vates 🪐 XCP-ng Team @Forza
                      last edited by

                      @Forza There's a new script here that will help you check the VM's status wrt. the Fix 1.

                      ForzaF 1 Reply Last reply Reply Quote 1
                      • ForzaF Offline
                        Forza @dinhngtu
                        last edited by

                        @dinhngtu said in Epyc VM to VM networking slow:

                        @Forza There's a new script here that will help you check the VM's status wrt. the Fix 1.

                        Thank you. It does indeed look like the EPYC fix is active in XOA.

                        [07:25 22] xoa:~$ python3 epyc-fix-check.py
                        'xen-platform-pci' PCI IO mem address is 0xFB000000
                        Grant table cacheability fix is ACTIVE.
                        

                        Has Vates checked if a newer kernel would help the network performance with XOA?

                        Current kernel is: linux-image-amd64/oldstable,now 6.1.148-1 amd64 [installed]

                        When trying to install any of the newer kernels (6.12.43-*) it immediately fails dependency check:

                        [07:30 22] xoa:~$ apt install linux-image-6.12.43+deb12-
                        linux-image-6.12.43+deb12-amd64                 linux-image-6.12.43+deb12-cloud-amd64-unsigned
                        linux-image-6.12.43+deb12-amd64-dbg             linux-image-6.12.43+deb12-rt-amd64
                        linux-image-6.12.43+deb12-amd64-unsigned        linux-image-6.12.43+deb12-rt-amd64-dbg
                        linux-image-6.12.43+deb12-cloud-amd64           linux-image-6.12.43+deb12-rt-amd64-unsigned
                        linux-image-6.12.43+deb12-cloud-amd64-dbg
                        
                        [07:30 22] xoa:~$ apt install linux-image-6.12.43+deb12-amd64
                        Reading package lists... Done
                        Building dependency tree... Done
                        Reading state information... Done
                        Some packages could not be installed. This may mean that you have
                        requested an impossible situation or if you are using the unstable
                        distribution that some required packages have not yet been created
                        or been moved out of Incoming.
                        The following information may help to resolve the situation:
                        
                        The following packages have unmet dependencies:
                         linux-image-6.12.43+deb12-amd64 : PreDepends: linux-base (>= 4.12~) but 4.9 is to be installed
                        E: Unable to correct problems, you have held broken packages.
                        
                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post