Custom Query (16363 matches)
Results (2284 - 2286 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2212 | fixed | VirtualBox.exe crashes VBoxSvc.exe on startup -> fixed in SVN/2.0.4 | ||
| Description |
After installing v2.0.2 (does not happen with 1.6.2-6, 2.0.0), VirtualBox.exe seems to be crashing VBoxSVC on startup. If I go straight to VirtualBox.exe, I get a Debug Dialog indicating VBoxSVC has had an unhandled exception, and offers to debug (I have VS2008 installed). After saying no to debugging, I am then prompted with a critical error from VirtualBox as it is unable to create a COM Object. Error: "Callee RC: CO_E_SERVER_EXEC_FAILURE (0x80080005)" I am pretty sure that it isn't VBoxSvc crashing on its own as I can manually start VBoxSvc from the command line and it runs stable until VirtualBox or VBoxSDL is started, at which it crashes immediately. I Uninstalled 166, installed 202, and had the crash. I then uninstalled 202 and installed 200, worked just fine. Upgraded (Installed over) back to 202 and its crashing again. Uninstalled 202 and deleted the three left over drivers in Win\System32, then rebooted installed, rebooted and tried and crashed. I was in the chat room earlier trying to troubleshoot the issue and there was another individual with the exact same issue. This makes VBox 2.0.2 completely unusable. TEMPORARY SOLUTION See below. |
|||
| #2213 | fixed | FreeBSD completely broken with hardware virtualization enabled | ||
| Description |
I had FreeBSD 7 somewhat working in 1.6.4, but after moving to 2.0 (and then 2.0.2) it seems to be completely broken. Like, badly--BUT--only when hardware virtualization is enabled. With HV turned off, it seems to run okay (I installed and booted from disk just fine with HV off). Unfortunately I can't run two VMs this way. :( When you boot (after installing with HV off) or try to install, the same thing happens. The screen constantly gets flooded with "BTX halted" messages (too fast for me to read them). I will attach a screenshot and the log file; hopefully one or both will be visible and useful. |
|||
| #2214 | duplicate | Unable to start VMs which boot from a raw partition using the SATA controller | ||
| Description |
Any attempt to start a guest whose boot disk is a raw partition (via vmdk) and which uses the SATA controller fails immediately with the following error:
=================================================================== VBox status code: -2 (VERR_INVALID_PARAMETER).
Result Code: NS_ERROR_FAILURE (0x80004005) Looking in the log, it appears the problem is when the geometry of the disk is read: 00:00:32.354 AHCI: LUN#0: disk, PCHS=1/16/63, total number of sectors 0 The number of cylinders in the above line is supposed to be 16383 in my case. The guest type does not matter. When I switch to the IDE controller, it works fine. If I'm using a vdi and SATA controller, it works fine, too. I'm using Logical Volumes as the "raw" disks so that might be a factor, but this setup was working fine in Virtualbox 1.6.6. I'm attaching the log, and vmdk file for one of the failing guests. |
|||

