Custom Query (16363 matches)
Results (2152 - 2154 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19069 | invalid | Progress bar is visable even if VB started in headless mode. | ||
| Description |
Progress bar is visable even if VB started in headless mode. |
|||
| #8528 | fixed | COM error - Unkown exception - E_FAIL (0x80004005) - problem launching Virtualbox on a Windows 7 Host | ||
| Description |
Hi, I used Virtualbox 3.2.12 for a while and all was fine. I then upgraded to 4.0.4 and found that it would not work with some VHD images that I ported over from Virtual PC. The symptom was a non boot and a black screen. Other threads have indicated that there are some problems with VHD images and 4.0.4. I therefore decided to revert back to 3.2.12 until the issues are sorted and that's when my troubles began. Every time I try to launch Virtualbox I now get an error: Failed to create the virtualbox COM object. The application will now terminate Unkown exception d:\tinderbox\win-4.0\src\vbox\main\src-server\virtualboximpl.cpp[518] (virtualbox::init) Result Code: E_FAIL (0x80004005) Component: VirtualBox Interface: IVirtualBox {d2de270c-1d4b-4c9e-843f-bbb9b47269ff} Okay I thought - a problem with going back to an old release. So I thought I would go "back to the future" to 4.0.4 and use a conversion tool to convert the VHD's to VDI's. Problem is that I am still getting the error above. I tried deleting the files in .virtualbox under my profile (xml and prev files) but this does not help in either release. I also was careful to reboot after each install / uninstall. |
|||
| #8532 | fixed | problem in 4.0.4 with VHD image - image will not boot => Fixed in SVN | ||
| Description |
I was on 3.2.12 and happlily running a VM with W2K3 which was originally created as a VHD with Virtual PC for Windows7. All was good. I then upgraded to 4.0.4 and now when I try to start the VM I just get a black screen. I do not get any disk activity at all. I tried all of the usual tweaking of the settings just in case 4.0.4 had a default setting that was different to 3.2.12 but nothing worked. I then used CloneVDI to migrate the VHD file to a VDI file. Set all of the settings back to the way they were before I upgraded (i.e. virtualization, CPU's, IO APIC etc) and it booted first time - no problem. Just to be sure I detached the VDI and reattached the VHD and got the black screen again with no activity whatsoever on the disk. I think there is an issue with the upgrade to 4.0.4 or a compatability issue with VHD that is not there in 3.x. Something gets screwed when its a VHD of a certain type. |
|||

