Accessing virtual machine consoles

In the OKD console, click Virtualization → VirtualMachines from the side menu.

Select a virtual machine to open the VirtualMachine details page.

Click the Console tab. The VNC console opens by default.

Click Disconnect to ensure that only one console session is open at a time. Otherwise, the VNC console session remains active in the background.

Click the VNC Console drop-down list and select Serial Console.

Click Disconnect to end the console session.

Optional: Open the serial console in a separate window by clicking Open Console in New Window.

In the OKD console, click Virtualization → VirtualMachines from the side menu.

Select a virtual machine to open the VirtualMachine details page.

Click the Console tab. The VNC console opens by default.

Optional: Open the VNC console in a separate window by clicking Open Console in New Window.

Optional: Send key combinations to the virtual machine by clicking Send Key.

Click outside the console window and then click Disconnect to end the session.

In the OKD console, click Virtualization → VirtualMachines from the side menu.

Click a Windows virtual machine to open the VirtualMachine details page.

Click the Console tab.

In the Console list, select Desktop Viewer.

In the Network Interface list, select the layer-2 NIC.

Click Launch Remote Desktop to download the console.rdp file.

Open an RDP client and reference the console.rdp file. For example, using remmina:

$ remmina --connect /path/to/console.rdp

Enter the Administrator user name and password to connect to the Windows virtual machine.

Run the following command to create the fedora-vm-ssh service:

$ virtctl expose vm <fedora-vm> --port=22 --name=fedora-vm-ssh --type=nodeport (1)

Check the service to find out which port the service acquired:

$ oc get svc

NAME            TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)           AGE
fedora-vm-ssh   nodeport   127.0.0.1      <none>        22:32551/TCP   6s

Log in to the VMI via SSH. Use the ipAddress of any of the cluster nodes and the port that you found in the previous step:

$ ssh username@<node_IP_address> -p 32551

In the YAML file for the VM, add the label and a value for exposing the service for SSH connections. Enable the masquerade feature for the interface:

apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
  namespace: ssh-ns (1)
  name: vm-ssh
spec:
  running: false
  template:
    metadata:
      labels:
        kubevirt.io/vm: vm-ssh
        special: vm-ssh (2)
    spec:
      domain:
        devices:
          disks:
          - disk:
              bus: virtio
            name: containerdisk
          - disk:
              bus: virtio
            name: cloudinitdisk
          interfaces:
          - masquerade: {} (3)
            name: testmasquerade (4)
          rng: {}
        machine:
          type: ""
        resources:
          requests:
            memory: 1024M
      networks:
      - name: testmasquerade
        pod: {}
      volumes:
      - name: containerdisk
        containerDisk:
          image: kubevirt/fedora-cloud-container-disk-demo
      - name: cloudinitdisk
        cloudInitNoCloud:
          userData: |
            #cloud-config
            user: fedora
            password: fedora
            chpasswd: {expire: False}
# ...

Create the VM:

$ oc create -f <path_for_the_VM_YAML_file>

Start the VM:

$ virtctl start vm-ssh

In the YAML file for the service, specify the service name, port number, and the target port.

apiVersion: v1
kind: Service
metadata:
  name: svc-ssh (1)
  namespace: ssh-ns (2)
spec:
  ports:
  - targetPort: 22 (3)
    protocol: TCP
    port: 27017
  selector:
    special: vm-ssh (4)
  type: nodeport
# ...

Create the service:

$ oc create -f <path_for_the_service_YAML_file>

Verify that the VM is running:

$ oc get vmi

NAME    AGE     PHASE       IP              NODENAME
vm-ssh 6s       Running     10.244.196.152  node01

Check the service to find out which port the service acquired:

$ oc get svc

NAME            TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)           AGE
svc-ssh     nodeport       10.106.236.208 <none>        27017:30093/TCP   22s

Run the following command to obtain the IP address for the node:

$ oc get node <node_name> -o wide

NAME    STATUS   ROLES   AGE    VERSION  INTERNAL-IP      EXTERNAL-IP
node01  Ready    worker  6d22h  v1.23.0  192.168.55.101   <none>

Log in to the VM via SSH by specifying the IP address of the node where the VM is running and the port number. Use the port number displayed by the oc get svc command and the IP address of the node displayed by the oc get node command. The following example shows the ssh command with the username, node’s IP address, and the port number:

$ ssh fedora@192.168.55.101 -p 30093

Connect to the graphical interface with the virtctl utility:

$ virtctl vnc <VMI>

If the command failed, try using the -v flag to collect troubleshooting information:

$ virtctl vnc <VMI> -v 4

Log in to the OKD Virtualization cluster through the oc CLI tool as a user with an access token.

$ oc login -u <user> https://<cluster.example.com>:8443

Use oc describe vmi to display the configuration of the running Windows virtual machine.

$ oc describe vmi <windows-vmi-name>

...
spec:
  networks:
  - name: default
    pod: {}
  - multus:
      networkName: cnv-bridge
    name: bridge-net
...
status:
  interfaces:
  - interfaceName: eth0
    ipAddress: 198.51.100.0/24
    ipAddresses:
      198.51.100.0/24
    mac: a0:36:9f:0f:b1:70
    name: default
  - interfaceName: eth1
    ipAddress: 192.0.2.0/24
    ipAddresses:
      192.0.2.0/24
      2001:db8::/32
    mac: 00:17:a4:77:77:25
    name: bridge-net
...

Identify and copy the IP address of the layer 2 network interface. This is 192.0.2.0 in the above example, or 2001:db8:: if you prefer IPv6.

Open an RDP client and use the IP address copied in the previous step for the connection.

Enter the Administrator user name and password to connect to the Windows virtual machine.