Hello Andrea,<br><br><div class="gmail_quote">2010/7/2 Andrea Turli <span dir="ltr"><<a href="mailto:andrea.turli@eng.it">andrea.turli@eng.it</a>></span>
<div> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div text="#000000" bgcolor="#ffffff">
this public IP is one of our subnet <a href="http://62.101.90.192/27" target="_blank">62.101.90.192/27</a> without DHCP.<br>
<br>
<br>
some network parameters are not correct (like NETWORK; NETMASK and
BROADCAST). In fact, if I change them manually and restart the network,
everything works.<br>
Is there any way to configure it in the "<a href="http://publi.net" target="_blank">publi.net</a>" vnet file?<br>
<br>
Thank you,<br><font color="#888888">
Andrea</font><div><div></div><div class="h5"><br></div></div></div></blockquote><div><br>The default MAC - IP assignment schema assumes a 255.255.255.0 netmask, and may not cover all situations. To learn more about this script, please visit [0] and [1].<br>
<br>If you need more control, and want to customize the way your machines are contextualized, you can use the init.sh script and perform there the changes you haven been doing manually.<br>You could add this parameters in the template at the CONTEXT section:<br>
<br>CONTEXT = [<br> ETH0_NETMASK = "225.225.225.224",<br>]<br><br>Please refer to [2] for a complete guide on how to use this contextualization feature.<br><br>I hope you find the way to adapt OpenNebula to your infrastructure with the instructions given in the documentation, but please don't hesitate to ask about any problem you may find.<br>
<br>Regards,<br>Carlos<br><br>[0] <a href="http://www.opennebula.org/documentation:rel1.4:vgg#using_the_leases_within_the_virtual_machine">http://www.opennebula.org/documentation:rel1.4:vgg#using_the_leases_within_the_virtual_machine</a><br>
[1] <a href="http://dev.opennebula.org/projects/opennebula/repository/revisions/master/show/share/scripts">http://dev.opennebula.org/projects/opennebula/repository/revisions/master/show/share/scripts</a><br>[2] <a href="http://www.opennebula.org/documentation:rel1.4:cong">http://www.opennebula.org/documentation:rel1.4:cong</a><br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div text="#000000" bgcolor="#ffffff"><div><div class="h5">
<blockquote type="cite"><br clear="all">
Carlos Martín, Cloud Technology Engineer/Researcher<br>
DSA Research Group: web <a href="http://dsa-research.org" target="_blank">http://dsa-research.org</a>
and blog <a href="http://blog.dsa-research.org" target="_blank">http://blog.dsa-research.org</a><br>
OpenNebula Open Source Toolkit for Cloud Computing: <a href="http://www.OpenNebula.org" target="_blank">http://www.OpenNebula.org</a><br>
<br>
<br>
<div class="gmail_quote">El 30 de junio de 2010 16:18, Andrea Turli <span dir="ltr"><<a href="mailto:andrea.turli@eng.it" target="_blank">andrea.turli@eng.it</a>></span>
escribió:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff">Hi Carlos,
<div><br>
<br>
On 06/30/2010 04:07 PM, Carlos Martín Sánchez wrote:
<blockquote type="cite">Hi Andrea,<br>
<br>
Did you manage to access the VM through ssh? or are you using VNC?<br>
</blockquote>
</div>
Not yet, I can access through virt-manager or virsh to the VM but not
through ssh, cause network doesn't work.
<div><br>
<blockquote type="cite"><br>
If you can't ping anything from the VM, maybe you could try adding
other VMs to that private network and check if they see each other.<br>
Or just configure the VM template to attach a network interface to the
public network.<br>
<br>
</blockquote>
</div>
Any ideas?
<div>
<div><br>
<br>
<br>
<blockquote type="cite">Regards,<br>
<br clear="all">
Carlos Martín, Cloud Technology Engineer/Researcher<br>
DSA Research Group: web <a href="http://dsa-research.org" target="_blank">http://dsa-research.org</a>
and blog <a href="http://blog.dsa-research.org" target="_blank">http://blog.dsa-research.org</a><br>
OpenNebula Open Source Toolkit for Cloud Computing: <a href="http://www.OpenNebula.org" target="_blank">http://www.OpenNebula.org</a><br>
<br>
<br>
<div class="gmail_quote">2010/6/28 Andrea Turli <span dir="ltr"><<a href="mailto:andrea.turli@eng.it" target="_blank">andrea.turli@eng.it</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff">Hi all,<br>
<br>
unfortunately also running the fsck on the .img didn't solve the
problem. Here my situation:<br>
<br>
- 1 x frontend: ubuntu 10.04 - KVM - NFS<br>
- 1 x cluster node: ubuntu 10.04 - KVM - NFS<br>
<br>
A ttylinux VM has been started correctly on the worker node. From the
front end:<br>
# onevm list<br>
ID USER NAME STAT CPU MEM HOSTNAME TIME<br>
21 oneadmin ttylinux runn 0 65536 <a href="http://grids21.eng.it" target="_blank">grids21.eng.it</a> 00
00:10:22<br>
<br>
# onevnet list<br>
ID USER NAME TYPE BRIDGE #LEASES<br>
8 oneadmin public Ranged br0 0<br>
9 oneadmin private Fixed br0 1<br>
<br>
<br>
The ttylinux VM shows this:<br>
# ifconfig <br>
eth0 ..... inet address 192.168.0.6 ...<br>
<br>
but I cannot ping anything from this VM<br>
<br>
<br>
To help the investigation, here the bctrl show command on the cluester
node<br>
$ brctl show<br>
bridge name bridge id STP enabled interfaces<br>
br0 8000.0019b9e57ae5 no eth0 vnet0<br>
virbr0 8000.000000000000 yes <br>
<br>
Thank you again for any help,<br>
<font color="#888888">Andrea</font>
<div>
<div><br>
<br>
On 06/26/2010 09:50 AM, ranjith k wrote:
<blockquote type="cite">hello,<br>
run the command "qemu-syetm_x86 ttylinux.img" from the ttylinux image
directory..you can see a window and will start boot ttylinux...<br>
and asked password for recover from the disk failure after entering the
password "password" you just run the command "fsck /dev/hda1" it will
remove the error and properly shutdown the system by typing the command
halt or shutdown ....after the correct shutdown and close the window
...and try to run the ttylinux again and verify...is it ok then again
shutdown correctly and copy this ttylinux image for your cloud .....<br>
<br>
<div class="gmail_quote">On Fri, Jun 25, 2010 at 3:51 PM,
Andrea
Turli <span dir="ltr"><<a href="mailto:andrea.turli@eng.it" target="_blank">andrea.turli@eng.it</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"><tt><font size="-1">Dear
all,<br>
<br>
I'm trying to access through ssh to my instance of ttylinux VM created
following this guide </font><a href="http://www.opennebula.org/documentation:rel1.4:vmg" target="_blank">http://www.opennebula.org/documentation:rel1.4:vmg</a><br>
<font size="-1">The VM is running and I've this IP address
(192.168.0.5) according to the "Small Network" network definition but I
cannot neither ping it not access it on ssh.<br>
<br>
I've seen also this thread</font><a href="http://lists.opennebula.org/pipermail/users-opennebula.org/2010-June/002220.html" target="_blank">
http://lists.opennebula.org/pipermail/users-opennebula.org/2010-June/002220.html</a>
with a similar problem, but also fsck on that VM doesn't help me to
solve the situation.<br>
<br>
Could it be related to the network configuration of my kvm host?</tt> <br>
<pre cols="72">--
Andrea Turli
Ricercatore
Direzione Ricerca e Innovazione
<a href="mailto:andrea.turli@eng.it" target="_blank">andrea.turli@eng.it</a>
Engineering Ingegneria Informatica spa
Via Riccardo Morandi, 32 00148 Roma (RM)
Tel. +39 06 8307 4710
Fax +39 06 8307 4200
<a href="http://www.eng.it" target="_blank">www.eng.it</a>
</pre>
</div>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br>
</blockquote>
</div>
<br>
</blockquote>
<br>
<br>
<pre cols="72">--
Andrea Turli
Ricercatore
Direzione Ricerca e Innovazione
<a href="mailto:andrea.turli@eng.it" target="_blank">andrea.turli@eng.it</a>
Engineering Ingegneria Informatica spa
Via Riccardo Morandi, 32 00148 Roma (RM)
Tel. +39 06 8307 4710
Fax +39 06 8307 4200
<a href="http://www.eng.it" target="_blank">www.eng.it</a>
</pre>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br>
</blockquote>
</div>
<br>
</blockquote>
<br>
<br>
<pre cols="72">--
Andrea Turli
Ricercatore
Direzione Ricerca e Innovazione
<a href="mailto:andrea.turli@eng.it" target="_blank">andrea.turli@eng.it</a>
Engineering Ingegneria Informatica spa
Via Riccardo Morandi, 32 00148 Roma (RM)
Tel. +39 06 8307 4710
Fax +39 06 8307 4200
<a href="http://www.eng.it" target="_blank">www.eng.it</a>
</pre>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</blockquote>
<br>
<br>
<pre cols="72">--
Andrea Turli
Ricercatore
Direzione Ricerca e Innovazione
<a href="mailto:andrea.turli@eng.it" target="_blank">andrea.turli@eng.it</a>
Engineering Ingegneria Informatica spa
Via Riccardo Morandi, 32 00148 Roma (RM)
Tel. +39 06 8307 4710
Fax +39 06 8307 4200
<a href="http://www.eng.it" target="_blank">www.eng.it</a>
</pre>
</div></div></div>
</blockquote></div><br clear="all">Carlos Martín, Cloud Technology Engineer/Researcher<br>DSA
Research Group: web <a href="http://dsa-research.org">http://dsa-research.org</a> and blog
<a href="http://blog.dsa-research.org">http://blog.dsa-research.org</a><br>OpenNebula Open Source Toolkit for Cloud
Computing: <a href="http://www.OpenNebula.org">http://www.OpenNebula.org</a><br>