Custom Query (16363 matches)
Results (1954 - 1956 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16407 | fixed | Windows XP - bridged network issue=> Fixed in SVN | ||
| Description |
I just updated (clean install after a full uninstall) an old 5.0.0 build to the newest 5.1.14 on an old host machine (with P4 S478 3.4GHz CPU), which is running Windows XP Professional SP3 32bit, but had to downgrade it back to the last build in the 5.0 branch (5.0.32), because i discovered, that bridged networking breaks the host's internet connection, through PPPOE ("No remote access - 797", "Cannot access modem", etc. appears). Unfortunatelly, all of the builds in the 5.1 branch are producing exactly this same problem. For better explanation, i attached some pictures too. |
|||
| #16405 | worksforme | Ubuntu not booting after GuestAdditions 5.1.14.112925 update | ||
| Description |
I am running Ubuntu 16.04.1 in VirtualBox inside of Windows 10. On Ubuntu side there was popup suggesting update of GuestAdditions to latest one which I did and installed version 5.1.14.112924 and rebooted guest OS. After that Ubuntu is not anymore booting up but everytime hangs for phase were there is black screen changing the size constantly. I have tried to disable 3D acceleration as well but without success. Then I did fresh install of Ubuntu and after I installed again latest Guest Additions same thing happens again, so this 100% repro for me. I can provide logs files in case you provide instructions how to take/provide those. Thanks! |
|||
| #16404 | fixed | vboxsf does not get autoloaded when a mount happens (fs-vboxsf alias missing) | ||
| Description |
When the vboxsf kernel module is not loaded, mounting a shared folder (e.g. mount -t vboxsf foo /media/foo` fails with ENODEV. The reason for this is that vboxsf lacks the fs-vboxsf alias, which is what the kernel uses to autoload filesystem modules during mount. This can be fixed by adding the following to vboxsf/vfsmod.c: MODULE_ALIAS_FS("vboxsf"); Alternatively, it can be worked around by adding "alias fs-vboxsf vboxsf" to a file in /etc/modprobe.d. Please see the attached MIT-licensed patch for a proposed fix. |
|||

