WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Problems accessing to the image

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Problems accessing to the image
From: <juanluis.prietomartinez@xxxxxx>
Date: Thu, 29 Jan 2009 10:43:53 -0000
Delivery-date: Thu, 29 Jan 2009 02:44:54 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmB/npM01qi75MbQf+66aG5YNIvPg==
Thread-topic: Problems accessing to the image

Hi all,

This is my first post in the list. Nowadays I am starting with xen due a work task, for some of you my problem should be something very basic but for me it is taking long hours doing research on the issue and trying different things.

What I have is a Xen image already built and what I want to do is just play it and make it accessible by the network. I can play it, that is not a problem at all, well I had to create a new initialization ram disk due to a conflict between different scsi components. To do that I used this command.

 mkinitrd --omit-scsi-modules --with=xennet --with=xenblk --preload=xenblk initrd-$(uname -r)-no-scsi.img $(uname -r)

Once I did this, I edited the configuration file to point this new disk and the image started as it should have done at the beginning. I am using 4 as run level. This is my configuration file with the network options in it.

    #
    #  Configuration file for the Xen instance agasy, created on
    # Fri Nov 28 14:15:21 2008.
    #


    #
    #  Kernel + memory size
    #
    #kernel  = '/boot/vmlinuz-2.6.18-6-xen-vserver-686'
    #ramdisk = '/boot/initrd.img-2.6.18-6-xen-vserver-686'
    kernel = '/boot/vmlinuz-2.6.18-8.el5xen'
    #ramdisk = '/boot/initrd-2.6.18-8.el5xen.img'
    ramdisk = '/boot/initrd-2.6.18-8.el5xen-no-scsi.img'

    memory  = '512'


    #
    #  Disk device(s).
    #
    root    = '/dev/sda1 ro'

    disk    = [ 'file:/xen/domains/agasy/disk.img,sda1,w', 'file:/xen/domains/agasy/swap.img,sda2,w' ]

    #
    #  Hostname
    #
    name    = 'agasy'


    #
    #  Networking
    #
    #vif  = [ 'ip=193.147.51.146' ]
    #vif = ['bridge=eth0']
    ip='172.25.192.160'
    netmask = '255.255.255.0'
    gateway = '172.25.192.1'

    #
    #  Behaviour
    #

    on_reboot   = 'restart'
    on_crash    = 'restart'

The kernel command for networking is this:

    Bootdata ok (command line is  ip=172.25.192.160:1.2.3.4:172.25.192.1:255.255.255.0::eth0:off root=/dev/sda1 ro)

Everything seems to be ok but still the image is not reachable from anywhere doing ssh on a remote computer. Not even from the host computer, so I know that is running but still I cannot log in to the image.

I have read for the ssh issue that I should run this command:

    ethtool -K eth0 tx off

I have done it already but the result is the same.
Can you please help me with this issue? At this point in the time I don't really know what to do.

Thanks in advance

Juan Luis


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Problems accessing to the image, juanluis.prietomartinez <=