[one-users] NICs configuration

[Túlio Gomes]

Hmm, i don't think so Carlos, because i can configure the third nic
manually.

But i'll try to instantiate a vm using an ubuntu image and return to you.


2013/2/19 Carlos Martín Sánchez <cmartin at opennebula.org>

> Hi,
>
> I've checked that template, the 3 NICs are created correctly, and the
> deployment file contains the 3 network interfaces. It must be a limitation
> of ttylinux.
>
> Regards
> --
> Carlos Martín, MSc
> Project Engineer
> OpenNebula - The Open-source Solution for Data Center Virtualization
> www.OpenNebula.org | cmartin at opennebula.org | @OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>
>
>
> On Mon, Feb 18, 2013 at 8:06 PM, Túlio Gomes <tulio.gomesbarbosa at gmail.com
> > wrote:
>
>> Hi guys,
>>
>> i'd tried to deploy a virtual machine with three nic's using the
>> following template:
>>
>> <TEMPLATE>
>>  <CPU>0.2</CPU>
>> <MEMORY>128</MEMORY>
>>  <DISK> <IMAGE_ID>7</IMAGE_ID> </DISK>
>> <NIC> <NETWORK_ID>26</NETWORK_ID> </NIC> <!-- control network -->
>>  <NIC> <NETWORK_ID>23</NETWORK_ID> </NIC> <!-- test network 1; vlan
>> isolation -->
>> <NIC> <NETWORK_ID>25</NETWORK_ID> </NIC> <!-- test network 2; vlan
>> isolation -->
>> </TEMPLATE>
>>
>> I also used the ttylinux image available at opennebula marketplace.
>>
>> The deploy was completed successfully, but when i ssh the vm i'd noticed
>> that only two nics was configured (eth0 and eth1).
>>
>> What can i do to configure all the nics using the NIC attribute?
>>
>> --
>> Atenciosamente,
>> Túlio Gomes Barbosa
>> br.linkedin.com/in/tuliogomesbarbosa
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>


-- 
Atenciosamente,
Túlio Gomes Barbosa
br.linkedin.com/in/tuliogomesbarbosa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130219/201d9700/attachment-0002.htm>