Opened 5 years ago
Last modified 5 years ago
#18973 new defect
BSOD (crash) on Windows 10 host with console Linux guest in network driver
| Reported by: | MaaSoftware | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 6.0.12 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
Bug previously opened as #18854 (BSOD on Windows 10 host with console CentOS 7 Linux guest in network driver) is still exist in VirtualBox 6.0.12. It is releated to active network I/O operations on Windows 10 x64 host with Linix guests (CentOS 7 or Debian 10 x64, for example). I have reproduce it again when I have created and installed Debian 10 guest and have executed the command cd /opt && mkdir -p ttt && wget -O - --user UserName --password Password ftp://192.168.0.28/full_backup_29.09.2019 | restore -x -a -T /opt/ttt -f /dev/stdin where: 192.168.0.28 is IP address of Windows 10 host 192.168.0.91 is IP address of Debian 10 guest 192.168.0.0/24 is a 1 Gbps network on "Intel(R) Ethernet Connection (2) I219-V" NIC adapter.
Change History (4)
comment:2 by , 5 years ago
Replying to MmaaSoftware:
Bug previously opened as #18854 (BSOD on Windows 10 host with console CentOS 7 Linux guest in network driver) is still exist in VirtualBox 6.0.12.
Then can I ask why you created a new ticket? And why this ticket shouldn't be closed as a [Duplicate] of #18854? If you opened this one, just because it's dealing with a newer VirtualBox version, please don't. If new tickets were opened for every version, then there would be a flood of tickets... ;)
comment:3 by , 5 years ago
Bug #18854 can't be modified to set it is Windows host related because of limit of bug tracking system. And it have no comments still. So some clarification was made here.
comment:4 by , 5 years ago
I hear you... once that "Submit" button has been pressed, there's no editing of the ticket itself. You can modify/edit/change your comments, but not the initial report.
Here's what I would do:
- Post a comment asking for an admin to make the corrections to that initial report.
- Post the additional details on #18854, since it's my strong belief that this ticket will be closed as a duplicate really soon.
- Wait for a reply... there have been tickets that haven't had an answer for months and months, opening a new ticket won't improve the situation.
