Custom Query (16363 matches)
Results (1450 - 1452 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1482 | invalid | Trying VirtualBox on Vista trashed latter --> Vista re-install | ||
| Description |
We have a recent system (summary below) and installing Linux wouldn't work, because SATA chip I think. Anyway, that's another thread. So I thought I'd try out VirtualBox which sounds like it could have solved our problem. Installing went smoothly. Creating the VM went fine (except that I thought three hours to prepare the fixed-size, 16G VDI file was very long). Then I donwloaded Fedora-8-Live-i686.iso (Fedora live CD), mounted it to the VM. I also configured a host network interface and attached that to the VM. Otherwise, pretty much everything was default I think. At this point, I clicked on START, expecting the live CD to come up. The VM window opened, and, after a few seconds, a final message appeared in the black text window saying (roughly) that it couldn't boot from the device. Within a second, an Apple process on Vista (~ QT helper) popped up a message complaining about something being broken. Then I clicked to close the VM window, and got a BSoD. The BSoD said: STOP 0x0000007E (0xC0000005, 0x80D66EE3, 0x88B67858, 0x88B67554). It referred to bowser.sys. It then said something about initializing the disk and dumping memory to that. After power cycling (my only option), Vista wouldn't boot: File \windows\system32\winload.exe, Status: 0xc000000f, File missing or corrupt. Repair attempts failed (perhaps I missed something), so I ended up having to re-install everthing :-(. So no VirtualBox logs of course. I doubt I'll try VirtualBox again, but maybe above can help future users. Two final notes: it could very well be Vista itself that auto-destructed on the BSoD (the message about initializing the disk sounds scary!). Question: could the problem with VirtualBox be related to Vista SP1 (a very recent install on my Vista)? Your notes don't mention Vista SPs. A bit disappointed, Pierre The system in a few lines:
|
|||
| #1483 | fixed | Keyboard, mouse and VT-x/AMD-V issues on VirtualBox 1.6 (Ubuntu 8.04) -> fixed in 1.6.2 | ||
| Description |
My computer configuration is as the following : Athlon 64x2 4200+ with nForce 570 Ultra chipset 3072 MB RAM GeForce 8500GT display card Operating System (host) : Ubuntu 8.04 Guest : Ubuntu 8.04 Live CD The VirtualBox 1.6 does not work when Compiz Fusion is enabled. When Compiz Fusion is disabled, the keyboard cannot be captured. Meanwhile, the VT-x/AMD-V is enabled, the Virtualbox does not work. Furthermore, the mouse pointer cannot be toggled by issuing Right-Ctrl. Samiux |
|||
| #1484 | fixed | VirtualBox 1.6 cant start VM (Solaris10 Update4 VERR_FILE_NOT_FOUND) | ||
| Description |
When startinga VM via VirtualBox or VBoxHeadless i get
Machine/Solaris10u4 is amd64 - 64bit ldd for VBoxDD.so shows a problem with LIBDLPI.SO - which only exists as 32-bit library. I tried to follow a hit in the forum, to dowload a newer SUNWclsr and put libdlpi.so and libdladm.so beneath VirtualBox via setting LD_LIBRARY_PATH. It solved the "ldd VBoxDD.so" error output ( libdlpi.so.1 -> not found ) but still i get this "unable to load ..." error. What is missing? Do i need to upgrade to Sol10update5? |
|||

