Any guest crashes with Linux 5.5 as host and VBox > 6.0.0

[Thermi]

Ever since going from VBox 5.x to 6.x, guests are practically unusable because they crash or have other severe problems (corruption of data passed from host to guest, e.g. network data, file data, ...). Log is attached of one of the cases with a Windows 10 Guest.

[Thermi]

Virtualbox log, zipped (Was > 512.0 KB ins size)

[Frank Batschulat (Oracle)]

The log shows a Linux host 5.5.4-arch1-1

CPUM: Matched host CPU INTEL 0x6/0x5e/0x3 Intel_Core7_Skylake with CPU DB entry 'Intel Core i7-6700K' (INTEL 0x6/0x5e/0x3 Intel_Core7_Skylake)

running Virtualbox 6.1.4 r136177 and a guest Windows 10 Pro 6.1.2 GAs crashing with the following error:

00:02:05.334063 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:02:05.336517 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
[...]
00:02:05.824232 xHCI: Hardware reset                                                                                               
00:02:05.824861 VUSB: HidMouse: reset request is ignored, the device is already resetting!                                         
00:02:05.826219 xHCI: USB Operational                                                                                              
00:02:05.834674 xHCI: Root hub-attached device reset completed with VINF_SUCCESS                                                   
00:02:06.041478 AHCI#0: Reset the HBA                                                                                              
00:02:06.041493 VD#0: Cancelling all active requests                                                                               
00:02:06.162312 EFI: VBoxDbg> loadimage64 'bootmgfw.efi' 0x10000000 LB 0x1b8000                                                    
00:02:07.575837 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'                                                          
00:02:07.575859 Console: Machine state changed to 'GuruMeditation'                                                                 
00:02:07.576395 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!                                             
00:02:07.576396 !!                                                                                                                 
00:02:07.576396 !!         VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)                                                      
00:02:07.576402 !!                                                                                                                 
00:02:07.576409 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT                                                 
00:02:07.576429 !!                                                                                                                 
00:02:07.576429 !! {mappings, <NULL>}                                                                                              
00:02:07.576430 !!                                                                                                                 
00:02:07.576459 !!                                                                                                                 
00:02:07.576459 !! {hma, <NULL>}