Custom Query (16363 matches)
Results (619 - 621 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12000 | duplicate | Previously Working VM Will Not Start | ||
| Description |
This message pops up when I attempt to run a virtual machine that has previously worked: "Failed to load VMMR0.r0 (VERR_LDR_MISMATCH_NATIVE)" I have searched in the forums on this website for a solution, but no one seems to know what causes this error or how to fix it. |
|||
| #10422 | fixed | Enabling gnome-shell crashes virtual machine | ||
| Description |
Running VirtualBox 4.1.12 on Windows XP (host) and Debian Wheezy (guest). Despite 3D support is enabled in VM and session seems to be accelerated, GNOME automatically loads the fallback mode. I'm attaching 2 files:
If I manually force the load of gnome-shell ("gnome-shell --replace"), gnome-shell is loaded but as soon as I click over the top bar, the VM crashes affecting "atioglxx.dll". I'm attaching 2 files:
|
|||
| #14234 | duplicate | inotify does not work on Mac OS X with Ubuntu hosts | ||
| Description |
In the latest years there have been a lot of projects that have become popular among the develop community that leverage VirtualBox as development system. Vagrant and docker-machine are just some notable examples. It is very common that people use a shared folder to share their source code on Mac OS X with the virtual machine and use the virtual machine to run a production-like environment . There are a few tools that listen for changes on the file system to immediately run rebuilding scripts or restart a server (ex: nodemon, pm2 or gulp in node.js) that rely on inotify. But inotify is not implemented on shared folders. Work arounds have led to active polling all files in the project and all its subfolders that increase CPU consumption to unacceptable level. Implementing inotify on shared folders on Mac OS X for ext3 and ext4 guests will fix most of the problems. One example of bug: https://github.com/remy/nodemon/issues/419 |
|||

