Custom Query (16363 matches)
Results (2248 - 2250 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #13330 | obsolete | Corruption with 4.3.14 under OSX host and .vdi disk | ||
| Description |
I have a few Linux VMs running under VirtualBox on OSX 10.8.5 that are showing random corruption/behavior since upgrading to 4.3.14. This corruption/behavior seems to happen only if the virtual disk format is ".vdi" (cannot reproduce if the disk format is ".vmdk"). Some examples of what I'm seeing on a CentOS 6.x 64bit VM:
Uninstalling 4.3.14 and reinstalling 4.3.12 makes all these go away. I also have another 64bit VM with Debian 7.x where weird things like I/O errors causing filesystems to remount read-only can also be seen. Why I believe this only affects ".vdi" disks: I have another OSX 10.9.5 machine with VirtualBox 4.3.14 where I wasn't seeing any strange behavior. So I exported the previously mentioned CentOS VM and imported it there, but still no strange behavior. Then I noticed that all my VMs there have ".vmdk" disks (they were all exported from another machine). I copied the ".vdi" for the CentOS VM and booted it there and... the weird behaviors start happening. |
|||
| #11255 | duplicate | Could not able to allocate and lock memory | ||
| Description |
i was trying to install oracle 64-bit os in my virtual box when i reached a stage where partioning has to be done and i clicked "Write changes to disk" and a window popped up saying "Could not able to allocate and lock memory". Can you help me with this. Thanks in advance. |
|||
| #7449 | invalid | Could not create the HDD | ||
| Description |
1) Install VB in the first time
|
|||

