Custom Query (16363 matches)
Results (1762 - 1764 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16773 | worksforme | Не удалось открыть сессию для виртуальной машины | ||
| Description |
Не удалось открыть сессию для виртуальной машины Tails. VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED). Код ошибки: E_FAIL (0x80004005) Компонент: ConsoleWrap Интерфейс: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} |
|||
| #16772 | fixed | VirtualBox No Longer Installs On 32bit Slackware Current | ||
| Description |
After recent changes to Slackware current 32bit, VirtualBox will no longer install. I use the VirtualBox-5.1.22-115126-Linux_x86.run script to install. Have tried going back to earlier versions of VirtualBox but these don't work either so fairly sure its an upgrade to a package that causes problem. Don't know if it is the bump in kernel version (4.9.28) or the upgrade to gcc-7.1.0. Either way it's possible this will be seen in other distributions at some point. When running the script I get the following diagnostics... Verifying archive integrity... All good. Uncompressing VirtualBox for Linux installation............. VirtualBox Version 5.1.22 r115126 (2017-04-28T15:48:48Z) installer Removing previous installation of VirtualBox 5.1.14 r112924 from /opt/VirtualBox Installing VirtualBox to /opt/VirtualBox Python found: python, installing bindings... vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why. There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why. and dmesg shows several lines with: vboxdrv: Unknown symbol __udivmoddi4 (err 0) As a result of this there is no kernel driver installed and no guests can be launched. |
|||
| #16769 | duplicate | winxp error | ||
| Description |
hi when run windows xp on virtualbox appears message "Critical error ..." keriks |
|||

