Opened 14 years ago
Closed 13 years ago
#5705 closed defect (fixed)
VB consumes all CPU utilization and Ram on host
Reported by: | Taz Higgins | Owned by: | |
---|---|---|---|
Component: | network/NAT | Version: | VirtualBox 3.1.0 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description
Running windows XP as the guest, windows vista as the host. The Host PC has an i7 and 8GB Ram
Virtual Box consumed increasing amounts of CPU Utilization on the Host while the guest was doing nothing. It reached over 80% utilization on a 4 cores of the host.
Virtual Box consumed increasing amounts of Ram on the Host while the guest was doing nothing, it grabbed over 6GB ram.
The guest OS was unusably slow when this happened
Closing down the guest session returned all my CPU and Ram to the host system.
Attachments (1)
Change History (8)
comment:1 by , 14 years ago
by , 14 years ago
Log file from a session where the utilization ran at 75%
comment:2 by , 14 years ago
I had the issue with massive CPU utilization on the Host happen again, and I have attached the log file.
What I did was start up SQL Server version 8 Enterprise manager and I tried to add in another server to it, I didn't give the correct user/password combo and at that point the utilization jumped up massivly.
comment:3 by , 14 years ago
Thanks. If you are able to try out host interface networking, could you try to see if that makes a difference. (to rule out NAT problems)
comment:4 by , 14 years ago
I experimented with the different network modes and it does appear to be a NAT problem.
comment:5 by , 14 years ago
Component: | host support → network/NAT |
---|
comment:6 by , 14 years ago
So utilization is jumped up, after entering wrong user/password, right? Could you please follow instructions and please send me result pcap file to vasily _dot_ levchenko _at_ Sun _dot_ COM? (I'd appreciated if you can do it in the way described in last 4 steps).
comment:7 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if still relevant with VBox 3.2.12.
Not very useful without the VBox.log file of that session.