5 ms·

Too bad none of these two bugs has been fixed: https://www.virtualbox.org/ticket/9069 https://www.virtualbox.org/ticket/9069 https://www.virtualbox.org/ticket

Too bad none of these two bugs has been fixed: https://www.virtualbox.org/ticket/9069 https://www.virtualbox.org/ticket/9069 https://www.virtualbox.org/ticket/12597 https://www.virtualbox.org/ticket/12597 (cannot use `sendfile` in nginx inside a virtualbox, due to an eight year old bug)

nickjj 8y ago
Yeah it's crazy that it's not fixed yet. About 5 years when I was using VMs for my development environment I remember that bug causing all sorts of issues with assets not loading correctly. It's also why I recommend people avoid Docker Toolbox like the plague since it uses VirtualBox under the hood. Either use Docker for Windows (if you have Windows 10 Pro), or roll your own VMWare Player (free) VM which doesn't have that bug, has way better I/O performance in the end and isn't much harder to set up.
- user5994461 8y ago
  This might surprise you but neither of these 2 are bugs. VirtualBox shared folders simply don't offer the guarantees of a local filesystem. They are not a local filesystem, they are network drives mounted as NFS, with the abysmal support and quirk that comes with that. sendfile() doesn't work on network drives. it never did. the host is not aware of changes made to the remote filesystem from another host. it cannot see updated files unless it checks for remote changes.
  - fuzzy2 8y ago
    > They are not a local filesystem, they are network drives mounted as NFS, with the abysmal support and quirk that comes with that. They’re actually not, which is exactly the problem. vboxsf is its own “real” filesystem. The code is super simple (too simple, perhaps): https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/linux/sharedfolders https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Addit... It contains many shortcuts with reporting free inodes and whatnot.
  - nickjj 8y ago
    But from our point of view (the end user), it feels like a bug with VirtualBox because this problem doesn't exist when using VMWare or Hyper-V. I used a VMWare Player driven VM as a primary Linux development environment for full time web development for literally 4 years straight and I encountered the issue 0 times, but with VirtualBox I encountered the issue in 1 day. Maybe it's not technically a bug with VirtualBox, but it is something that makes VirtualBox unsuitable as a dev environment for web development.
    - pas 8y ago
      You're right that it's a major UX hurdle. But it's not a bug in an advertised feature. Not a technical oversight, not a glitch. Yes, vboxfs is very restrictive, but then again, the whole cross platform virtualization is a very thin curtain of magic over the nasty differences behind.

nickjj 8y ago

Yeah it's crazy that it's not fixed yet. About 5 years when I was using VMs for my development environment I remember that bug causing all sorts of issues with assets not loading correctly. It's also why I recommend people avoid Docker Toolbox like the plague since it uses VirtualBox under the hood. Either use Docker for Windows (if you have Windows 10 Pro), or roll your own VMWare Player (free) VM which doesn't have that bug, has way better I/O performance in the end and isn't much harder to set up.

user5994461 8y ago
This might surprise you but neither of these 2 are bugs. VirtualBox shared folders simply don't offer the guarantees of a local filesystem. They are not a local filesystem, they are network drives mounted as NFS, with the abysmal support and quirk that comes with that. sendfile() doesn't work on network drives. it never did. the host is not aware of changes made to the remote filesystem from another host. it cannot see updated files unless it checks for remote changes.
- fuzzy2 8y ago
  > They are not a local filesystem, they are network drives mounted as NFS, with the abysmal support and quirk that comes with that. They’re actually not, which is exactly the problem. vboxsf is its own “real” filesystem. The code is super simple (too simple, perhaps): https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/linux/sharedfolders https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Addit... It contains many shortcuts with reporting free inodes and whatnot.
- nickjj 8y ago
  But from our point of view (the end user), it feels like a bug with VirtualBox because this problem doesn't exist when using VMWare or Hyper-V. I used a VMWare Player driven VM as a primary Linux development environment for full time web development for literally 4 years straight and I encountered the issue 0 times, but with VirtualBox I encountered the issue in 1 day. Maybe it's not technically a bug with VirtualBox, but it is something that makes VirtualBox unsuitable as a dev environment for web development.
  - pas 8y ago
    You're right that it's a major UX hurdle. But it's not a bug in an advertised feature. Not a technical oversight, not a glitch. Yes, vboxfs is very restrictive, but then again, the whole cross platform virtualization is a very thin curtain of magic over the nasty differences behind.