It may be that the domains listed in /etc/xen/auto loaded in a certain order? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Vladimir Elizarov wrote on Tue, 06 Jan 2009 13:15:19 +0300:> It may be that the domains listed in /etc/xen/auto loaded in a certain > order?alphabetical - what else? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Kai Schaetzl wrote:> Vladimir Elizarov wrote on Tue, 06 Jan 2009 13:15:19 +0300: > > >> It may be that the domains listed in /etc/xen/auto loaded in a certain >> order? >> > > alphabetical - what else? > >Thanks, I have not thought about it. My problem is domain with dhcp loaded later than other domains. Although name config domain with dhcp in "dhcp.example.local". The other names configs come after "d". _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On January 6, 2009 10:37 am Vladimir Elizarov wrote:> Kai Schaetzl wrote: > > Vladimir Elizarov wrote on Tue, 06 Jan 2009 13:15:19 +0300: > >> It may be that the domains listed in /etc/xen/auto loaded in a certain > >> order? > > > > alphabetical - what else? > > Thanks, I have not thought about it. My problem is domain with dhcp > loaded later than other domains. Although name config domain with dhcp > in "dhcp.example.local". The other names configs come after "d".No, it''s alphabetical based on the filenames in /etc/xen/auto. It doesn''t matter what the hostname of the VMs is. You can even prefix the filenames in /etc/xen/auto with numbers to control the order. -- Freddie fjwcash@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On January 6, 2009 10:42 am Freddie Cash wrote:> On January 6, 2009 10:37 am Vladimir Elizarov wrote: > > Kai Schaetzl wrote: > > > Vladimir Elizarov wrote on Tue, 06 Jan 2009 13:15:19 +0300: > > >> It may be that the domains listed in /etc/xen/auto loaded in a > > >> certain order? > > > > > > alphabetical - what else? > > > > Thanks, I have not thought about it. My problem is domain with dhcp > > loaded later than other domains. Although name config domain with dhcp > > in "dhcp.example.local". The other names configs come after "d". > > No, it''s alphabetical based on the filenames in /etc/xen/auto. It > doesn''t matter what the hostname of the VMs is. You can even prefix the > filenames in /etc/xen/auto with numbers to control the order.If you do an "ls -1 /etc/xen/auto" (that''s the number one, not the letter el), this will show the order that the VMs are loaded, from top-to-bottom (first-to-last). -- Freddie fjwcash@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Freddie Cash wrote:> On January 6, 2009 10:42 am Freddie Cash wrote: > >> On January 6, 2009 10:37 am Vladimir Elizarov wrote: >> >>> Kai Schaetzl wrote: >>> >>>> Vladimir Elizarov wrote on Tue, 06 Jan 2009 13:15:19 +0300: >>>> >>>>> It may be that the domains listed in /etc/xen/auto loaded in a >>>>> certain order? >>>>> >>>> alphabetical - what else? >>>> >>> Thanks, I have not thought about it. My problem is domain with dhcp >>> loaded later than other domains. Although name config domain with dhcp >>> in "dhcp.example.local". The other names configs come after "d". >>> >> No, it''s alphabetical based on the filenames in /etc/xen/auto. It >> doesn''t matter what the hostname of the VMs is. You can even prefix the >> filenames in /etc/xen/auto with numbers to control the order. >> > > If you do an "ls -1 /etc/xen/auto" (that''s the number one, not the letter > el), this will show the order that the VMs are loaded, from top-to-bottom > (first-to-last). > >Sorry. I mean just the filenames in /etc/xen/auto. lrwxrwxrwx 1 root root 26 2009-01-05 22:28 dhcp0.example.local -> /etc/xen/dhcp0.example.local lrwxrwxrwx 1 root root 24 2009-01-05 22:28 gw0.example.local -> /etc/xen/gw0.example.local _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Freddie Cash wrote:> On January 6, 2009 10:42 am Freddie Cash wrote: > >> On January 6, 2009 10:37 am Vladimir Elizarov wrote: >> >>> Kai Schaetzl wrote: >>> >>>> Vladimir Elizarov wrote on Tue, 06 Jan 2009 13:15:19 +0300: >>>> >>>>> It may be that the domains listed in /etc/xen/auto loaded in a >>>>> certain order? >>>>> >>>> alphabetical - what else? >>>> >>> Thanks, I have not thought about it. My problem is domain with dhcp >>> loaded later than other domains. Although name config domain with dhcp >>> in "dhcp.example.local". The other names configs come after "d". >>> >> No, it''s alphabetical based on the filenames in /etc/xen/auto. It >> doesn''t matter what the hostname of the VMs is. You can even prefix the >> filenames in /etc/xen/auto with numbers to control the order. >> > > If you do an "ls -1 /etc/xen/auto" (that''s the number one, not the letter > el), this will show the order that the VMs are loaded, from top-to-bottom > (first-to-last). > >The logs in domain that has not given ip from dhcp and time domain is not correct. [32456.405762] __ratelimit: 190 messages suppressed [32456.405762] clocksource/0: Time went backwards: ret=4a51f13d56 delta=-32873747927363 shadow=4a46189697 offset=bd8eddd After the restart domain, the address is given, time domain is right. configuration: Linux dom0-00 2.6.26-1-xen-amd64 #1 SMP Mon Dec 15 20:07:26 UTC 2008 x86_64 GNU/Linux auto xenbr0 iface xenbr0 inet manual bridge_ports wan0 bridge_stp off bridge_fd 0 post-up ethtool -K xenbr0 tx off auto xenbr1 iface xenbr1 inet static address 192.168.10.4 netmask 255.255.255.0 gateway 192.168.10.10 bridge_ports lan0 bridge_stp off bridge_fd 0 post-up ethtool -K xenbr1 tx off (logfile /var/log/xen/xend.log) (loglevel DEBUG) (network-script network-example) (vif-script vif-bridge) (dom0-min-mem 196) (dom0-cpus 0) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Vladimir Elizarov wrote:>Thanks, I have not thought about it. My problem is domain with dhcp >loaded later than other domains. Although name config domain with >dhcp in "dhcp.example.local". The other names configs come after >"d".From the later message you posted, yes, your DHCP server will be started before the other. BUT ... AFAIK, it will not be given time to boot up and start all it''s services before starting the next VM - so it''s quite likely that a second VM will be trying to access services (like DHCP) before the first VM has started that service. I''m not aware of any mechanism to make Xen wait until one VM has reached a certain point before it starts the next. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Simon Hobson wrote:> Vladimir Elizarov wrote: > >> Thanks, I have not thought about it. My problem is domain with dhcp >> loaded later than other domains. Although name config domain with >> dhcp in "dhcp.example.local". The other names configs come after "d". > > From the later message you posted, yes, your DHCP server will be > started before the other. BUT ... > > AFAIK, it will not be given time to boot up and start all it''s > services before starting the next VM - so it''s quite likely that a > second VM will be trying to access services (like DHCP) before the > first VM has started that service. > > I''m not aware of any mechanism to make Xen wait until one VM has > reached a certain point before it starts the next. >thanks. It seems the problem is that loading dhcp0 slowed because of problems with time: [32456.405762] __ratelimit: 190 messages suppressed [32456.405762] clocksource/0: Time went backwards: ret=4a51f13d56 delta=-32873747927363 shadow=4a46189697 offset=bd8eddd I install ntp to dom0 and domu, but it seems does not work. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users