Hi, You can define any extra attribute, like NETMASK, in the Virtual Network template when you create it. Those attributes can be accessed within the VM using contextualization. In [1], there's a brief example with a DNS field.
Don't forget to make your vmcontext script do something useful with that new attribute. Regards, Carlos. [1] http://opennebula.org/documentation:rel2.2:cong#defining_context -- Carlos Martín, MSc Project Major Contributor OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org <http://www.opennebula.org/> | [email protected] On Tue, Apr 26, 2011 at 3:27 AM, qian.shen <[email protected]> wrote: > I think the "255.255.255.0" is not suitable for the "B" type network. > > > [email protected] wrote: > >> >> In script vmcontexttty ,the subnet mask of virtual machine is setted as >> "255.255.255.0". If the subnet mask of physical PC isn't equal to >> "255.255.255.0", then the physical PC can communicate with virtual machine >> or not? >> >> >> For example: >> >> The physical PC's IP is "10.1.29.105", subnet mask is "255.255.0.0". >> >> The virtual machine's IP is "10.1.29.106", subnet mask is "255.255.255.0". >> >> The physical PC ping the virtual machine failure. >> >> >> I set virtual machine's subnet mask as "255.255.0.0" by using VNC, then >> The physical PC ping the virtual machine success. >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >> >> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
