The disk usage is nearly 100% when the .vdi file of a VM is stored on a Seagate SSHD

[merced]

I added a Seagate SSHD (Solid State Hybrid Drive, a HDD with a 8GB flash to speedup reading of frequently used files) to my desktop computer a few days ago. After I moved the .vdi file of a Win10 VM to that drive and started the VM, I found the disk usage in Task Manager of the guest OS is nearly 100% and the system response is notably slower than VMs whose .vdi files are stored in an HDD. The disk usage of the SSHD in host OS is extremely high (80% to 95%) too, but I did not run any application at that moment. The same VM (.vdi file) runs very well when it locates both in a HDD and in a SSD. When it runs quite slowly in the seagate SSHD, Task Manager shows that the VirtualBox process occupies most of disk operation times. What is the matter? Hardware config: Core i7 6700K, 16GB DDR4, 1TB HDD+2TB SSHD(Seagate ST2000LX001) Host OS: Windows 10 x64 1709 VirtualBox version: 5.1.30 Guest OS: Windows 10 x86 1709, 3GB memory

[Socratis]

May I also suggest something? It's usually better and faster, if issues like this one (configuration, question) get first addressed in the ​VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

So, if you can, please open a new thread in the ​VirtualBox on Windows Hosts section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number. Please be sure to include a ZIPPED VBox.log:

• Follow a "start the VM from cold-boot" / "observe error" / "shutdown the VM" cycle.

• 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.

• You were supposed to follow these steps when you filed the bug:

  Attach a (full) log file ("Machine" menu/"Show Log" in the main VirtualBox Manager window) straight away to save time for you and for us. The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run. Please do not cut and paste it.

[Socratis]

I just realized that you had already posted the question in the forums: ​https://forums.virtualbox.org/viewtopic.php?f=1&t=85949

As I have mentioned there, VirtualBox doesn't necessarily care about its storage medium, the host OS does. You need to find which process in the guest takes all the CPU and act accordingly.

This doesn't sound like a VirtualBox issue...

[Socratis]

Based on discussion on the forums, this seems to be a background Win10 update, coupled perhaps with the cache algorithms from the SSHD manufacturer.

The ticket could therefore be closed as either "Invalid", or "WorksForMe".

[Valery Ushakov]

Thanks for the investigation!