Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos XG Home, vCPU limitations

Sophos XG isn't able to detect the correct topology of the CPU therefore in virtual environments is not able to differentiate virtual and physical cores. Sophos XG home is limited to 4 physical cores with its threads (8)

I configure a KVM machine, this is the extract that affects to the CPU. I try to assign 3 physical cores (6 Threads) but only us 4 threads, instead the 3 physical cores completely

vcpu 4 and 5 aren't use despite the topology is defined correctly.

  <vcpu placement='static'>6</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='4'/>
    <vcpupin vcpu='2' cpuset='1'/>
    <vcpupin vcpu='3' cpuset='5'/>
    <vcpupin vcpu='4' cpuset='2'/>
    <vcpupin vcpu='5' cpuset='6'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-q35-5.1'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'>
    <topology sockets='1' dies='1' cores='3' threads='2'/>
    <cache mode='passthrough'/>
    <feature policy='require' name='topoext'/>
  </cpu>



This thread was automatically locked due to age.