virtualbox.org

Hi,
I have VBox running on my laptop and it's been great, but the last week or so it has started acting strangely. I've had issues installing Ubuntu on new VMs (the installer has crashed), the VBox interface freezes, errors loading old VMs.

I did some testing with some new VMs, all fixed size vdi disks, 100MB, 1GB and 10GB - no CD image, just getting to the no bootable medium found screen.
Pressing the close button for each (to bring up the Close virtual machine menu) VBox freezes, but the time depends on the size of the disk image.
100MB, about 2 seconds.
1GB about 12 seconds.
10GB about 2 minutes.

This was from the 1GB test:
PDMR3Suspend: Driver 'VD'/0 on LUN#0 of device 'ahci'/0 took 8 697 886 408 ns to suspend

The Windows task manager shows disk access for VBox when I click the close button (shows around 100MB/s). I've tried the latest 6.1.14 and an older 6.06 and the same happens.

Any ideas what is going on here?

System Info
Dell Precision 5530
Windows 10 Enterprise 1809
Hyper-V is disabled

ChrisHigs wrote:Any ideas what is going on here?

No, at least not yet. There's another current thread about the same behavior (and several unrelated behaviors), and the investigation is still ongoing: Powering down Linux guest taking a long time.

One important question from my point of view is, which process accesses which file on the host's file system. Your tests seem to imply that the virtual hard disk image is the file being accessed. To investigate more about the disk accesses inside the Windows host OS, you could use Sysinternals DiskMon or Process Monitor.

Another idea: If you've been using the VirtualBox Manager for starting the VMs so far, please close the VirtualBox Manager, wait for at least 10 seconds, and start the VMs from the command line. Does the behavior still exist?

Please provide a zip file containing the .vbox files and the VBox.log files for the 1 GB and 10 GB test VMs.

I'm not sure what has changed but suddenly this seems to be working again.

The only difference is that I went back to 6.1.14 after trying 6.06, even though I had tried uninstalling and reinstalling 6.1 previously.

If I get problems again I will post some logs here. Cheers