Hello Rubén, thanks for reporting this, it is in fact a bug. We have created a new ticket and applied a patch. This will be fixed for OpenNebula 3.0.
http://dev.opennebula.org/issues/671 cheers, Jaime On Mon, Jun 6, 2011 at 2:14 PM, Ruben Diez <rd...@cesga.es> wrote: > Hi: > > We are attempt to use an "e1000" network card in a virtual machine running > in a xen virtualization node under OpenNebula control..... > > In a direct xen configuración file this is done by the line: > > vif = > ['model=e1000,mac=02:fe:xx:xx:xx:xx,ip=xxx.xxx.xxx.xxx,bridge=virbrXX',] > > But when we use this line in the openebula template: > > > NIC=[ NETWORK="AAAAAA", IP=xxx.xxx.xxx.xxx, MODEL="e1000" ] > > The generated line in the deployment.0 file is: > > vif = > ['type=e1000,mac=02:fe:xx:xx:xx:xx,ip=xxx.xxx.xxx.xxx,bridge=virbrXX',] > > instead the correct one: > > vif = > ['model=e1000,mac=02:fe:xx:xx:xx:xx,ip=xxx.xxx.xxx.xxx,bridge=virbrXX',] > > > So: how can we do in order to force the xen "model" parameter from the > opennebula machine template??? > > Note that a "model" parameter in the opennebula template correspond to a > "type" parameter in the xen deployment.0, not to a "model" parameter... > > Regards. > > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > -- Jaime Melis, Cloud Technology Engineer/Researcher Major Contributor OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | jme...@opennebula.org
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org