I'm trying to access VirtualBox through libvirt on OS X (Lion). I installed libvirt 0.9.4 using Homebrew. However, libvirt fails to connect to VirtualBox:
# virsh -c vbox:///session
error: internal error unable to initialize VirtualBox driver API
error: failed to connect to the hypervisor
In a similar SO question about Ubuntu, the answer was that the Ubuntu libvirt package doesn't build support for VirtualBox. How can I check if this is the problem in the case of the Homebrew package, or if it's a different issue? If it's the same problem, how do I rebuild the Homebrew package with VirtualBox support?
Edit: libvirt 0.9.7 has been released, and I no longer get this error.
Your libvirt is build with VirtualBox support. I can tell because the error message you see comes from the VirtualBox driver in libvirt.
There was a similar problem reported on the libvirt users maling list today. The problem there was that support for VirtualBox 4.1 was added quite recently to libvirt. It's not in a released version yet and will be part of the next libvirt release 0.9.7.
To get some more useful information try running this:
LIBVIRT_LOG_FILTERS=1:vbox virsh -c vbox:///session
I suspect that you have VirtualBox 4.1 installed, but libvirt 0.9.4 supports only up to VirtualBox 4.0.
You can either a) upgrade your libvirt to current git version (that supports VirtualBox 4.1), or b) wait for the next libvirt release (it's expected in this week) or c) downgrade your VirtualBox version to 4.0 to fix this, assuming your problem is really as I suspect.
Related
This question was migrated from Stack Overflow because it can be answered on Super User.
Migrated 25 days ago.
I am trying to use WSL under Windows 10 Pro, and while WSL itself was installed without a problem, I cannot install any Linux distribution under it.
PS C:\WINDOWS\system32> wsl --version
WSL version: 1.0.3.0
Kernel version: 5.15.79.1
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19042.2486
PS C:\WINDOWS\system32> wsl -l
Windows Subsystem for Linux has no installed distributions.
Use 'wsl.exe --list --online' to list available distributions
and 'wsl.exe --install <Distro>' to install.
Distributions can also be installed by visiting the Microsoft Store:
https://aka.ms/wslstore
Error code: Wsl/WSL_E_DEFAULT_DISTRO_NOT_FOUND
PS C:\WINDOWS\system32> wsl -l -o
The following is a list of valid distributions that can be installed.
Install using 'wsl.exe --install <Distro>'.
NAME FRIENDLY NAME
Ubuntu Ubuntu
Debian Debian GNU/Linux
kali-linux Kali Linux Rolling
SLES-12 SUSE Linux Enterprise Server v12
SLES-15 SUSE Linux Enterprise Server v15
Ubuntu-18.04 Ubuntu 18.04 LTS
Ubuntu-20.04 Ubuntu 20.04 LTS
Ubuntu-22.04 Ubuntu 22.04 LTS
OracleLinux_8_5 Oracle Linux 8.5
OracleLinux_7_9 Oracle Linux 7.9
PS C:\WINDOWS\system32> wsl --install Ubuntu
Installing: Ubuntu
Error: 0x80244018 0.0% ]
Error code: Wsl/InstallDistro/0x80244018
PS C:\WINDOWS\system32> wsl --install Debian
Installing: Debian GNU/Linux
Error: 0x80244018 0.0% ]
Error code: Wsl/InstallDistro/0x80244018
PS C:\WINDOWS\system32>
I did try disabling proxy, as I found in one of the posts, but instead of Error: 0x80244018 got Catastrophic Failure.
Can anybody recommend what I can do to install a distro?
As I believe you've discovered (from your proxy comment), this error is usually due to a failure in the Windows Update service. By default, WSL uses this service to install distributions from the Microsoft Store, but many other Windows components and applications use the service as well.
While the information below may help with WSL, it's likely that you have a more significant issue that you'll need to resolve. If that's the case, you'll probably want to post a new question that is broader in scope, rather than just this one that focuses on WSL.
That said, my suggested workaround for installing WSL distributions would be to try:
wsl --install --web-download Debian
The --web-download option skips the Store (and shouldn't use the Windows Update service), and will download the distribution directly then install it.
Alternatively, if you can get access to a working Docker installation apart from this system, you could use the steps found in Import any Linux distribution to use with WSL.
All of a sudden Vagrant is broken on my machine.
I don't see what might have caused this. It came up with an older version of Virtualbox and Vagrant 1.9.8. I updated both to the current version in hope to get it fixed.
I run
Windows 10 Pro 1709
Virtualbox 5.2.0-118431
Vagrant 2.0.1
I was using a current Ruby installation in parallel but removed it for testing.
For any Vagrant command I get this error:
https://gist.github.com/cfoellmann/b8c50dc386d241d44ed0fca60e7680d1
I have read about issues with the ffi gem but I see no way to fix the bundled components of the vagrant install.
Any pointer into debugging this will be much appreciated.
I try to install Metatrader 5, on Ubuntu 17.04 (64-bit).
I get stuck, and need somebody to help me to solve this problem.
I've installed wine-2.0.1, which is the latest stable version at the moment, and it's for 64-bit.
Finally, after successfully installing Metatrader 5, on launching the application appears an error window: terminal64.exe, with message:
A debugger has been found running in your system.
Please, unload it from memory and restart your programm.
On wiki.winehq.org, I've found that is needed to install 2 separate versions of wine: 32-bit and 64-bit. I try to do all like in:
https://wiki.winehq.org/Building_Biarch_Wine_On_Ubuntu
, but at the stage "Build 64-bit Wine", for: make clean, I got:
make: *** No rule to make target 'clean'. Stop.
There is a way to really install mt5 on Ubuntu 17.04 ?
Just installed it after suffering a little bit. After seeing many requests from the installer to provide a proxy!
First install the latest Wine from the instructions given in its website for Ubuntu (this is the one that will work!)
sudo dpkg --add-architecture i386
wget -nc https://dl.winehq.org/wine-builds/Release.key
sudo apt-key add Release.key sudo apt-add-repository
https://dl.winehq.org/wine-builds/ubuntu/
sudo apt-get update
Stable branch:
sudo apt-get install --install-recommends winehq-stable
Configure Wine to 32 bits (only your user)
WINEARCH=win32 WINEPREFIX=~/.wine32 wineboot
Install Metatrader 5
WINEPREFIX=~/.wine32 wine start /unix /path/to/mt5setup.exe
Happiness
Finally to run MetaTrader 5 add the following to your .bashrc our .profile. And type metatrader on your terminal.
export WINEPREFIX=~/.wine32
alias metatrader='wine start "C:\program files\metatrader 5\terminal.exe"'
Thanks to #Kaleshwar Chand
I recently installed metatrader5 on ubuntu 17.04, using the instructions found on mql5 thread
basically mt5 is 32 bit and your ubuntu is 64 bit so you need to change arch to 32 bit to install/use it properly
enter into terminal
WINEARCH=win32 WINEPREFIX=/home/user/.wine32 wineboot
replace user with your username
then install with
WINEPREFIX=/home/user/.wine32 wine start /unix /path/to/mtsetup.exe
again replace user with your username
I am running MT5 on Arch,
in my case, a 64bit wineprefix is needed for connect with other apis so...
For install and run it correctly I installed:
wine, wine-mono, wine_gecko, winetricks, playonlinux
winetircks corefonts, winetricks winhttp
libgnutls allowed to skip the required proxy error
MT5 was installed throught playonlinux on a 64bit wineprefix
Follow the steps from office winehq at https://wiki.winehq.org/
and find your OS you are using
Android (WineHQ binary packages for Android)
Ubuntu (WineHQ binary packages for Ubuntu 16.04, 18.04, 19.04, and 19.10)
Debian (WineHQ binary packages for Debian Stretch, Buster, and Bullseye)
Fedora (WineHQ binary packages for Fedora 30 and 31)
MacOS (WineHQ binary packages for macOS 10.8 through 10.14)
I'm spending way too muhc time on trying to figure this out, so I decided to ask you guys for a little help.
I downloaded VMWare Workstation 12.5.5 on kernel 4.10.8 (Linux Mint 18.1).
A popup show up saying I don't have gcc >= 6.2.0.
After trying to compile it I realised there's a version hosted on a ppa:
deb http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial
main
sudo apt update
sudo apt install gcc-6
I relaunch vmware and I still get this error. Entering the path manually to /usr/bin/gcc-6 doesn't work either. /usr/bin/gcc-6 -v gives me gcc version 6.2.0 20160901 (Ubuntu 6.2.0-3ubuntu11~16.04)
How can I run VMware on my machine? Thanks! :D
There is a nasty bug in Docker 1.9.x that is causing java
processes to hang and frankly hang up the entire container
instance, spinning 100% CPU.
I currently have docker 1.9.1 installed because that is all that
the docker install tool will install. There is no opportunity during
the install process to select any other version.
This is completely preventing me from building a cordova
build container. In my internet research I have found many
others who are encountering the same problem.
I've done some research and seen that others are reporting this
problem does not occur with Docker 1.8.3.
I've searched in vain for some hints on how to install older versions
of docker on OS-X. I tried replacing the boot2docker.iso in ~/.docker/machine/machines/default with the 1.8.3 version downloaded
from here: https://github.com/boot2docker/boot2docker/releases/tag/v1.8.3 but that fails miserably. I am guessing that there are other things about my default machine (which had been created with 1.9.1) that are incompatible with it.
If anybody has hints as to how I could create a new machine or modify
the existing machine to work with 1.8.3 I would very much appreciate
it.
Alternatively, let me know if there is some other installation method that would allow me to specify which version of docker to install.
I figured out that what I needed to do is to find an older version of DockerToolbox and that would install the version of docker that I wanted.
I went to the github repository for DockerToolbox:
https://github.com/docker/toolbox/releases?after=v1.9.
and there I found a link to the 1.8.3 binary:
https://github.com/docker/toolbox/releases/download/v1.8.3/DockerToolbox-1.8.3.pkg
I still had to uninstall my previous installation of docker so I followed the uninstall instructions on this page:
https://medium.com/#itseranga/install-old-version-of-docker-osx-c92ebd5f15f7#.5qh1z0ino
Once I had uninstalled and reinstalled via the legacy DockerToolbox, I managed to build the cordova container:
https://github.com/oren/docker-cordova
without incident.
I've been using the following:
https://get.docker.com/builds/$(uname -s)/$(uname -m)/docker-.tgz
See https://github.com/docker/for-mac/issues/1120.
If you happen to know the build number (e.g. 14937) -- not the git commit you see when running docker --version or docker version -- you can form the URL:
https://download.docker.com/mac/{{ beta | stable}}/{{ version }}.{{ build number }}/Docker.dmg
# example:
https://download.docker.com/mac/stable/1.12.6.14937/Docker.dmg