qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michal Suchanek <hramrach@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1832877] [NEW] qemu-bridge-helper undocumented and broken
Date: Fri, 14 Jun 2019 17:07:04 -0000	[thread overview]
Message-ID: <156053202418.26991.16452462538743379773.malonedeb@chaenomeles.canonical.com> (raw)

Public bug reported:

qemu output:

access denied by acl file
qemu-system-ppc64: bridge helper failed

Option description:

      -netdev bridge,id=id[,br=bridge][,helper=helper]
           Connect a host TAP network interface to a host bridge device.

           Use the network helper helper to configure the TAP interface and attach it to the bridge. The default network
           helper executable is /path/to/qemu-bridge-helper and the default bridge device is br0.

           Examples:

                   #launch a QEMU instance with the default network helper to
                   #connect a TAP device to bridge br0
                   qemu-system-i386 linux.img -netdev bridge,id=n1 -device virtio-net,netdev=n1


                   #launch a QEMU instance with the default network helper to
                   #connect a TAP device to bridge qemubr0
                   qemu-system-i386 linux.img -netdev bridge,br=qemubr0,id=n1 -device virtio-net,netdev=n1


What is the acl file? What is the interface to qemu-bridge-helper?

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1832877

Title:
  qemu-bridge-helper undocumented and broken

Status in QEMU:
  New

Bug description:
  qemu output:

  access denied by acl file
  qemu-system-ppc64: bridge helper failed

  Option description:

        -netdev bridge,id=id[,br=bridge][,helper=helper]
             Connect a host TAP network interface to a host bridge device.

             Use the network helper helper to configure the TAP interface and attach it to the bridge. The default network
             helper executable is /path/to/qemu-bridge-helper and the default bridge device is br0.

             Examples:

                     #launch a QEMU instance with the default network helper to
                     #connect a TAP device to bridge br0
                     qemu-system-i386 linux.img -netdev bridge,id=n1 -device virtio-net,netdev=n1


                     #launch a QEMU instance with the default network helper to
                     #connect a TAP device to bridge qemubr0
                     qemu-system-i386 linux.img -netdev bridge,br=qemubr0,id=n1 -device virtio-net,netdev=n1

  
  What is the acl file? What is the interface to qemu-bridge-helper?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1832877/+subscriptions


             reply	other threads:[~2019-06-14 17:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 17:07 Michal Suchanek [this message]
2019-06-14 17:13 ` [Qemu-devel] [Bug 1832877] Re: qemu-bridge-helper undocumented and broken Michal Suchanek
2021-05-05 11:46 ` Thomas Huth

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=156053202418.26991.16452462538743379773.malonedeb@chaenomeles.canonical.com \
    --to=hramrach@gmail.com \
    --cc=1832877@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).