Custom Query (16363 matches)
Results (1885 - 1887 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16564 | fixed | Shared folder mount fails with "No such file or directory" after upgrade | ||
| Description |
I have a Windows 10 host and several Linux (mostly Ubuntu) virtual machines created by Vagrant. After upgrading from 5.1.14 to 5.1.16 shared folder mount stopped working: # mount -t vboxsf vagrant /vagrant /sbin/mount.vboxsf: mounting failed with the error: No such file or directory I noticed that Vagrant registered shared folder paths in the following format: \\?\C:\Path\To\MyStuff
As soon as I removed the leading After downgrading back to 5.1.14, the mount works again without any issues, so this looks like a regression in 5.1.16. |
|||
| #16563 | duplicate | Could not create the medium storage | ||
| Description |
I've installed VirtualBox 5.1.16 r113841 (Qt5.5.1) on a new installation of Ubuntu 16.04.2. When I try to create a fixed disk for a new virtual machine using the GUI (guest operating system is Linux 64-bit), I get the following error: Could not create the medium storage unit '/home/.../VirtualBox VMs/HDNode1/HDNode1.vdi'. VDI: setting image size failed for '/home/.../VirtualBox VMs/HDNode1/HDNode1.vdi' (VERR_INVALID_PARAMETER). Result Code: VBOX_E_FILE_ERROR (0x80BB0004) Component: MediumWrap Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda} I see that this is a duplicate of Ticket #16464, but I have additional information.
|
|||
| #16562 | obsolete | mouse locks up in (some) VMs after some uptime when using vbox after 5.1.10 | ||
| Description |
Using 5.1.12 or later on a CentOS 6.8 host, certain VMs experience a loss of response to mouse clicks (both left and right) after some amount of uptime (usually a day or so). This was also observed on 5.0.30 and after. MI is enabled, and ALL VMs are configured to use tablet device. The guest most likely to have the problem is an ArchLinux variant called obarun (obarun.org for more info). GAs are up-to-date on all guests. Guests are generally kept up to date on system software as well. Workaround has been to downgrade to 5.1.10 (or 5.0.28) where the problem is not experienced. |
|||

