Custom Query (16363 matches)
Results (1552 - 1554 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2758 | fixed | VirtualBox Failed to update VM configs | ||
| Description |
After upgrade to 2.1, all my VM with a configuration similar to the bellow failed
The error was: Assertion failed: [!name.isNull()] at '/home/vbox/vbox-2.1.0/src/VBox/Main/NetworkAdapterImpl.cpp' (1068) in nsresult NetworkAdapter::loadSettings(const settings::Key&). Please contact the product vendor!. Código de Resultado: NS_ERROR_FAILURE (0x80004005) Componente: NetworkAdapter Interface: INetworkAdapter {a876d9b1-68d9-43b1-9c68-ddea0a473663} |
|||
| #2761 | fixed | FreeBSD 7.0 crashes during boot (Assertion Failed / Expression: <NULL> / VBoxRecompiler.c(4325) cpu_abort) -> Fixed in SVN | ||
| Description |
Trying to boot FreeBSD 7.0 under VBox 2.1.0 Host Windows Vista 32 Bit Intel Core 2 Duo 00:00:21.238 !!Assertion Failed!!
00:00:21.238 Expression: <NULL>
00:00:21.238 Location : C:/vbox/32/w32-rel/src/recompiler_new/VBoxRecompiler.c(4325) cpu_abort
00:00:21.238 fatal error in recompiler cpu: Trying to execute code with memory type
addr_code=0000000028052020 addend=00000000d7fae000 at 0000000028052c56.
(iHandlerMemType=0x40 iMMIOMemType=0x38)
With and Without VT-X I get the following error during the boot process. It happens very shortly after kernel loading/hardware detecting (The part where the kernel lsits all the devices found) It happens at a slightly different location each time (sometimes it would output that all disks where "clean" (check-disk) , sometimes it goes down before. I happens independent off the selected network adapter, and even if all networking is disabled. Sound is disabled, cd is disabled. Only one disk is enabled, and configured as primary master. (other disks where enabled before, but it made no diff) PIIX3 or PIIX4 => no difference I could not test SATA, that seems to fail at an earlier stage. |
|||
| #2763 | fixed | Vista (32 bit) host with ATI x1250 -> Linux guest -> BSOD / fixed in SVN/2.1.4 | ||
| Description |
Bug since (at least) version 1.6.0: Following combination leads to a BSOD:
Starting the virtual machine leads to a BSOD (host) after selecting something in linux (guest) bootmanager. Windows Eventmanager tells me something about a crash of the display driver (in german it says: Anzeigetreiber atikmdag reagiert nicht mehr und wurde erfolgreich wieder hergestellt., in english it's something like Display driver atikmdag stopped responding and was successfully recovered. Display driver and bios of laptop is up-to-date. A workaround is to enable AMD-V, guest will run normally then. BSOD will only appear with disabled AMD-V (which is the default setting after installation). |
|||

