unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: myglc2 <myglc2@gmail.com>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 24156@debbugs.gnu.org
Subject: bug#24156: QEMU '-net bridge' --> "qemu-system-x86_64: -net bridge: bridge helper failed"
Date: Mon, 11 Jan 2021 13:36:59 +0100	[thread overview]
Message-ID: <86o8hvtztg.fsf@gmail.com> (raw)
In-Reply-To: <86wnxevquj.fsf@gmail.com> (zimoun's message of "Fri, 18 Dec 2020 20:47:32 +0100")

Hi,

On Fri, 18 Dec 2020 at 20:47, zimoun <zimon.toutoune@gmail.com> wrote:
> On Thu, 04 Aug 2016 at 22:40, myglc2 <myglc2@gmail.com> wrote:

>> Motivation: bridging or routing is required to enable a connection to be
>> made inward to a QEMU VM. TAP seems like the best of the available
>> solutions. But connecting to a TAP device produces an error when the
>> QEMU bridge helper fails.
>>
>> Example:
>>
>> g1@g1 ~/src/vmb$ qemu-system-x86_64 -net user -net bridge -net nic,model=virtio -enable-kvm -m 4096 -k en-us -display curses /home/g1/src/vmb/tmp/img6/vm.img
>> failed to parse default acl file `/gnu/store/1072khbm9124a8a1pyyyw4mr1p12jsfq-qemu-2.6.0/etc/qemu/bridge.conf'
>> qemu-system-x86_64: -net bridge: bridge helper failed
>
> Since a lot of things changed, is this bug report still relevant?  If
> yes, what could be the next actionable step?  Otherwise, let close it or
> mark it as wishlist.

If no moreinfo is provided to detail what could the next actionable
step, then I will close this more-than-3-years bug report in the coming
days.


All the best,
simon

http://issues.guix.gnu.org/issue/24156




  reply	other threads:[~2021-01-11 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05  2:40 bug#24156: QEMU '-net bridge' --> "qemu-system-x86_64: -net bridge: bridge helper failed" myglc2
2020-12-18 19:47 ` zimoun
2021-01-11 12:36   ` zimoun [this message]
2021-01-11 21:38     ` George Clemmer
2021-01-13 20:59       ` zimoun

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86o8hvtztg.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=24156@debbugs.gnu.org \
    --cc=myglc2@gmail.com \
    --cc=othacehe@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).