From: Aurelien Jarno <aurel32@debian.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 584153] Re: no useful error message when tap device open fails
Date: Sun, 20 Feb 2011 17:13:31 -0000 [thread overview]
Message-ID: <20110220171333.12440.41007.launchpad@palladium.canonical.com> (raw)
In-Reply-To: 20100522095537.15293.25862.malonedeb@gandwana.canonical.com
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/584153
Title:
no useful error message when tap device open fails
Status in QEMU:
Fix Released
Status in “qemu-kvm” package in Debian:
Fix Released
Bug description:
When using tap network devices and it fails, qemu gives no information
about what the problem is (permission denied, device busy or other),
making debugging of such situations, especially for newbies, very
difficult. The proposed patch just adds strerror() around the place,
making it more friendly.
See also Debian bug#578154, http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=578154 and a discussion on qemu-devel at
http://marc.info/?t=127192875200003 .
prev parent reply other threads:[~2011-02-20 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 9:55 [Qemu-devel] [Bug 584153] [NEW] no useful error message when tap device open fails Michael Tokarev
2010-05-22 9:55 ` [Qemu-devel] [Bug 584153] " Michael Tokarev
2010-05-22 16:27 ` Loïc Minier
2010-05-22 17:28 ` Bug Watch Updater
2010-06-02 17:02 ` Joel Schopp
2010-06-02 17:24 ` Luiz Capitulino
2011-01-16 14:24 ` Aurelien Jarno
2011-02-20 17:13 ` Aurelien Jarno [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=20110220171333.12440.41007.launchpad@palladium.canonical.com \
--to=aurel32@debian.org \
--cc=584153@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 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).