[2.5] s390x VM creation is broken due to serial console logging

I tried creating a VM with virt-manager on an s390x system that had a serial device outputting to a file. virt-manager threw this error when trying to start the installation of the machine:

Unable to complete install: 'internal error: qemu unexpectedly closed the monitor: d set=2,fd=30 -chardev file,id=charserial0,path=/dev/fdset/2,append=on -device sclpconsole,chardev=charserial0,id=serial0 -chardev pty,id=charconsole1 -device sclpconsole,chardev=charconsole1,id=console1 -device virtio-balloon-ccw,id=balloon0,devno=fe.0.0002 -msg timestamp=on
2019-01-17T02:45:29.877709Z qemu-system-s390x: -device sclpconsole,chardev=charconsole1,id=console1: Multiple VT220 operator consoles are not supported
2019-01-17T02:45:29.877728Z qemu-system-s390x: -device sclpconsole,chardev=charconsole1,id=console1: SCLP event initialization failed.'

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/create.py", line 2553, in _do_async_install
    guest.start_install(meter=meter)
  File "/usr/share/virt-manager/virtinst/guest.py", line 498, in start_install
    doboot, transient)
  File "/usr/share/virt-manager/virtinst/guest.py", line 434, in _create_guest
    domain = self.conn.createXML(install_xml or final_xml, 0)
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3603, in createXML
    if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
libvirtError: internal error: qemu unexpectedly closed the monitor: d set=2,fd=30 -chardev file,id=charserial0,path=/dev/fdset/2,append=on -device sclpconsole,chardev=charserial0,id=serial0 -chardev pty,id=charconsole1 -device sclpconsole,chardev=charconsole1,id=console1 -device virtio-balloon-ccw,id=balloon0,devno=fe.0.0002 -msg timestamp=on
2019-01-17T02:45:29.877709Z qemu-system-s390x: -device sclpconsole,chardev=charconsole1,id=console1: Multiple VT220 operator consoles are not supported
2019-01-17T02:45:29.877728Z qemu-system-s390x: -device sclpconsole,chardev=charconsole1,id=console1: SCLP event initialization failed.

This seems to be a bug with KVM on s390x as this is not related to MAAS in any shape or form.

This is no really a bug with s390x. Rather, it’s not implemented
functionality for the architecture.

“s390x doesn't support double output to serial console.”

On Thu, Jan 17, 2019 at 4:55 AM Newell Jensen <email address hidden>
wrote:

> I tried creating a VM with virt-manager on an s390x system that had a
> serial device outputting to a file. virt-manager threw this error when
> trying to start the installation of the machine:
>
> Unable to complete install: 'internal error: qemu unexpectedly closed the
> monitor: d set=2,fd=30 -chardev
> file,id=charserial0,path=/dev/fdset/2,append=on -device
> sclpconsole,chardev=charserial0,id=serial0 -chardev pty,id=charconsole1
> -device sclpconsole,chardev=charconsole1,id=console1 -device
> virtio-balloon-ccw,id=balloon0,devno=fe.0.0002 -msg timestamp=on
> 2019-01-17T02:45:29.877709Z qemu-system-s390x: -device
> sclpconsole,chardev=charconsole1,id=console1: Multiple VT220 operator
> consoles are not supported
> 2019-01-17T02:45:29.877728Z qemu-system-s390x: -device
> sclpconsole,chardev=charconsole1,id=console1: SCLP event initialization
> failed.'
>
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in
> cb_wrapper
> callback(asyncjob, *args, **kwargs)
> File "/usr/share/virt-manager/virtManager/create.py", line 2553, in
> _do_async_install
> guest.start_install(meter=meter)
> File "/usr/share/virt-manager/virtinst/guest.py", line 498, in
> start_install
> doboot, transient)
> File "/usr/share/virt-manager/virtinst/guest.py", line 434, in
> _create_guest
> domain = self.conn.createXML(install_xml or final_xml, 0)
> File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3603, in
> createXML
> if ret is None:raise libvirtError('virDomainCreateXML() failed',
> conn=self)
> libvirtError: internal error: qemu unexpectedly closed the monitor: d
> set=2,fd=30 -chardev file,id=charserial0,path=/dev/fdset/2,append=on
> -device sclpconsole,chardev=charserial0,id=serial0 -chardev
> pty,id=charconsole1 -device sclpconsole,chardev=charconsole1,id=console1
> -device virtio-balloon-ccw,id=balloon0,devno=fe.0.0002 -msg timestamp=on
> 2019-01-17T02:45:29.877709Z qemu-system-s390x: -device
> sclpconsole,chardev=charconsole1,id=console1: Multiple VT220 operator
> consoles are not supported
> 2019-01-17T02:45:29.877728Z qemu-system-s390x: -device
> sclpconsole,chardev=charconsole1,id=console1: SCLP event initialization
> failed.
>
>
> This seems to be a bug with KVM on s390x as this is not related to MAAS in
> any shape or form.
>
> ** Changed in: maas
> Status: Triaged => In Progress
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1811986
>
> Title:
> [2.5] s390x VM creation is broken due to serial console logging
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1811986/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=maas; milestone=2.5.1; status=In Progress;
> importance=Critical; <email address hidden>;
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug...

I'm experiencing the same issue using maas 2.5.1 installed from ppa:maas/stable:
Installed: 2.5.1-7508-gb70537f3d-0ubuntu1~18.04.1

I received a note that the fix landed in MAAS 2.5.2.

Just a note, this is still broken in 2.5.2 and now appears to be targeted for release in 2.5.3

When taking a look at this again - please consider the discussion that was held in https://bugs.launchpad.net/ubuntu-z-systems/+bug/1812360