I've downloaded and extracted the vmnetcfg.exe and vmnetcfglib.dll following this guide
But when I click the file to open it nothing happens.
Running as admin doesn't work as well.
VMWare player 6.
vmnet extracted from workstation 10.
Running windows 8.1
Solved by downloading VMware 6.03 (link)
And then downloading the missing vmnetcfg.exe & vmnetcfglib.dll from HERE
Related
I installed MacOS 10.15 "Catalina" on VMWare Workstation Player in Windows 10 as host.
Now I want to install VMWare Tools so I clicked Player -> Manage -> Install VMware tools but I got this error:
I am using this version of player:
VMware® Workstation 15 Player
15.5.2 build-15785246
You can download the latest version here:
https://packages.vmware.com/tools/releases/latest/windows/x64/
Notice this folder is for Windows x64, browse for your OS, if different.
Download to your VM and install... then close the VM to get everything in sync.
Goal
I was attempting to install Elastix 4.0 on a home PC via a Bootable USB, but never had any luck getting it to install past the CentOS7 part (it kept giving me a "Warning: /dev/root does not exist" error).
What I've Tried
My main PC is Windows 10 Pro, so after downloading the latest Elastix 4.0 .iso from "http://www.elastix.com/en/downloads/" (Elastix-4.0.74-Stable-x86_64-bin-10Feb2016.iso) I used UNetbootin to create my Bootable USB for Elastix 4.0. I put the now Bootable USB into the PC I want to put Elastix 4.0 on and started it up.
It gave me the "Install Elastix 4" menu, so I hit enter and waited. Then the install proceeded to do its checks for CentOS7, but ended up getting stuck and gave me an error message "dracut-initqueue[580]: Warning: Could not boot." and "Warning: /dev/root does not exist".
This is where I am stuck and cannot proceed.
EDIT #1: I signed up for the Elastix forms, and someone else also had this issue. They said they downloaded the .iso and used Rufus to make a Bootable USB, and then booted the installation using the Troubleshooting -> Install CentOS 7 using Basic Graphics ... but according to them, that apparently corrupted something else and then they opted to just use a DVD.
EDIT #2: I tested this, and making a Bootable DVD of the .iso does work great for local machines. Installing it via a VM also seems to work without hassle. As a personal goal, I would like to get this working via a Bootable USB.
Research
I did some research but a lot of the solutions I've noticed are using the dd command in Linux to make a Bootable USB for just CentOS7 because it is (was?) known that UNetbootin did not properly make a Bootable USB for CentOS7, and I can't seem to find anything that would assist in making the Elastix 4.0 .iso work properly via a Bootable USB. I did try other tools such as Rufus 2.7, Win32 Disk Imager, ISO2USB, and dd for Windows, though most rendered my USB not bootable at all (Rufus worked OK, but still got stuck at the CentOS7 part). Also, installing via a CD/DVD is not ideal, as I have no CD/DVD drive (and I want to see if I can get this working via a Bootable USB drive).
There seem to be a few guides out there for trying to create a Bootable USB for Elastix 2.x, but nothing for Elastix 4.0. Reviewing those, it looks like the guides reference some files that do not exist in the new .iso (ex: ks_default.cfg). Still, my issue pertains mainly to the CentOS7 error I'm getting so I don't think this is related.
Any assistance with this is appreciated, and if you require more information from my end just let me know. I'm willing to try / re-try anything.
Thank you in advance.
http://henrysittechblog.blogspot.ru/2014/01/install-elastix-from-usb-step-by-step.html
Look for this line, but it may change:
append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=cdrom:/dev/cdrom:/ks/anaconda-ks.cfg quiet
Change it to:
append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=sdb1:/dev/sdb1:/ks/anaconda-ks.cfg quiet
Hi there i solve this problem 80%.
i did some manual change at line:
inst.ks=cdrom:/dev/cdrom:/ks/anaconda-ks.cfg quiet
Mine:
inst.ks=scsi:/dev/sdb1:/ks/anaconda-ks.cfg quiet
hd is not recogniced by Centos7.
made my usb bootable with rufus 2.9
then open isolinux.cfg with notepad++
just change the line
inst.ks=hd:sdb1:/ks/anaconda-ks.cfg quiet
where sdb1 used to say cdrom
After installing Xamarin studio and Xamarin android player along with Oracle VirtualBox. I have created demo code and installed Nexus 4 (kitkat) virtual device in Android player but after running application Xamarin Android player gets started but got following window with error.
This worked for me:
Network Connections -> Right click VirtualBox Host-Only Network -> Properties -> Enable (or Disable then Enable) "VirtualBox NDIS6 Bridged Networking Driver"
I found another question similar to the current question. see it Here
If you are using windows 10 then you need to have latest version of virtual box installed. you can get it from Virtual Box Downloads page.
I hope it helps.
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 :)
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