Custom Query (16363 matches)
Results (2419 - 2421 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2349 | duplicate | CPU Core maxed out with Vista 64 host | ||
| Description |
I'm running on Vista 64 and when running either a Vista 32 or XP Guest OS the process VBoxSVC.EXE maxes out one of my cores and makes my host machine too slow to use. My host machine is a 3GHz Dual Core machine with 3 GB of RAM. I give the VMs 1 Gig of RAM and only run one at a time but very soon after running them the host becomes unusable. |
|||
| #2350 | fixed | MoveFile does not report failure when the target exists => Fixed in 2.0.4 | ||
| Description |
As described in MSDN, MoveFile should fail if the target file exists. However, when the files are located in a shared folder, it apparently returns success without actually doing anything. It makes using msysgit with repositories located on shared folders impossible, except in read-only mode.
Steps to reproduce with msysgit: It'll output a bunch of errors, and leave a .../.git/config.lock file: error: could not lock config file E:/Work/test/.git/config error: could not lock config file E:/Work/test/.git/config error: could not lock config file E:/Work/test/.git/config error: could not lock config file E:/Work/test/.git/config Workaround: if I make it ignore the result of rename(), and try MoveFileEx anyway, it works properly: --- a/compat/mingw.c
+++ b/compat/mingw.c
@@ -869,11 +869,12 @@ int mingw_rename(const char *pold, const char *pnew)
* Try native rename() first to get errno right.
* It is based on MoveFile(), which cannot overwrite existing files.
*/
+ int ok = 0;
if (!rename(pold, pnew))
- return 0;
- if (errno != EEXIST)
+ ok++;
+ if (!ok && errno != EEXIST)
return -1;
- if (MoveFileEx(pold, pnew, MOVEFILE_REPLACE_EXISTING))
+ if (MoveFileEx(pold, pnew, MOVEFILE_REPLACE_EXISTING) || ok)
return 0;
/* TODO: translate more errors */
if (GetLastError() == ERROR_ACCESS_DENIED) {
Guest: Windows 2000 & XP, Host: Fedora 9 |
|||
| #2351 | fixed | Solaris install successful even with postinstall failure | ||
| Description |
I tried installing VirtualBox on a Solaris 10 box using the Readme.txt instructions. The following step:
produced the following error messages during the postinstall phase: [...] ## Executing postinstall script. Configuring VirtualBox kernel module... /opt/VirtualBox/vboxdrv.sh: /usr/xpg4/bin/id: not found /opt/VirtualBox/vboxdrv.sh: test: argument expected /opt/VirtualBox/vboxdrv.sh: /usr/xpg4/bin/id: not found /opt/VirtualBox/vboxdrv.sh: test: argument expected Configuring VirtualBox NetFilter kernel module... /opt/VirtualBox/vboxdrv.sh: /usr/xpg4/bin/id: not found /opt/VirtualBox/vboxdrv.sh: test: argument expected Creating links... devfsadm: driver failed to attach: vboxdrv Done. but the package manager still thought the installation went well:
Apparently, the problem was that this machine was missing the /usr/xpg4/bin/id command (from the SUNWxcu4 package). In any case, I'm assuming that the "devfsadm: driver failed to attach: vboxdrv" message means that the install wasn't successful and that the overall package installation should have failed too. |
|||

