Opened 14 years ago
Closed 11 years ago
#8992 closed defect (worksforme)
Guest-additions installation on GNU/Linux is PAINFUL
| Reported by: | vuurmur | Owned by: | |
|---|---|---|---|
| Component: | guest additions | Version: | VirtualBox 4.0.8 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | other |
Description (last modified by )
Installation script doesn't care about anything.
- --nox11 doesn't seem to work
- Always complains about kernel source, despite its correctly installed and other modules build without any problem
- VERY dirty installation, leaves previous attempts' leftovers all around the system; it not even checks for successful compilation.
Change History (2)
comment:1 by , 14 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 11 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → worksforme |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Your description lacks some information. If the installation fails, there is an error message displayed (which one is it in your case?) and the error message usually points to a log file (please attach).
If the compilation of the kernel modules fails, the installer will not remove anything because the user is free to install the missing components and can then recompile the kernel modules without the need to reinstall all files. Uninstalling the Guest Additions is clearly documented in the user manual (for your info, section 4.2.2.4). After you've done so, the Guest Additions should be completely vanished from your guest.
The --nox11 option does exactly what it is supposed to do: It would spawn an xterm (or rxvt, dtterm, eterm, Eterm, kvt, konsole, aterm in that order) if you would not start the installer from a terminal. This is a generic option of the makeself installer framework. Probably rarely used but nevertheless works.