unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / Atom feed
* bug#24156: QEMU '-net bridge' --> "qemu-system-x86_64: -net bridge: bridge helper failed"
@ 2016-08-05  2:40 myglc2
  2020-12-18 19:47 ` zimoun
  0 siblings, 1 reply; 5+ messages in thread
From: myglc2 @ 2016-08-05  2:40 UTC (permalink / raw)
  To: 24156

[-- 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 --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#24156: QEMU '-net bridge' --> "qemu-system-x86_64: -net bridge: bridge helper failed"
  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
  0 siblings, 1 reply; 5+ messages in thread
From: zimoun @ 2020-12-18 19:47 UTC (permalink / raw)
  To: myglc2, Mathieu Othacehe; +Cc: 24156

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




^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#24156: QEMU '-net bridge' --> "qemu-system-x86_64: -net bridge: bridge helper failed"
  2020-12-18 19:47 ` zimoun
@ 2021-01-11 12:36   ` zimoun
  2021-01-11 21:38     ` George Clemmer
  0 siblings, 1 reply; 5+ messages in thread
From: zimoun @ 2021-01-11 12:36 UTC (permalink / raw)
  To: myglc2; +Cc: Mathieu Othacehe, 24156

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




^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#24156: QEMU '-net bridge' --> "qemu-system-x86_64: -net bridge: bridge helper failed"
  2021-01-11 12:36   ` zimoun
@ 2021-01-11 21:38     ` George Clemmer
  2021-01-13 20:59       ` zimoun
  0 siblings, 1 reply; 5+ messages in thread
From: George Clemmer @ 2021-01-11 21:38 UTC (permalink / raw)
  To: zimoun; +Cc: Mathieu Othacehe, 24156

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





^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#24156: QEMU '-net bridge' --> "qemu-system-x86_64: -net bridge: bridge helper failed"
  2021-01-11 21:38     ` George Clemmer
@ 2021-01-13 20:59       ` zimoun
  0 siblings, 0 replies; 5+ messages in thread
From: zimoun @ 2021-01-13 20:59 UTC (permalink / raw)
  To: George Clemmer; +Cc: Mathieu Othacehe, 24156-done

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




^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2021-01-13 21:10 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2021-01-11 21:38     ` George Clemmer
2021-01-13 20:59       ` zimoun

unofficial mirror of bug-guix@gnu.org 

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://yhetil.org/guix-bugs/0 guix-bugs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 guix-bugs guix-bugs/ https://yhetil.org/guix-bugs \
		bug-guix@gnu.org
	public-inbox-index guix-bugs

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.gnu.guix.bugs
	nntp://news.gmane.io/gmane.comp.gnu.guix.bugs


AGPL code for this site: git clone http://ou63pmih66umazou.onion/public-inbox.git