Custom Query (16363 matches)
Results (2296 - 2298 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10918 | obsolete | Error Starting VM (Win2008) After Upgrade to VB 4.1.22 r80657 | ||
| Description |
Just upgraded to VB 4.1.22 r80657 on my Win 7 x64 Host, and nearly every time I launch my Guest Win 2008 R2 VM, I get a: "VirtualBox - Error" window with: "Failed to open a session for the virtual machine Windows 2008. General Failure - DON'T USE THIS!!!. (VERR_GENERAL_FAILURE)." The Details section is: "Result Code: E_FAIL (0x80004005) Component: Console Interface: Console {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}" |
|||
| #10922 | obsolete | kernel oops, maybe in kmem_cache_alloc | ||
| Description |
VirtualBox caused kernel oops, maybe in kmem_cache_alloc (since that's in EIP) Call Trace: printk panic forget_original_parent exit_nootify do_exit print_oops_end_marker opps_end no_context __bad_area_nosemaphore filemap_fault bad_area_nosemaphore do_page_fault unlock_page do_page_fault error_code getname kmem_cache_alloc getname getname do_sys_open sys_open sysenter_do_call The rest is scrolled off the console and not stored in a log file. See attached screenshot and vbox.log |
|||
| #10925 | obsolete | Importing VM: check ovf sha1 checksum before vmdk's one | ||
| Description |
Having the ovf and vmdk files, when importing the two files and checksum is verified as stated in the .mf file, check first the ovf file because has much less size, and prevents wastes of time in case the ovf has been modified to workaround missconfigurations. |
|||

