Custom Query (16363 matches)
Results (1579 - 1581 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1612 | fixed | append does not work correctly on a vboxsf filesystem => Fixed in SVN | ||
| Description |
The following commands demonstrate that ticket 1178 is not correctly solved: $ echo 'a very long line with text' >/XP/file.txt $ echo 'a bit more' >>/XP/file.txt $ cat /XP/file.txt a bit more line with text $ This is with a Debian/testing guest on a Windows XP/sp2 host, and /XP is the result of # mount -t vboxsf -o defaults,uid=matthijs,gid=matthijs C_DRIVE /XP |
|||
| #1613 | fixed | build_in_tmp not found => remove /etc/vbox/vbox.cfg | ||
| Description |
After a recent update to hardy heron (26 May 2008) which included a kernel update. Virtual box ceased to run a VM and produced a kernel module error. The Error message: VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root. VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED). Result Code: 0x80004005 Component: Console Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf} After running the suggested command to resolve the issue. The output log contained only the following line: /etc/init.d/vboxdrv: 311: /usr/lib/virtualbox/src/build_in_tmp: not found |
|||
| #1614 | fixed | Missing Run Level shortcuts with generic Linux .RUN install => Fixed in 1.6.2 | ||
| Description |
I have installed VB three times, using the generic Linux .RUN installer. I noticed that the VirtualBox kernel driver and networking are not initialized in run level 2, which is the default run level in Debian. I'm using "testing" and "unstable", so the pre-packaged Debian binaries for "stable" are not usable for me. Symbolic links S20vboxdrv -> ../init.d/vboxdrv S20vboxnet -> ../init.d/vboxnet are installed in /etc/rc3.d/ and /etc/rc5.d/ but not /etc/rc2.d/ which is the Debian default run level. Please consider putting the symbolic links into Run Levels 2 through 5. People who know enough to alter their run level will know to delete these symbolic links if they do not want those drivers to be active. Sadly, it took me a while to figure out why VirtualBox would give me an error when I first started my machine, but work once I "rebuilt" the driver. The initial installation and subsequent driver "rebuilds" all occurred in Run Level 2, which I must assume your installer does not check before creating the symbolic links. |
|||

