Custom Query (16363 matches)
Results (997 - 999 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12388 | obsolete | Linux based Guest Blank Screen after upgrading to Vbox 4.3.2 | ||
| Description |
Dear Support, I used to run a virtual ESXi ver 5.1 lab successfully on virtualbox 4.2.18 without any issue. Since I have upgraded to ver 4.3.2 the ESXi 5.1 failed to complete the start and stops on blank screen. Also trying to install a fresh ESXi 5.1 or 5.5 stops at blank screen after the first loading screen. It appears that there is something that has changed in the latest release possible with the video not sure that got us to lose such great feature of virtualbox which is the ability to nest other hypervisors in it for testing. Please check the bug and fix. Thank you Regards Vant |
|||
| #13193 | duplicate | virtualbox 4.3.14 failed to start multiple .dll errors | ||
| Description |
I have been running ver 4.3.12 without issue. After installing the latest version vbox failed to strat and generated multiple .dll errors. I tried clean installation as well and the same. now I reverted back to 4.3.12. This issue happened on Win 7 x64 home premium edition. i5 CPU, 8 GB RAM thank you |
|||
| #11961 | invalid | Ubuntu host filesystem crash | ||
| Description |
Hi, I have experienced a very big issue in our server several times (actually 3 times). We are using one host Linux with 4 four virtual machines:
We have on the server 32 GB of RAM memory, so the we are closed the maximum. The issue is that the host is freezed and cannot be restarted because the filesystem looks like corrupted (Grub issue that cannot find any boot file). We have tried to restart it with a live cd and almost all of the data have been lost. When we mount the host hard drives to check the data, almost all data are erased on the file system of the host (log files, binary, virtual hard drive ...). Here are some errors that I can see into the live cd log:
We are using Virtual Box 4.2.16 (but the problem appears also with the version 4.1). The host is a Linux Ubuntu 12.04 (but the problem appears also with Ubuntu 10.04) The server is IBM System X3100 M4 2582C2A The issue appears 3 times in one week so we need to know if this issue is linked to virtual box and what can be the problem. It looks like the issue appears everytime we are adding a new VM. Is it an hardware issue (memory ...) or a virtual box issue. Thanks for your help |
|||

