On 09/13/2013 10:24 PM, Gianluca Cecchi wrote:
On Sat, Sep 14, 2013 at 1:52 AM, Thomas Suckow wrote:
Everything was completely broken until I disabled NetworkManager, it seemed
to be doing something with the bridge despite NM_MANAGED=no
Donna if it was only a copy/paste typo, but just in ase
On 09/04/2013 09:42 PM, Markus Stockhausen wrote:
Hello,
just in case someone else got this problem. For me it seems to be a naming
convention problem. ifcfg file names did not match the shown interfaces.
Steps to fix it included:
- rename ifcfg-enp1s0, ... scripts to real interface names
On Sat, Sep 14, 2013 at 1:52 AM, Thomas Suckow wrote:
On 09/04/2013 09:42 PM, Markus Stockhausen wrote:
Everything was completely broken until I disabled NetworkManager, it seemed
to be doing something with the bridge despite NM_MANAGED=no
Donna if it was only a copy/paste typo, but just
I was also noticing needing to muck with the network interfaces and
services during the beta. I find it interesting the need to disable
NetworkManager and enable the legacy network service. I found no
reference to this in the documentation for 3.3 and people seem to be
installing it without
Von: users-boun...@ovirt.org [users-boun...@ovirt.org]quot; im Auftrag von
quot;Thomas Suckow [thomas.suc...@pnnl.gov]
Gesendet: Montag, 9. September 2013 18:58
An: users@ovirt.org
Betreff: Re: [Users] OVirt-Engine 3.3 RC - Add Fedora 19 host fails [SOLVED]
I was also noticing needing
Hello,
just in case someone else got this problem. For me it seems to be a naming
convention problem. ifcfg file names did not match the shown interfaces.
Steps to fix it included:
- rename ifcfg-enp1s0, ... scripts to real interface names ifcfg-p49p1, ...
- remove parameter NAME from these
6 matches
Mail list logo
