Comment 21 for bug 1859656
Revision history for this message
| Frank Heimes (fheimes) wrote Re: [2.6] Unable to reboot s390x KVM machine after initial deploy | #21 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
In between I found the time to setup an env. build upon older releases:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
$ dpkg -l | grep -i qemu
ii qemu-block-
ii qemu-kvm 1:2.11+
ii qemu-system-common 1:2.11+
ii qemu-system-s390x 1:2.11+
ii qemu-utils 1:2.11+
$ apt-cache policy maas
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://
500 http://
500 http://
2.
500 http://
500 http://
In this environment MAAS is not able to Commission ("Failed commissioning").
Trying to start the vm manually with virsh ends up with:
$ virsh start vm1 --console
Domain vm1 started
Connected to domain vm1
Escape character is ^]
done
Using IPv4 address: 192.168.122.102
Requesting file "boots390x.bin" via TFTP from 192.168.122.1
Receiving data: 0 KBytesfile not found: boots390x.bin
Failed to load OS from network
So that is expecting, since the qemu packages version 1:2.11+
The first qemu packages that should be good are the ones with version 1:2.11+
But (after discussing with cpaelzer) the qemu packages didn't really changed since 1:2.11+
$ sudo apt install qemu-block-extra qemu-kvm qemu-system-common qemu-system-s390x qemu-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
debootstrap
Recommended packages:
sharutils
The following packages will be upgraded:
qemu-block-extra qemu-kvm qemu-system-common qemu-system-s390x qemu-utils
5 upgraded, 0 newly installed, 0 to remove and 167 not upgraded.
Need to get 3,249 kB of archives.
After this operation, 32.8 kB of additional disk space will be used.
Get:1 http://
Get:2 http://
Get:3 http://
Get:4 http://
Get:5 http://
Fetched 3,249 kB in 0s (8,360 kB/s)
(Reading database ... 67530 files and directories currently installed.)
Preparing to unpack .../qemu-
Unpacking qemu-utils (1:2.11+
Preparing to unpack .../qemu-
..
Unpacking qemu-system-common (1:2.11+
7) ...
Preparing to unpack .../qemu-
Unpacking qemu-block-
untu7) ...
Preparing to unpack .../qemu-
Unpacking qemu-kvm (1:2.11+
Preparing to unpack .../qemu-
.
Unpacking qemu-system-s390x (1:2.11+
) ...
Setting up qemu-block-
Setting up qemu-utils (1:2.11+
Processing triggers for man-db (2.8.3-2) ...
Setting up qemu-system-common (1:2.11+
Setting up qemu-system-s390x (1:2.11+
Setting up qemu-kvm (1:2.11+
And with that the Commissioning worked and ended correctly,
and I was also able to complete a Deployment afterwards.
I deployed 19.04 (disco, since I think that Sean faced the issue while he tried to deploy disco, too) and it worked. The system (vm1) came up and I was able to login:
$ ssh ubuntu@
The authenticity of host '192.168.122.201 (192.168.122.201)' can't be established.
ECDSA key fingerprint is SHA256:
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.122.201' (ECDSA) to the list of known hosts.
Welcome to Ubuntu 19.04 (GNU/Linux 5.0.0-38-generic s390x)
* Documentation: https:/
* Management: https:/
* Support: https:/
System information as of Mon Feb 10 10:44:33 UTC 2020
System load: 0.19 Processes: 95
Usage of /: 42.4% of 7.27GB Users logged in: 0
Memory usage: 15% IP address for enc1: 192.168.122.201
Swap usage: 0%
4 updates can be installed immediately.
4 of these updates are security updates.
The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/
Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
ubuntu@vm1:~$