</p>
<ul>
- <li>If no <code>targetType</code> attribue is set, then the default
+ <li>If no <code>targetType</code> attribute is set, then the default
device type is according to the hypervisor's rules. The default
type will be added when re-querying the XML fed into libvirt.
For fully virtualized guests, the default device type will usually
<li>Only the first <code>console</code> element may use a <code>targetType</code>
of <code>serial</code>. Secondary consoles must all be paravirtualized.
</li>
+ <li>On s390, the <code>console</code> element may use a
+ <code>targetType</code> of <code>sclp</code> or <code>sclplm</code>
+ (line mode). SCLP is the native console type for s390. There's no
+ controller associated to SCLP consoles.
+ <span class="since">Since 1.0.2</span>
+ </li>
</ul>
<p>
</devices>
...</pre>
+<pre>
+ ...
+ <devices>
+ <!-- KVM s390 sclp console -->
+ <console type='pty'>
+ <source path='/dev/pts/1'/>
+ <target type='sclp' port='0'/>
+ </console>
+ </devices>
+ ...</pre>
+
<p>
If the console is presented as a serial port, the <code>target</code>
element has the same attributes as for a serial port. There is usually
VIR_DOMAIN_CHR_CONSOLE_TARGET_TYPE_VIRTIO,
VIR_DOMAIN_CHR_CONSOLE_TARGET_TYPE_LXC,
VIR_DOMAIN_CHR_CONSOLE_TARGET_TYPE_OPENVZ,
+ VIR_DOMAIN_CHR_CONSOLE_TARGET_TYPE_SCLP,
+ VIR_DOMAIN_CHR_CONSOLE_TARGET_TYPE_SCLPLM,
VIR_DOMAIN_CHR_CONSOLE_TARGET_TYPE_LAST
};