[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1859656] [NEW] [2.6] Unable to reboot s390x KVM machine after initi
From: |
Launchpad Bug Tracker |
Subject: |
[Bug 1859656] [NEW] [2.6] Unable to reboot s390x KVM machine after initial deploy |
Date: |
Tue, 21 Jan 2020 14:54:04 -0000 |
You have been subscribed to a public bug:
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
** Affects: maas
Importance: Undecided
Assignee: Lee Trager (ltrager)
Status: Incomplete
** Affects: qemu
Importance: Undecided
Status: New
** Affects: ubuntu-z-systems
Importance: High
Assignee: MAAS (maas)
Status: Triaged
--
[2.6] Unable to reboot s390x KVM machine after initial deploy
https://bugs.launchpad.net/bugs/1859656
You received this bug notification because you are a member of qemu-devel-ml,
which is subscribed to QEMU.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1859656] [NEW] [2.6] Unable to reboot s390x KVM machine after initial deploy,
Launchpad Bug Tracker <=