|  |  | 
  
    |  |  | 
 
  |   |  | 
  
    |  |  | 
  
    |  |  | 
  
    |   xen-users
Re: [Xen-users] Re: Xen kernel problem 
| The box is currently connected to a basic linksys router at my house, 
until I take it to the data center. I also have 4 other machines running 
similar xen configuration, all of them are working fine and grep the IP 
from the linksys router fine, except this one. I'll try it with 
specifyin a mac address, let's see what will happen. 
Thanks!
Michael McCabe wrote:
 
One thing that you may have to do is set a different MAC address for
your network card.  I've seen this problem before depending on the the
setup of the DHCP server.
Mike
On Fri, 2005-08-05 at 19:11 -0700, Alexander Attarian wrote:
 
Sure, here is my /etc/sysconfig/network:
NETWORKING=yes
HOSTNAME=ossboxU
here is /etc/sysconfig/network-scripts/ifcfg-eth0:
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=ON
and here is /etc/xen/dom1:
# Kernel image file
kernel = "/boot/vmlinuz-2.6.12-xenU"
# Initial memory allocation (in megabytes) for the new domain.
memory = 1024
# A name for your domain. All domains must have different names.
name = "ossdom1"
cpu = 0   # leave to Xen to pick
disk = [ 'phy:sda5,sda1,w', 'phy:sda6,sda2,w' ]
# Set root device.
root = "/dev/sda1 ro"
# Sets runlevel 4.
extra = "4"
Hope this helps!
Thanks
Michael McCabe wrote:
 
Can you please post your networking configuration files and your Xen
config file?
On Fri, 2005-08-05 at 18:22 -0700, Alexander Attarian wrote:
 can login via the console to dom1 and 
to the system. The only problem is 
  
       
 
__________ NOD32 1.1170 (20050715) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
 
__________ NOD32 1.1170 (20050715) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
 
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
 | 
 |  | 
  
    |  |  |