From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
David Hildenbrand <david@redhat.com>,
Sascha Silbe <silbe@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] Crash when deleting the diag288 watchdog
Date: Wed, 16 Aug 2017 11:23:49 +0200 [thread overview]
Message-ID: <20170816112349.5cf3c106.cohuck@redhat.com> (raw)
In-Reply-To: <451ff313-11c5-9f67-d7f1-a606c02efc79@redhat.com>
On Wed, 16 Aug 2017 07:05:37 +0200
Thomas Huth <thuth@redhat.com> wrote:
> Hi,
>
> I recently noticed that QEMU abort()s if you try to remove the diag288
> watchdog. For example:
>
> $ qemu-system-s390x -nographic -nodefaults -S -monitor stdio
> QEMU 2.9.92 monitor - type 'help' for more information
> (qemu) device_add diag288,id=x
> (qemu) device_del x
> **
> ERROR:/home/thuth/devel/qemu/qdev-monitor.c:872:qdev_unplug: assertion
> failed: (hotplug_ctrl)
> Aborted (core dumped)
>
> This is ugly, can we fix this somehow? For example, should the diag288
> device be hot-pluggable at all, or can it only be used via the
> "-watchdog" parameter instead? In the latter case, we could simply mark
> the device with "user_creatable = false", I guess?
I don't think the diag288 watchdog should be hotpluggable. IIUC, it is
simply present on z/VM (and I don't think it's different on LPAR, but I
could not find docs for that). So yes, user_creatable = false sounds
like the right thing to do.
Related: We currently only handle diag288 via kvm if I did not miss
something. It probably makes sense to wire it up for tcg as well.
next prev parent reply other threads:[~2017-08-16 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 5:05 [Qemu-devel] Crash when deleting the diag288 watchdog Thomas Huth
2017-08-16 9:23 ` Cornelia Huck [this message]
2017-08-16 13:36 ` Thomas Huth
2017-08-16 13:50 ` Cornelia Huck
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=20170816112349.5cf3c106.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=silbe@linux.vnet.ibm.com \
--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).