virtualbox.org

Hello,

It's good that I can install windows 10 without upgrading now if you have windows 7 product key. So I installed windows 10 64bit as a guest on virtualbox 5.0.10 (the host is windows 10 64bit, too).
It works fine with no problem except it's relatively slow compare to windows 7 32bit guest.
I just hope that someone could give me any advise to increase windows 10 64bit guest's speed.

Thanks,
tono777

With the VM fully shut down, right click its icon in the VirtualBox Manager, select "Show Log" and save "VBox.log" to a zip file. Attach the zip here.

Same here. Also the 32 bit version Works a Little faster than the 64 bit. I had to disable the sound and the vBox additions and usb Support in order to get a Little more speed, but it’s lag is noticeable.

melinerunen wrote:Same here. Also the 32 bit version Works a Little faster than the 64 bit. I had to disable the sound and the vBox additions and usb Support in order to get a Little more speed, but it’s lag is noticeable.

Your CPU has 2 cores/4 Threads. You have both cores assigned to the guest. Try reducing it to 1.

Also, you are running a test build. You should use the matching extension pack.
https://www.virtualbox.org/download/tes ... ox-extpack

FWIW, I think in general test builds run slightly slower than the release builds. I always assumed it was because they contain debugging code. I coulld be wrong about that however.

loukingjr wrote:I think in general test builds run slightly slower than the release builds.

Any evidence to support that? From my understanding they contain unreleased patches and/or testcase code, not debugging code.

nope. strictly observational. as I said I just assumed they were slower because of debugging code. It may have been just the Beta versions. I don't run test builds very often anymore.

For this case is the same performance between the stable .10 and the test build .11 is the same. Going back to the stable, with 1 processor, enabled sound and usb back. Also enabled EFI support. Same performance. New log file

I only have one host with a 2core/4thread CPU running a Windows 10 guest. But, I have to say, Windows 10 does a number of things in the background which a user can't disable which probably accounts for some of the slowness. Of course slow is relative.

Any new Windows installation will be slow, until Windows has finished all the update checking and disk indexing that it wants to do. Instead of speculating on the cause of slowness it's usually easy to pop open the task list and know for sure. Look for somebody using either excessive I/O or CPU.

another user noticed disk activity will spike to 100% at times. I saw the same thing. I assume it is update checking which can't be turned off, Windows 10 calling home periodically which isn't easily turned off, and in general it is a work in progress anyway. All the broken cumulative updates Microsoft has released for it can't be helping. All in all though, it doesn't seem overly slow on any of my hosts.

mpack wrote:Any new Windows installation will be slow, until Windows has finished all the update checking and disk indexing that it wants to do. Instead of speculating on the cause of slowness it's usually easy to pop open the task list and know for sure. Look for somebody using either excessive I/O or CPU.

I installed windows in the VM like two months ago. So this is not the problem. The slowness comes by processing and not reading disk or excessive CPU usage. A good example is writing something or viewing a youtube video. The speed is not compared to Windows Vista or 7 (yes i used to use Vista as a VM )

I installed Windows 10 insider preview in May. It's now updated to 1511 10586.29 and it's still slow sometimes. I don't think it has anything to do with VirtualBox.

loukingjr wrote:FWIW, I think in general test builds run slightly slower than the release builds. I always assumed it was because they contain debugging code. I coulld be wrong about that however.

Indeed you are. Sometimes there is instrumentation in specific parts of code but in general the builds are not different from official releases. So if you see test builds consistently run slower, you're most likely imagining things. Actual debug builds are entirely different -- definitely slower but unless you build it yourself, you won't get one.

As I mentioned, it may have just have been the Beta 5.0 builds. Or maybe my metabolism was running fast.

But I believe you.