loukingjr wrote:Just trying to help. I take it you didn't read the info on the Bugtracker page.
Look forward to your "fix".
I did read the bug tracker page, but I didn't see the use in posting anything else. In all honesty, this is a really low priority issue, and the devs are probably better off fixing real issues.
Using the i7-i7-4790K as an example, to do this right Linux should be setup with 4 CPUs x 2 threads per CPU. When it runs with 8 CPUs x 1 thread per CPU, it probably doesn't know which logical cores are paired. To take full advantage of the logical cores, the two threads in a physical core should be from the same process.
This is probably why the warning exists, but it is by no means worded correctly. It is also a limitation of VirtualBox, not user error. Practically speaking, I don't know how much it matters.
I found the documentation to correctly determine logical cores and physical cores for Intel and AMD.
giacomo wrote:This is probably why the warning exists, but it is by no means worded correctly. It is also a limitation of VirtualBox, not user error.
So your main point was you object to how the warning is worded?
It's just a guideline. How is that a limitation?
I wasn't aware of anyone saying anything about user error.
Talk about making a mountain out of a mole hill.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
The implementation is incorrect and the warning is misleading and you have added nothing to this discussion other than to show how little you understand about the topic.
What I understand about the topic is, many, MANY users who assigned all cores to a guest, not even counting threads had issues up to and including their guests crashing. Which just coincedently went away when they reduced the number of CPUs they set for the guest.
Which is why the warning exists.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
No wait it is a bug. I'm sure they wouldn't have a warning for something that certainly works properly: assigning more cpus than exist physical cores. Whether or not that is a good idea is a separate issue. The fact remains that it should be possible, without a warning, to give as much of my CPU to the guest as possible.
