MAAS

  1. Bug #1859656
  2. Comment #22

Comment 22 for bug 1859656

Revision history for this message
Christian Ehrhardt  (paelzer) wrote : Re: [2.6] Unable to reboot s390x KVM machine after initial deploy

The one that currently is deployed is using the same "list network and hd" which should not work.
It will boot network but should not internally fall back to disk.
 10 <os>
 11 <type arch='s390x' machine='s390-ccw-virtio-bionic'>hvm</type>
 12 <boot dev='network'/>
 13 <boot dev='hd'/>
 14 </os>

Now lets understand how/what works here...

Qemu is given both boot options (we know it will ignore the second ... or at least we think and are told so).
   ... -boot strict=on ... id=virtio-disk0,bootindex=2 ... mac=52:54:00:02:a3:f9,devno=fe.0.0001,bootindex=1

I'd expect this one to "just" netboot, but we need to understand how it got "up" from there.
Fortunately there was a full log of the serial console on disk.

Attaching files from this test ...