[WorksForMe] Win 10 Guest "High CPU "( host Linux Minth 18.3) Version 5.2.2 r119230 (Qt5.6.1)

[Jeff Bourdeau]

My host station has 8 gig
Any Guest VM works well but WIndow 10 with 3 gig of RAM (Guest) always has it's CPU at 100% so it is making it very slow

Host : Version 5.2.2 r119230 (Qt5.6.1) LINUX MINT 18.3

PLayed with video carte settings, disabling some features as recommended on the web but Can't find a way to make Win 10 not has it's CPU at 100%

JF

[socratis]

Use the Win10 Task Manager to find out which process is requiring all the CPU. Could be Windows updates...

[Jeff Bourdeau]

I did check the Performance monitor of the Guest but the something taking the CPU is not showing
it's not window Update, system is up to date and always stays at 100% CPU

Screenshot from 2017-12-17 12-38-24.png (21.28 KiB) Viewed 3099 times

[mpack]

Go to the details tab in Win10 task manager and look for a process doing lots of I/O, including network I/O. The guest doesn't have real DMA hardware, so I/O time shows as CPU time on the host.

How have you shared cores with the host? In fact, if you need to discuss this any further then provide a VM log file. With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[Jeff Bourdeau]

Vbox.log.zip

(23.72 KiB) Downloaded 10 times

Here is the log
Yes I shared 2 processor in the GUI ( 2 out of 4 )

JF
Tks !

[socratis]

00:00:15.366195 GUI: 2D video acceleration is disabled

And so is the 3D acceleration. Shutdown the VM and enable them in the VM settings » Display. Then re-install the Guest Additions (GAs) in the guest.

00:00:02.665411 Console: Machine state changed to 'Restoring'
00:00:39.361076 Changing the VM state from 'SUSPENDED' to 'SAVING'

I'm afraid that this is a problem. You need to repeat the procedure as follows, because if you "Restore" the VM, I have no information whatsoever about the installed GAs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM.
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).

00:00:02.798349 NumCPUs <integer> = 0x0000000000000002 (2)
00:00:03.111210 CPUM: Physical host cores: 2

You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors, not logical ones. See also the information from Intel about your "Core2 Duo E8400" CPU.

Other than that, your log seems fine. You got to realize the CPU that you're having is not the most powerful in the market (it's almost 10 years old) and it's going to show, especially in a fresh Windows installation, when everything needs to be indexed and updated.

Disconnecting the network cable will show quite effectively that the whole thing will be... calm, since it doesn't want to / it can't update anything...

[Jeff Bourdeau]

TKs socratis ! Some HomeWork for tonight
JF
I know the pc is not so new LOL I am a former IT consultant from the WIndows World, prior to that was an Apple Mac consultant. Now retired aving fund to run on " OLD PC with linux " as my main machines for years !! without having to buy the latest and the greatest PC anymore... But as for runing VMs, you are right
JF

[Jeff Bourdeau]

I took my SSD drive ( host linux mint) and connected it to my son PC and " WOW " amazingly fast and No problem with Windows

So I overestimated the capacity of my Pc/Linux to run VM

CLosing the case

JF
Windows was running very well in the VM on the other PC....

[socratis]

So I overestimated the capacity of my Pc/Linux to run VM

Glad you got it going. Marking as [WorksForMe].