Custom Query (16363 matches)
Results (1558 - 1560 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18170 | duplicate | install of VirtualBox-5.2-5.2.22_126460_fedora26-1.x86_64.rpm fails; libvpx.so.4 missing -> duplicate of #18113 | ||
| Description |
I have tried several of the builds VB 5.2.20 and VB 5.2.22) in order to get VB installed but NONE but the development version (which has a console problem) works. This host is a fresh Fedora 30 x86_64 installation and libvpx is at the libvpx-1.7.0-7.fc29.x86_64 level. I had to make a .so.4 link to the .so.5 library but this doesn't work for some reason. Even after running ldconfig. fc30-bash 4.4 /isos# rpm -Uvh VirtualBox-5.2-5.2.22_126460_fedora26-1.x86_64.rpm warning: VirtualBox-5.2-5.2.22_126460_fedora26-1.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 98ab5139: NOKEY error: Failed dependencies:
fc30-bash 4.4 /isos# ls -al /usr/lib64/libvpx.* lrwxrwxrwx 1 root root 15 Jul 20 01:55 /usr/lib64/libvpx.so -> libvpx.so.5.0.0 lrwxrwxrwx 1 root root 15 Dec 4 22:10 /usr/lib64/libvpx.so.4 -> libvpx.so.5.0.0 lrwxrwxrwx. 1 root root 15 Jul 20 01:55 /usr/lib64/libvpx.so.5 -> libvpx.so.5.0.0 lrwxrwxrwx. 1 root root 15 Jul 20 01:55 /usr/lib64/libvpx.so.5.0 -> libvpx.so.5.0.0 -rwxr-xr-x. 1 root root 2382120 Jul 20 01:55 /usr/lib64/libvpx.so.5.0.0 |
|||
| #18280 | invalid | install esxi 6.7 in vbox | ||
| Description |
i want to install es-xi 6.7 in v box but when i check box on the efi box, in which i can enable the virtualization on the cpu but no display will be shown please guide me |
|||
| #14234 | duplicate | inotify does not work on Mac OS X with Ubuntu hosts | ||
| Description |
In the latest years there have been a lot of projects that have become popular among the develop community that leverage VirtualBox as development system. Vagrant and docker-machine are just some notable examples. It is very common that people use a shared folder to share their source code on Mac OS X with the virtual machine and use the virtual machine to run a production-like environment . There are a few tools that listen for changes on the file system to immediately run rebuilding scripts or restart a server (ex: nodemon, pm2 or gulp in node.js) that rely on inotify. But inotify is not implemented on shared folders. Work arounds have led to active polling all files in the project and all its subfolders that increase CPU consumption to unacceptable level. Implementing inotify on shared folders on Mac OS X for ext3 and ext4 guests will fix most of the problems. One example of bug: https://github.com/remy/nodemon/issues/419 |
|||

