Custom Query (16363 matches)
Results (4 - 6 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| #1312 | fixed | kmk fails on zfs | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
You cannot build virtualbox on solaris in a zfs filesystem because kmk will fail attempting to create directories with its builtin mkdir. Apparently, kmk's logic for directory existence is... less than optimal - it seems to try creating directories from /, whether or not they exist (unlike mkdir which tries to create the leaf dir and fails upward). The problem happens when it reaches a ZFS mountpoint, where mkdir(2) will return ENOSYS, instead of its expect EEXIST, causing kmk to bail out. Only workaround is to build on a ufs filesystem, as kmk will do mkdirs whether or not the target exists. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #18667 | fixed | Kernel panic in Debian 9 guest at shut down when shared folders are enabled => Fixed in SVN | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
When shared folders are enabled the guest experiences a kernel panic at shutdown. When shared folders are disabled the guest shuts down as expected. This issue seems to affect Debian guests only (CentOS seems to be fine).
I have attached two sets of files showing the VBox.log, the guest console output (minicom.cap), and where applicable, a core dump captured with
The files with the "error_" prefix were captured with shared folders enabled - the The files marked with the "normal_" prefix were captured with shared folders disabled (no panic) and should hopefully provide a useful baseline. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #234 | fixed | I18N progress | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
[Update: This ticket is closed, any further discussion goes to its successor ticket:2018] This ticket is intended for two purposes:
Step 1 is done by contributors willing to add support for a new language to the VirtualBox product. An accepted translation file appears in the SVN repository and becomes available in the binary builds. Even after that, contributors remain responsible for updating translation files to keep them in sync with updates to the VirtualBox UI. Step 2 is performed by the GUI maintainer at innotek before a new release (or after a major UI change) to inform contributors that translation files need to be updated. More info about the translation process can be found here. The current list of translators:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

