From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
qemu-s390x <qemu-s390x@nongnu.org>,
Thomas Huth <thuth@redhat.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>,
Richard Henderson <rth@twiddle.net>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] s390/ipl: fix ipl with -no-reboot
Date: Thu, 21 Jun 2018 19:01:04 +0200 [thread overview]
Message-ID: <9e4312c4-4694-e15d-84be-7bcd35decb6b@redhat.com> (raw)
In-Reply-To: <f21788b0-6417-dddb-fd5e-9dd9d17cfc66@de.ibm.com>
On 21.06.2018 18:51, Christian Borntraeger wrote:
>
>
> On 06/21/2018 06:35 PM, Christian Borntraeger wrote:
>> kexec/kdump as well as the bootloader use a subcode of diagnose 308
>> that is supposed to reset the subsystem but not comprise a full
>> "reboot". With the latest refactoring this is now broken when
>> -no-reboot is used. This for example break virt-install from
>> iso images.
>
> Its even worse. With this patch I can IPL with --no-reboot, but
> virt-install still creates an xml like
>
> <on_poweroff>destroy</on_poweroff>
> <on_reboot>destroy</on_reboot>
> <on_crash>destroy</on_crash>
>
> With you patch a "soft reset" still seems to trigger an qapi event
> so that libvirt kills the guest due to that...
Either
>
>>
>> We need to mark these "soft" reboots as ok for rebooting.
>>
>> Fixes: a30fb811cbe9 (s390x: refactor reset/reipl handling)
>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> ---
>> hw/s390x/ipl.c | 8 +++++++-
>> include/sysemu/sysemu.h | 3 +++
>> vl.c | 2 +-
>> 3 files changed, 11 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/s390x/ipl.c b/hw/s390x/ipl.c
>> index 0d67349004..ade6896af6 100644
>> --- a/hw/s390x/ipl.c
>> +++ b/hw/s390x/ipl.c
>> @@ -535,7 +535,13 @@ void s390_ipl_reset_request(CPUState *cs, enum s390_reset reset_type)
>> ipl->iplb_valid = s390_gen_initial_iplb(ipl);
>> }
>> }
>> - qemu_system_reset_request(SHUTDOWN_CAUSE_GUEST_RESET);
>> + if (reset_type == S390_RESET_MODIFIED_CLEAR ||
>> + reset_type == S390_RESET_LOAD_NORMAL) {
>> + /* ignore -no-reboot */
>> + qemu_system_reset_request(SHUTDOWN_CAUSE_GUEST_RESET_FORCE);
>> + } else {
>> + qemu_system_reset_request(SHUTDOWN_CAUSE_GUEST_RESET);
>> + }
>> /* as this is triggered by a CPU, make sure to exit the loop */
>> if (tcg_enabled()) {
>> cpu_loop_exit(cs);
>> diff --git a/include/sysemu/sysemu.h b/include/sysemu/sysemu.h
>> index e893f72f3b..345369d924 100644
>> --- a/include/sysemu/sysemu.h
>> +++ b/include/sysemu/sysemu.h
>> @@ -44,6 +44,9 @@ typedef enum ShutdownCause {
>> turns that into a shutdown */
>> SHUTDOWN_CAUSE_GUEST_PANIC, /* Guest panicked, and command line turns
>> that into a shutdown */
>> + SHUTDOWN_CAUSE_GUEST_RESET_FORCE,/* Guest reset that should ignore
>> + --no-reboot. This is useful for reset
>> + like actions as s390 kexec/kdump */
>> SHUTDOWN_CAUSE__MAX,
>> } ShutdownCause;
>>
>> diff --git a/vl.c b/vl.c
>> index b3426e03d0..722c3b9963 100644
>> --- a/vl.c
>> +++ b/vl.c
>> @@ -1674,7 +1674,7 @@ void qemu_system_guest_panicked(GuestPanicInformation *info)
>>
>> void qemu_system_reset_request(ShutdownCause reason)
>> {
>> - if (no_reboot) {
>> + if (no_reboot && reason != SHUTDOWN_CAUSE_GUEST_RESET_FORCE) {
>> shutdown_requested = reason;
>> } else {
>> reset_requested = reason;
>>
>
Maybe
SHUTDOWN_CAUSE_GUEST_RESET_FORCE -> SHUTDOWN_CAUSE_GUEST_RESET_INTERNAL
diff --git a/vl.c b/vl.c
index b3426e03d0..198285be4b 100644
--- a/vl.c
+++ b/vl.c
@@ -1628,7 +1628,7 @@ void qemu_system_reset(ShutdownCause reason)
} else {
qemu_devices_reset();
}
- if (reason) {
+ if (reason != SHUTDOWN_CAUSE_GUEST_RESET_INTERNAL) {
qapi_event_send_reset(shutdown_caused_by_guest(reason),
&error_abort);
}
Or revert ;)
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2018-06-21 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 16:35 [Qemu-devel] [PATCH v2] s390/ipl: fix ipl with -no-reboot Christian Borntraeger
2018-06-21 16:51 ` Christian Borntraeger
2018-06-21 17:00 ` Christian Borntraeger
2018-06-21 17:01 ` David Hildenbrand [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e4312c4-4694-e15d-84be-7bcd35decb6b@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).