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        HOSTNAME        TIME
  21 oneadmin ttylinux runn   0   65536  grids21.eng.it 00 00:10:22

# onevnet list
  ID USER     NAME              TYPE BRIDGE #LEASES
   8 oneadmin public          Ranged    br0       0
   9 oneadmin private          Fixed    br0       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 name    bridge id        STP enabled    interfaces
br0        8000.0019b9e57ae5    no        eth0   vnet0
virbr0        8000.000000000000    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 <andrea.tu...@eng.it <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  <mailto: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  <http://www.eng.it>


    _______________________________________________
    Users mailing list
    Users@lists.opennebula.org <mailto: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

Reply via email to