Suddenly, i lost all Geny motion emulators (maybe after upgrading to Geny motion 2.2, not sure) and when ever i download a new virtual machine or emulator i get the "failed to import OVA" error and i can't use the virtual machines i downloaded at all in Geny motion, however they work in virtual box!
and i have cleared the cache and deleted old OVAs and re-downloaded other emulators again and again, but it's no use!
any clue what's going on?
is there a way to re-import emulators i already downloaded by Geny motion to Geny motion again instead of keeping downloading new emulators and getting the same error?
I solved the problem for myself. In my case, I had the same problem after defragmenting my computer. Deleting the ova and deploying files did not work (neither did reinstalling help). Solved it by clearing the cache in the app itself:
Settings>Misc>Cache Usage>Clear Cache
Try to see if that helps. If it doesn't then I can't help.
So I upgraded to the latest version of Genymotion 2.6.0. Tried to install the new Virtual Devices and I got the same error.
I tried to clear the cache as suggested above but it didn't help instead it removed the downloaded .ova file of the device and I had to download again.
I checked for update on VirtualBox and it shows that you're on the latest build. I checked the version and it showed 4.2.x.
Checked the latest version on the site and damn... It was version 5.0 available on the website.
Upgraded the VirtualBox to the latest 5.0 and here you go... Everything was back in place and my Genymotion Virtual Device was imported and is running fine.
So do check the versions of VirtualBox and see if it is the latest available on the website.
Deleting the Genymotion cached .ova file, deleting the corrupted deployed image, redownloading the image, and reinstalling it addressed the issue for me.
Note that the deployed images are under: ~/.Genymobile/Genymotion/deployed
the cached ova files are under: ~/.Genymobile/Genymotion/ova
this link : Unable to create Genymotion Virtual Device
Update :
Settings>Misc>Cache Usage>Clear Cache
Try to upgrade VirtualBox to the latest release, this solved the problem for me.
UPDATE
Some VirtualBox version are not compatibles with genymotion: review FAQ Genymotions in https://www.genymotion.com/help/desktop/faq/#compatible-virtualbox-versions
If you see the log file of Genimotions you'll find this:
VBoxManage.exe: error: 'Linux_64' is not a valid Guest OS type
The problem is the version of Virtual Box, I thought I had the last version (4.2) because virtual box said me that it was the lastest version, but it wasn't true: The last version actually is 5.0.20
I've installed the last version (5.0.20), and ova is ok
If you're using Windows:
The folder left after uninstallation is located at:
C:\Users\Your_User_Name\AppData\Local\Genymobile\Genymotion\
Before proceeding, in the OVA folder, save the ova files in there if you do not want to redownload the images all over again.
Clear the Genymotion cache, and then uninstall Genymotion (and Oracle VBOX if needed)
Remove the whole Genymotion folder in the above path
Reinstall genymotion and VirtualBox
Copy back the ova files into the ova folder.
Re-add the virtual device accordingly (the ova files name should be identifiable easily enough)
Genymotion will then verify the integrity of the stuffs and should now works fine.
I just Run Genymotion with Administrator right (run as Administrator)! It work perfect!
I had the same issue and also tried deleting the Genymotion cached .ova file and old images but to no avail.
To get my Genymotion working again in my environment I completely uninstalled VirtualBox and Genymotion using the TrashMe app to ensure no trace was left on my system. You can achieve the same result with the free app App Cleaner.
I then completely deleted the ~/.Genymobile directory as this seems to get left behind when deleting/uninstalling Genymotion. I think this is the only thing I did differently this time.
I then re-downloaded the latest versions of VirtualBox and Genymotion and installed them in that order. (Versions at time of writing: VB - 4.3.13 r93733 / GM - 2.2.2)
I then launched Genymotion, connected to my account, added a new device and I am now back up and running.
Hopefully that helps..
I encountered this error when my hard drive was almost full. It looked like it had enough space for the emulator, but Genymotion still failed with failed to import eva
Solved by freeing up a couple Gigs on disk.
Updating VirtualBox to the latest version, Worked for me
I deleted all the virtual devices and cleared Cache. After that I added the device again. Worked for me.
I had the same problem, I fixed it with uninstalling, reinstalling and running Gennymotion with Admin rights. Make sure you not upgrade Oracle VM and use the one you installed with Genymotion. Also at installing Genymotion make sure you reinstall VM too. It should work, I lost my devices too and this method only solve the OVA problem. If you run the virtual device and get an error, reboot computer, if you didn't do after installing Oracle VM. Hope it helped.
it turns for me I restored the system from the backup
Click geny settings->virtualbox tab, have to correct the folder to keep the VM
I had deleted /Users//.Genymobile/ directory and Genimotion started work fine
make sure you choose the correct android sdk
in Linux
just delete
home/user/.config/Genymobile/Genymotion.conf
and it's work
I downloaded ova that match with version i want (example android 5)
http://fatihcamuz.com/2015/04/download-links-of-genymotion-ova/
then add ova file to genymotion
https://www.youtube.com/watch?v=0MiYhVUv4KE
Related
After I upgraded to macOS 13. I found a problem with command in nextjs first. I tried to run my project with: npm run dev
This is result:
> dev
> next dev
It stucked on this log very very long time.
and I tried to create another project using:
npx create-next-app#latest
Result same to nextjs
About my computer:
Macbook pro 2018 13-inch 4 ports
I used Oh My Zsh on terminal
my node.js version is 16.18.0 (16.9.1 on this question created)
UPDATED 27/10/22
After I asked in this community. I tried many way to solve this issues.
This is way I tried:
Reinstall macOS Ventura and not working
Change node.js version to 16.18.0 => 19.0.0 and downgraded to 16.18.0 and not working
And now this problem is still. I still can't resolve this problem :(
I also had the same problem when I tried to run the nestjs application. Also failed to install packages, I got this error every time
It turned out that this could be a problem related to the IPv6 configuration. I disabled this setting and everything started working fine
Maybe it will also help you.
UPDATES
You can find this settings
Updated 28/10/2022 This problem I can resolved!!!!!
Today, I tried to clean install macOS Ventura (by backup internal storage => erase internal storage => install macOS Ventura by bootable drive and recovery data from backup hard disk)
All commands worked normally!
If you found a problem like this, you can resolve by clean install macOS!
When updating raspbian on my PI3 some package failed and after that, reboot failed.
The green led doesn't even give a "blink" and nothing on the screen.
So I think I have to reinstall it. But then the whole card will be formatted.
As I have some measurements on the card I want to know if there is a way to restore the database on a new installation.
The card seems ok as I can read all files on it. I just have to copy /var/lib/influxdb to another computer.
But is it then possible to restore the data to a new installation?
Well, I solved it.
I copied the influx directory (recursively)to another computer.
I installed a new OS on my PI3.
I copied the directory, again recursively, to /var/lib/on the new OS.
I Installed influxdb and started InfluxDB. Voila! The data was there!
Happy I am.
Thank's for watching!
WSL2 stopped working suddenly. If I do a new installation of linux distros. Then it throws the following error, when I click launch button for the linux distro from play store:
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070003
Error: 0x80070003 The system cannot find the path specified.
the wsl --help command works properly. All other wsl command hangs or throws error as shown below
like wsl -l command throws this error
The system cannot find the path specified.
I had the same thing happening to me after I moved the directory of my distro.
You have to unregister the distro from WSL;
wslconfig /u Ubuntu-20.04
and then just execute the installed exe and install the whole distro to WSL again.
I had to reinstall the windows to fix the issue. Something got corrupted in the OS. However, before reinstalling the OS as I had lot of work stored in the WSL2, I took the backup of the entire WSL2 image, the big .vhdx file. This file is the Virtual Hard Disk of WSL2 Linux. The files inside cannot be directly explored from Windows at the moment.
If one has not moved the file anywhere else, it is stored here: %LOCALAPPDATA%\Packages\<PackageFamilyName>\LocalState\ext4.vhdx
Before reinstalling the OS, after taking the backup, I wanted to test if this backup runs fine on new install of WSL2. For that, I tested it on another machine, by installing the same Ubuntu WSL2 distro and replacing the .vhdx file created with the backup file. It ran fine.
So, it felt safe to do entire OS reinstall and then reinstalling WSL2 Ubuntu and finally replacing the .vhdx file with the old backup .vhdx file. So, I did loose some time. But, my data and all the applications/programs on WSL2 were intact.
I know this is old but I had the same problem after deleting a driver associated with Hyper V and fixed it by uninstalling the virtual machine platform and Windows Hypervisor along with WSL, rebooted, reinstalled all 3 and then I could install Ubuntu again
This is my first answer on stack overflow and English is not my first language.
So, I will answer this question in images. My solution would not delete the date in any existing installed Linux distribution, at least for me.
Hope you can solve this problem successfully.
enter image description here
enter image description here
enter image description here
"Enable" Virtualization from your bios settings.
Settings may differ from bios to bios (search for your machine options)
Just installed (copied over the app from the downloaded dmg) DevCenter 1.6 on my mac, running macOs Sierra 10.12.6 with jdk 8u152 installed. The application loads a UI (splash screen then a couple of checkboxes in a window for getting started) but the UI is frozen (with the splash screen still there). No response to mouse clicks or keyboard. Also can't click on the app name in the menu bar. The app however is not labeled "Not responding" by activity monitor.
So far I've tried -
Looking at the logs both in the app folder and in ~/.devcenter. Nothing fishy there
Running the app from a different user account - same issue there
Deleting all datastax and devcenter related files (searched by name) on my machine and fresh start - still the same issue
any ideas what I could do here?
I was running DevCenter on a previous mac with the same config / os version but a slightly older JDK, never had issues then.
On OSX, you can specify which version of Java DevCenter uses so that you do not need to downgrade your global Java version.
Right-click on Devcenter.app
Click "show package contents"
Open Contents/info.plist
At the bottom of the file, there's an Eclipse key with lines commented out explaining how to specify the version of Java. Uncomment the line and specify the version of Java that you want DevCenter to use.
Save & Re-launch DevCenter
The updated info.plist file should look something like this:
<key>Eclipse</key>
<array>
<string>-vm</string><string>/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java</string>
</array>
I reached out to someone at Datastax and learnt that complaints have surfaced about this behavior when using DevCenter with jdk 8u152.
For now, I've downgraded to jdk 8u151 and that fixes the issue.
Without downgrade the Java version
Scenario
I couldn't create any connection and press buttons and everything was frozen; Changing the swt plugin in the DevCenter plugin folder worked. This was my configuration:
DevCenter version DevCenter-1.6.0-macosx-x86_64
Mac OSX version 10.14.6
JDK Version jdk1.8.0_231.jdk
Steps to fix it
From here download the version 3.108.0. (This version works for me)
Rename the file downloaded as swt.jar (short name)
[Optionally] create a backup of the current swt plugin jar of the DevCenter
cp DevCenter/DevCenter.app/plugins/org.eclipse.swt.cocoa.macosx.x86_64_3.103.2.v20150203-1351.jar ~/Desktop
Replace the plugin with the swt.jar downloaded
mv swt.jar DevCenter/DevCenter.app/plugins/org.eclipse.swt.cocoa.macosx.x86_64_3.103.2.v20150203-1351.jar
Startup DevCenter
Finally it worked
When I try to launch VM in Oracle VirtualBox on Windows 10 it says "Cannot access the kernel driver". I tried complete reinstall (remove everything and install), repair installation (repair in the installer) and installing 2 drivers manually (VBoxUSBMon and VBoxDrv). Nothing worked. I'm using VirtualBox 4.3.12 because I was not able to launch newer version on Windows 10 for some reason.
The problem is with the installer. The new location of the driver is at C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.sys. However the installer points to the old driver location of C:\Program Files\Oracle\VirtualBox\VBoxDrv.sys.
To fix the problem you need to point the registry value to the new location. Step to do that:
Close VirtualBox
Open regedit.exe from the Start Menu
Navigate to HKEY_LOCAL_MACHINE\system\currentcontrolset\services\vboxdrv
Double click the name ImagePath
Change the value from \??\C:\Program Files\Oracle\VirtualBox\VBoxDrv.sys to \??\C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.sys
Restart VirtualBox
I found this answer in the VirtualBox Forum
I went to Control Panel > Programs and Feature (or right click Windows logo) then selected Oracle VM VirtualBox(4.3.12) and then hit repair at the top.
I restarted then it worked!!
Im running windows 10.0 Home
Downgrade to VirtualBox 4.3.10.
This worked fine for me after trying all that is mentioned above.
Download an old copy of your Virtualbox installer (make sure it's the
same version!)
Run the installer
Select "Repair"
Reboot
Uninstall the old version
Install the new version
Hope it helps!
I have VirtualBox 4.3.14 and I got the "Cannot access the kernel driver" . I did the traditional repair ,reboot and didn't solve a thing.
After a manual installation of these drivers everything works again.
Go to
C:\Program Files\Oracle\VirtualBox\drivers\USB\filter
Select VBoxUSBMon.inf and click the right mouse button. Then pick Install.
Go to
C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv
Select VBoxDrv.inf and click the right mouse button. Then pick install.
VirtualBox should now work again as expected.
I hope this helps ! :D
Just faced this problem after updating to virtual box 6.1.2 version in windows.
The answer by AllanT worked for me, except that it required one more step:
Execute this from the command line as admin: sc.exe start vboxdrv
(restarting the vbox service was not enough).
Note: I would've added this as a comment to AllanT's post but I still don't have enough rep!
You can open the CMD as admin and locate the folder that you have the Oracle Virtual Box in and run each of the the following with your Virtual Machine's name, if you are using an iso file or a vmdk:
cd "C:\Program Files\Oracle\VirtualBox\"
VBoxManage.exe modifyvm "Your VM Name" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
VBoxManage setextradata "Your VM Name" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3"
VBoxManage setextradata "Your VM Name" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata "Your VM Name" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Iloveapple"
VBoxManage setextradata "Your VM Name" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
VBoxManage setextradata "Your VM Name" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1
Make sure to replace "Your VM Name" with "Your actual VM name".
For more on the latest OS X check an example here: https://techsprobe.com/6-step-install-macos-catalina-on-virtualbox-on-windows-pc/
Just wanted to add, I had this problem on Windows 10. None of the fixes I found worked. Turned out it was due to Trusteer Endpoint Protection, which once uninstalled fixed this perfectly.
This is because VirtualBox gets confused about some of their files and settings. When i updated my VirtualBox to 6.0.14 from 6.0.10 then i got this error.
In my case i just deleted C>Username>Program Files>Oracle>VirtualBox folder. And after that i uninstalled VirtualBox from my machine.
After these steps i did a simple fresh install of VirtualBox on my machine and this solves my issue. Hope you also got some help.
Have a nice day random man and great future..
I faced the same issue. I am not sure which file was missing. Uninstall and install worked for me :)