[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial
From: |
Christian Ehrhardt |
Subject: |
[Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy |
Date: |
Thu, 23 Jan 2020 09:55:46 -0000 |
TBH I'd really want to see how this worked as we didn't push anything to
Bionic that would have changed this recently.
I checked and the only change in that regard is really old.
It was for bug 1790901 which was a prereq for real IPXE on s390x.
So I doubt that MAAS could have worked before that.
Never the less to be sure I was trying the old verson (which needed an odd
bundle of kernel+initrd to build into what you reply on netboot).
But even that - if netboot is failing - it does not fall through (as I'd
expected, but I wanted to be sure).
root@testkvm-bionic-from:~# virsh start netboot --console
Domain netboot started
Connected to domain netboot
Escape character is ^]
done
Using IPv4 address: 192.168.122.33
Requesting file "" via TFTP from 192.168.122.1
Receiving data: 0 KBytesICMP ERROR "port unreachable"
Failed to load OS from network
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1859656
Title:
[2.6] Unable to reboot s390x KVM machine after initial deploy
Status in MAAS:
New
Status in QEMU:
Incomplete
Status in Ubuntu on IBM z Systems:
Triaged
Bug description:
MAAS version: 2.6.1 (7832-g17912cdc9-0ubuntu1~18.04.1)
Arch: S390x
Appears that MAAS can not find the s390x bootloader to boot from the
disk, not sure how maas determines this. However this was working in
the past. I had originally thought that if the maas machine was
deployed then it defaulted to boot from disk.
If I force the VM to book from disk, the VM starts up as expected.
Reproduce:
- Deploy Disco on S390x KVM instance
- Reboot it
on the KVM console...
Connected to domain s2lp6g001
Escape character is ^]
done
Using IPv4 address: 10.246.75.160
Using TFTP server: 10.246.72.3
Bootfile name: 'boots390x.bin'
Receiving data: 0 KBytes
TFTP error: file not found: boots390x.bin
Trying pxelinux.cfg files...
Receiving data: 0 KBytes
Receiving data: 0 KBytes
Failed to load OS from network
==> /var/log/maas/rackd.log <==
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info]
boots390x.bin requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info]
s390x/65a9ca43-9541-49be-b315-e2ca85936ea2 requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info]
s390x/01-52-54-00-e5-d7-bb requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info]
s390x/0AF64BA0 requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info]
s390x/0AF64BA requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info]
s390x/0AF64B requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF64
requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF6
requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF
requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0A
requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0
requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info]
s390x/default requested by 10.246.75.160
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1859656/+subscriptions
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Christian Ehrhardt , 2020/01/21
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Christian Ehrhardt , 2020/01/21
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Sean Feole, 2020/01/21
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Sean Feole, 2020/01/21
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Frank Heimes, 2020/01/22
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Frank Heimes, 2020/01/23
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy,
Christian Ehrhardt <=
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Christian Ehrhardt , 2020/01/23
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Frank Heimes, 2020/01/23
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Frank Heimes, 2020/01/23
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Christian Ehrhardt , 2020/01/23
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Lee Trager, 2020/01/23
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Frank Heimes, 2020/01/28
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Frank Heimes, 2020/01/28
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy, Frank Heimes, 2020/01/30