I figured to call the VM “Android x86_64”, but name it anything you like. When you click “Customize Settings you first get an opportunity to rename your VM to something better. Here we click on “Customize Settings” and not “Finish” as the defaults need to be tweaked for the VM to run better. Select “Legacy BIOS”, not UEFIįor the firmware option, it is recommended to stick to the “Legacy BIOS”. That guest OS type isn’t exactly correct, but it doesn’t matter for getting this to work. iso file you dragged onto it selected and it detected it as “FreeBSD 10 or earlier”. The create a new virtual machine wizardĪs you can see I had installed android earlier. iso file onto the designated area and press the Continue button. In VMware Fusion, from the menu select File -> New.ĭrag your downloaded. So I figured to write this post.įor this post I used the latest release Android 9.0 r1 which you can download from OSDN with this direct link android-x86_ Install Android 9.0 as a VM Getting this to work requires a few additional steps that are not exactly obvious. Hopefully it should now be much more responsive.Thanks to the Android x86 project you can run Android as a VM in VMware Fusion. You can possibly leave it there, but I deleted it. I find that 30 is a good number: ayBuffer = "30""įinally, if you already tweaked the sound.bufferTime parameter with the new hdaudio device, I'm not sure it makes a difference or not. Next, add this line if it is not already present, and experiment with the buffer length. If the line "sound.virtualDev = "hdaudio"" is present, change it to "sound.virtualDev = "es1371"" Bring up the context menu, find "open with" and open it in your favorite text editor. vmwarevm package, and bring up the context menu. Shut down your virtual machine and quit VMware fusion. Find "install" in the context menu, and press enter on it. Locate the file "vmaudio.inf", and press shift+f10 (or right click) on it.ĩ. "VMware\VMware Tools\VMware\Drivers\audio\Vista"Ĩ. Within this directory navigate to the following path: Using Windows explorer, go to the directory where you extracted the VMware tools. Follow the instructions on screen, and extract to a folder of your choosing.ħ. Run this command on the drive your VMware tools install is mounted:Ħ. I like to type "D:" to get to my cd-drive, but you can also type the path directly. Open up a command prompt (windows key+r, then type "cmd")ĥ. Go to the menu bar > Virtual Machine >Reinstall VMware Tools, and dismiss the auto-play notification or the setup dialog if they appear.Ĥ. vmwarevm package somewhere else, just in case you need to revert later.ģ. While it's shut down and VMware fusion is closed, back up your virtual machine by storing a copy of your. If there are quotes within the quotes, you do have to include those when you copy the text.ġ. NB: Whenever something is between quotes, assume that everything between the quotes has to be copied or executed. This makes my Windows 10 run like my Windows 7 VM latency-wise, and I figured everyone else could use this info, so here goes (note: This worked for me, but I'm not responsible if your audio breaks): Changing the buffer time didn't make a huge difference, but now I've found a way to install the VMaudio driver and revert to the old es1371 audio device so I can lower the latency. Ever since I changed to using Windows 10 in my VMware Fusion virtual machine, I've struggled with a fair bit of latency and audio problems when using the standard HDAudio device.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |