Hi,
before starting my main task and „Move Windows 2000 to VBox“ (viewtopic.php?f=2&t=109204)
I tried to check whether an installation of W2K from scratch would run successfully.
So I loaded an ISO of Windows 2000 SP4 to VBox 7.0.8 with the following attributes (see below).
Opened only the Task Manager and Windows Explorer and minimized the latter.
This is kind of idle for a real installation and would require around max. 5% CPU.
Now in VBox this system does not go idle.
From a total of 70 minutes runtime the CPU went more than 50% to the taskmanager and others as the manager indicates:
33:05 idle (46%)
16:47 taskmgr (23%)
08:49 explorer.exe(12%)
04:50 VBoxService.exe (6%)
03:47 System (5%)
01:55 crss.exe
01:45 lsass.exe
01:07 VBoxTray.exe
01:06 services.exe
00:34 winlogon.exe
At the end the host (Thinkpad P1 Intel i7-11850H @2.5 GHz, 32 GB RAM) goes to 25% CPU load and the ventilator sucks.
Now my question: Is this the deal and normal for W2K on VBox or have I just made stupid settings?
- Main memory 750 MB
- 2 CPU
- Chipset PIIX3
- TPM none
- IO-APIC activated
- PAE/NX off
- Paravirtualization standard
- Nested paging activated
- Graphics memory 16 MB
- Graphics controller VBoxVGA
- Guest additions 8.0.7 installed successfully
[SOLVED] Windows 2000 needs 54% CPU in idle
[SOLVED] Windows 2000 needs 54% CPU in idle
Last edited by Cannobina on 2. May 2023, 14:24, edited 1 time in total.
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Windows 2000 needs 54% CPU in idle
Provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
Re: Windows 2000 needs 54% CPU in idle
Here we go...
- Attachments
-
- W2KFromScratch.zip
- (28.93 KiB) Downloaded 6 times
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Windows 2000 needs 54% CPU in idle
You have Hyper-v enabled on your Windows host. This often results in poor performance of VirtualBox since it is forced to run as a Hyper-v client. There also seems to be something unusual happening with the Hyper-v API, but it must be present since VirtualBox cannot run without VT-x.00:00:03.682115 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:03.713783 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
HMR3Init: Attempting fall back to NEM (Hyper-V is active).
Re: Windows 2000 needs 54% CPU in idle
[Solved]
Thank you mpack,
I ran Admin:CMD: "bcdedit /set hypervisorlaunchtype off".
Note that this changed a boot option, hence it will only take effect on next boot. So make sure to fully power down and reboot the host after changing the Hyper-v setting.
Now the CPU in the VM ist around 0-1 % and the host is nearly sleeping at 1% CPU.
Thank you mpack,
I ran Admin:CMD: "bcdedit /set hypervisorlaunchtype off".
Note that this changed a boot option, hence it will only take effect on next boot. So make sure to fully power down and reboot the host after changing the Hyper-v setting.
Now the CPU in the VM ist around 0-1 % and the host is nearly sleeping at 1% CPU.