Re: [Xen-users] Re: problems with xen installation

[Anand <xen.mails@xxxxxxxxx>]

Dear Fernando,

Thanks for the reply.

The reason why i am interested in those directives because we want to deploy several domains in an automated fashion. Everytime doing network config inside each domain will be time consuming hence i thought these directives could be used to do the configuration part.

Any other ideas on how this can be automated ?

On 12/29/05, Fernando Maior <fernando.souto.maior@xxxxxxxxx > wrote:

On 12/29/05, Anand <xen.mails@xxxxxxxxx > wrote:
> Ok i finally got domain1 working with the centos image. It was a stupid
> typo.
>
> Now i modified the cfg file so i can supply the ip, netmask, gateway and
> hostname to the image. Here is the modified cfg file:
>
> kernel = "/boot/vmlinuz- 2.6-xen"
> memory = 128
> name = "centos.4-2"
> nics = 1
> ip="192.168.1.230"
> netmask=" 255.255.255.0"
> gateway=" 192.168.1.1"
> hostname="xentest1"
> extra="selinux=0"
> #dhcp = "dhcp"
> disk = ['file:/root/xen/centos.4-2.img,sda1,w',
> 'file:/root/xen/centos.swap,sda2,w']
> root = "/dev/sda1 ro"

Hi Anand,

Just do not use the directives "ip", "netmask", "gateway" and "hostname"
at all. Try configuring network inside your domain. It runs. It is logically
correct. It is easy. Remember, the domain do not know how to configure
every network interface, if you do not tell him.

I have not proof on that, but I believe those directives are for the network
interface OUT of the domain, not IN the domain. So, the domain remains
without any configuration for an interface.

Last but not least, try understand Xen as a real network with real hosts,
configure your host as they were real ones.

--
Bye,
Fernando Maior
LPIC/1(31908)
LinuxCounter(391325)

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users