Ticket #6694 (closed defect: fixed)

Opened 8 years ago

Last modified 5 years ago

Number of processors slide bar incorrect when using hyperthreaded processors

Reported by: ToddAndMargo Owned by:
Priority: minor Component: host support
Version: VirtualBox 3.1.8 Keywords:
Cc: Guest type: other
Host type: other

Description (last modified by ramshankar) (diff)

This bug has caused absolute havoc at two different customer sites on two mission critical servers.

When setting up a new VM, the console gives a slide bar for the number of processors. On the x5650 and on the i7-920, this bar goes red, meaning you have exceeded your maximum processors, at the number of hyperthreaded processors not the number of actual physical processors.

Bug: this slide bar should go red at the actual number of *physical* processors, not the hyperthreaded processors.

And, if you take the slide bar at face value and give the VM more processors than it actually has (staying in the black portion of the bar), your VM will randomly go into a race condition (CPU storm), freezing up your VM (two mission critical servers in my case).

The attachment is of a CPU storm on an i7-920 configured for seven processors (4 physical, 8 hyperthread). Notice that all seven processors are showing the exact activity, which is not ever suppose to happen.

Many thanks, -T


CpuStormTS2003.jpeg Download (94.3 KB) - added by ToddAndMargo 8 years ago.
CPU Storm when processors are exceeded

Change History

Changed 8 years ago by ToddAndMargo

CPU Storm when processors are exceeded

comment:1 Changed 8 years ago by frank

  • Component changed from other to host support

Right, we should take hyperthreads into account and we will probably do this in a future release. However, this isn't high-priority.

comment:2 Changed 8 years ago by sandervl73

  • Priority changed from major to minor

comment:3 Changed 5 years ago by ramshankar

  • Description modified (diff)

VirtualBox 4.3 takes into account physical cores and not hyperthreads.

Closing as fixed. Please reopen if the problem still persists.

comment:4 Changed 5 years ago by ramshankar

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use