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

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

[myglc2]

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]


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 #2: img-tap --]
[-- Type: application/octet-stream, Size: 1195 bytes --]

#!/run/current-system/profile/bin/bash
set -xe

# guix vm examples

# usage
# $ <scriptname> mk  [vm#] - mak image
# $ <scriptname> run [vm#] - run image

CMD=`basename "$0"`
VMNUM=${2:-""}
TMPDIR=$PWD/tmp/$CMD$VMNUM
mkdir -p $TMPDIR
cp $CMD $TMPDIR/$CMD

case $1 in
    mk)
	# save the vm config
	cp v1.scm $TMPDIR
	# save guix version 
	(stat $HOME/.config/guix/latest | grep File:) > $TMPDIR/guix-version
	# save guix config
	git -C ~/.config/guix/latest branch -av | grep '* master' >> $TMPDIR/guix-version
	# be sure the version of guix we have checked out is the one we are using
	make -C $HOME/.config/guix/latest -s > $TMPDIR/guix-make.log
	# make vm & copy image from of store
	cp -n $(guix system vm-image $TMPDIR/v1.scm --image-size=4GB) $TMPDIR/vm.img
	# make writeable
	chmod u+w $TMPDIR/vm.img
	;;

    run)
	# run the image
	# Note: '-k en-us' is a hack to get Mac XQuartz keys to "sort of work"
	qemu-system-x86_64 \
	    -net user \
	    -net bridge \
	    -net nic,model=virtio \
	    -enable-kvm \
	    -m 4096 \
	    -k en-us \
	    -display curses \
	    $TMPDIR/vm.img
	;;

    *)

	echo ERROR: you typed: \"$CMD $*\" which has missing arguments or invalid arguments

esac

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

[zimoun]

Hi,

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.


All the best,
simon

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

[zimoun]

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

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

[George Clemmer]

zimoun <zimon.toutoune@gmail.com> writes:

> 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

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

[zimoun]

Hi

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

[...]

> 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