Virtual machine console access
There is no VMConnect capability for console access to the VM as there is with Hyper-V.
So in the situation where I lost connectivity, by misconfiguration, or system failure, is there only one very time and bandwith consuming way to fix it - download the VHDs on-premise, boot it in Hyper-V and VMConnect to repair VM, then upload all GBs back to the Azure...
I requesting console access, also with ability to mount some image for repair and boot from it (as we do it in standard environment).
Last week, still don't know why it happened, we had a problem connecting to one of our VMs. We ended up removing and recreating it. I wish we can connect via console connection, just like how we can with our on prem VMM.
We will likely start with serial output information, first, and see how much that helps.
Chris Barth commented
Serial output information would probably not help very much. If the firewall was misconfigured to block RDP, the download VHD option is still the only one.
What would be useful, and perhaps just as easy as serial output, is a command prompt or PowerShell console that we could interact with via windowsazure.com (similar to Server Core). It could work like a web-based chat program. The 'chat window' could also show the messages from a boot-time, like "OS boot information" and verbose startup and shutdown messages.
Having a way to see and interact with the console would really help improve the confidence I and others have with having vm's with critical applications in azure.
it's also pretty soul-destroying when a reboot (which normally takes a few minutes) hasn't come back up 15 minutes later because the Event Notification Service has hung on shutdown... and you can't tell if it's going to come back up or not.
We absolutely need console access. I locked myself out due to RDP licensing issues and could not fix the issue.
Please, I need console access to Azure VM. Today I got alert error journaling from one of my production linux vm on Azure, all partition are in read only mode, I need to reboot it and do the fsck -fy (with option Yes), but it is impossible for now in Azure. I still have other more than 10 vms on Azure, I can't imagine how long the troubleshoot process will take time if there is no Console access. Really really need Console access!
Shahin Kohan commented
This is really needed. Sometimes the server gets a blue screen of death. The admin can not troubleshoot this issue without some access to the console.
It seems really odd to not be able todo such a basic item..
Any progress on this?
Steven Ao commented
Not acceptable to have no console access.
Without Console access to VM's its very difficult to maintain these Azure VM's.
Any updates when console access will be given ?
I did stumbled on this http://www.hyper-v.nu/archives/marcve/2013/09/windows-azure-pack-console-connect/ and looks like console access is intentionally disabled for tenants.
Matt Cain commented
Any progress on this?
Not having console access puts a damper on uploading your on-prem vhd's created in Hyper-V as the machines will not have network ability once uploaded to Azure.