subject:"Re\: \[one\-users\] Can't access to VM through ssh"

Re: [one-users] Can't access to VM through ssh

2010-07-06 Thread Andrea Turli


Hello Carlos,

thank you for your explanation.

On 07/05/2010 03:19 PM, Carlos Martín Sánchez wrote:

Hello Andrea,

2010/7/2 Andrea Turli mailto:andrea.tu...@eng.it>>

this public IP is one of our subnet 62.101.90.192/27
 without DHCP.


some network parameters are not correct (like NETWORK; NETMASK and
BROADCAST). In fact, if I change them manually and restart the
network, everything works.
Is there any way to configure it in the "publi.net
" vnet file?

Thank you,
Andrea


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].


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.

You could add this parameters in the template at the CONTEXT section:

CONTEXT = [
ETH0_NETMASK = "225.225.225.224",
]

Please refer to [2] for a complete guide on how to use this 
contextualization feature.

I've customized the CONTEXT section in ttylinux.one like this:

CONTEXT = [
netmask = "225.225.225.224",
hostname= "$NAME",
files  =  "/srv/cloud/one/one-templates/init.sh",
target  = "hdc",
]

which works perfectly but for the netmask parameter. Infact though I've 
specified netmask = "225.225.225.224" on the VM I got:


# ifconfig
eth0  Link encap:Ethernet  HWaddr 00:03:3E:65:5A:C4
  Bcast:62.255.255.255  Mask:255.0.0.0

and it's not correct, obviously.

If I set manually inside "init.sh" the NETMASK value, everything works.


Thank you very much,
Andrea



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.


Regards,
Carlos

[0] 
http://www.opennebula.org/documentation:rel1.4:vgg#using_the_leases_within_the_virtual_machine
[1] 
http://dev.opennebula.org/projects/opennebula/repository/revisions/master/show/share/scripts

[2] http://www.opennebula.org/documentation:rel1.4:cong



Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing:
http://www.OpenNebula.org


El 30 de junio de 2010 16:18, Andrea Turli mailto:andrea.tu...@eng.it>> escribió:

Hi Carlos,


On 06/30/2010 04:07 PM, Carlos Martín Sánchez wrote:

Hi Andrea,

Did you manage to access the VM through ssh? or are you
using VNC?

Not yet, I can access through virt-manager or virsh to the VM
but not through ssh, cause network doesn't work.



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.
Or just configure the VM template to attach a network
interface to the public network.


Any ideas?




Regards,

Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing:
http://www.OpenNebula.org


2010/6/28 Andrea Turli mailto:andrea.tu...@eng.it>>

Hi all,

unfortunately also running the fsck on the .img didn't
solve the problem. Here my situation:

- 1 x frontend: ubuntu 10.04 - KVM - NFS
- 1 x cluster node: ubuntu 10.04 - KVM - NFS

A ttylinux VM has been started correctly on the worker
node. From the front end:
# onevm list
  ID USER NAME STAT CPU MEM   
HOSTNAMETIME

  21 oneadmin ttylinux runn   0   65536 grids21.eng.it
 00 00:10:22

# onevnet list
  ID USER NAME  TYPE BRIDGE #LEASES
   8 oneadmin public  Rangedbr0   0
   9 oneadmin private  Fixedbr0   1


The ttylinux VM shows this:
# ifconfig
eth0  . inet address 192.168.0.6 ...

but I cannot ping anything from this VM


To help the investigation, here the bctrl show command
on the cluester node
$ brctl show
bridge namebridge idSTP enabledinterfaces
br08000.0019b9e57ae5noeth0   vnet0
virbr08000.yes

Thank you again for any help,
Andrea


On 06/26/2010 09:50 AM, ranjith k wrote:

hello,
run the command "qemu-syetm_x86 ttylinux.img" from the
ttylinux image directory..you ca

Re: [one-users] Can't access to VM through ssh

2010-07-05 Thread Carlos Martín Sánchez

Hello Andrea,

2010/7/2 Andrea Turli 


> this public IP is one of our subnet 62.101.90.192/27 without DHCP.
>
>
> some network parameters are not correct (like NETWORK; NETMASK and
> BROADCAST). In fact, if I change them manually and restart the network,
> everything works.
> Is there any way to configure it in the "publi.net" vnet file?
>
> Thank you,
> Andrea
>
>
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].

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.
You could add this parameters in the template at the CONTEXT section:

CONTEXT = [
ETH0_NETMASK = "225.225.225.224",
]

Please refer to [2] for a complete guide on how to use this
contextualization feature.

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.

Regards,
Carlos

[0]
http://www.opennebula.org/documentation:rel1.4:vgg#using_the_leases_within_the_virtual_machine
[1]
http://dev.opennebula.org/projects/opennebula/repository/revisions/master/show/share/scripts
[2] http://www.opennebula.org/documentation:rel1.4:cong


>
> Carlos Martín, Cloud Technology Engineer/Researcher
> DSA Research Group: web http://dsa-research.org and blog
> http://blog.dsa-research.org
> OpenNebula Open Source Toolkit for Cloud Computing:
> http://www.OpenNebula.org
>
>
> El 30 de junio de 2010 16:18, Andrea Turli  escribió:
>
>> Hi Carlos,
>>
>>
>> On 06/30/2010 04:07 PM, Carlos Martín Sánchez wrote:
>>
>> Hi Andrea,
>>
>> Did you manage to access the VM through ssh? or are you using VNC?
>>
>>  Not yet, I can access through virt-manager or virsh to the VM but not
>> through ssh, cause network doesn't work.
>>
>>
>> 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.
>> Or just configure the VM template to attach a network interface to the
>> public network.
>>
>>  Any ideas?
>>
>>
>>
>> Regards,
>>
>> Carlos Martín, Cloud Technology Engineer/Researcher
>> DSA Research Group: web http://dsa-research.org and blog
>> http://blog.dsa-research.org
>> OpenNebula Open Source Toolkit for Cloud Computing:
>> http://www.OpenNebula.org
>>
>>
>> 2010/6/28 Andrea Turli 
>>
>>> Hi all,
>>>
>>> unfortunately also running the fsck on the .img didn't solve the problem.
>>> Here my situation:
>>>
>>> - 1 x frontend: ubuntu 10.04 - KVM - NFS
>>> - 1 x cluster node: ubuntu 10.04 - KVM - NFS
>>>
>>> A ttylinux VM has been started correctly on the worker node. From the
>>> front end:
>>> # onevm list
>>>   ID USER NAME STAT CPU MEMHOSTNAMETIME
>>>   21 oneadmin ttylinux runn   0   65536  grids21.eng.it 00 00:10:22
>>>
>>> # onevnet list
>>>   ID USER NAME  TYPE BRIDGE #LEASES
>>>8 oneadmin public  Rangedbr0   0
>>>9 oneadmin private  Fixedbr0   1
>>>
>>>
>>> The ttylinux VM shows this:
>>> # ifconfig
>>> eth0  . inet address 192.168.0.6 ...
>>>
>>> but I cannot ping anything from this VM
>>>
>>>
>>> To help the investigation, here the bctrl show command on the cluester
>>> node
>>> $ brctl show
>>> bridge namebridge idSTP enabledinterfaces
>>> br08000.0019b9e57ae5noeth0   vnet0
>>> virbr08000.yes
>>>
>>> Thank you again for any help,
>>> Andrea
>>>
>>>
>>> On 06/26/2010 09:50 AM, ranjith k wrote:
>>>
>>> hello,
>>> run the command "qemu-syetm_x86 ttylinux.img" from the ttylinux image
>>> directory..you can see a window and will start boot ttylinux...
>>> 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 .
>>>
>>> On Fri, Jun 25, 2010 at 3:51 PM, Andrea Turli wrote:
>>>
 Dear all,

 I'm trying to access through ssh to my instance of ttylinux VM created
 following this guide http://www.opennebula.org/documentation:rel1.4:vmg
 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.

 I've seen also this 
 threadhttp://lists.opennebula.org/pipermail/users-opennebula.org/2010-June/002220.htmlwith
  a similar problem, but also fsck on that VM doesn't help me to solve
 the situation.

 Could it be related to the network configuration of my kvm

Re: [one-users] Can't access to VM through ssh

2010-07-02 Thread Andrea Turli


Hi Carlos,

On 06/30/2010 04:37 PM, Carlos Martín Sánchez wrote:

Hi again,

Let's check the basics, just in case:
a) The ttylinux machine you are using is the one downloaded from our 
site, so it is correctly contextualized.
b) And you are trying to access the VM 192.168.0.6 from a machine in 
the same 192.168.0.X network, right?


You may want to try adding another NIC attribute to the template, 
attached to your public network. This way you could access the VM from 
anywhere, not just the private network.
We area trying to add another NIC to our template. This is the public 
vnet file we have prepared:


NAME = "public"
TYPE = FIXED

#Now we'll use the cluster private network (physical)
BRIDGE = br0
LEASES = [IP=62.101.90.195]

this public IP is one of our subnet 62.101.90.192/27 without DHCP.

If we create a VM starting from ttylinux template you provided with this 
public vnet, I can start the machine but in the boot log I can see this 
problem:


/etc/rc.d/rc.startup/10.network: line 78 : ./ifup-eth0.template: No such 
file or directory


Anyway I can log in through virt-manager and ifconfig show this

# ifconfig
eth0  Link encap:Ethernet  HWaddr 00:03:3E:65:5A:C3
  inet addr:62.101.90.195  Bcast:62.101.90.223  
Mask:255.255.255.224

  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:74 errors:0 dropped:0 overruns:0 frame:0
  TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:8683 (8.4 KiB)  TX bytes:4177 (4.0 KiB)
  Interrupt:11 Base address:0xc100

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


and there is the problem:

# cat /etc/sysconfig/network-scripts/ifcfg-eth0
ENABLE=yes
NAME=Ethernet
IPADDRESS=62.101.90.195
CIDRLEN=24
NETWORK=62.101.90.0
NETMASK=255.255.255.0
BROADCAST=62.101.90.255
DHCP=no
GATEWAY=62.101.90.1

some network parameters are not correct (like NETWORK; NETMASK and 
BROADCAST). In fact, if I change them manually and restart the network, 
everything works.

Is there any way to configure it in the "publi.net" vnet file?

Thank you,
Andrea




Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog 
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing: 
http://www.OpenNebula.org



El 30 de junio de 2010 16:18, Andrea Turli > escribió:


Hi Carlos,


On 06/30/2010 04:07 PM, Carlos Martín Sánchez wrote:

Hi Andrea,

Did you manage to access the VM through ssh? or are you using VNC?

Not yet, I can access through virt-manager or virsh to the VM but
not through ssh, cause network doesn't work.



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.
Or just configure the VM template to attach a network interface
to the public network.


Any ideas?




Regards,

Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing:
http://www.OpenNebula.org


2010/6/28 Andrea Turli mailto:andrea.tu...@eng.it>>

Hi all,

unfortunately also running the fsck on the .img didn't solve
the problem. Here my situation:

- 1 x frontend: ubuntu 10.04 - KVM - NFS
- 1 x cluster node: ubuntu 10.04 - KVM - NFS

A ttylinux VM has been started correctly on the worker node.
From the front end:
# onevm list
  ID USER NAME STAT CPU MEM   
HOSTNAMETIME

  21 oneadmin ttylinux runn   0   65536 grids21.eng.it
 00 00:10:22

# onevnet list
  ID USER NAME  TYPE BRIDGE #LEASES
   8 oneadmin public  Rangedbr0   0
   9 oneadmin private  Fixedbr0   1


The ttylinux VM shows this:
# ifconfig
eth0  . inet address 192.168.0.6 ...

but I cannot ping anything from this VM


To help the investigation, here the bctrl show command on the
cluester node
$ brctl show
bridge namebridge idSTP enabledinterfaces
br08000.0019b9e57ae5noeth0   vnet0
virbr08000.yes

Thank you again for any help,
Andrea


On 06/26/2010 09:50 AM, ranjith k wrote:

hello,
run the command "qemu-syetm_x86 ttylinux.img" from the

Re: [one-users] Can't access to VM through ssh

2010-06-30 Thread Carlos Martín Sánchez

b) And you are trying to access the VM 192.168.0.6 from a machine in the
same 192.168.0.X network, right?


Opss ... shall I? I mean, I'm trying to access to the machine from the
> opennebula cluster node which has a public IP. Is it correct?
>

Yes, try reaching the VM from the 192.168.0.X network, that's probably your
problem.

Good luck,

Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing:
http://www.OpenNebula.org
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Can't access to VM through ssh

2010-06-30 Thread Andrea Turli


Hi,

On 06/30/2010 04:37 PM, Carlos Martín Sánchez wrote:

Hi again,

Let's check the basics, just in case:
a) The ttylinux machine you are using is the one downloaded from our 
site, so it is correctly contextualized.
I think so, I'm following the guide here 
http://www.opennebula.org/documentation:rel1.4:vmg
b) And you are trying to access the VM 192.168.0.6 from a machine in 
the same 192.168.0.X network, right?
Opss ... shall I? I mean, I'm trying to access to the machine from the 
opennebula cluster node which has a public IP. Is it correct?


You may want to try adding another NIC attribute to the template, 
attached to your public network. This way you could access the VM from 
anywhere, not just the private network.


Thank you again.



Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog 
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing: 
http://www.OpenNebula.org



El 30 de junio de 2010 16:18, Andrea Turli > escribió:


Hi Carlos,


On 06/30/2010 04:07 PM, Carlos Martín Sánchez wrote:

Hi Andrea,

Did you manage to access the VM through ssh? or are you using VNC?

Not yet, I can access through virt-manager or virsh to the VM but
not through ssh, cause network doesn't work.



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.
Or just configure the VM template to attach a network interface
to the public network.


Any ideas?




Regards,

Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing:
http://www.OpenNebula.org


2010/6/28 Andrea Turli mailto:andrea.tu...@eng.it>>

Hi all,

unfortunately also running the fsck on the .img didn't solve
the problem. Here my situation:

- 1 x frontend: ubuntu 10.04 - KVM - NFS
- 1 x cluster node: ubuntu 10.04 - KVM - NFS

A ttylinux VM has been started correctly on the worker node.
From the front end:
# onevm list
  ID USER NAME STAT CPU MEM   
HOSTNAMETIME

  21 oneadmin ttylinux runn   0   65536 grids21.eng.it
 00 00:10:22

# onevnet list
  ID USER NAME  TYPE BRIDGE #LEASES
   8 oneadmin public  Rangedbr0   0
   9 oneadmin private  Fixedbr0   1


The ttylinux VM shows this:
# ifconfig
eth0  . inet address 192.168.0.6 ...

but I cannot ping anything from this VM


To help the investigation, here the bctrl show command on the
cluester node
$ brctl show
bridge namebridge idSTP enabledinterfaces
br08000.0019b9e57ae5noeth0   vnet0
virbr08000.yes

Thank you again for any help,
Andrea


On 06/26/2010 09:50 AM, ranjith k wrote:

hello,
run the command "qemu-syetm_x86 ttylinux.img" from the
ttylinux image directory..you can see a window and will
start boot ttylinux...
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 .

On Fri, Jun 25, 2010 at 3:51 PM, Andrea Turli
mailto:andrea.tu...@eng.it>> wrote:

Dear all,

I'm trying to access through ssh to my instance of
ttylinux VM created following this guide
http://www.opennebula.org/documentation:rel1.4:vmg
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.

I've seen also this thread

http://lists.opennebula.org/pipermail/users-opennebula.org/2010-June/002220.html
with a similar problem, but also fsck on that VM doesn't
help me to solve the situation.

Could it be related to the network configuration of my
kvm host?

-- 
Andrea Turli

Ricercatore
Direzione Ricerca e Innovazione
andrea.tu...@eng.it  

Engineering Ingegneria Informatica spa
Via Riccardo Morandi, 32 00148 Roma (RM)

Re: [one-users] Can't access to VM through ssh

2010-06-30 Thread Carlos Martín Sánchez

Hi again,

Let's check the basics, just in case:
a) The ttylinux machine you are using is the one downloaded from our site,
so it is correctly contextualized.
b) And you are trying to access the VM 192.168.0.6 from a machine in the
same 192.168.0.X network, right?

You may want to try adding another NIC attribute to the template, attached
to your public network. This way you could access the VM from anywhere, not
just the private network.

Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing:
http://www.OpenNebula.org


El 30 de junio de 2010 16:18, Andrea Turli  escribió:

>  Hi Carlos,
>
>
> On 06/30/2010 04:07 PM, Carlos Martín Sánchez wrote:
>
> Hi Andrea,
>
> Did you manage to access the VM through ssh? or are you using VNC?
>
> Not yet, I can access through virt-manager or virsh to the VM but not
> through ssh, cause network doesn't work.
>
>
> 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.
> Or just configure the VM template to attach a network interface to the
> public network.
>
>  Any ideas?
>
>
>
> Regards,
>
> Carlos Martín, Cloud Technology Engineer/Researcher
> DSA Research Group: web http://dsa-research.org and blog
> http://blog.dsa-research.org
> OpenNebula Open Source Toolkit for Cloud Computing:
> http://www.OpenNebula.org
>
>
> 2010/6/28 Andrea Turli 
>
>> Hi all,
>>
>> unfortunately also running the fsck on the .img didn't solve the problem.
>> Here my situation:
>>
>> - 1 x frontend: ubuntu 10.04 - KVM - NFS
>> - 1 x cluster node: ubuntu 10.04 - KVM - NFS
>>
>> A ttylinux VM has been started correctly on the worker node. From the
>> front end:
>> # onevm list
>>   ID USER NAME STAT CPU MEMHOSTNAMETIME
>>   21 oneadmin ttylinux runn   0   65536  grids21.eng.it 00 00:10:22
>>
>> # onevnet list
>>   ID USER NAME  TYPE BRIDGE #LEASES
>>8 oneadmin public  Rangedbr0   0
>>9 oneadmin private  Fixedbr0   1
>>
>>
>> The ttylinux VM shows this:
>> # ifconfig
>> eth0  . inet address 192.168.0.6 ...
>>
>> but I cannot ping anything from this VM
>>
>>
>> To help the investigation, here the bctrl show command on the cluester
>> node
>> $ brctl show
>> bridge namebridge idSTP enabledinterfaces
>> br08000.0019b9e57ae5noeth0   vnet0
>> virbr08000.yes
>>
>> Thank you again for any help,
>> Andrea
>>
>>
>> On 06/26/2010 09:50 AM, ranjith k wrote:
>>
>> hello,
>> run the command "qemu-syetm_x86 ttylinux.img" from the ttylinux image
>> directory..you can see a window and will start boot ttylinux...
>> 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 .
>>
>> On Fri, Jun 25, 2010 at 3:51 PM, Andrea Turli wrote:
>>
>>> Dear all,
>>>
>>> I'm trying to access through ssh to my instance of ttylinux VM created
>>> following this guide http://www.opennebula.org/documentation:rel1.4:vmg
>>> 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.
>>>
>>> I've seen also this 
>>> threadhttp://lists.opennebula.org/pipermail/users-opennebula.org/2010-June/002220.htmlwith
>>>  a similar problem, but also fsck on that VM doesn't help me to solve
>>> the situation.
>>>
>>> Could it be related to the network configuration of my kvm host?
>>>
>>> --
>>> Andrea Turli
>>> Ricercatore
>>> Direzione Ricerca e innovazioneandrea.tu...@eng.it
>>>
>>> Engineering Ingegneria Informatica spa
>>> Via Riccardo Morandi, 32 00148 Roma (RM)
>>> Tel. +39 06 8307 4710
>>> Fax +39 06 8307 4200 www.eng.it
>>>
>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>
>>>
>>
>>
>> --
>> Andrea Turli
>> Ricercatore
>> Direzione Ricerca e innovazioneandrea.tu...@eng.it
>>
>> Engineering Ingegneria Informatica spa
>> Via Riccardo Morandi, 32 00148 Roma (RM)
>> Tel. +39 06 8307 4710
>> Fax +39 06 8307 4200 www.eng.it
>>
>>
>> ___
>> Users mailing list
>> Users@lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>
>
> --
> Andrea Turli
> Ricercatore
> Direzione Ricerca e innovazioneandrea.tu...@eng.it
>
> Engineering Ingegneria Informatica spa
> Via Riccardo Morandi, 32 00148 Roma (RM)
> Tel

Re: [one-users] Can't access to VM through ssh

2010-06-30 Thread Andrea Turli


Hi Carlos,

On 06/30/2010 04:07 PM, Carlos Martín Sánchez wrote:

Hi Andrea,

Did you manage to access the VM through ssh? or are you using VNC?
Not yet, I can access through virt-manager or virsh to the VM but not 
through ssh, cause network doesn't work.


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.
Or just configure the VM template to attach a network interface to the 
public network.



Any ideas?



Regards,

Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog 
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing: 
http://www.OpenNebula.org



2010/6/28 Andrea Turli mailto:andrea.tu...@eng.it>>

Hi all,

unfortunately also running the fsck on the .img didn't solve the
problem. Here my situation:

- 1 x frontend: ubuntu 10.04 - KVM - NFS
- 1 x cluster node: ubuntu 10.04 - KVM - NFS

A ttylinux VM has been started correctly on the worker node. From
the front end:
# onevm list
  ID USER NAME STAT CPU MEMHOSTNAMETIME
  21 oneadmin ttylinux runn   0   65536 grids21.eng.it
 00 00:10:22

# onevnet list
  ID USER NAME  TYPE BRIDGE #LEASES
   8 oneadmin public  Rangedbr0   0
   9 oneadmin private  Fixedbr0   1


The ttylinux VM shows this:
# ifconfig
eth0  . inet address 192.168.0.6 ...

but I cannot ping anything from this VM


To help the investigation, here the bctrl show command on the
cluester node
$ brctl show
bridge namebridge idSTP enabledinterfaces
br08000.0019b9e57ae5noeth0   vnet0
virbr08000.yes

Thank you again for any help,
Andrea


On 06/26/2010 09:50 AM, ranjith k wrote:

hello,
run the command "qemu-syetm_x86 ttylinux.img" from the ttylinux
image directory..you can see a window and will start boot ttylinux...
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 .

On Fri, Jun 25, 2010 at 3:51 PM, Andrea Turli
mailto:andrea.tu...@eng.it>> wrote:

Dear all,

I'm trying to access through ssh to my instance of ttylinux
VM created following this guide
http://www.opennebula.org/documentation:rel1.4:vmg
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.

I've seen also this thread

http://lists.opennebula.org/pipermail/users-opennebula.org/2010-June/002220.html
with a similar problem, but also fsck on that VM doesn't help
me to solve the situation.

Could it be related to the network configuration of my kvm host?

-- 
Andrea Turli

Ricercatore
Direzione Ricerca e Innovazione
andrea.tu...@eng.it  

Engineering Ingegneria Informatica spa
Via Riccardo Morandi, 32 00148 Roma (RM)
Tel. +39 06 8307 4710
Fax +39 06 8307 4200
www.eng.it  

 



___
Users mailing list
Users@lists.opennebula.org 
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org





-- 
Andrea Turli

Ricercatore
Direzione Ricerca e Innovazione
andrea.tu...@eng.it  

Engineering Ingegneria Informatica spa
Via Riccardo Morandi, 32 00148 Roma (RM)
Tel. +39 06 8307 4710
Fax +39 06 8307 4200
www.eng.it  

 



___
Users mailing list
Users@lists.opennebula.org 
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org





--
Andrea Turli
Ricercatore
Direzione Ricerca e Innovazione
andrea.tu...@eng.it

Engineering Ingegneria Informatica spa
Via Riccardo Morandi, 32 00148 Roma (RM)
Tel. +39 06 8307 4710
Fax +39 06 8307 4200
www.eng.it


___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Can't access to VM through ssh

2010-06-30 Thread Carlos Martín Sánchez

Hi Andrea,

Did you manage to access the VM through ssh? or are you using VNC?

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.
Or just configure the VM template to attach a network interface to the
public network.

Regards,

Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing:
http://www.OpenNebula.org


2010/6/28 Andrea Turli 

>  Hi all,
>
> unfortunately also running the fsck on the .img didn't solve the problem.
> Here my situation:
>
> - 1 x frontend: ubuntu 10.04 - KVM - NFS
> - 1 x cluster node: ubuntu 10.04 - KVM - NFS
>
> A ttylinux VM has been started correctly on the worker node. From the front
> end:
> # onevm list
>   ID USER NAME STAT CPU MEMHOSTNAMETIME
>   21 oneadmin ttylinux runn   0   65536  grids21.eng.it 00 00:10:22
>
> # onevnet list
>   ID USER NAME  TYPE BRIDGE #LEASES
>8 oneadmin public  Rangedbr0   0
>9 oneadmin private  Fixedbr0   1
>
>
> The ttylinux VM shows this:
> # ifconfig
> eth0  . inet address 192.168.0.6 ...
>
> but I cannot ping anything from this VM
>
>
> To help the investigation, here the bctrl show command on the cluester node
> $ brctl show
> bridge namebridge idSTP enabledinterfaces
> br08000.0019b9e57ae5noeth0   vnet0
> virbr08000.yes
>
> Thank you again for any help,
> Andrea
>
>
> On 06/26/2010 09:50 AM, ranjith k wrote:
>
> hello,
> run the command "qemu-syetm_x86 ttylinux.img" from the ttylinux image
> directory..you can see a window and will start boot ttylinux...
> 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 .
>
> On Fri, Jun 25, 2010 at 3:51 PM, Andrea Turli  wrote:
>
>> Dear all,
>>
>> I'm trying to access through ssh to my instance of ttylinux VM created
>> following this guide http://www.opennebula.org/documentation:rel1.4:vmg
>> 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.
>>
>> I've seen also this 
>> threadhttp://lists.opennebula.org/pipermail/users-opennebula.org/2010-June/002220.htmlwith
>>  a similar problem, but also fsck on that VM doesn't help me to solve
>> the situation.
>>
>> Could it be related to the network configuration of my kvm host?
>>
>> --
>> Andrea Turli
>> Ricercatore
>> Direzione Ricerca e innovazioneandrea.tu...@eng.it
>>
>> Engineering Ingegneria Informatica spa
>> Via Riccardo Morandi, 32 00148 Roma (RM)
>> Tel. +39 06 8307 4710
>> Fax +39 06 8307 4200 www.eng.it
>>
>>
>> ___
>> Users mailing list
>> Users@lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>
>
> --
> Andrea Turli
> Ricercatore
> Direzione Ricerca e innovazioneandrea.tu...@eng.it
>
> Engineering Ingegneria Informatica spa
> Via Riccardo Morandi, 32 00148 Roma (RM)
> Tel. +39 06 8307 4710
> Fax +39 06 8307 4200 www.eng.it
>
>
> ___
> Users mailing list
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Can't access to VM through ssh

2010-06-28 Thread Andrea Turli


Hi all,

unfortunately also running the fsck on the .img didn't solve the 
problem. Here my situation:


- 1 x frontend: ubuntu 10.04 - KVM - NFS
- 1 x cluster node: ubuntu 10.04 - KVM - NFS

A ttylinux VM has been started correctly on the worker node. From the 
front end:

# onevm list
  ID USER NAME STAT CPU MEMHOSTNAMETIME
  21 oneadmin ttylinux runn   0   65536  grids21.eng.it 00 00:10:22

# onevnet list
  ID USER NAME  TYPE BRIDGE #LEASES
   8 oneadmin public  Rangedbr0   0
   9 oneadmin private  Fixedbr0   1


The ttylinux VM shows this:
# ifconfig
eth0  . inet address 192.168.0.6 ...

but I cannot ping anything from this VM


To help the investigation, here the bctrl show command on the cluester node
$ brctl show
bridge namebridge idSTP enabledinterfaces
br08000.0019b9e57ae5noeth0   vnet0
virbr08000.yes

Thank you again for any help,
Andrea

On 06/26/2010 09:50 AM, ranjith k wrote:

hello,
run the command "qemu-syetm_x86 ttylinux.img" from the ttylinux image 
directory..you can see a window and will start boot ttylinux...
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 .


On Fri, Jun 25, 2010 at 3:51 PM, Andrea Turli > wrote:


Dear all,

I'm trying to access through ssh to my instance of ttylinux VM
created following this guide
http://www.opennebula.org/documentation:rel1.4:vmg
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.

I've seen also this thread

http://lists.opennebula.org/pipermail/users-opennebula.org/2010-June/002220.html
with a similar problem, but also fsck on that VM doesn't help me
to solve the situation.

Could it be related to the network configuration of my kvm host?

-- 
Andrea Turli

Ricercatore
Direzione Ricerca e Innovazione
andrea.tu...@eng.it  

Engineering Ingegneria Informatica spa
Via Riccardo Morandi, 32 00148 Roma (RM)
Tel. +39 06 8307 4710
Fax +39 06 8307 4200
www.eng.it  

 



___
Users mailing list
Users@lists.opennebula.org 
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org





--
Andrea Turli
Ricercatore
Direzione Ricerca e Innovazione
andrea.tu...@eng.it

Engineering Ingegneria Informatica spa
Via Riccardo Morandi, 32 00148 Roma (RM)
Tel. +39 06 8307 4710
Fax +39 06 8307 4200
www.eng.it


___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Can't access to VM through ssh

2010-06-26 Thread ranjith k

hello,
run the command "qemu-syetm_x86 ttylinux.img" from the ttylinux image
directory..you can see a window and will start boot ttylinux...
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 .

On Fri, Jun 25, 2010 at 3:51 PM, Andrea Turli  wrote:

>  Dear all,
>
> I'm trying to access through ssh to my instance of ttylinux VM created
> following this guide http://www.opennebula.org/documentation:rel1.4:vmg
> 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.
>
> I've seen also this 
> threadhttp://lists.opennebula.org/pipermail/users-opennebula.org/2010-June/002220.htmlwith
>  a similar problem, but also fsck on that VM doesn't help me to solve
> the situation.
>
> Could it be related to the network configuration of my kvm host?
>
> --
> Andrea Turli
> Ricercatore
> Direzione Ricerca e innovazioneandrea.tu...@eng.it
>
> Engineering Ingegneria Informatica spa
> Via Riccardo Morandi, 32 00148 Roma (RM)
> Tel. +39 06 8307 4710
> Fax +39 06 8307 4200 www.eng.it
>
>
> ___
> Users mailing list
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Can't access to VM through ssh

Re: [one-users] Can't access to VM through ssh

Re: [one-users] Can't access to VM through ssh

Re: [one-users] Can't access to VM through ssh

Re: [one-users] Can't access to VM through ssh

Re: [one-users] Can't access to VM through ssh

Re: [one-users] Can't access to VM through ssh

Re: [one-users] Can't access to VM through ssh

Re: [one-users] Can't access to VM through ssh

Re: [one-users] Can't access to VM through ssh

10 matches

Site Navigation

Mail list logo

Footer information