[one-users] one-context 4.6 RPM on Fedora 20 VM
terletskiy at emu.ru
Tue Jul 15 07:52:17 PDT 2014
I found the problem in my setup. I'm using 4.2 and it is generating next
As I see 00-network in "get_context_interfaces()" function generating
list of devices from context variables and looking for ETH[0-9] or
ETH[0-9]_MAC in env. My 4.2 not generating this variables, so no network
config. Is it possible to update this package somehow to add backward
compatibility with 4.2?
15.07.2014 17:59, Javier Fontan пишет:
> The configuration file is correctly generated
> (/etc/sysconfig/network-scripts/ifcfg-ens3) but is not started up.
> I've added an ifup after interface configuration. Here is the new
> On Tue, Jul 15, 2014 at 3:08 PM, Javier Fontan <jfontan at opennebula.org> wrote:
>> The linked package is meant to be a fix and should work with network
>> names not called ETH*. I've tested here with a virtio network. I'll
>> try with an emulated card then.
>> On Tue, Jul 15, 2014 at 12:56 PM, Maxim Terletskiy <terletskiy at emu.ru> wrote:
>>> I just installed CentOS 7 and one-context package you linked. All scripts
>>> works ok except network configurator. Looks like this is because vmcontext
>>> script looking for interfaces named eth*, but I configured vm with rtl8139
>>> card and in system this card showing as ens3.
>>> Any ideas about how to fix it?
>>> 14.07.2014 19:14, Javier Fontan пишет:
>>>> I have made some changes to the context packages that hopefully fix
>>>> the problem with Fedora 20. I still could not try the package in
>>>> Fedora 20. It would be great if someone could give it a try.
>>>> It is tested in CentOS 7 and works fine
>>> Users mailing list
>>> Users at lists.opennebula.org
>> Javier Fontán Muiños
>> OpenNebula - Flexible Enterprise Cloud Made Simple
>> www.OpenNebula.org | @OpenNebula | github.com/jfontan
More information about the Users