Windows 10 extremely slow on Virtualbox 6

[Marco Sulla]

Ok, I attached the log of 6.1 with Hyper-V and 6 cpus.

I do NOT attach the log of 5.2, since I noticed that with Hyper-V it gets slow! So 5.2 works with multiple cpus only with KVM.

[scottgus1]

I attached the log of 6.1 with Hyper-V and 6 cpus

we'd need a log with 2 processors for a decent comparison.

Salah, I said no camels, that's seven camels! Can't you count?

[Marco Sulla]

Can I ask you why you're breaking the netiquette because I've set six and not 2 cpus?

[scottgus1]

I'm not quite certain what this means:

why you're breaking the netiquette

But I asked for 2 because Windows 10 runs very well on 2 processors in a VM, per many reports from users on the forum. More than 2 causes a slowdown of the VM, due to extra scheduling oversight required on the host. Until one installs 3rd-party parallel-processing software in a VM that can fill up more cores, the forum advice is to keep to 2 processors for Windows 10 and other modern OSs in a VM.

[Marco Sulla]

I'm not quite certain what this means:

why you're breaking the netiquette

This means you're laughing at my face. Is this not against the netiquette?

But I asked for 2 because Windows 10 runs very well on 2 processors in a VM, per many reports from users on the forum. More than 2 causes a slowdown of the VM, due to extra scheduling oversight required on the host. Until one installs 3rd-party parallel-processing software in a VM that can fill up more cores, the forum advice is to keep to 2 processors for Windows 10 and other modern OSs in a VM.

I didn't know this, I thought that the more, the better. Furthermore, in the GUI the green is at the half of your number of threads. So I set the recommended maximum of the Virtualbox GUI. I'll retry with 2 cores and I'll send the log.

[scottgus1]

The green and red thing has thrown people off, yes. We had a discussion on it once, see viewtopic.php?f=8&t=98388

This means you're laughing at my face. Is this not against the netiquette?

I supposed it could be interpreted that way, though laughing at you was not the way I meant it. The laughy-face can be used, when it's not used after saying something one thinks is funny, to help people take gentle and kind counsel gently and kindly. You did disregard my instructions....

[Marco Sulla]

This is the log of a run with VirtualBox 6.1, Hyper-V, 2 CPUs. Useless to say it's slow as before.

PS: Linux guest on Windows hosts never got me problems. The more cores I give them, the better.

[Marco Sulla]

I post also my (censored) .vbox file.

[fth0]

I'd suggest to use the VirtualBox version 6.1.22 from Oracle, install the matching Virtualbox 6.1.22 Guest Additions and change Display > Screen > Graphics Controller to VBoxSVGA.

[Marco Sulla]

I'd suggest to use the VirtualBox version 6.1.22 from Oracle

I installed Virtualbox 6 using the _official_ PPA of Oracle

install the matching Virtualbox 6.1.22 Guest Additions

Guest Additions are installed:

Code: Select all

      <GuestProperties>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxControl.exe" value="5.2.44r139111" timestamp="1617304399533748000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxCredProv.dll" value="-" timestamp="1617304404583347000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxDisp.dll" value="-" timestamp="1617304401104235000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxGINA.dll" value="-" timestamp="1617304404582948000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxGuest.sys" value="5.2.44r139111" timestamp="1617304405668099000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxHook.dll" value="5.2.44r139111" timestamp="1617304401103828000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxMRXNP.dll" value="5.2.44r139111" timestamp="1617304404488677000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxMouse.sys" value="5.2.44r139111" timestamp="1617304405668661000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxOGL.dll" value="-" timestamp="1617304404692778000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxOGLarrayspu.dll" value="-" timestamp="1617304404684492000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxOGLcrutil.dll" value="-" timestamp="1617304404689761000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxOGLerrorspu.dll" value="-" timestamp="1617304404690016000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxOGLfeedbackspu.dll" value="-" timestamp="1617304404692551000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxOGLpackspu.dll" value="-" timestamp="1617304404692096000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxOGLpassthroughspu.dll" value="-" timestamp="1617304404692328000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxSF.sys" value="5.2.44r139111" timestamp="1617304405669056000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxService.exe" value="5.2.44r139111" timestamp="1617304402494489000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxTray.exe" value="5.2.44r139111" timestamp="1617304402492404000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Components/VBoxVideo.sys" value="-" timestamp="1617304405669322000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/HostVerLastChecked" value="5.2.44" timestamp="1617314037628746000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/InstallDir" value="C:/Program Files/Oracle/VirtualBox Guest Additions" timestamp="1617304397454355000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Revision" value="139111" timestamp="1617304397454276000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Version" value="5.2.44" timestamp="1617304397454151000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/VersionExt" value="5.2.44" timestamp="1617304397454212000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestInfo/Net/0/Status" value="Up" timestamp="1617304407346426000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestInfo/Net/Count" value="1" timestamp="1617377033445040000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestInfo/OS/Product" value="Windows 10" timestamp="1617304397453546000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestInfo/OS/Release" value="10.0.19042" timestamp="1617304397453878000" flags=""/>
        <GuestProperty name="/VirtualBox/HostInfo/GUI/LanguageID" value="en_US" timestamp="1617377037549725000" flags=""/>
      </GuestProperties>

and change Display > Screen > Graphics Controller to VBoxSVGA.

I tried in paste also VBoxSVGA without success.

[scottgus1]

I installed Virtualbox 6 using the _official_ PPA of Oracle

The ubuntu fork is still installed:

00:00:00.860475 VirtualBox VM 6.1.16_Ubuntu r140961 linux.amd64 (Apr 29 2021 15:42:15) release log

Try that install again, and don't forget the prerequisites.

*******************************

Guest Additions are installed

Not by fth0's recomendation:

00:00:11.349779 VMMDev: Guest Additions information report: Version 5.2.44 r139111 '5.2.44'

*******************************

I tried in paste also VBoxSVGA without success.

What does "in paste" mean?

After these changes are made, please post a new log.

[Marco Sulla]

I installed Virtualbox 6 using the _official_ PPA of Oracle

The ubuntu fork is still installed:

00:00:00.860475 VirtualBox VM 6.1.16_Ubuntu r140961 linux.amd64 (Apr 29 2021 15:42:15) release log

Try that install again, and don't forget the prerequisites.

You're right. Probably Virtualbox 6.1 is present also in the official repo of Ubuntu 20.04. If with "prerequisite" you mean ext pack, I installed it.

Guest Additions are installed

Not by fth0's recomendation:

00:00:11.349779 VMMDev: Guest Additions information report: Version 5.2.44 r139111 '5.2.44'

This answer is cryptic... anyway, GA are irrelevant, since the slowdown is noticeable from the boot, before GA are loaded by the guest OS.

I tried in paste also VBoxSVGA without success.

What does "in paste" mean?

You continue to break the Netiquette: is considered a bad behavior to remark the grammatical errors. It's clear from the context that this is a typo and I mean "in past"
Anyway I activated VBoxSVGA.

After these changes are made, please post a new log.

All changes done, log attached, slowdown continues....

[mpack]

It's clear from the context that this is a typo and I mean "in past"

That certainly was not clear to me. And I would guess the same goes for Scott since he asked for clarification.

I'd appreciate more technical discussion, less discussion about your perceived slights please (very slight slights). At least half of this topic is a waste of bandwidth.

[Marco Sulla]

I'd appreciate more technical discussion, less discussion about your perceived slights please (very slight slights). At least half of this topic is a waste of bandwidth.

I completely agree. Have you a solution to my problem, please?

[scottgus1]

Marco, Mpack is correct, I did not understand what "in paste" meant. I was legitimately asking for an explanation. None of what I said was intended to insult you, and you're too sensitive. Bring up another supposed 'slight', and this topic gets locked.

"don't forget the prerequisites" means the link I posted earlier on the subject of prerequisites for Linux installation for Virtualbox.

GA are irrelevant, since the slowdown is noticeable from the boot

GAs will help the VM run better, by providing better drivers for some Virtualbox hardware. Showing the version actually installed in the log indicates you hadn't updated the GAs yet.

The new log still shows 5.2.44 GAs.

Both this new log and the 5.2.44 log with one processor from the beginning show the VM being reset after the first boot, then booting again and loading well. The 5.2.44 log shows boot-to-GAs-startup-report of 4 seconds for the 5.2.44 and 6 seconds for the 6.1.22. From boot to what I think is turning on the desktop screen, 23 seconds for 5.2.44 and 32 seconds for 6.1.22. Based on these two logs the VM seems to slow down 25-30-ish percent.

However, the 6.1.16_Ubuntu log with one processor, though showing 4 seconds from boot to GAs report, shows 55 seconds from boot to desktop turn-on. In comparison, majorly slow despite one processor.

Regrettably I'm not certain why. Most folks report better running with two processors. Makes me wonder if maybe the host OS has a glitch.

How long has your host OS been running? Has it been updated a lot or is it a brand-new install on a clean empty disk?

If the host OS has been around a while, please try switching disks in the host and installing the host OS fresh, then installing prerequisites and official Virtualbox, then try the two-processor VM again.

Another possibility: Get the correct bundled GAs installed, then enable 3D acceleration in the VM's Display settings. Windows 10 has a lot of video to process. (If you do enable 3D then see a transparent Start menu, disable Settings > Personalization > Colors > Transparency Effects in your Windows 10 VM.)