As the picture displayed, select the Apply Windows key combinations on the remote computer when you directly connect to the remote Azure VM with the remote desktop connection. Currently, Azure Bastion also does not help direct the windows key to the remote VM.Īs a workaround, you can use the Windows key shortcuts on the remote VM via KeyBoard redirection on the remote desktop connection. In fact, in this case, you are not directly connecting to the remote VM in an RDP session. When you connect to remote VM via Azure Bastion, Azure Bastion uses an HTML5 based web client that is automatically streamed to your local device, so that you get your RDP/SSH session over SSL on port 443 enabling you to traverse corporate firewalls securely. It provides secure and seamless RDP/SSH connectivity to your virtual machines directly in the Azure portal over SSL. You may even delete the line calling virsh, as the domain may be started from the virt-manager console.I don't think there is a way to use the Windows key shortcuts on the remote VM via the Azure Bastion connection as the Azure Bastion service is a new fully platform-managed PaaS service. QEMU/KVM) and then using "Details" in the context menu.
The result will be the same: Windows Task Manager will start: Tags: ctrl alt del windows 7, ctrl alt del, windows 7 CTrl Alt Delete Screen, ctrl alt del screen windows 7, windows 7 CTRL ALT DEL screenshot. The connection URI may be found in the virt-manager main window by selecting the respective connection (e.g. Right-click on empty space in your Windows 7 taskbar and select Task Manager, like on the picture below: 2. in my script this would be /usr/bin/virt-manager -connect=qemu:///system -show-domain-console $1 If you really need the console window of virt-manager, just call it like virt-manager -connect= -show-domain-console Į.g. Especially, if the domain is not known to virsh or fails to start, virt-viewer will probably wait forever. There is no error handling in the script you may add some if necessary. It will start the domain (if not already started), then start virt-viewer to connect with this domain.Ī sample desktop file (sktop) Įxec=~/scripts/StartVirtDomain.sh Win7Proĭid the job (domain name is Win7Pro). You may call it with the name of the domain as parameter.
Virt-viewer should be installed with virt-manager if not, sudo apt-get install virt-viewer. usr/bin/virt-viewer -w $1 # -w to wait until domain is running. usr/bin/virsh start $1 # domain must be known to virsh # call this script with domainname as parameter I wrote a small script "~/scripts/StartVirtDomain.sh" #!/bin/sh You can also add the command directly to the menu with the parameters, but often it is easier for debugging problems to get the command running in the command line as a script. $ chmod u+x ~/bin/run-vmĪnd, then you should be able to add this command to your menu - see for example Answer on Unix and Linux Stackoverflow site. Virt-manager -connect qemu:///system -show-domain-console win7 If that works, you should be able to put it in a simple script $ cat > ~/bin/run-vm $ virt-manager -connect qemu:///system -show-domain-console win7 Where URI and name are where you got them from above. $ virt-manager -connect > -show-domain-console >
Use the virt-manager to find the "Libvirt URI" (select the VM, Edit -> Connection Details), then the name of the VM (select the VM, Edit -> Virtual Machine Details - if you have the machine open, you will have to make sure it is not maximized, then View -> Details, and go back to the Console when you're done.)