Ticket #6474 (closed defect: fixed)
High CPU when changing network to NAT
| Reported by: | xok | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 3.1.6 |
| Keywords: | nat, bridge, network, high cpu | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description
Hi,
Host is Win XP SP3, Guest is Windows Server 2003.
Start the VM as bridge, when OS is running, change the network connectivity to NAT.
Any request to the Internet (e.g. IE) will push up the CPU to 100% use up to 7 ou 8 seconds.
Setting back to bridge connectivity will get back to normal.
Attachments
-
_cssdgo-2010-04-01-19-23-08.log
(60.9 KB) -
added by xok 13 years ago.
-
_cssdgo-2010-04-01-19-23-08.2.log
(60.9 KB) -
added by xok 13 years ago.
-
_cssdgo-2010-04-06-17-13-02.log
(49.8 KB) -
added by xok 13 years ago.
Change History
comment:2 Changed 13 years ago by xok
Hello,
I have made an regression to v3.1.4, the version v3.1.6 seems to consume a lot of CPU.
comment:3 Changed 13 years ago by Hachiman
"use up to 7 ou 8 seconds" does it mean that cpu usage up to 100% for 7-8 seconds ant then calm down? What happens if start vm with NAT networking?
comment:4 Changed 13 years ago by xok
"use up to 7 ou 8 seconds" does it mean that cpu usage up to 100% for 7-8 seconds ant then calm down?
Yes, when changing adapter type and using NAT consumes a lot of CPU (e.g. browsing on the web and using Numara Track-It! Server / Client) when compared to Bridge.
I have made an regression for 3.1.4, which seems more stable in my environment (notebook Asus M50SV) and consumes a lot less CPU.
Could you please attach log file?