I took the time and recreated a MAAS setup (latest stable 2.2) on s390x and it looks like this:
- I could start a deployment and ran through the states:
- Power On, Commissioning (Performing PXE boot)
- Power On, Commissioning (Gathering Information)
- Power On, Ready
- Power Off, Ready
(I may have have missed some states in between.)
- Power Off, Ready is the final state at that point
and on the console it's:
$ virsh list --all
Id Name State
----------------------------------------------------
- vm1 shut off
- xml VM definition is:
$ virsh dumpxml vm1
<domain type='kvm'>
<name>vm1</name>
<uuid>0f7d1d61-9368-4bfe-8c65-c709e90e8780</uuid>
<memory unit='KiB'>1048576</memory>
<currentMemory unit='KiB'>1048576</currentMemory>
<vcpu placement='static'>1</vcpu>
<os>
<type arch='s390x' machine='s390-ccw-virtio-bionic'>hvm</type>
<boot dev='network'/>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/bin/kvm</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/var/lib/libvirt/maas-images/6addbfeb-ff2c-4350-b34d-11a56ea34f1d'/>
<target dev='vda' bus='virtio'/>
<serial>6addbfeb-ff2c-4350-b34d-11a56ea34f1d</serial>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0002'/>
</disk>
<interface type='network'>
<mac address='52:54:00:ea:11:5f'/>
<source network='default'/>
<model type='virtio'/>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0001'/>
</interface>
<console type='pty'>
<log file='/var/log/libvirt/qemu/vm1-serial0.log' append='off'/>
<target type='sclp' port='0'/>
</console>
<memballoon model='virtio'>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0000'/>
</memballoon>
<panic model='s390'/>
</devices>
</domain>
So it largely looks like assumed (after initially reading the bug),
PXE itself seems to work, but the boot issue it due to:
<boot dev='network'/>
<boot dev='hd'/>
That confirms the situation (on s390x and MAAS 2.6.2)m but it still raises the question why it seem to have worked with 2.6.0?
I took the time and recreated a MAAS setup (latest stable 2.2) on s390x and it looks like this: ------- ------- ------- ------- ------- ------- --- 0f7d1d61- 9368-4bfe- 8c65-c709e90e87 80</uuid> >1048576< /memory> >1048576< /currentMemory> 'static' >1</vcpu> 's390-ccw- virtio- bionic' >hvm</type> destroy< /on_poweroff> restart< /on_reboot> destroy< /on_crash> /usr/bin/ kvm</emulator> var/lib/ libvirt/ maas-images/ 6addbfeb- ff2c-4350- b34d-11a56ea34f 1d'/> serial> 6addbfeb- ff2c-4350- b34d-11a56ea34f 1d</serial> '52:54: 00:ea:11: 5f'/> var/log/ libvirt/ qemu/vm1- serial0. log' append='off'/>
- I could start a deployment and ran through the states:
- Power On, Commissioning (Performing PXE boot)
- Power On, Commissioning (Gathering Information)
- Power On, Ready
- Power Off, Ready
(I may have have missed some states in between.)
- Power Off, Ready is the final state at that point
and on the console it's:
$ virsh list --all
Id Name State
-------
- vm1 shut off
- xml VM definition is:
$ virsh dumpxml vm1
<domain type='kvm'>
<name>vm1</name>
<uuid>
<memory unit='KiB'
<currentMemory unit='KiB'
<vcpu placement=
<os>
<type arch='s390x' machine=
<boot dev='network'/>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>
<on_reboot>
<on_crash>
<devices>
<emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/
<target dev='vda' bus='virtio'/>
<
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0002'/>
</disk>
<interface type='network'>
<mac address=
<source network='default'/>
<model type='virtio'/>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0001'/>
</interface>
<console type='pty'>
<log file='/
<target type='sclp' port='0'/>
</console>
<memballoon model='virtio'>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0000'/>
</memballoon>
<panic model='s390'/>
</devices>
</domain>
So it largely looks like assumed (after initially reading the bug),
PXE itself seems to work, but the boot issue it due to:
<boot dev='network'/>
<boot dev='hd'/>
That confirms the situation (on s390x and MAAS 2.6.2)m but it still raises the question why it seem to have worked with 2.6.0?