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).
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
It would be nice to have a virtual console (terminal/shell) that hooks unto the VM for troubleshooting purposes. If the hosted OS has a wrong configuration that prevent a VM from booting up, a virtual console will help the SA to use it to log in and fix any config issue. When VM cannot boot up, ssh or rdp becomes useless.
A month ago I tweeted Corey about this topic. He mentioned that there will be news "soon": https://twitter.com/CoreySandersWA/status/855139996847755265
It is insane that this is still not a thing. Virtual console access is a _basic functional need_ for VMs.
We are evaluating Azure but are also missing console Access. Having to download, fix and upload vhd's is waisting valuable time when you need to repair a business critical vm. So we need to deploy our vm's in an availability set to ensure uptime of our service?
Scott Ragen commented
Is there any update on this?
I have a small environment where the DC was blue screening on boot (second time in two years i've had to fix a persistent BSOD). This time I needed to reboot it in safe mode with domain services repair to fix. To accomplish this (other than restoring from offsite backup) I had to to delete the vm (this is another pet peeve as you can't detach a system disk from an existing vm!). Then create another vm attaching the original as a secondary disk, using bcdedit to boot into safe mode dsrepair. detach, create a new vm with the safe mode image and remote into it to fix. I'm lucky that dsrepair enables networking otherwise I would have had to restore from backup.
Note to the other two asking for port opening/disabling modprobe, it can be accomplished similarly, if not more easily with the method I mentioned, mount & modify the config files. Not ideal, but it does work.
We are going to migrate over 500 VMs to Azure. Not having a console access, makes it very hard and in some cases impossible to troubleshoot an OS issue. For example, over the weekend, we wanted to run an OS upgrade on few of our Azure VMs so we can configure Azure backup for the VMs. I tired on one VM and failed. Because I lost RDP access to the VM in the middle of the upgrade. I had to roll back to the on-prem VM. Please add console access to Azure VMs
Preetpal Sohal commented
This is honestly pretty vital (please add this urgently). Like for example there are some filesystem setting changes (like using `tunefs` to enable/disable trim on UFS2 in FreeBSD (which you would need to use to upgrade a VM to use solid state drives)) you cannot do unless you boot into single-user mode (where network access is not available and virtual machine console access would be vital). There are also situations such as botched OS upgrades that would require console access as well. Also note that if you improperly configure the Firewall on a VM or have some other configuration mishap related to your server's SSH service configuration, you would benefit greatly from being able to resort to console access. So please add this feature urgently as it would make configuration changes to Virtual Machines less stressful.
Jayadeava B commented
We had raised two support cases for Redhat Linux VMs with MS support team and issue fixed only after recreating the VM with the fixed OS disk.
This is not the best solution or user-friendly approach by MS.
Please provide console access granted for the respective subscription owner at least.
This way, we could solve most of the issues related to ssh, fsck errors, system booted into maintenance etc.
MS team, please hear our pains and solve as soon as possible.
Michael Banks commented
This really is kind of amazing. They have the capability to do this in Hyper-V. Why not in Azure
when something goes wrong you need a console
it would be great to such a task that simulate the connection to a KVM console to monitor the machine during the bootstrap process the same way we see it using ILO management interfaces
This one issue alone makes Azure a non-starter for us.
Brad K commented
This amazes me. A multi billion dollar company like MS can't implement console access even though every paying customer is asking for it. I love my vmware environment but it seems like the bean counters want to move away from a tried and true technology that has worked flawlessly for the last decade to "azure". In the middle of trying to upgrade to windows 2016 which I had no issues doing in my vmware environment only to end up here- searching as to why I can't console in to click an accept button. What a waste of time this exercise was, time to restore.
Did console access every get implemented?
Admin Spotcrowd commented
I need to run one command to re-open the SSH port in my UFW firewall.
How do I do that? I cannot access my VM at the moment
While PowerShell Direct is nice, console access really is a necessity. Something that does not depend on the guest running - to diagnose and repair any pre-boot issues (e.g. resulting from a failed update). Even better if it supports booting from an uploaded (e.g. ISO) image. Something like the out-of-band remote access provided by IPMI/KVM-over-IP (e.g. iDRAC, ILO) and standard hypervisors (VMware/ESXi, Hyper-V, etc.).
Sample on fail on Azure Linux VM and wont boot.
[[0;32m OK [0m] Started ifup for eth0.
[[0;32m OK [0m] Started Raise network interfaces.
[[0;32m OK [0m] Reached target Network.
Starting Initial cloud-init job (metadata service crawler)...
[ 25.364088] blk_update_request: I/O error, dev fd0, sector 0
So how to blacklist floppy (modprob / initramfs) without a console or download and then upload the VM
Dirk Gillis commented
"I don’t have a timeline but we know this is critical" and 1330 days later still nothing. In Exchange we are already waiting 15 years for some feature requests (like OOF automation).
Time for action instead of words.
Most needed feature request which would help us during incidents with VMs would be a proper bi-directional console access to VMs.
At the moment console access is only one way with screenshots & serial output, but it does not help when any config change is needed to get recovered.
Aws does not have console access either. Just a log