Custom Query (16363 matches)
Results (574 - 576 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #6362 | fixed | [Fedora 12] 'mount c /mnt/c -t vboxsf' in rc.local fails w/SELinux error => Fixed in SVN | ||
| Description |
Configuration:
Issue:
It appears than when mount is run from an init script that any mount "helpers" (eg: mount.vboxsf) must have "mount_exec_t" security context. So: I suspect that /opt/VBoxGuestAdditions-3.1.4/lib/VBoxGuestAdditions/mount.vboxsf should be installed with mount_exec_t context (not usr_t). (After I made this change, a 'mount ... -t vboxsf' in rc.local then worked properly). SELinux error:
SELinux is preventing /bin/mount "execute" access to
/opt/VBoxGuestAdditions-3.1.4/lib/VBoxGuestAdditions/mount.vboxsf.
...
Source Context system_u:system_r:mount_t:s0
Target Context unconfined_u:object_r:usr_t:s0
Target Objects /opt/VBoxGuestAdditions-3.1.4/lib/VBoxGuestAdditio
ns/mount.vboxsf [ file ]
Source mount
Source Path /bin/mount
|
|||
| #14510 | obsolete | vboxadd.service startup times out on Fedora 22 boot | ||
| Description |
I recently started getting the following when booting my Fedora 22 guest system on my Windows 7 host. [...] systemd[1]: vboxadd.service start operation timed out. Terminating. [...] systemd[1]: Failed to start VirtualBox Linux Additions kernel modules. [...] systemd[1]: Unit vboxadd.service entered failed state. [...] systemd[1]: vboxadd.service failed. After some poking around I determined that the timeout occurred while executing the following in the vboxadd init script: if $MODPROBE -c 2>/dev/null | grep -q '^allow_unsupported_modules *0'; then
MODPROBE="$MODPROBE --allow-unsupported-modules"
fi
I changed the timeout specified in the vboxadd.service config file from 5 minutes to 10 minutes and the timeout no longer occurred. I should note that this timeout started happening only after some recent Fedora 22 updates. I had no problems previously. |
|||
| #11784 | obsolete | Critical Windows 8 freeze after start-up since updating to VB 4.2.12 | ||
| Description |
I previously had a perfectly functional Windows 8 guest virtual machine working within Mac OS X Mountain Lion, I believe using VB 4.2.4. I updated to VB 4.2.12 earlier this week and have since been unable to functionally run the virtual machine. On starting the machine, I get as far as the Windows 8 logo screen (i.e. not very far) but the 'loading circles' never appear. VB remains responsive for a short while but the screen never changes and eventually I can only force quit the application. |
|||

