[2.5] s390x VM creation is broken due to serial console logging
Bug #1811986 reported by
Andres Rodriguez
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Newell Jensen | ||
2.5 |
Fix Released
|
Critical
|
Newell Jensen | ||
Ubuntu on IBM z Systems |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
VM's being create on a s390x host fail to start because of serial logging.
s390x doesn't support double output to serial console.
Related branches
~newell-jensen/maas:2.5-lp1811986
- Newell Jensen (community): Approve
-
Diff: 21 lines (+1/-5)1 file modifiedsrc/provisioningserver/drivers/pod/virsh.py (+1/-5)
~newell-jensen/maas:lp1811986
Merged
into
maas:master
- Björn Tillenius: Approve
- MAAS Lander: Approve
-
Diff: 21 lines (+1/-5)1 file modifiedsrc/provisioningserver/drivers/pod/virsh.py (+1/-5)
Changed in maas: | |
milestone: | none → 2.5.1 |
importance: | Undecided → Critical |
status: | New → Triaged |
assignee: | nobody → Andres Rodriguez (andreserl) |
Changed in maas: | |
assignee: | Andres Rodriguez (andreserl) → Newell Jensen (newell-jensen) |
description: | updated |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Changed in ubuntu-z-systems: | |
status: | New → Fix Released |
Changed in maas: | |
milestone: | 2.5.1 → 2.6.0alpha1 |
To post a comment you must log in.
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 17T02:45: 29.877709Z qemu-system-s390x: -device sclpconsole, chardev= charconsole1, id=console1: Multiple VT220 operator consoles are not supported 17T02:45: 29.877728Z qemu-system-s390x: -device sclpconsole, chardev= charconsole1, id=console1: SCLP event initialization failed.'
2019-01-
2019-01-
Traceback (most recent call last): virt-manager/ virtManager/ asyncjob. py", line 89, in cb_wrapper asyncjob, *args, **kwargs) virt-manager/ virtManager/ create. py", line 2553, in _do_async_install start_install( meter=meter) virt-manager/ virtinst/ guest.py" , line 498, in start_install virt-manager/ virtinst/ guest.py" , line 434, in _create_guest createXML( install_ xml or final_xml, 0) python2. 7/dist- packages/ libvirt. py", line 3603, in createXML 'virDomainCreat eXML() failed', conn=self) 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 17T02:45: 29.877709Z qemu-system-s390x: -device sclpconsole, chardev= charconsole1, id=console1: Multiple VT220 operator consoles are not supported 17T02:45: 29.877728Z qemu-system-s390x: -device sclpconsole, chardev= charconsole1, id=console1: SCLP event initialization failed.
File "/usr/share/
callback(
File "/usr/share/
guest.
File "/usr/share/
doboot, transient)
File "/usr/share/
domain = self.conn.
File "/usr/lib/
if ret is None:raise libvirtError(
libvirtError: internal error: qemu unexpectedly closed the monitor: d set=2,fd=30 -chardev file,id=
2019-01-
2019-01-
This seems to be a bug with KVM on s390x as this is not related to MAAS in any shape or form.