Windows guest freezes when working with RS232 / USB to RS232

[ivan84]

Hello,
After upgrading VirtualBox to version 6.0.6, the emulated windows freezes when working with a peripheral port attached to a serial port or usb (using USB VCP).

This is information about the host:

Code: Select all

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 19.04
Release:        19.04
Codename:       disco

ls -l /dev/ttyS*
crw-rw---- 1 root dialout 4, 64 май  7 13:14 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 май  7 13:14 /dev/ttyS1
crw-rw---- 1 root dialout 4, 74 май  7 13:14 /dev/ttyS10
crw-rw---- 1 root dialout 4, 75 май  7 13:14 /dev/ttyS11
crw-rw---- 1 root dialout 4, 76 май  7 13:14 /dev/ttyS12
crw-rw---- 1 root dialout 4, 77 май  7 13:14 /dev/ttyS13
crw-rw---- 1 root dialout 4, 78 май  7 13:14 /dev/ttyS14
crw-rw---- 1 root dialout 4, 79 май  7 13:14 /dev/ttyS15
crw-rw---- 1 root dialout 4, 80 май  7 13:14 /dev/ttyS16
crw-rw---- 1 root dialout 4, 81 май  7 13:14 /dev/ttyS17
crw-rw---- 1 root dialout 4, 82 май  7 13:14 /dev/ttyS18
crw-rw---- 1 root dialout 4, 83 май  7 13:14 /dev/ttyS19
crw-rw---- 1 root dialout 4, 66 май  7 13:14 /dev/ttyS2
crw-rw---- 1 root dialout 4, 84 май  7 13:14 /dev/ttyS20
crw-rw---- 1 root dialout 4, 85 май  7 13:14 /dev/ttyS21
crw-rw---- 1 root dialout 4, 86 май  7 13:14 /dev/ttyS22
crw-rw---- 1 root dialout 4, 87 май  7 13:14 /dev/ttyS23
crw-rw---- 1 root dialout 4, 88 май  7 13:14 /dev/ttyS24
crw-rw---- 1 root dialout 4, 89 май  7 13:14 /dev/ttyS25
crw-rw---- 1 root dialout 4, 90 май  7 13:14 /dev/ttyS26
crw-rw---- 1 root dialout 4, 91 май  7 13:14 /dev/ttyS27
crw-rw---- 1 root dialout 4, 92 май  7 13:14 /dev/ttyS28
crw-rw---- 1 root dialout 4, 93 май  7 13:14 /dev/ttyS29
crw-rw---- 1 root dialout 4, 67 май  7 13:14 /dev/ttyS3
crw-rw---- 1 root dialout 4, 94 май  7 13:14 /dev/ttyS30
crw-rw---- 1 root dialout 4, 95 май  7 13:14 /dev/ttyS31
crw-rw---- 1 root dialout 4, 68 май  9 15:21 /dev/ttyS4
crw-rw---- 1 root dialout 4, 69 май  9 15:47 /dev/ttyS5
crw-rw---- 1 root dialout 4, 70 май  7 13:14 /dev/ttyS6
crw-rw---- 1 root dialout 4, 71 май  7 13:14 /dev/ttyS7
crw-rw---- 1 root dialout 4, 72 май  7 13:14 /dev/ttyS8
crw-rw---- 1 root dialout 4, 73 май  7 13:14 /dev/ttyS9

$ id
uid=1000(office) gid=1000(office) groups=1000(office),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),115(lpadmin),130(sambashare),131(vboxusers),137(libvirtd),142(docker)

[mpack]

00:00:01.296427 VirtualBox VM 6.0.6_Ubuntu r129722 linux.amd64 (Apr 16 2019 22:08:12) release log

That isn't VirtualBox. That's a fork.

[ivan84]

Well,
I changed the version with the last uploaded to the official site (6.0.6 r130049 linux.amd64) and the windows frozen as soon as I turned on the device.

I then installed version 5.2.28 r130011 linux.amd64, installed extension 5.2.28 and replayed the test. This time everything works well. I turned the device on and off several times, but the problem did not occur.

I apply the log files from both versions if they can be useful for diagnosing and fixing the problem.

[mpack]

VirtualBox VM 5.2.28 r130011 linux.amd64 (Apr 12 2019 14:51:18) release log
...
00:00:11.259556 VMMDev: Guest Additions information report: Version 6.0.6 r130049 '6.0.6'

It probably isn't relevant, but have GAs that are more recent than the host software version is a BIG no-no. Especially v6 GAs which might be looking for a completely different graphics chipset.

Also in this VM it looks like you're using software rendered host OpenGL. ISTM you might as well disable 3D acceleration and let the guest do its own software rendering.