VBox - CPU Utilization Creeps Up

Antman said:

VBox 3.08 hosting XP32, running EdgeStream Client in WiMP10. Viewing video stream on TFCnow.com

Host CPU usage begins at 10-40%, fluctuating. I can live with that. After some time, CPU starts hitting 85-90+. The delay between 'normal' CPU and spiked CPU can be 5 minutes to 30+ minutes.

Pausing/Stopping WiMP returns the CPU to a lower rate, but resuming immediately spikes.

Is it possibly related to the codec utilized by the stream source?

Another thing, vbox NAT network may be the cause of high cpu. If you are using NAT, then try to change to a bridged network with a real physical ip address

Airbot said:

Not to go too much off topic but having Vbox installed screws up Rainmeter for me. After Vbox is installed, it will slow the refresh rate of Rainmeter on the Host machine and RM also starts crashing. I believe you use both Antman, have you had this happen as well?

Not currently running RainMeter on this install. I will load it up though for testing purposes.

I had to drive to the UPS warehouse and pick up my FREE Windows 7 Ultimate license and DVDs. Got lost twice. Thank you to the *sshole who stole my GPS last year while I was at the post office.

huisinro said:

Antman said:

VBox 3.08 hosting XP32, running EdgeStream Client in WiMP10. Viewing video stream on TFCnow.com

Host CPU usage begins at 10-40%, fluctuating. I can live with that. After some time, CPU starts hitting 85-90+. The delay between 'normal' CPU and spiked CPU can be 5 minutes to 30+ minutes.

Pausing/Stopping WiMP returns the CPU to a lower rate, but resuming immediately spikes.

Is it possibly related to the codec utilized by the stream source?

Another thing, vbox NAT network may be the cause of high cpu. If you are using NAT, then try to change to a bridged network with a real physical ip address

Will also try that before I ditch this build.

But, you have found the only difference between my pre 3.x and post 3.x versions of VBox. In 2.x, I was not using NAT. Also noteworthy, this CPU issue appears to be a new development. I may have not noticed before, regardless of my experience once I updated to 3.06 - but I do not think so. It is a fairly big problem.

@Jimbo - I have not installed the VMserver yet. Been in the car basically all day - with another 80 mile trip before I eat dinner.