Custom Query (16363 matches)
Results (2428 - 2430 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18506 | invalid | any VMs do not start, Window10 host | ||
| Description |
no one VM do not start with error verr_sup_vp_memory_read_error |
|||
| #18046 | fixed | another VMMR0.r0 BSOD => fixed in svn | ||
| Description |
I noticed it few months (year?) ago, and it's still not fixed. Regardless of Win host system all guests fails sometimes with bridged networking on Realtek 8111F, with BSOD. NAT works correctly. I also have the latest drivers for every aspect in my system (so in this case it is 10.30.815.2018, but it happened with different version of W10, and drivers). Other systems with Intel cards (e.g. I219-V) are not affected. Every time when the guest is performing some network activity the host is crashed with STOP "driver irql not less or equal" error. (log and dump attached). |
|||
| #1466 | fixed | announced backward compatibility link "VBoxVRDP->VBoxHeadless" is wrong in Windows => Fixed in SVN | ||
| Description |
quoted manual: "VirtualBox therefore comes with yet another front-end that produces no visible output on the host at all, but instead only delivers VRDP data. With VirtualBox 1.6, this “headless server” is now aptly called VBoxHeadless. (In previous versions, it was called VBoxVRDP. For the sake of backwards compatibility, the VirtualBox installation still installs an executable with that name as well.)" So the link should be going by the name of "VBoxVRDP", but it is actually "VBoxRDP" with a missing second "V" instead. This brings up some compatibility issues with (e.g.) my contributed project "VBoxVmService" or any secondary software, that would call the deprecated "VBoxVRDP" command... |
|||

