From: Cornelia Huck <cohuck@redhat.com>
To: qemu-s390x@nongnu.org
Cc: Cornelia Huck <cohuck@redhat.com>, qemu-devel@nongnu.org
Subject: [PATCH 2/3] docs/s390x: document 3270
Date: Tue, 5 May 2020 15:50:24 +0200 [thread overview]
Message-ID: <20200505135025.14614-3-cohuck@redhat.com> (raw)
In-Reply-To: <20200505135025.14614-1-cohuck@redhat.com>
Add some basic info how to use 3270 devices.
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
---
docs/system/s390x/3270.rst | 32 ++++++++++++++++++++++++++++++++
docs/system/target-s390x.rst | 1 +
2 files changed, 33 insertions(+)
create mode 100644 docs/system/s390x/3270.rst
diff --git a/docs/system/s390x/3270.rst b/docs/system/s390x/3270.rst
new file mode 100644
index 000000000000..e367a457e001
--- /dev/null
+++ b/docs/system/s390x/3270.rst
@@ -0,0 +1,32 @@
+3270 devices
+============
+
+With the aid of the ``x3270`` emulator, QEMU provides limited support
+for making a single 3270 device available to a guest. Note that this
+supports basic features only.
+
+To provide a 3270 device to a guest, create a ``x-3270device`` linked to
+a ``tn3270`` chardev. The guest will see a 3270 channel device. In order
+to actually be able to use it, attach the ``x3270`` emulator to the chardev.
+
+Example configuration
+---------------------
+
+* Add a ``tn3270`` chardev and a ``x-3270device`` to the QEMU command line::
+
+ -chardev socket,id=char_0,host=0.0.0.0,port=23,nowait,server,tn3270
+ -device x-terminal3270,chardev=char_0,devno=fe.0.000a,id=terminal_0
+
+* Start the guest. In the guest, use ``chccwdev -e 0.0.000a`` to enable
+ the device.
+
+* On the host, start the ``x3270`` emulator::
+
+ x3270 <host>:23
+
+* In the guest, locate the 3270 device node under ``/dev/3270/`` (say,
+ ``tty1``) and start a getty on it::
+
+ systemctl start serial-getty@3270-tty1.service
+
+This should get you an addtional tty for logging into the guest.
diff --git a/docs/system/target-s390x.rst b/docs/system/target-s390x.rst
index 37ca032d98ef..2592a05303ef 100644
--- a/docs/system/target-s390x.rst
+++ b/docs/system/target-s390x.rst
@@ -24,6 +24,7 @@ or vfio-ap is also available.
.. toctree::
s390x/vfio-ap
s390x/css
+ s390x/3270
Architectural features
======================
--
2.21.3
next prev parent reply other threads:[~2020-05-05 13:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 13:50 [PATCH 0/3] s390x: improve documentation Cornelia Huck
2020-05-05 13:50 ` [PATCH 1/3] docs/s390x: document the virtual css Cornelia Huck
2020-05-15 7:04 ` Thomas Huth
2020-05-15 8:51 ` Cornelia Huck
2020-05-15 8:57 ` Thomas Huth
2020-05-15 9:40 ` Cornelia Huck
2020-05-05 13:50 ` Cornelia Huck [this message]
2020-05-15 7:29 ` [PATCH 2/3] docs/s390x: document 3270 Thomas Huth
2020-05-15 9:00 ` Cornelia Huck
2020-05-15 9:14 ` Thomas Huth
2020-05-15 9:45 ` Cornelia Huck
2020-05-15 10:01 ` Thomas Huth
2020-05-05 13:50 ` [PATCH 3/3] docs/s390x: document vfio-ccw Cornelia Huck
2020-05-15 7:54 ` Thomas Huth
2020-05-15 9:15 ` Cornelia Huck
2020-05-14 6:13 ` [PATCH 0/3] s390x: improve documentation Cornelia Huck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200505135025.14614-3-cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).