High CPU using Windows 10 Version 1803 as host and guest
Re: High CPU using Windows 10 Version 1803 as host and guest
Hello.
I had the same problem and solve it by changing the following setting : VirtualBox Manager / System / Chipset : PIIX3 ==> ICH9.
But take a snapshot before trying this solution
Regards.
I had the same problem and solve it by changing the following setting : VirtualBox Manager / System / Chipset : PIIX3 ==> ICH9.
But take a snapshot before trying this solution
Regards.
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: High CPU using Windows 10 Version 1803 as host and guest
That isecassette wrote:by changing the following setting : VirtualBox Manager / System / Chipset : PIIX3 ==> ICH9
Do not change the chipset to something that's labelled as unsupported!
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: High CPU using Windows 10 Version 1803 as host and guest
Hello,
I must admit that don't know if this is risky.
But it worked for my VMs.
You can test by booting from an ISO image of a W10 installation disk :
-Configuration : Chipset = PIIX3
--Boot the VM from an ISO image of a W10 V1703 installation disk and wait for the first prompt : host UC used by VirtualBox Manager = 0 percent
--Boot the VM from an ISO image of a W10 V1803 installation disk and wait for the first prompt : host UC used by VirtualBox Manager = constant N percent (25 for my host)
-Configuration : Chipset = ICH9
---Boot the VM from an ISO image of a W10 V1803 installation disk and wait for the first prompt : host UC used by VirtualBox Manager = 0 percent
Regards
Eric
I must admit that don't know if this is risky.
But it worked for my VMs.
You can test by booting from an ISO image of a W10 installation disk :
-Configuration : Chipset = PIIX3
--Boot the VM from an ISO image of a W10 V1703 installation disk and wait for the first prompt : host UC used by VirtualBox Manager = 0 percent
--Boot the VM from an ISO image of a W10 V1803 installation disk and wait for the first prompt : host UC used by VirtualBox Manager = constant N percent (25 for my host)
-Configuration : Chipset = ICH9
---Boot the VM from an ISO image of a W10 V1803 installation disk and wait for the first prompt : host UC used by VirtualBox Manager = 0 percent
Regards
Eric
-
- Posts: 4
- Joined: 22. Jun 2018, 08:03
Re: High CPU using Windows 10 Version 1803 as host and guest
EDIT: ignore this post, was just a coincidence. See my later post below.
I've been a bit time-poor lately but I did a little more digging around and some accidental testing:
I've been a bit time-poor lately but I did a little more digging around and some accidental testing:
- I built a VM with the latest 1803 ISO, fully updated it and found it did not have the issue
- I activated the VM which was pegging a core ... later that afternoon I checked the host CPU utilisation and it was normal ie. the problem had stopped
- I then realised I activated it with the wrong key (already using it on a different host), so I uninstalled it with 'slmgr /upk' and it started pegging a core again!
Last edited by sessionzero on 30. Jun 2018, 00:56, edited 1 time in total.
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: High CPU using Windows 10 Version 1803 as host and guest
Coincidence. And if it worked, don't expect it to be a problem-free ride for too long.ecassette wrote:But it worked for my VMs.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 4
- Joined: 22. Jun 2018, 08:03
Re: High CPU using Windows 10 Version 1803 as host and guest
Had some time this morning and can replicate the issue. And it's strange!
So I have two Windows 10 Pro VMs both running 1803. They're limited on resources to 1 core and 2GB RAM. If I run one VM by itself it will chew up a core. The moment I start the other VM, they both go back to idle. And then I stop a VM and the remaining one's CPU use will go back straight back up. I can keep doing this with the same result
Also if I give the VM an additional core it doesn't have the issue.
So I have two Windows 10 Pro VMs both running 1803. They're limited on resources to 1 core and 2GB RAM. If I run one VM by itself it will chew up a core. The moment I start the other VM, they both go back to idle. And then I stop a VM and the remaining one's CPU use will go back straight back up. I can keep doing this with the same result
Also if I give the VM an additional core it doesn't have the issue.
Re: High CPU using Windows 10 Version 1803 as host and guest
I also have something like this.
Host: Windows 10 Pro 64bit
VM: Windows 10 Pro 64bit
After sometime I start the VM(it can be 2 hours or 2 days, I can't figure when it happens), VM OS get very slow and the task manager of the host shows max cpu usage for Virtualbox. In that state, when I check the cpu usage in VM, it shows no cpu load. But the VM OS it's nearly unresponsive and unusable. After restarting the VM OS, it works normally for some time.
I'm using the latest build now, 5.2.14. This is going on for some months.
Is there a solution?
Host: Windows 10 Pro 64bit
VM: Windows 10 Pro 64bit
After sometime I start the VM(it can be 2 hours or 2 days, I can't figure when it happens), VM OS get very slow and the task manager of the host shows max cpu usage for Virtualbox. In that state, when I check the cpu usage in VM, it shows no cpu load. But the VM OS it's nearly unresponsive and unusable. After restarting the VM OS, it works normally for some time.
I'm using the latest build now, 5.2.14. This is going on for some months.
Is there a solution?
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: High CPU using Windows 10 Version 1803 as host and guest
Do you have Drag'n'Drop enabled? See if you disable it (VM Settings » General » Advanced » Drag'n'Drop) changes the situation...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Volunteer
- Posts: 321
- Joined: 7. Oct 2009, 12:40
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: various
Re: High CPU using Windows 10 Version 1803 as host and guest
This is definitely a bug. It's very easy to reproduce. All you have to do is boot the 64-bit disk image of Windows 10 1803. For comparison, boot the 1709 setup image. The EMT thread is spinning something, it might be related to a timer device.
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: High CPU using Windows 10 Version 1803 as host and guest
I have. And I haven't seen any differences. I'm talking guest here, not host, right? My Win10-64 1803 is not on the power side, but I could try it there, as long as I know what I'm looking for... (see next Q).mhanor wrote:All you have to do is boot the 64-bit disk image of Windows 10 1803.
What's the "EMT thread"?mhanor wrote:The EMT thread is spinning something
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Volunteer
- Posts: 321
- Joined: 7. Oct 2009, 12:40
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: various
Re: High CPU using Windows 10 Version 1803 as host and guest
About EMT: https://www.virtualbox.org/pipermail/vb ... 11184.html
In my case, I see that the EMT thread is eating CPU time, while the guest is idling. It's all about the guest, not about the host.
In my case, I see that the EMT thread is eating CPU time, while the guest is idling. It's all about the guest, not about the host.
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: High CPU using Windows 10 Version 1803 as host and guest
How? And assuming that you see "a thread", how do you know it's the EMT thread? Could you post a VBox.log to see the CPU internals of your host?mhanor wrote:I see that the EMT thread is eating CPU time
PS. You're going to make me fire up the "grandpa" after all, you got my curiosity up and running...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Volunteer
- Posts: 321
- Joined: 7. Oct 2009, 12:40
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: various
Re: High CPU using Windows 10 Version 1803 as host and guest
I've build a non-hardened debug build, I can look at the individual threads of the VirtualBox process.
- Attachments
-
- VBoxlog.zip
- (53.76 KiB) Downloaded 29 times
Re: High CPU using Windows 10 Version 1803 as host and guest
Upgraded to 5.2.16, today it happened again. I wasn't even using the Vm Os but it went off. Had to restart the Vm.socratis wrote:Do you have Drag'n'Drop enabled? See if you disable it (VM Settings » General » Advanced » Drag'n'Drop) changes the situation...
Now I will disable the Drag'n Drop and see if it works. Thanks.
Re: High CPU using Windows 10 Version 1803 as host and guest
Try this:
- Uninstall VirtualBox
- Delete Oracle folder in C:\Program Files\
- Rename the folder ".VirtualBox" to XVirtualBox in C:\Users\your-user\
Now, install VirtualBox afresh then VirtualBox_Extension_Pack, then install Windows 1803 and check if you still have the problem..
To get your original setup, uninstall VirtualBox and delete the new ".VirtualBox" in C:\Users\your-user\ then rename XVirtualBox back to ".VirtualBox" before reinstalling VirtualBox.
Good Luck.
- Uninstall VirtualBox
- Delete Oracle folder in C:\Program Files\
- Rename the folder ".VirtualBox" to XVirtualBox in C:\Users\your-user\
Now, install VirtualBox afresh then VirtualBox_Extension_Pack, then install Windows 1803 and check if you still have the problem..
To get your original setup, uninstall VirtualBox and delete the new ".VirtualBox" in C:\Users\your-user\ then rename XVirtualBox back to ".VirtualBox" before reinstalling VirtualBox.
Good Luck.