Custom Query (16363 matches)
Results (1189 - 1191 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #6906 | fixed | Cannot restart saved guests after change Windows 7 Display Language from English to Simplified Chinese | ||
| Description |
Host Machine: Windows 7 Ultimate AMD64 Reason: The Network Interface name is changed after Display Language changed. (NIC_name_changed.png) Affects: Then the guest OS which has a network bridged to it will suffer to recognize the original interface. Sugguestion: Why not use device unique id or something else to recognized the network interface, other than its name. Steps to reproduce the bug: 1) Initially Windows has English Display 2) Start a guest OS and saved it 3) Change "Display Language" in control panel to Simplified Chinese, restart host, and login 4) Start the guest OS saved in step 2) 5) Failed to start the guest (failed_to_start_guest.png) |
|||
| #11425 | duplicate | VirtualBox 4.2.6 crashes on OS X host when host OS wakes up from sleep | ||
| Description |
Since I upgraded to 4.2.6, VirtualBox regularly (but not always) crashes when the host OS wakes up from sleep. This was also reported on the forum (Random crashes - WinXP 32bit guest since 4.2.6). Host OS: OS X 10.8.2 Guest OS: Linux 2.6.38 (Fedora 14, 64 bit) Guest additions v4.2.6 installed Signature of the crash: Crashed Thread: 4 TIMER Exception Type: EXC_ARITHMETIC (SIGFPE) Exception Codes: EXC_I386_DIV (divide by zero) Thread 4 Crashed:: TIMER 0 VBoxC.dylib 0x000000010d89a82b 0x10d800000 + 632875 1 VBoxRT.dylib 0x00000001002728aa RTTimerLRDestroy + 442 2 VBoxRT.dylib 0x000000010023fdaf RTThreadCreateF + 271 3 VBoxRT.dylib 0x000000010029219c RTThreadPoke + 540 4 libsystem_c.dylib 0x00007fff87fde742 _pthread_start + 327 5 libsystem_c.dylib 0x00007fff87fcb181 thread_start + 13 |
|||
| #11438 | obsolete | VirtualBox crashes when using kexec in a VM with more than 1 core | ||
| Description |
Running VB 4.2.6 Host OS: OS X 10.8.2 on an i7-3615QM Guest OS: Linux 2.6.38 (Fedora 14, 64 bit) Guest additions v4.2.6 installed I have a slightly unconventional setup in which I first boot on a .iso that contains a boot loader that then kexec's into the real kernel stored on the virtual disk. This works fine, except if I give the VM more than 1 core (e.g. if I give it 2 cores or 4 cores), in which case the VM crashes. I'm not 100% sure yet, but it appears to be right at the time where I kexec the new kernel that the crash occurs. |
|||

