On Tue, 27 Feb 2018 11:05:13 +0100
Thomas Huth wrote:
> If QEMU fails to load 's390-netboot.img', the guest firmware currently
> loops forever and just floods the console with "Network boot device
> detected" messages. The code in ipl.c apparently already tried to stop
> the VM
On 02/27/2018 02:11 PM, Thomas Huth wrote:
On 27.02.2018 18:26, Farhan Ali wrote:
On 02/27/2018 05:16 AM, Viktor Mihajlovski wrote:
On 27.02.2018 11:05, Thomas Huth wrote:
If QEMU fails to load 's390-netboot.img', the guest firmware currently
loops forever and just floods the console with
On 27.02.2018 18:26, Farhan Ali wrote:
>
>
> On 02/27/2018 05:16 AM, Viktor Mihajlovski wrote:
>> On 27.02.2018 11:05, Thomas Huth wrote:
>>> If QEMU fails to load 's390-netboot.img', the guest firmware currently
>>> loops forever and just floods the console with "Network boot device
>>>
On 02/27/2018 05:16 AM, Viktor Mihajlovski wrote:
On 27.02.2018 11:05, Thomas Huth wrote:
If QEMU fails to load 's390-netboot.img', the guest firmware currently
loops forever and just floods the console with "Network boot device
detected" messages. The code in ipl.c apparently already tried
On 27.02.2018 11:16, Viktor Mihajlovski wrote:
> On 27.02.2018 11:05, Thomas Huth wrote:
>> If QEMU fails to load 's390-netboot.img', the guest firmware currently
>> loops forever and just floods the console with "Network boot device
>> detected" messages. The code in ipl.c apparently already
On 27.02.2018 11:05, Thomas Huth wrote:
> If QEMU fails to load 's390-netboot.img', the guest firmware currently
> loops forever and just floods the console with "Network boot device
> detected" messages. The code in ipl.c apparently already tried to stop
> the VM with vm_stop() in this case, but
On 27.02.2018 11:05, Thomas Huth wrote:
> If QEMU fails to load 's390-netboot.img', the guest firmware currently
> loops forever and just floods the console with "Network boot device
> detected" messages. The code in ipl.c apparently already tried to stop
> the VM with vm_stop() in this case, but
If QEMU fails to load 's390-netboot.img', the guest firmware currently
loops forever and just floods the console with "Network boot device
detected" messages. The code in ipl.c apparently already tried to stop
the VM with vm_stop() in this case, but this is in vain since the run
state is later