KVM installation: Unable to locate package ia32-libs-multiarch - android-studio

I'm trying to install KVM for avd of android studio and I ran this command:
sudo apt-get install qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils ia32-libs-multiarch
But on running it gives me this error:
Unable to locate package ia32-libs-multiarch
I tried resolving it using this command but that also didn't work:
sudo apt-get install librtmp0 librtmp0:i386
I'm running a 64-bit machine with ubuntu 14.04
Is what I'm doing the required steps for 32-bit???

I've gotten the same error Unable to locate package ia32-libs-multiarch
Then I decided to trust Ubuntu KVM Installation help page and tried it out.
https://help.ubuntu.com/community/KVM/Installation
Actually there is only one difference. The command doesn't include ia32-libs-multiarch part.
Outcome is successful.
$ kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used

I believe you are trying to run AVD on Linux machine in KVM mode(called HAXM on Windows and OS X machines)
Install KVM by executing following command
$ sudo apt-get install qemu-kvm libvirt-bin virtinst bridge-utils cpu-checker
Next check KVM installed successfully by executing following command
$ kvm-ok
the output will be something like this
INFO: /dev/kvm exists
KVM acceleration can be used
Next add your username to KVM and libvirtd and run the AVD from the tools directory of your android SDK
$sudo adduser `id -un` libvirtd
$sudo adduser `id -un` kvm
$ ./emulator64-x86 -avd < your AVD name> -qemu -m 2047 -enable-kvm
Note: To find the names of your available AVDs, open the AVD manager from tools folder of android sdk by executing command $./android avd
Find more information on installing KVM form these links,
Link 1
Link 2

Install Necessary Packages to avoid this error - Updated for 2020
Cosmic (18.10) or later
sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils
Lucid (10.04) or later
sudo apt-get install qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils
based on ubuntu help community site

Related

Getting an error by making VBox full screen on Windows?

Despite installation of the package, getting same error again.
Error : kernel module failed
Kernel headers not found for target kernel4.19.0-8-amd64. Please install them and execute
Host: Win 10
VBox: Debian 10
This is typical issue, actually not an issue simply missing headers. Run following
commands
$ sudo apt install linux-headers-4.19.0-8-amd64
$ sudo apt install dkms
Then run guest script again
sudo sh VBoxLinuxAdditions.run
Finally reboot the machine
$ sudo reboot

Error: NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver

The NVIDIA-SMI is throwing this error:
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA
driver. Make sure that the latest NVIDIA driver is installed and
running
I purged NVIDIA and installed it again following steps mentioned here.
My device specs are as follows:
Server with a Tesla M40
Running on Ubuntu 16.04
Kernel version Linux 4.4.0-116-generic x86_64
Driver: nvidia-384
Can someone please help in solving the error?
The issue might due to a confirmed "bug" in 4.4.0-116 patch. I ran into the same issue with nvidia-390. If you still want to use a newer version of Nvidia-driver, I followed the instructions here and managed to solve the problem. In general, use the following steps:
If you cannot login to the desktop and fall into to the fail-loop, press ctrl + alt + F1 to login into the command line mode.
Check if the version of gcc is outdated, if so, update it: gcc --version
If the gcc version is 5+, uninstall the nvidia driver first: sudo apt-get remove nvidia-390
Purge the 4.4.0-116 kernel: sudo apt-get purge linux-headers-4.4.0-116 linux-headers-4.4.0-116-generic linux-image-4.4.0-116-generic linux-image-extra-4.4.0-116-generic linux-signed-image-4.4.0-116-generic
Reinstall the kernel: sudo apt-get install linux-generic linux-signed-generic
Reinstall the nvidia-390: sudo apt-get install nvidia-390
Check if the problem is solved by modinfo nvidia-390 -k 4.4.0-116-generic | grep vermagic, make sure retpoline shows up this time
Reboot: sudo reboot
Hope this works for you and other people who run into the same issue. The post in the forum saved my weekend.
Note: this answer is from 2018 and works for Ubuntu 16.04, which is very much out-of-date. Don't try this on recent Ubuntu versions.
Try
Download the driver from here
sudo apt-get purge nvidia* - To remove your current installations
dpkg -i nvidia-diag-driver-local-repo-ubuntu1604_375.66-1_amd64.deb - installing what you downloaded earlier
sudo apt-get update
sudo apt-get install cuda-drivers
After this, go on and reboot your computer.
When it's up again, the nvidia-smi command should run smoothly
to download latest driver as of this answer:
sudo apt install libnvidia-compute-435 libnvidia-compute-435
sudo apt install libnvidia-gl-435 nvidia-dkms-435 nvidia-kernel-source-435
nvidia-utils-435 xserver-xorg-video-nvidia-435 libnvidia-ifr1-435
sudo apt install nvidia-driver-435
sudo reboot
and then:
nvidia-smi
If you're running this on Google Colab, just go to Runtime > Change Runtime Type > select GPU. That worked for me.

VirtualBox VERR_VM_DRIVER_VERSION_MISMATCH on Ubuntu

I trying to install VirtualBox on Ubuntu 14.04. I've installed VirtualBox from Ubuntu repository:
sudo apt-get install virtualbox
Then I added my user to vboxusers:
sudo usermod -G vboxusers -a user
I also installed an extrapack for my vb vsion:
wget http://download.virtualbox.org/virtualbox/5.0.10/Oracle_VM_VirtualBox_Extension_Pack-4.3.36-105129.vbox-extpack
sudo vboxmanage extpack install Oracle_VM_VirtualBox_Extension_Pack-5.0.10-104061.vbox-extpack
But when I trying to start vm, I get an error:
RTR3InitEx failed with rc=-1912 (rc=-1912)The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing '/etc/init.d/vboxdrv setup'may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.
where: supR3HardenedMainInitRuntime
what: 4
VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.
And I have no /etc/init.d/vboxdrv file.
How can I fix this problem?
I've removed all the virualbox packages:
sudo apt-get purge 'virtualbox*'
Then I've installed virtualbox v.5
sudo apt-get install virtualbox-5.0
After that I've enabled virtualization in BIOS.
Now it works.
Check what version of virtualbox you installed
dpkg --list 'virtualbox*'
may be it's not aligned with the Extension pack.
Remove your installation
sudo apt-get autoremove 'virtualbox*'
Don't install fron Ubuntu repositories but run a fresh installation following the instuctions from official Oracle Virtualbox Download page about Debian-based Linux distributions.
Check that Virtualbox is running before installing the Extension pack.
I had the same error starting a vm client in ubuntu 16.4 .
Coincidentally I noticed in the file /var/crash/_usr_lib_virtualbox_VirtualBox.0.crash the following message:
Title: VirtualBox crashed with SIGABRT in QMessageLogger::fatal()
UnreportableReason: Sie haben einige veraltete Paketversionen
installiert. Bitte aktualisieren Sie die folgenen Pakete und prüfen
Sie, ob das Problem danach noch auftritt:
virtualbox-dkms
Translated: You have some outdated package versions installed. Please update the following packages and check, if the problem still occurs after that:
After the command:
sudo apt-get install --only-upgrade virtualbox-dkms
all was OK :)

VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005) with meanjs and vagrant

I am trying to run mean.js project based on vagrant , but I get the following error with the vagrant up command on ubuntu 14.04 LTS 64 bit.
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "d660b7d6-06a3-49bc-8b90-cbad92632c11", "--type", "headless"]
Stderr: VBoxManage: error: The virtual machine 'pets_default_1473142645576_38190' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
I solved the using following steps:
I have completely remove older VirtualBox versions before installing VirtualBox-5.0 !
Uninstall VirtualBox
sudo apt-get purge "^virtualbox-.*"
Update the software repositories
sudo apt-get update
Clean up
sudo apt-get autoremove | sudo apt-get autoclean | sudo apt-get clean
Setup API repository (For Ubuntu 14.04 ("Trusty"))
echo "deb http://download.virtualbox.org/virtualbox/debian trusty contrib" | sudo tee /etc/apt/sources.list.d/oracle-vbox.list
Setup Oracle Key
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
6.Install Oracle Virtualbox
sudo apt-get update
sudo apt-get install virtualbox-5.1
Start Virtualbox
virtualbox
For more help check to here.
I have reinstalled virtual box and the issue has been solved for me.
On my mac while installing virtual box, It has not allowed me to install. So i went system preference -> security & privacy - > general - 'allow apps download from' -> click on the "allow" button.
I have successfully installed virtual box after the above changes on system preference.
Kitchen converge -> successfully done.
I was using macOS and I had this error after updating VirtualBox. I solved the error by going to:
System Preferences --> Security & Privacy and then clicked on lock to make changes. Then, I clicked on "Allow" as shown in the picture below:
After you make the changes, a restart is requested by the system, after restart the command should work just ok :)
Move to directory:
cd /sbin/
Run script:
sudo ./vboxconfig
Start VM:
VBoxManage startvm "VM name" --type headless
It works:)
Root this problem - system updating. VBox updated partially. This script fix this problem.
For some reason my virtualbox linux host was having an outdated vboxdrv kernel module.
I did the whole remove VirtualBox package, then reinstall, but this old version kernel module remained.
Manually deleted the unwanted module, then freshly reinstalled latest VirtualBox, then usual vboxconfig to rebuild the latest modules, and we're done.
/usr/bin/vboxmanage startvm Win10-Server --type headless now working as expected. :-)
I also faced the same issue, but Santosh Shinde's answer helped me to figure it out.
I, however, want to add to it:
After uninstalling every old/previous version of Virtualbox available on your PC:
sudo apt-get purge "^virtualbox-.*"
And cleaning your system:
sudo apt-get autoremove
Rather than installing Virtualbox from the Apt repository of Ubuntu, simply visit the downloads page of Virtualbox, to download the most current version of Virtualbox.
This is because the Apt repository may not have the latest version of Virtualbox.
I have the same error after install some cripto plugin to Chrome.Then see that Virtual box extension is not working under root and user. In my linux distributive /opt owner was changed to user by cripto plugin installator. Changing /optto root owner has solved the problem.
I just had this happen on a FreeBSD box where vagrant wasn't involved at all.
[root#freebsdserver ~]# vboxmanage startvm yavm
Waiting for VM "yavm" to power on...
VBoxManage: error: The virtual machine 'yavm' has terminated unexpectedly during startup because of signal 6
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
In this case it's because "freebsdserver" is running headless. The fix was to run:
# vboxmanage startvm yavm --type headless

Error message when setting up ADT in Linux

I installed Ubuntu 11.10, installed GNOME 3 (replaced Unity), installed Eclipse from the Ubuntu Software Center, installed the android sdk and ADT.
Now when I start eclipse I get a message saying:
Failed to get ADB version : Cannot run program
/home/ayush/android-sdk/platform-tools/adb":java.io.IOException:error=2,
No such file or directory
What is causing this error and how do I fix it?
The command to install IA32 libraries on Ubuntu is:
apt-get install ia32-libs
sudo dpkg --add-architecture i386
sudo apt-get update
apt-get install ia32-libs
Before that please check your ubuntu version. if you are running with 64 bits, you need to install a linux emulator, IA32 bit I thinks. Verify on Google.
after that, your ADB can run easily on ubuntu.
I'm using Fedora 17 and I got the same error as the poster:
[2013-08-29 21:44:08 - adb] Unexpected exception 'Cannot run program
"/home/el/adt-bundle-linux-x86_64-20130729/sdk/platform-tools/adb":
error=2, No such file or directory' while attempting to get adb version from
'/home/el/adt-bundle-linux-x86_64-20130729/sdk/platform-tools/adb'
I know this works if you are using Fedora 17/18 (login as root)
yum install redhat-lsb.i686
And then restart the IDE and the errors no longer show.
I had the exact same error as you had, but on my Ubuntu 12.04 LTS version.
The following avoided that error for me:
1) Install 'adb' and 'fastboot' provided by the following third-party PPA.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
2) Replace the copy of 'adb' and 'fastboot' provided by the official Android SDK with those installed from the above step:
cp /usr/bin/adb <path-to-your-adt-sdk-package>/sdk/platform-tools/adb
cp /usr/bin/fastboot <path-to-your-adt-sdk-package>/sdk/platform-tools/fastboot
3) Restart(re-execute) your eclipse binary.
Full credits:
http://www.webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html
They have the binaries for 12.10, 11.10 and 11.04 as well.
Don't try to install ia32-libs, this library has been obsoleted.
So, you should install these libraries:
sudo apt-get install libc6-i386 lib32stdc++6 lib32gcc1 lib32ncurses5
Cheers

Resources