Custom Query (16363 matches)
Results (1111 - 1113 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #720 | fixed | Failed assertion in current svn | ||
| Description |
The following Assert failure happens in current svn VMMR0.r0 is importing SUPR0LowFree which we couldn't find !!Assertion Failed!! Expression: <NULL> Location : /u/user/Build/vbox/src/VBox/HostDrivers/Support/SUPLib.cpp(1377) int supLoadModuleResolveImport(RTLDRMODINTERNAL*, const char*, const char*, unsigned int, RTUINTPTR*, void*) VMMR0.r0 is importing SUPR0LowFree which we couldn't find The full logfile is attached |
|||
| #752 | invalid | VDI not accessible after crash of Virtualbox | ||
| Description |
As s side effect of some crashes of VirtualBox I noticed the following behaviour: When starting VirtualBox after a crash, the message that "One or more of the virtual hard discs are not accessible ..." appears and opening the VDI manager is offered. I have not found a way to correct this (unregister/register, ...) but when I press Ignore, the vm starts anyway. I assume this is some locking but I have not found where the locking is stored and how to remove it |
|||
| #800 | worksforme | Network regression (Linux host, W2003 Server guest) | ||
| Description |
When upgrading from 1.5.0 to 1.5.2, networking no longer works in our configuration. Going back to 1.5.0 solved the problem. The guest (Windows 2003 server) was not able to send packets, it seemed it was able to receive packets. |
|||

