Ticket #7943 (closed defect: invalid)

Opened 12 years ago

Last modified 9 years ago

VMM/Guest SMP: Very slow performance on over-commit

Reported by: Technologov Owned by:
Component: VMM/HWACCM Version: VirtualBox 4.0.0
Keywords: Cc:
Guest type: other Host type: other

Description (last modified by ramshankar) (diff)

Very slow performance when over-commit CPU.

Host = 1 CPU, Guest = 2 CPUs. (same happens with Host = 4 CPUs and guest with 8 CPUs)

Host: WinXP/32 and RHEL5/x64, Intel Core 2 Duo (2nd core disabled in BIOS), VBox 4.0.0

Guest: WinXP (problem happens even without GA)

Only one VM is running. XP boot takes longer than 20 minutes. I decided to kill VM.

-Technologov, 29.12.2010.


Windows XP Unattended3-2010-12-15-09-00-34.log Download (46.8 KB) - added by Technologov 12 years ago.
VBox Log

Change History

Changed 12 years ago by Technologov

VBox Log

comment:1 Changed 12 years ago by Technologov

Host: Win 7 x64 + Intel Core i7 2600K CPU + VBox 4.1.0_BETA1

Guest: Debian Linux 6.0 x64 + 8-way SMP

Guest workload: Compiling VirtualBox.

*Host* OS becomes extremely unresponsive, like soft-lockup effect.

$ kmk

Workaround is to limit task to available _physical_ cores:

$ kmk -j4

(Host OS no longer locks-up)


comment:2 Changed 9 years ago by ramshankar

  • Status changed from new to closed
  • Resolution set to invalid
  • Description modified (diff)

You're not supposed to overcommit CPUs. Anyway, you probably already know that by now. Closing.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use