On Thu, Aug 28, 2014 at 01:50:22PM +0530, Shanil S wrote:
> Hi Aill,
>
> We are creating two nics using the api, but it seems the second network is
> not come up and the first one is working. The following xml is used to for
> the nic creation
>
> <nic>
>     <interface>virtio</interface>
>     <name>eth0</name>
>     <boot_protocol>static</boot_protocol>
>     <mac address='".$ip->mac_address."'/>
>     <network>
>      <ip address='".$ip->mac_ip."' netmask='255.255.255.0'
> gateway='".$ip->mac_gateway."'/>
>     </network>
>     <on_boot>true</on_boot>
>     <vnic_profile id='bbabc471-667d-4221-bc8e-4ab30b3dcc34' />
>    </nic>
>
> <nic>
>     <interface>virtio</interface>
>     <name>eth1</name>
>     <boot_protocol>static</boot_protocol>
>     <mac address='".$ip->mac_address."'/>
>     <network>
>      <ip address='".$ip->mac_ip."' netmask='255.255.255.0'
> gateway='".$ip->mac_gateway."'/>
>     </network>
>     <on_boot>true</on_boot>
>     <vnic_profile id='037d806f-d76b-4da3-84b6-ac7a5087f836' />
>    </nic>
>
> When i checked the configuration file
> (/etc/sysconfig/network-scripts/ifcfg-eth1) after creating...i find it
> seems the ONBOOT=no.....eventhough we set it true from the api. Is this a
> bug ?

I do not know what "on_boot" means in oVirt API, but it certainly is not
passed to Vdsm or the guest, and as such cannot control what's in the
guest's /etc/sysconfig/network-scripts/ifcfg-eth1.

The guest may have ifcfg files, it may run NetworkManager, or it may be
Ubunto or Windows. oVirt is responsible to exposing a (virtual) NIC to
the guest, but does not interfere with its configuration.

Dan