Hey,
as many of you have noticed there wasn't any well working oVirt Node ISO
around for oVirt 3.3.
To get this ball rolling again I've put together a draft image of ALPHA
quality. It contains many fixes some of us have been working on over the
last weeks.
- Source & ISO -
To not drown Jenkins in
Hi Laercio,
Am Freitag, den 17.01.2014, 14:49 -0200 schrieb Laercio Motta:
> I tested the ISO here.
Thanks for being that brave! ;)
> - I was able to register with the engine and aprove (thing with
> 'oVirt-node-3.0.1-iso-1.0.2.vdsm.el6.iso' version was not possible)
Great that this works now
Hi,
> Could you explain this a bit more?
> Did all NICs appear, or did to many NICs appear?
I'm used to udev leave my NIC in sequence.
And in this case it got messed up:
common:
eth0 -> port 1
eth1 -> port 2
ethx >> port X
What happened:
eth0 -> port 1
eth4 -> port 3
eth5 -> port 4
eth6 -> port
Understand?? o.0
2014/1/17 Laercio Motta
> Hi,
>
>
> > Could you explain this a bit more?
> > Did all NICs appear, or did to many NICs appear?
>
> I'm used to udev leave my NIC in sequence.
> And in this case it got messed up:
> common:
> eth0 -> port 1
> eth1 -> port 2
> ethx >> port X
>
> Wha
Am Montag, den 20.01.2014, 13:10 -0200 schrieb Laercio Motta:
> Understand?? o.0
Hey Laercio,
sorry for the delay.
I think I do understand the problem: The NIC order is different the
previously, right?
When you configure a NIC you cna use the button
to identify a special NIC.
We won't change t
No problem.
But I believe this is because the file already has something.
Or he's duplicating information. As you can see in the file I sent, the MAC
of NIC and eth1 eth6 are the same ..
Well, we stayed anyway: P
2014/1/20 Fabian Deutsch
> Am Montag, den 20.01.2014, 13:10 -0200 schrieb Laercio
6 matches
Mail list logo
