diff options
| author | Farhan Ali <alifm@linux.vnet.ibm.com> | 2018-02-22 11:22:24 -0500 |
|---|---|---|
| committer | Christian Borntraeger <borntraeger@de.ibm.com> | 2018-03-14 19:21:17 +0000 |
| commit | 258400304225a219a2d98f29fe957df98789a843 (patch) | |
| tree | 8b8e47814888b5b14b1d99fdd2d225c175d9955d /arch/s390/kvm | |
| parent | daea5469e184209420770fcf47f3db3d7a6d04ee (diff) | |
| download | op-kernel-dev-258400304225a219a2d98f29fe957df98789a843.zip op-kernel-dev-258400304225a219a2d98f29fe957df98789a843.tar.gz | |
s390/setup: enable display support for KVM guest
The S390 architecture does not support any graphics hardware,
but with the latest support for Virtio GPU in Linux and Virtio
GPU emulation in QEMU, it's possible to enable graphics for
S390 using the Virtio GPU device.
To enable display we need to enable the Linux Virtual Terminal (VT)
layer for S390. But the VT subsystem initializes quite early
at boot so we need a dummy console driver till the Virtio GPU
driver is initialized and we can run the framebuffer console.
The framebuffer console over a Virtio GPU device can be run
in combination with the serial SCLP console (default on S390).
The SCLP console can still be accessed by management applications
(eg: via Libvirt's virsh console).
Signed-off-by: Farhan Ali <alifm@linux.vnet.ibm.com>
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-Id: <e23b61f4f599ba23881727a1e8880e9d60cc6a48.1519315352.git.alifm@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/s390/kvm')
0 files changed, 0 insertions, 0 deletions
