I advise you not to do this by hand if you don't now what you are
doing. From the top of my head (have not tested the procedure):
* Change /var/lib/one/vms/20/context.sh to add network contextualization info:
ETH0_GATEWAY=172.16.192.1
ETH0_IP=172.16.192.64
ETH0_MASK=255.255.0.0
* Create a
The problem is indeed your context section. It does not have
networking configuration.
When creating the template using Sunstone make sure the option Add
Network contextualization in the Context tab is activated.
In case you are creating the template manually add NETWORK=YES in CONTEXT.
On Mon,
Thanks Javier,
Much appreciated. However, how do I fix my current VMs? Is there a way to
do so?
Regards
On Tue, Feb 18, 2014 at 7:21 AM, Javier Fontan jfon...@opennebula.orgwrote:
The problem is indeed your context section. It does not have
networking configuration.
When creating the
Unfortunately the contextualization CD is not regenerated after the VM
is created so the only way to fix it is creating the context CD again
manually.
What you can do is modify the template from where the VMs were created
and start them again.
On Tue, Feb 18, 2014 at 4:52 PM, SysSolutions99
thank You for your help Javier. Here are the details -
$ onevm show 20 -a
VIRTUAL MACHINE 20 INFORMATION
ID : 20
NAME: testvm3
USER: oneadmin
GROUP : oneadmin
STATE : ACTIVE
LCM_STATE : RUNNING
RESCHED
Can you send us the VM definition (onevm show 20 -a). It looks like
the network info is not in the context section.
On Wed, Feb 12, 2014 at 10:21 PM, SysSolutions99
syssolution...@gmail.com wrote:
Hi,
The netmask on my network is 255.255.0.0, yet the VMs get plumbed with
255.255.255.0.
I
