Changes between Version 5 and Version 6 of Ticket #19738, comment 2

Ticket #19738, comment 2

v5	v6
4	4	The storage controller "VIRTIO", which I had used to attach some VMDK disks, was responsible. The idea behind using them was that complete hardware emulation of a SATA-AHCI interface was not required, and that cutting out the unnecessary emulation would allow for more efficiency via the virtualization aware block level VIRTIO drivers in the guest operating system.
5	5
6		Troubleshooting: I added a SATA-AHCI controller, moved the ~~Virtual disk over, and deleted the VIRTIO Storage controller. The I attempted the hide-in-background/show exercise and confirmed that virtualbox did not crash. This confirms~~ that that the component causing the crash was the VIRTIO storage controller.
	6	Troubleshooting: I added a SATA-AHCI controller, moved the virtual disks over and deleted the VIRTIO Storage controller. The I attempted the hide-in-background/show exercise and confirmed that virtualbox did not crash. This confirmed that that the component causing the crash was the VIRTIO storage controller.
7	7
8	8	Hence, the "Workaround" to avoid this bug, is, to avoid using VIRTIO Storage controller