[Qemu-devel] [Bug 584153] [NEW] no useful error message when tap device open fails

[Qemu-devel] [Bug 584153] [NEW] no useful error message when tap device open fails

[Michael Tokarev]

Public bug reported:

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 .

** Affects: qemu
     Importance: Undecided
         Status: New


** Tags: patch

-- 
no useful error message when tap device open fails
https://bugs.launchpad.net/bugs/584153
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

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 .

[Qemu-devel] [Bug 584153] Re: no useful error message when tap device open fails

[Michael Tokarev]

** Attachment added: "tap-open-give-useful-error-messages.diff"
   http://launchpadlibrarian.net/48914447/tap-open-give-useful-error-messages.diff

-- 
no useful error message when tap device open fails
https://bugs.launchpad.net/bugs/584153
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

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 .

[Qemu-devel] [Bug 584153] Re: no useful error message when tap device open fails

[Loïc Minier]

** Bug watch added: Debian Bug tracker #578154
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578154

** Also affects: qemu-kvm (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578154
   Importance: Unknown
       Status: Unknown

-- 
no useful error message when tap device open fails
https://bugs.launchpad.net/bugs/584153
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New
Status in “qemu-kvm” package in Debian: Unknown

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 .

[Qemu-devel] [Bug 584153] Re: no useful error message when tap device open fails

[Bug Watch Updater]

** Changed in: qemu-kvm (Debian)
       Status: Unknown => Fix Released

-- 
no useful error message when tap device open fails
https://bugs.launchpad.net/bugs/584153
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New
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 .

[Qemu-devel] [Bug 584153] Re: no useful error message when tap device open fails

[Joel Schopp]

Please send this patch with a signed-off-by: to the linux kernel mailing
list and netdev mailing lists, see
http://www.kernel.org/pub/linux/docs/lkml/#s3-3

** Changed in: qemu
       Status: New => Incomplete

-- 
no useful error message when tap device open fails
https://bugs.launchpad.net/bugs/584153
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: Incomplete
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 .

[Qemu-devel] [Bug 584153] Re: no useful error message when tap device open fails

[Luiz Capitulino]

Michael's fix is good, but it got forgotten, probably because he has
submitted it in the middle of a thread.

I'm going resubmit it again.

** Changed in: qemu
       Status: Incomplete => In Progress

-- 
no useful error message when tap device open fails
https://bugs.launchpad.net/bugs/584153
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: In Progress
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 .

[Qemu-devel] [Bug 584153] Re: no useful error message when tap device open fails

[Aurelien Jarno]

** Changed in: qemu
       Status: In Progress => Fix Committed

-- 
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 Committed
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 .

[Qemu-devel] [Bug 584153] Re: no useful error message when tap device open fails

[Aurelien Jarno]

** 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 .