Sophos XG vCPU or physical CPU limitation

Hi l0rdraiden ,

If you are using Home Edition , the limitation is 4 cores, Depending on the no of cores your CPU can manage will be variable , you may choose 1 CPU 4 core or 2 CPU 2 core etc.

We have SFOS 17.5.0-310 i.e. GA available on My Sophos Portal

VI-17.5.0_GA.HYV-310.gpg       
MD5:9e910d288729066f25aa108f5c143429

You gave a similar answer here but the questions remains.

 community.sophos.com/.../xg-home-edition-4-core-limit-apply-to-threads

If I run Sophos XG in a virtual machine can I assign 8 vcores if the processor in reality has 4 cores 8 threads?

Does sophos differentiate if the vcore is based on a physical core or on a thread?

The answer is quite clear. 4 VCores.

Clear?

So if I have a cpu with 4 cores 8 threads

• If I install Sophos XG in the physical machine I can use the 4 cores with its 8 threads (8 "v"cores)
• but If I install SophosXG in the same processor as a virtual machine I can only use 4 vcores.

Right?

Clear?

So if I have a cpu with 4 cores 8 threads

• If I install Sophos XG in the physical machine I can use the 4 cores with its 8 threads (8 "v"cores)
• but If I install SophosXG in the same processor as a virtual machine I can only use 4 vcores.

Right?

Hi l0rdraiden ,

We support Hyper Threading so the 4 cores will be as 8 threads and as the VM we cannot comment on that as it would depend on the Virtual Machine if hyper threading is supported or not if so it may convey as 8 logical cores and SFOS will only able to use 4.

Thats my point, any hypervisor will show to the guest OS a number of cores (vcores), and from a VM perspective all those cores are equal, so it's unfair compared with a physical setup.

Any modern processor has 1 core 2 threads ratio so it would be fair in a virtualize environment to allow 8 cores.

RAM is usually not and issue becasue in a home environment you deal with low users high speed connections, so if we want to play the the security features cores are more important than RAM.