I have installed Android Studio in Windows 2012 Server machine on Google Cloud. But, I cannot run Emulator on it. It shows the below error.
"HAXM doesn't support nested virtual machines"
Consider that nested virtualisation is not enabled out of the box for Compute Engine instances.
Therefore you need to enable it manually, however it is not available yet for Windows instances as you can check in the documentation page:
Nested virtualization does not currently support Windows instances.
Related
I am currently working form home for an organisation.
Is it possible to run Android Emulator via Android Studio on a Virtual Desktop which has Windows 10 installed.
Also, should I keep my specs low for the Emulator, as I have enough RAM in my VDI.
And do I need to ask the organisation to enable Virtualization in the Virtual Machine, As it may not be possible for me to do so. Or, there is no such things in Virtual Machines?
Currently, When I try to run Emulator, it just gets stuck on black screen forever and timeouts.
I have tried multiple options. But none of them works.
No, after digging in a lot.
It was Azure VDI, windows 10.
And it's not possible to run a virtual machine (Android Emulator) inside another virtual machine.
It may be possible to run in another OS.
But not on Windows which asks to enable Hyper-V.
Which won't allow installation of Intel HAXM.
Our goal is to run UI tests with Appium on our CI build. But it seems that running the Android emulator (Hyper-V based) within virtual build machine (Windows Server 2016) on Azure might not be supported.
So my question is, does Hyper-V based nested virtualization is supported from a Windows Server 2016 virtual machine on Azure ?
note: using a CPU Android emulation is not an option
Yes, it is possible, you need to be on Dv3 or Ev3 SKU.
https://learn.microsoft.com/en-us/azure/virtual-machines/windows/nested-virtualization
I have a vm created in Azure, Windows Server 2012, x64 with Visual Studio 2015.
I'm trying the Weather application example from the site https://taco.visualstudio.com/en-us/docs/get-started-first-mobile-app/
When I try to start the application running the emulator VS Emulator 5 KitKat (4.4) I have errors with internet connection but I actually can connect to the internet.
Just after launch the application I get this message:
I hit Accept and then, after display the screen, I get next messages (Although the message is talking about Hyper-V, i´m using my MSDN account and Azure)
When I try to start the application running the emulator VS Emulator 5 KitKat (4.4) I have errors with internet connection but I actually can connect to the internet.
VS Emulators run as Hyper-V Virtual Machines. And if you are already in a Windows Server 2012 VM environment, it is not possible to to start another VM inside of it.
In Windows Server 2016 or Windows 10 VM it is possible to start an VM inside. For details, please refer to Enable Nested Virtualization.
I think I misunderstood the whole Azure development concept. I thought I could run the Visual Studio IDE within Internet Explorer or something along those lines.
You can, but you'll use an RDP client (like mstsc.exe) instead of internet explorer. You can create a Virtual Machine in Azure that has visual studio installed on it and develop on that VM. There are a number of images already in the platform that support this scenario if you're an MSDN subscriber, I believe.
Even if you're not an MSDN subscriber, you can create a VM and set it up for development yourself. Then you can use your remote desktop client to log into that machine from anywhere and develop on it instead of your local box. This isn't limited to a Window dev env't either, of course.
I use this in scenarios where I have a constrained laptop but good connectivity and a desire to get some work done. You could use this to develop with a full IDE from a Surface RT, e.g. :)
I think I misunderstanded the whole Azure development concept, I
thought I could run Visual Studio IDE within Internet Explorer or
something
Azure is a web hosting environment in a nutshell. I think you are talking about Visual Studio Online in which you can run VS IDE inside browser.
Once you finish writing code in Visual Studio Online, you can deploy it to Azure.
Visual-Studio-Online-Monaco
channel9 - Visual Studio Online Monaco
Windows 7, VS2012-Update1, x64.
If i start e new MVC-project, and add the Azure project to it. I can't debug it locally in the azure emulator.
The error:
Operation taking longer than expected
A 64-bit debugging operation is
taking longer than expected. This may be caused by incompatibilities
with 3rd party networking softwar. See help for troubleshooting these issues.
When i Terminate that message (twice):
Windows Azure Tools for Microsoft Visual Studio
There was en error attaching the debugger t the role intances
'deployment18(18).mvctest.Azure.Website_IN_0' with prces Id:'8752'.
Unable to attach. The Microsoft Visual Studio remote debugging monitor
has been closed on the remote machine.
The first message, I already found that if you change your website target to x86 that this can solve the problem. (this solved a problem for debugging unit-tests)
But if I change it to x86, the nex message pops up:
Windows Azure Tools for Microsoft Visual Studio
Cannot start debugging. The role was built for a platform incompatible with the windows azure compute emulator. On this system the compute emulator supports anyCPU and x64.
If i start without debugging (not x86), the windows emulator starts, and the website opens.
Is there a solution to solve this that we can debug x64 websites on the azure emulator?
Thanks.
Problem solved:
The issue was, that oour normal account didnt had admin privileges, and that we had to use an other admin user his credentials to run it in admin mode.
If i logged on with that admin user and started everything, that user couldn't also load the azure emulator.
Every co-developer had the same issue.
But when the normal account had back the admin privileges, the emulator started normally.
So i assume that there was something missing for those admin account (what i don't know)
Ensure that the remote debugging service and the machine debug manager (for x64) are properly installed and running (services in Automatic, especially not disabled).
You can also try to download and reinstall the remote debugging tools following instructions here
Even if it is on the same machine, chances are that debugging for the emulator goes through the remote debugging path
Been googleing this for a while now and it looks like the problem is connected to network drivers installed on windows. Do you have a VPN installed? Uninstall it and try again.
Otherwise it could be some of the network card drivers. Same here, uninstall and try again.
Some people have solved this by upgrading visual studio.