[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] DHCP server on Dom-0: guests fail to connect


  • To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Siddharth Wagh <siddharth.wagh@xxxxxxxxx>
  • Date: Wed, 3 Jun 2009 12:03:25 -0400
  • Delivery-date: Thu, 04 Jun 2009 02:11:38 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=hdF3dXqYKDubrPRfCUD7Q2KOv3qRTeyrHZxT26AQ7/O0WvJlaapU8eKRcOwR6m+hqS m0FUKn4ezoNHyJqAW93UHyOWV88PTzMEKiWy9G3UZ5KIGoOh0AyfyD9yljlMOZm6fL/w WLG8BehRpD3DdfEzb72J83DSPTQDpifd4FeGI=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello all,

I am working on a Centos 5.2 installation using Xen 3.0, and trying to set up a DHCP server on Domain-0 so as to assign a range of IP addresses to new guests. I installed dhcp package on Dom-0 and here are contents of dhcpd.conf file
(Dom-0 has eth0 - 128.6.237.10 and eth1 - 192.168.2.21 over crossover cable):

===================================================
ddns-update-style interim;
ignore client-updates;
authoritative;

subnet 128.6.237.0 netmask 255.255.255.0 {
host eth0     {
        hardware ethernet  00:21:9B:FC:D9:E9;
        fixed-address      128.6.237.10;
}
}
subnet 192.168.2.0 netmask 255.255.255.0 {
host eth1   {
        hardware ethernet  00:21:9B:FC:D9:EA;
        fixed-address      192.168.2.21;
}
}

# range of addresses to be assigned to new guests

subnet 192.168.1.0 netmask 255.255.255.0 {
# --- default gateway
        option routers                  192.168.1.1;
        option subnet-mask              255.255.255.0;
        option domain-name              "dw.vnet";
        option domain-name-servers      128.6.236.5, 128.6.224.114;

        option time-offset              -18000; # Eastern Standard Time
        range 192.168.1.128 192.168.1.254;
}
        default-lease-time 21600;
        max-lease-time 43200;
                              
===============================================

/etc/init.d/dhcpd start
Starting DHCP  [OK]

Then I am trying to create a guest with config file:
================================================
name = "sw_cp_fed8"
maxmem = 512
memory = 512
vcpus = 4
bootloader = "/usr/bin/pygrub"
>>>#vfb = [ "type=vnc,vncunused=1,keymap=en-us" ]
disk = [ "tap:aio:/var/lib/xen/images/sw_cp_fed8.img,xvda,w" ]
vif = ['']
dhcp="dhcp"
================================================

But the guest fails to start
Error:
TCP/IP error: VNC connection to hypervisor host got refused

/var/log/messages says:
=================================================
Jun  3 11:42:13 darkwing kernel: tap tap-62-51712: 2 getting info
Jun  3 11:42:14 darkwing kernel: device vif62.0 entered promiscuous mode
Jun  3 11:42:14 darkwing kernel: ADDRCONF(NETDEV_UP): vif62.0: link is not ready
Jun  3 11:42:14 darkwing kernel: blktap: ring-ref 8, event-channel 17, protocol 1 (x86_64-abi)
Jun  3 11:42:25 darkwing kernel: virbr0: port 1(vif62.0) entering disabled state
Jun  3 11:42:25 darkwing kernel: device vif62.0 left promiscuous mode
Jun  3 11:42:25 darkwing kernel: virbr0: port 1(vif62.0) entering disabled state
================================================

I need to run about 10 Virtual machines allotted dynamic IPs from DHCP server on Dom-0. Then I am seeking to stress test them on the machine, to study performance isolation among guests.
Can anyone help and guide me? Am I on the right path?



Thanks & Regards,
Siddharth Wagh
MS, Electrical & Computer Engineering
Rutgers University, NJ
Web: http://www.eden.rutgers.edu/~swagh/
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.