Skip to content

Commit d6f79df

Browse files
Modules for connecting to Windows VM via RDP console (over l2 vnic). GUI and CLI methods.
1 parent 0eff7b6 commit d6f79df

File tree

2 files changed

+115
-0
lines changed

2 files changed

+115
-0
lines changed
Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * TBD
4+
5+
[id="cnv-accessing-rdp-console-{context}"]
6+
= Connecting to a Windows virtual machine with an RDP console
7+
8+
The Remote Desktop Protocol (RDP) provides a better console experience for
9+
connecting to Windows virtual machines.
10+
11+
To connect to a Windows virtual machine with RDP, specify the IP address of the
12+
attached L2 vNIC to your RDP client.
13+
14+
.Prerequisites
15+
16+
* A running Windows virtual machine with the QEMU guest agent installed. The
17+
`qemu-guest-agent` is included in the VirtIO drivers.
18+
* A layer 2 vNIC attached to the virtual machine.
19+
* An RDP client installed on a machine on the same network as the
20+
Windows virtual machine.
21+
22+
.Procedure
23+
24+
. Log in to the {ProductName} cluster through the `oc` CLI tool as a user with
25+
an access token.
26+
+
27+
----
28+
$ oc login -u <user> https://<cluster.example.com>:8443
29+
----
30+
31+
. Use `oc describe vmi` to display the configuration of the running
32+
Windows virtual machine.
33+
+
34+
----
35+
$ oc describe vmi <windows-vmi-name>
36+
----
37+
+
38+
[source,yaml]
39+
----
40+
...
41+
spec:
42+
networks:
43+
- name: default
44+
pod: {}
45+
- multus:
46+
networkName: cnv-bridge
47+
name: bridge-net
48+
...
49+
status:
50+
interfaces:
51+
- interfaceName: eth0
52+
ipAddress: 198.51.100.0/24
53+
ipAddresses:
54+
198.51.100.0/24
55+
mac: a0:36:9f:0f:b1:70
56+
name: default
57+
- interfaceName: eth1
58+
ipAddress: 192.0.2.0/24
59+
ipAddresses:
60+
192.0.2.0/24
61+
2001:db8::/32
62+
mac: 00:17:a4:77:77:25
63+
name: bridge-net
64+
...
65+
----
66+
67+
. Identify and copy the IP address of the layer 2 network interface. This is
68+
`192.0.2.0` in the above example, or `2001:db8::` if you prefer IPv6.
69+
. Open an RDP client and use the IP address copied in the previous step for the
70+
connection.
71+
. Enter the *Administrator* user name and password to connect to the
72+
Windows virtual machine.
73+
74+

modules/cnv-vm-rdp-console-web.adoc

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * TBD
4+
5+
[id="cnv-vm-rdp-console-web-{context}"]
6+
= Connecting to the RDP console
7+
8+
The desktop viewer console, which utilizes the Remote Desktop Protocol (RDP),
9+
provides a better console experience for connecting to Windows virtual machines.
10+
11+
To connect to a Windows virtual machine with RDP, download the *_console.rdp_*
12+
file for the virtual machine from the *Consoles* tab in the
13+
*Virtual Machine Details* screen of the web console and supply it to your
14+
preferred RDP client.
15+
16+
.Prerequisites
17+
18+
* A running Windows virtual machine with the QEMU guest agent installed. The
19+
`qemu-guest-agent` is included in the VirtIO drivers.
20+
* A layer 2 vNIC attached to the virtual machine.
21+
* An RDP client installed on a machine on the same network as the
22+
Windows virtual machine.
23+
24+
.Procedure
25+
26+
. In the {ProductName} console, click *Workloads* -> *Virtual Machines*.
27+
. Select a Windows virtual machine.
28+
. Click the *Consoles* tab.
29+
. Click the *Consoles* list and select *Desktop Viewer*.
30+
. In the *Network Interface* list, select the layer 2 vNIC.
31+
. Click *Launch Remote Desktop* to download the *_console.rdp_* file.
32+
. Open an RDP client and reference the *_console.rdp_* file. For example, using
33+
*remmina*:
34+
+
35+
----
36+
$ remmina --connect /path/to/console.rdp
37+
----
38+
39+
. Enter the *Administrator* user name and password to connect to the
40+
Windows virtual machine.
41+

0 commit comments

Comments
 (0)