Custom Query (16363 matches)
Results (703 - 705 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1197 | fixed | BSOD on Vista host (VT-x init failure -> vmxon #GP -> fixed in SVN) | ||
| Description |
I got a BSOD a few seconds after starting my VM (not after starting VirtualBox). I don't really have any other info besides that. The stop error was all zeroes, and no driver was listed. This usually only happens the first time I try running the VM after a reboot. If I'm successful in starting the VM, then I can usually do whatever for the rest of my Windows session without any problems. Here's 2 minidumps (also attached) - |
|||
| #1198 | fixed | VM fails to start due to erroneous lack of memory | ||
| Description |
I created a VM and tried to boot it after creating a vdi for it and hooking it up to an Ubuntu 7.10 server installation iso. Initially I got an error about failing to load the clipboard sharing stuff, so I disabled that as per aeichner's suggestion on IRC. I then got an error saying this: VBox status code: -8 (VERR_NO_MEMORY). The whole log is at http://pastie.caboo.se/152891 The VM is supposed to claim 256MB, the host machine has 4GB of RAM with about 700MB free right now. This is version 1.5.51 running on Mac OS X 10.5.2. |
|||
| #1200 | fixed | Shared folders: read-only option => Fixed in 1.5.6 | ||
| Description |
Very nice enhancement would be possibility to connect shared folder in read-only mode (like in Vmware). This option could be important when testing "strange OS" while needing to provide data from host but protecting these data from changes. |
|||

