QEMU '-net bridge' --> "qemu-system-x86_64: -net bridge: bridge helper failed"

  • Done
  • quality assurance status badge
Details
2 participants
  • myglc2
  • zimoun
Owner
unassigned
Submitted by
myglc2
Severity
normal
M
M
myglc2 wrote on 5 Aug 2016 04:40
(address . bug-guix@gnu.org)
8637mk6ir4.fsf@gmail.com
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

This error was produced with the attached 'img-tap' script. e.g., to
build the vm ...

./img-tap mk 1

To (attempt to) run the vm ..

./img-tap run 1


Running Guix built from git checkout on GuixSD:
stat ~/.config/guix/latest | grep File:
File: '/home/g1/.config/guix/latest' -> '../../src/guix'
g1@g1 ~/src/vmb$ git -C ~/.config/guix/latest describe
v0.11.0-242-g7ccb874
Attachment: img-tap
Z
Z
zimoun wrote on 18 Dec 2020 20:47
(address . 24156@debbugs.gnu.org)
86wnxevquj.fsf@gmail.com
Hi,

On Thu, 04 Aug 2016 at 22:40, myglc2 <myglc2@gmail.com> wrote:
Toggle quote (11 lines)
> 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.


All the best,
simon
Z
Z
zimoun wrote on 11 Jan 2021 13:36
(name . myglc2)(address . myglc2@gmail.com)
86o8hvtztg.fsf@gmail.com
Hi,

On Fri, 18 Dec 2020 at 20:47, zimoun <zimon.toutoune@gmail.com> wrote:
Toggle quote (17 lines)
> 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

G
G
George Clemmer wrote on 11 Jan 2021 22:38
(name . zimoun)(address . zimon.toutoune@gmail.com)
85im83p31i.fsf@gmail.com
zimoun <zimon.toutoune@gmail.com> writes:

Toggle quote (15 lines)
> 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.
>
> 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.
>
> http://issues.guix.gnu.org/issue/24156
Hi Simon,

I can't easily provide more detail as I am not currently use QEMU.

Best, George
Z
Z
zimoun wrote on 13 Jan 2021 21:59
(name . George Clemmer)(address . myglc2@gmail.com)
86mtxcsgc9.fsf@gmail.com
Hi

On Mon, 11 Jan 2021 at 16:38, George Clemmer <myglc2@gmail.com> wrote:
Toggle quote (12 lines)
>> 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.
>>
>> 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.

[...]

Toggle quote (2 lines)
> I can't easily provide more detail as I am not currently use QEMU.

Therefore I am closing. Feel free to reopen it and discuss the wishlist
on guix-devel.


All the best,
simon
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 24156@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 24156
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch