From: Thomas Huth <1719689@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1719689] Re: [feature request] add flag to treat warnings as errors
Date: Thu, 22 Apr 2021 04:08:06 -0000 [thread overview]
Message-ID: <161906448630.23242.1198878878295712134.malone@gac.canonical.com> (raw)
In-Reply-To: 150644549574.30872.12487281678930398558.malonedeb@wampee.canonical.com
The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1719689
Title:
[feature request] add flag to treat warnings as errors
Status in QEMU:
Incomplete
Bug description:
Since booting could potentially take a lot of time and warnings are
likely to indicate that something is wrong, it would be useful to have
a command line flag which would abort the boot if there are any
warnings.
An example might be network configuration. The following output most
likely indicates that there is something the user has to fix before
starting and being able to use the guest os.
Warning: hub port hub0port0 has no peer
Warning: vlan 0 with no nics
Warning: netdev hub0port0 has no peer
Warning: requested NIC (anonymous, model vitrio-net-device) was not created (not supported by this machine?)
Ideally, there would be an option the user could pass which would
cause qemu to print these warnings then exit, rather than boot the
kernel.
Alternatively, or additionally, a dry run option would be helpful for
the same purpose: making sure qemu get to the booting the kernel stage
with everything in working order so that you do not have to wait for
the kernel to boot and then shut down while debugging things like
networking (things which can be debugged (at least partially) without
booting, or trying to boot, the guest os).
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1719689/+subscriptions
next prev parent reply other threads:[~2021-04-22 4:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 17:04 [Qemu-devel] [Bug 1719689] [NEW] [feature request] add flag to treat warnings as errors Erich Spaker
2020-09-26 16:58 ` [Bug 1719689] " Thomas Huth
2021-04-22 4:08 ` Thomas Huth [this message]
2021-06-21 4:17 ` Launchpad Bug Tracker
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=161906448630.23242.1198878878295712134.malone@gac.canonical.com \
--to=1719689@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.