[FITS] Created: (FL-2912) qemu-kvm looks for /etc/qemu/bridge.conf inside /usr/etc/qemu/bridge.conf at runtime ?

[ermo | Rune Morling (FITS)]

qemu-kvm looks for /etc/qemu/bridge.conf inside /usr/etc/qemu/bridge.conf at runtime ?
--------------------------------------------------------------------------------------

Key: FL-2912
URL: https://issues.foresightlinux.org/jira/browse/FL-2912
Project: Foresight Linux
Issue Type: Bug
Security Level: Public (Everyone can see this issue)
Components: Base Operating System
Affects Versions: 2.5.x
Environment: group-xfce-dist-devel=foresight.rpath.org@fl:2-devel/2.5.4+2013.07.05-0.1-5[~!gcc.core]
Reporter: ermo | Rune Morling
Assignee: ermo | Rune Morling


I'm trying to set up a KVM instance using a bridge network.

However, I'm getting this error message:

{code}
[root@mrwing ~]# qemu-kvm -netdev bridge,id=hn0 -device virtio-net-pci,netdev=hn0,id=nic1 openwrt-x86-kvm_guest-combined-ext4.img
failed to parse default acl file `/usr/etc/qemu/bridge.conf'
failed to launch bridge helper
qemu-kvm: -netdev bridge,id=hn0: Device 'bridge' could not be initialized
[root@mrwing ~]#
{code}

However, the bridge configuration default acl file exists in {{/etc/qemu/bridge.conf}}, suggesting that qemu-kvm was built with a missing/wrong ./configure parameter?

Looking at the kvm.recipe and ./configure --help, it turns out that --sysconfdir is never explicitly specified?

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.foresightlinux.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ermo | Rune Morling (FITS)]

[ https://issues.foresightlinux.org/jira/browse/FL-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ermo | Rune Morling updated FL-2912:
------------------------------------

Summary: qemu-kvm looks for /usr/etc/qemu/bridge.conf instead of /etc/qemu/bridge.conf at runtime ? (was: qemu-kvm looks for /etc/qemu/bridge.conf inside /usr/etc/qemu/bridge.conf at runtime ?)

> qemu-kvm looks for /usr/etc/qemu/bridge.conf instead of /etc/qemu/bridge.conf at runtime ?
> ------------------------------------------------------------------------------------------

>
> Key: FL-2912
> URL: https://issues.foresightlinux.org/jira/browse/FL-2912
> Project: Foresight Linux
> Issue Type: Bug

> Security Level: Public(Everyone can see this issue)

[ermo | Rune Morling (FITS)]

[ https://issues.foresightlinux.org/jira/browse/FL-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ermo | Rune Morling updated FL-2912:
------------------------------------

Environment: group-xfce-dist-devel=foresight.rpath.org@fl:2-devel/2.5.4+2013.07.12-0.1-1[~!gcc.core] (was: group-xfce-dist-devel=foresight.rpath.org@fl:2-devel/2.5.4+2013.07.05-0.1-5[~!gcc.core])

> qemu-kvm looks for /usr/etc/qemu/bridge.conf instead of /etc/qemu/bridge.conf at runtime ?
> ------------------------------------------------------------------------------------------
>

> Key: FL-2912
> URL: https://issues.foresightlinux.org/jira/browse/FL-2912
> Project: Foresight Linux
> Issue Type: Bug

> Security Level: Public(Everyone can see this issue)

> Components: Base Operating System
> Affects Versions: 2.5.x

> Environment: group-xfce-dist-devel=foresight.rpath.org@fl:2-devel/2.5.4+2013.07.12-0.1-1[~!gcc.core]

[ermo | Rune Morling (FITS)]

[ https://issues.foresightlinux.org/jira/browse/FL-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ermo | Rune Morling updated FL-2912:
------------------------------------

Description:

I'm trying to set up a KVM instance using a bridge network.

However, I'm getting this error message:

{code}
[root@mrwing ~]# qemu-kvm -netdev bridge,id=hn0 -device virtio-net-pci,netdev=hn0,id=nic1 openwrt-x86-kvm_guest-combined-ext4.img
failed to parse default acl file `/usr/etc/qemu/bridge.conf'
failed to launch bridge helper
qemu-kvm: -netdev bridge,id=hn0: Device 'bridge' could not be initialized
[root@mrwing ~]#
{code}

So, the bridge configuration default acl file exists in {{/etc/qemu/bridge.conf}}, suggesting that qemu-kvm was built with a missing/wrong ./configure parameter?

Looking at the kvm.recipe and ./configure --help, it turns out that --sysconfdir is never explicitly specified?

was:

I'm trying to set up a KVM instance using a bridge network.

However, I'm getting this error message:

{code}
[root@mrwing ~]# qemu-kvm -netdev bridge,id=hn0 -device virtio-net-pci,netdev=hn0,id=nic1 openwrt-x86-kvm_guest-combined-ext4.img
failed to parse default acl file `/usr/etc/qemu/bridge.conf'
failed to launch bridge helper
qemu-kvm: -netdev bridge,id=hn0: Device 'bridge' could not be initialized
[root@mrwing ~]#
{code}

However, the bridge configuration default acl file exists in {{/etc/qemu/bridge.conf}}, suggesting that qemu-kvm was built with a missing/wrong ./configure parameter?

Looking at the kvm.recipe and ./configure --help, it turns out that --sysconfdir is never explicitly specified?

> qemu-kvm looks for /usr/etc/qemu/bridge.conf instead of /etc/qemu/bridge.conf at runtime ?
> ------------------------------------------------------------------------------------------
>

> Key: FL-2912
> URL: https://issues.foresightlinux.org/jira/browse/FL-2912
> Project: Foresight Linux
> Issue Type: Bug

> Security Level: Public(Everyone can see this issue)

> Components: Base Operating System
> Affects Versions: 2.5.x

> Environment: group-xfce-dist-devel=foresight.rpath.org@fl:2-devel/2.5.4+2013.07.12-0.1-1[~!gcc.core]

> Reporter: ermo | Rune Morling
> Assignee: ermo | Rune Morling
>
> I'm trying to set up a KVM instance using a bridge network.
> However, I'm getting this error message:
> {code}
> [root@mrwing ~]# qemu-kvm -netdev bridge,id=hn0 -device virtio-net-pci,netdev=hn0,id=nic1 openwrt-x86-kvm_guest-combined-ext4.img
> failed to parse default acl file `/usr/etc/qemu/bridge.conf'
> failed to launch bridge helper
> qemu-kvm: -netdev bridge,id=hn0: Device 'bridge' could not be initialized
> [root@mrwing ~]#
> {code}

> So, the bridge configuration default acl file exists in {{/etc/qemu/bridge.conf}}, suggesting that qemu-kvm was built with a missing/wrong ./configure parameter?

[ermo | Rune Morling (FITS)]

[ https://issues.foresightlinux.org/jira/browse/FL-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932#action_17932 ]

ermo | Rune Morling commented on FL-2912:
-----------------------------------------

Ok, bug and bugfix confirmed:

Excerpted output of ./configure before fix: {{config directory /usr/etc}}

Excerpted output of ./configure after fix: {{config directory /etc}}

Checking in, building and committing ASAP. :)

> qemu-kvm looks for /usr/etc/qemu/bridge.conf instead of /etc/qemu/bridge.conf at runtime ?
> ------------------------------------------------------------------------------------------
>

> Key: FL-2912
> URL: https://issues.foresightlinux.org/jira/browse/FL-2912
> Project: Foresight Linux
> Issue Type: Bug

> Security Level: Public(Everyone can see this issue)

> Components: Base Operating System
> Affects Versions: 2.5.x

> Environment: group-xfce-dist-devel=foresight.rpath.org@fl:2-devel/2.5.4+2013.07.12-0.1-1[~!gcc.core]

[ermo | Rune Morling (FITS)]

[ https://issues.foresightlinux.org/jira/browse/FL-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ermo | Rune Morling reassigned FL-2912:
---------------------------------------

Assignee: António Meireles [aka doniphon] (was: ermo | Rune Morling)

So, my small configure patch works, but I still can't use qemu-kvm with a bridge setup (most likely a PEBKAC issue).

Could you perhaps provide a working example for me to try, which taps into a bridged network?

> qemu-kvm looks for /usr/etc/qemu/bridge.conf instead of /etc/qemu/bridge.conf at runtime ?
> ------------------------------------------------------------------------------------------
>

> Key: FL-2912
> URL: https://issues.foresightlinux.org/jira/browse/FL-2912
> Project: Foresight Linux
> Issue Type: Bug

> Security Level: Public(Everyone can see this issue)

> Components: Base Operating System
> Affects Versions: 2.5.x

> Environment: group-xfce-dist-devel=foresight.rpath.org@fl:2-devel/2.5.4+2013.07.12-0.1-1[~!gcc.core]
> Reporter: ermo | Rune Morling
> Assignee: António Meireles [aka doniphon]

>
> I'm trying to set up a KVM instance using a bridge network.
> However, I'm getting this error message:
> {code}
> [root@mrwing ~]# qemu-kvm -netdev bridge,id=hn0 -device virtio-net-pci,netdev=hn0,id=nic1 openwrt-x86-kvm_guest-combined-ext4.img
> failed to parse default acl file `/usr/etc/qemu/bridge.conf'
> failed to launch bridge helper
> qemu-kvm: -netdev bridge,id=hn0: Device 'bridge' could not be initialized
> [root@mrwing ~]#
> {code}

> So, the bridge configuration default acl file exists in {{/etc/qemu/bridge.conf}}, suggesting that qemu-kvm was built with a missing/wrong ./configure parameter?

[ermo | Rune Morling (FITS)]

[ https://issues.foresightlinux.org/jira/browse/FL-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933#action_17933 ]

ermo | Rune Morling edited comment on FL-2912 at 7/12/13 6:32 PM:
------------------------------------------------------------------

So, my small configure patch works, but I still can't use qemu-kvm with a bridge setup (most likely a PEBKAC issue).

Could you perhaps provide a working example for me to try, which taps into a bridged network?

I keep getting {{access denied by acl file}} ...

was (Author: ermo):

So, my small configure patch works, but I still can't use qemu-kvm with a bridge setup (most likely a PEBKAC issue).

Could you perhaps provide a working example for me to try, which taps into a bridged network?

> qemu-kvm looks for /usr/etc/qemu/bridge.conf instead of /etc/qemu/bridge.conf at runtime ?
> ------------------------------------------------------------------------------------------
>

> Key: FL-2912
> URL: https://issues.foresightlinux.org/jira/browse/FL-2912
> Project: Foresight Linux
> Issue Type: Bug

> Security Level: Public(Everyone can see this issue)

> Components: Base Operating System
> Affects Versions: 2.5.x

> Environment: group-xfce-dist-devel=foresight.rpath.org@fl:2-devel/2.5.4+2013.07.12-0.1-1[~!gcc.core]
> Reporter: ermo | Rune Morling
> Assignee: António Meireles [aka doniphon]

>
> I'm trying to set up a KVM instance using a bridge network.
> However, I'm getting this error message:
> {code}
> [root@mrwing ~]# qemu-kvm -netdev bridge,id=hn0 -device virtio-net-pci,netdev=hn0,id=nic1 openwrt-x86-kvm_guest-combined-ext4.img
> failed to parse default acl file `/usr/etc/qemu/bridge.conf'
> failed to launch bridge helper
> qemu-kvm: -netdev bridge,id=hn0: Device 'bridge' could not be initialized
> [root@mrwing ~]#
> {code}

> So, the bridge configuration default acl file exists in {{/etc/qemu/bridge.conf}}, suggesting that qemu-kvm was built with a missing/wrong ./configure parameter?

[ermo | Rune Morling (FITS)]

[ https://issues.foresightlinux.org/jira/browse/FL-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933#action_17933 ]

ermo | Rune Morling edited comment on FL-2912 at 7/12/13 6:34 PM:

------------------------------------------------------------------

So, my small configure patch works, but I still can't use qemu-kvm with a bridge setup (most likely a PEBKAC issue).

Could you perhaps provide a working example for me to try, which taps into a bridged network?

I keep getting {{access denied by acl file}} ...

EDIT: It turns out that I need to explicitly specify which bridge device I want to use like so:

{code}
qemu-kvm -netdev bridge,br=virbr0,id=hn0 -device virtio-net-pci,netdev=hn0,id=mywan openwrt-x86-kvm_guest-combined-ext4.img
{code}

was (Author: ermo):
So, my small configure patch works, but I still can't use qemu-kvm with a bridge setup (most likely a PEBKAC issue).

Could you perhaps provide a working example for me to try, which taps into a bridged network?

I keep getting {{access denied by acl file}} ...

> qemu-kvm looks for /usr/etc/qemu/bridge.conf instead of /etc/qemu/bridge.conf at runtime ?
> ------------------------------------------------------------------------------------------
>

> Key: FL-2912
> URL: https://issues.foresightlinux.org/jira/browse/FL-2912
> Project: Foresight Linux
> Issue Type: Bug

> Security Level: Public(Everyone can see this issue)

> Components: Base Operating System
> Affects Versions: 2.5.x

> Environment: group-xfce-dist-devel=foresight.rpath.org@fl:2-devel/2.5.4+2013.07.12-0.1-1[~!gcc.core]
> Reporter: ermo | Rune Morling
> Assignee: António Meireles [aka doniphon]

>
> I'm trying to set up a KVM instance using a bridge network.
> However, I'm getting this error message:
> {code}
> [root@mrwing ~]# qemu-kvm -netdev bridge,id=hn0 -device virtio-net-pci,netdev=hn0,id=nic1 openwrt-x86-kvm_guest-combined-ext4.img
> failed to parse default acl file `/usr/etc/qemu/bridge.conf'
> failed to launch bridge helper
> qemu-kvm: -netdev bridge,id=hn0: Device 'bridge' could not be initialized
> [root@mrwing ~]#
> {code}

> So, the bridge configuration default acl file exists in {{/etc/qemu/bridge.conf}}, suggesting that qemu-kvm was built with a missing/wrong ./configure parameter?

[ermo | Rune Morling (FITS)]

[ https://issues.foresightlinux.org/jira/browse/FL-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933#action_17933 ]

ermo | Rune Morling edited comment on FL-2912 at 7/12/13 7:20 PM:

------------------------------------------------------------------

So, my small configure patch works, but I still can't use qemu-kvm with a bridge setup (most likely a PEBKAC issue).

Could you perhaps provide a working example for me to try, which taps into a bridged network?

I keep getting {{access denied by acl file}} ...

EDIT: It turns out that I need to explicitly specify which bridge device I want to use like so:

{code}
qemu-kvm \
-netdev bridge,br=virbr0,id=hn0 \

-device virtio-net-pci,netdev=hn0,id=nic1 \
<other options>

{code}

was (Author: ermo):
So, my small configure patch works, but I still can't use qemu-kvm with a bridge setup (most likely a PEBKAC issue).

Could you perhaps provide a working example for me to try, which taps into a bridged network?

I keep getting {{access denied by acl file}} ...

EDIT: It turns out that I need to explicitly specify which bridge device I want to use like so:

{code}
qemu-kvm -netdev bridge,br=virbr0,id=hn0 -device virtio-net-pci,netdev=hn0,id=mywan openwrt-x86-kvm_guest-combined-ext4.img
{code}

> qemu-kvm looks for /usr/etc/qemu/bridge.conf instead of /etc/qemu/bridge.conf at runtime ?
> ------------------------------------------------------------------------------------------
>

> Key: FL-2912
> URL: https://issues.foresightlinux.org/jira/browse/FL-2912
> Project: Foresight Linux
> Issue Type: Bug

> Security Level: Public(Everyone can see this issue)

> Components: Base Operating System
> Affects Versions: 2.5.x

> Environment: group-xfce-dist-devel=foresight.rpath.org@fl:2-devel/2.5.4+2013.07.12-0.1-1[~!gcc.core]
> Reporter: ermo | Rune Morling
> Assignee: António Meireles [aka doniphon]

>
> I'm trying to set up a KVM instance using a bridge network.
> However, I'm getting this error message:
> {code}
> [root@mrwing ~]# qemu-kvm -netdev bridge,id=hn0 -device virtio-net-pci,netdev=hn0,id=nic1 openwrt-x86-kvm_guest-combined-ext4.img
> failed to parse default acl file `/usr/etc/qemu/bridge.conf'
> failed to launch bridge helper
> qemu-kvm: -netdev bridge,id=hn0: Device 'bridge' could not be initialized
> [root@mrwing ~]#
> {code}

> So, the bridge configuration default acl file exists in {{/etc/qemu/bridge.conf}}, suggesting that qemu-kvm was built with a missing/wrong ./configure parameter?

[ermo | Rune Morling (FITS)]

[ https://issues.foresightlinux.org/jira/browse/FL-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17935#action_17935 ]

ermo | Rune Morling commented on FL-2912:
-----------------------------------------

FWIW, the fixed version has been committed as {{kvm=/foresight.rpath.org@fl:2-devel/1.3.0-3-1}}

Note that 2-qa has the buggy {{kvm=/foresight.rpath.org@fl:2-devel/1.3.0-2-1}} version -- can it be promoted separately?

> qemu-kvm looks for /usr/etc/qemu/bridge.conf instead of /etc/qemu/bridge.conf at runtime ?
> ------------------------------------------------------------------------------------------
>

> Key: FL-2912
> URL: https://issues.foresightlinux.org/jira/browse/FL-2912
> Project: Foresight Linux
> Issue Type: Bug

> Security Level: Public(Everyone can see this issue)

> Components: Base Operating System
> Affects Versions: 2.5.x

> Environment: group-xfce-dist-devel=foresight.rpath.org@fl:2-devel/2.5.4+2013.07.12-0.1-1[~!gcc.core]
> Reporter: ermo | Rune Morling
> Assignee: António Meireles [aka doniphon]

>
> I'm trying to set up a KVM instance using a bridge network.
> However, I'm getting this error message:
> {code}
> [root@mrwing ~]# qemu-kvm -netdev bridge,id=hn0 -device virtio-net-pci,netdev=hn0,id=nic1 openwrt-x86-kvm_guest-combined-ext4.img
> failed to parse default acl file `/usr/etc/qemu/bridge.conf'
> failed to launch bridge helper
> qemu-kvm: -netdev bridge,id=hn0: Device 'bridge' could not be initialized
> [root@mrwing ~]#
> {code}

> So, the bridge configuration default acl file exists in {{/etc/qemu/bridge.conf}}, suggesting that qemu-kvm was built with a missing/wrong ./configure parameter?

[ermo | Rune Morling (FITS)]

[ https://issues.foresightlinux.org/jira/browse/FL-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17935#action_17935 ]

ermo | Rune Morling edited comment on FL-2912 at 7/14/13 7:38 AM:
------------------------------------------------------------------

FWIW, the fixed version has been committed as {{kvm=/foresight.rpath.org@fl:2-devel/1.3.0-3-1}}

Note that 2-qa has the buggy {{kvm=/foresight.rpath.org@fl:2-qa/1.3.0-2-1}} version -- can it be promoted separately?

was (Author: ermo):

FWIW, the fixed version has been committed as {{kvm=/foresight.rpath.org@fl:2-devel/1.3.0-3-1}}

Note that 2-qa has the buggy {{kvm=/foresight.rpath.org@fl:2-devel/1.3.0-2-1}} version -- can it be promoted separately?

> qemu-kvm looks for /usr/etc/qemu/bridge.conf instead of /etc/qemu/bridge.conf at runtime ?
> ------------------------------------------------------------------------------------------
>

> Key: FL-2912
> URL: https://issues.foresightlinux.org/jira/browse/FL-2912
> Project: Foresight Linux
> Issue Type: Bug

> Security Level: Public(Everyone can see this issue)

> Components: Base Operating System
> Affects Versions: 2.5.x

> Environment: group-xfce-dist-devel=foresight.rpath.org@fl:2-devel/2.5.4+2013.07.12-0.1-1[~!gcc.core]
> Reporter: ermo | Rune Morling
> Assignee: António Meireles [aka doniphon]

>
> I'm trying to set up a KVM instance using a bridge network.
> However, I'm getting this error message:
> {code}
> [root@mrwing ~]# qemu-kvm -netdev bridge,id=hn0 -device virtio-net-pci,netdev=hn0,id=nic1 openwrt-x86-kvm_guest-combined-ext4.img
> failed to parse default acl file `/usr/etc/qemu/bridge.conf'
> failed to launch bridge helper
> qemu-kvm: -netdev bridge,id=hn0: Device 'bridge' could not be initialized
> [root@mrwing ~]#
> {code}

> So, the bridge configuration default acl file exists in {{/etc/qemu/bridge.conf}}, suggesting that qemu-kvm was built with a missing/wrong ./configure parameter?