Custom Query (16363 matches)
Results (1672 - 1674 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16960 | fixed | VirtualBox 5.1.26 crashes when using VLAN in linux guest over Internal Network => Fixed in 5.1.28 | ||
| Description |
VirtualBox 5.1.26 crashes when using VLAN in linux guest over Internal Network. After 5-10 mins launching VM guest in Host console I hane an error: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [EMT-0:19382] The same bug was in 5.1.24 version and it there are only when using VLAN in guest VM via Internal Network in Host. Portion of logs attached (log in Host) |
|||
| #16959 | fixed | fatal error since 5.26: instruction 0x3f526d32 uses memory that can not be read | ||
| Description |
Host: win 8.1 64 bit; guest: Debian 8 The VM in question used to work until yesterday, with VBox up to 5.24. Today I updated to 5.26 and at VM boot I get the error as per the attached image. On the same host, another Debian 8 VM works fine. |
|||
| #16957 | obsolete | VBox Hypervisor Crash if Windows Server 2012 R2 has WiFi USB2.0 device driver installed but not wlanapi.dll | ||
| Description |
Okay, this one's a tricky one. I am not 100% confident that these are the trigger conditions, but here goes:
Steps:
The key triggers here seem to be:
I ran into this a few days ago trying to hijack the old Nintendo WFC adapter into working as a soft AP and went through the usual rounds of disabling the Windows Driver Verifier, so when I saw that 5.1.24 had been released, the fix from Bug #15741 sounded eerily familiar. But, I was still able to crash the hypervisor hard, even in 5.1.24. I upgraded to 5.1.26, but haven't tried crashing it there yet. I also discovered that choosing the USB 1.0 filter driver defeats the crash, because the Wifi dongle I tested (Realtek RT8811AU 802.1ac) can't do USB 1.0. I then tried USB 3.0, which does not crash the hypervisor, so I was able to try and run the Realtek wireless program, which then complained about a missing "wlanapi.dll" file. That's how I discovered that I was missing the "Wireless LAN service" feature. This suggests the bug is possibly in the USB 2.0 filter driver included in the extensions pack. However, because it crashes the hypervisor pretty hard, I selected "VMM" as the component, because I think that's the hypervisor core? Feel free to change to whatever is appropriate. I looked through the logs and all, but nothing gets left behind, hence why I am calling it a hard crash. I could *maybe* get a crash dump, as I do have the Windows Debugger kit loaded, but I don't know if the debug symbols for the VBox components are available anywhere (not that I've looked real hard). |
|||

