| 2 | | Ubuntu 20.4.4 host, Win8.1 64 Pro guest. After starting the VM, it needs quite some time until all drives attached to the VM are connected (Windows shows network drives not available). Drives are SSD's, HD's with ext4 and ntfs, sbm network NAS with four samba shares. This is resolved after about 10 secs, all drives are accessible. Only then, the second monitor can be toggled to the correct resolution by minimising and maximising the VBox guest window on the secon monitor. |
| 3 | | The virtual network card (NAT) is up and running. When starting a software with substantial IP traffic (i.e. access to a network scanner from Adobe Acrobat 11, or to an Access data base file on the NAS), the network interface in Windows display a warning sign as being restricted, IP traffic is stopped and the application hangs. |
| | 2 | Ubuntu 20.4.4 host, Win8.1 64 Pro guest. After starting the VM, it needs quite some time until all drives attached to the VM are connected (Windows shows network drives not available). Drives are SSD's, HD's with ext4 and ntfs, sbm network NAS with four samba shares. This is resolved after about 10 secs, all drives are accessible. Only then, the second monitor can be toggled to the correct resolution by minimising and maximising the VBox guest window on the second monitor. |
| | 3 | |
| | 4 | The virtual network card (NAT) is up and running. When starting a software with substantial IP traffic (i.e. access to a network scanner from Adobe Acrobat 11, or to an Access data base file on the NAS), the network interface in Windows after a few seconds displays a warning sign as being restricted, IP traffic is stopped and the application hangs. This happens in the midst of ongoing heavy IP traffic from that application. |
| 6 | | Problem is that often the Win program generating the IP traffic is hanging and completely blocking the VM (even AtlCtrlDel via VBox menue does not work) , so restart of the guest is unavailable. |
| 7 | | This blocking network happens quite reliable at the beginning of every new VM session (95% of all new sessions). Problem appeared before two weeks (probably related to update to 20.04.1 or Windows KB's - only security updates for the Win virus scanner and the Office package are installed, no rollups since they more than once shredded the installed Windows version). In a VB this is no big deal with vdi backups (including the backup points!), but on real hardware, it always had been a pain in the ass (permanent cycles of installing and restoring pre-installation status blocking the pc). |
| | 7 | Problem is that often the Win program generating the IP traffic is hanging and completely blocking the VM (even AltCtrlDel/Taskmanager via VBox menue does not work), so restart of the guest is unavoidable. |
| | 8 | This blocking network happens quite reliable at the beginning of every new VM session (95% of all new sessions). Problem appeared before two weeks (probably related to update to 20.04.1 or Windows KB's - only security updates for the Win virus scanner and the Office package are installed, no monthly rollups since they more than once shredded the installed Windows version). In a VB this is no big deal with vdi backups (including the backup points!), but on real hardware, it always had been a pain in the ass (permanent cycles of installing and restoring pre-installation status completely blocking the pc). Windows sucks. |
