| 
Hi!
I have the same problem! Any issues?
My configuration file is :
name="vm01"
kernel="/boot/vmlinuz-2.6.16-xen"
root="/dev/hda1"
memory=17
disk=['file:/vserver/images/vm01.img,hda1,w','file:/vserver/images/ 
vm01-swap.img,hda2,w'] 
# network
vif=[ '' ]
dhcp="off"
ip="192.168.1.11"
netmask="255.255.255.0"
gateway="192.168.1.1"
hostname="vm01"
extra="3"
When domU run the ip, hostname, ... aren't configured automatically  
with the conf file. I haven't this problem with xen3.0.1. 
My workstation configuration :
512 RAM
Intel Mobile technologie
Debian Sarge 3.1
Le 14 juin 06 à 12:02, Pablo Javier Roca Mendez a écrit :
 
Hello everybody,
short update on my issue:
I removed the Xen 3.0.2 packages (from Opensuse 10.1) and installed  
from
xen-3.0.1-install-x86_32.tgz; now the configuration options  
regarding IP 
address and hostname are not ignored.
Does anyone know why they are being ignored in the latest stable  
version? 
It also happens when installing xen-3.0.2-install-x86_32.tgz on  
Kubuntu 5.10, 
so it is not a problem with the packages in opensuse 10.1
Regards,
Pablo
On Tue, Jun 13, 2006 at 10:02:40AM +0200, Pablo Javier Roca Mendez  
wrote: 
Hello!
I have a problem with Xen 3.0.2 (xen-3.0.2_09656-4) on Opensuse  
10.1 regarding
setting the IP address for the domU in the configuration file: the  
settings 
are just ignored.
This problem doesn't happen when using Xen 2.0.7 (same image file,  
same 
configuration options).
This are my configuration options for domU:
kernel = "/work/xen/vmlinuz-2.6.16-xen"
#cpu = -1   # leave to Xen to pick
memory = 128
disk = ['file:///work/xen/knscsl021-vm3.sda,sda1,w']
name = "knscsl021-vm3-domain"
dhcp="off"
#vif=[ '' ]
vif = [ 'mac=aa:16:3E:aa:aa:cc, ip=172.28.77.99' ]
hostname = "knscsl021-vm3"
ip = "172.28.77.99"
network = "172.28.77.0"
netmask = "255.255.255.0"
gateway = "172.28.77.1"
root = "/dev/sda1 ro"
extra = "3"
restart = 'onreboot'
It doesn't matter what configuration options I choose for hostname  
or ip, they 
are ignored (i.e. the configuration in domU in ifcfg-eth0 is used)
The only difference I see between Xen3 and Xen2 is in the kernel  
commmand line: 
- For Xen 3:
Kernel command line:   
ip=172.28.77.99::172.28.77.1:255.255.255.0:knscsl021-vm3:eth0:off  
root=/dev/sda1 ro 3 
- For Xen 2:
Kernel command line:   
ip=172.28.77.99:1.2.3.4:172.28.77.1:255.255.255.0:knscsl021- 
vm3:eth0:off root=/dev/sda1 ro 3 
I know that setting the correct IP address in ifcfg-eth0 in domU  
works, but
that isn't a solution for me. The ideal solution would be that  
domU uses the IP
provided in the domU configuration file, but I can't understand  
why it works 
for Xen 2.7.0 but not for Xen 3.0.2. Does anybody have any ideas?
Thanks in advance.
Regards,
Pablo
 
--
Pablo Javier Roca Mendez
Intel GmbH/Bruehl, Hermuelheimer Str. 8a, 50321 Bruehl, Germany
Tel.: +49-2232-209024
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
 
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
 |