It took some time (due to travel), but I was now able to do a setup based on the old 2.6.0 version [2.6.0 (7803-g6fc5f26eb-0ubuntu1~18.04.1)] for testing.
And with the combination:
$ apt-cache policy maas
maas:
Installed: 2.6.0-7803-g6fc5f26eb-0ubuntu1~18.04.1
Candidate: 2.6.0-7803-g6fc5f26eb-0ubuntu1~18.04.1
Version table:
*** 2.6.0-7803-g6fc5f26eb-0ubuntu1~18.04.1 500
500 http://ppa.launchpad.net/maas-maintainers/testing/ubuntu bionic/main s390x Packages
100 /var/lib/dpkg/status
2.4.2-7034-g2f5deb8b8-0ubuntu1 500
500 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/main s390x Packages
2.4.0~beta2-6865-gec43e47e6-0ubuntu1 500
500 http://us.ports.ubuntu.com/ubuntu-ports bionic/main s390x Packages
and:
$ apt-cache policy qemu
qemu:
Installed: (none)
Candidate: 1:2.11+dfsg-1ubuntu7.21
Version table:
1:2.11+dfsg-1ubuntu7.21 500
500 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/universe s390x Packages
1:2.11+dfsg-1ubuntu7.20 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe s390x Packages
1:2.11+dfsg-1ubuntu7 500
500 http://us.ports.ubuntu.com/ubuntu-ports bionic/universe s390x Packages
the system seems to successful commissions, similar to the latest maas 2.6.2 version (see above).
But then the VM ends again in state Ready / off.
virsh shows the VM as shutoff:
ubuntu@s1lp11:~$ sudo -H -u maas bash -c 'virsh -c qemu+ssh://ubuntu@192.168.122.1/system list --all'
ubuntu@192.168.122.1's password:
Id Name State
----------------------------------------------------
- vm1 shut off
The os element looks like this - with the two entries:
<os>
<type arch='s390x' machine='s390-ccw-virtio-bionic'>hvm</type>
<boot dev='network'/>
<boot dev='hd'/>
</os>
A manual start (with the help of virsh, console enabled) shows that it network boots (see attachment).
Removing the network entry and booting didn't work - looks like no OS deployed on disk yet.
To sum it up - also not working on this 2.6.0 env. that I've just created.
It took some time (due to travel), but I was now able to do a setup based on the old 2.6.0 version [2.6.0 (7803-g6fc5f26e b-0ubuntu1~ 18.04.1) ] for testing.
And with the combination:
$ apt-cache policy maas g6fc5f26eb- 0ubuntu1~ 18.04.1 g6fc5f26eb- 0ubuntu1~ 18.04.1 g6fc5f26eb- 0ubuntu1~ 18.04.1 500 ppa.launchpad. net/maas- maintainers/ testing/ ubuntu bionic/main s390x Packages dpkg/status 4.2-7034- g2f5deb8b8- 0ubuntu1 500 us.ports. ubuntu. com/ubuntu- ports bionic-updates/main s390x Packages 4.0~beta2- 6865-gec43e47e6 -0ubuntu1 500 us.ports. ubuntu. com/ubuntu- ports bionic/main s390x Packages dfsg-1ubuntu7. 21 2.11+dfsg- 1ubuntu7. 21 500 us.ports. ubuntu. com/ubuntu- ports bionic- updates/ universe s390x Packages 2.11+dfsg- 1ubuntu7. 20 500 ports.ubuntu. com/ubuntu- ports bionic- security/ universe s390x Packages 2.11+dfsg- 1ubuntu7 500 us.ports. ubuntu. com/ubuntu- ports bionic/universe s390x Packages
maas:
Installed: 2.6.0-7803-
Candidate: 2.6.0-7803-
Version table:
*** 2.6.0-7803-
500 http://
100 /var/lib/
2.
500 http://
2.
500 http://
and:
$ apt-cache policy qemu
qemu:
Installed: (none)
Candidate: 1:2.11+
Version table:
1:
500 http://
1:
500 http://
1:
500 http://
the system seems to successful commissions, similar to the latest maas 2.6.2 version (see above).
But then the VM ends again in state Ready / off.
virsh shows the VM as shutoff: //ubuntu@ 192.168. 122.1/system list --all' 192.168. 122.1's password: ------- ------- ------- ------- ------- ------- ---
ubuntu@s1lp11:~$ sudo -H -u maas bash -c 'virsh -c qemu+ssh:
ubuntu@
Id Name State
-------
- vm1 shut off
The os element looks like this - with the two entries: 's390-ccw- virtio- bionic' >hvm</type>
<os>
<type arch='s390x' machine=
<boot dev='network'/>
<boot dev='hd'/>
</os>
A manual start (with the help of virsh, console enabled) shows that it network boots (see attachment).
Removing the network entry and booting didn't work - looks like no OS deployed on disk yet.
To sum it up - also not working on this 2.6.0 env. that I've just created.