Hi there, my Server: Debian 4.0, XEN xen-hypervisor-3.0.3-1-i386-pae I have successfully installed and running 13 domU. I have enough free ressources for number 14. I set it up in exactly the same way like the others. Once started this dumU Nr 14, every other domU lost its network connection. If I shutdown Nr 14, everything is working finde again. Is there a maximum number of domUs per Host? I checked if the interface is installed correctly, there seems to be no problem. A new vif device is added when starting the new server. The problem occurs on three slightly different servers (other hardware, other xen-version) as well. Any help would be highly appreciated! Thanks! Hanno -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Sep 15, 2009 at 11:48:20AM +0200, hbh@gmx.de wrote:> Hi there, > > my Server: Debian 4.0, XEN xen-hypervisor-3.0.3-1-i386-pae > > I have successfully installed and running 13 domU. > > I have enough free ressources for number 14. I set it up in exactly the same way like the others. > > Once started this dumU Nr 14, every other domU lost its network connection. If I shutdown Nr 14, everything is working finde again. > > Is there a maximum number of domUs per Host? > > I checked if the interface is installed correctly, there seems to be no problem. A new vif device is added when starting the new server. > > The problem occurs on three slightly different servers (other hardware, other xen-version) as well. > > Any help would be highly appreciated! >What does "xm info" say about free memory before and after starting the 14th domU? Does your dom0 memory get ballooned (too much) down? Check the amount of dom0 memory aswell before and after 14th domU. Anything in dom0 logs? dmesg? /var/log/messages file? How about xen logs? xm dmesg? xm log? -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, thanks for the hints.> What does "xm info" say about free memory before and after starting the > 14th domU?It is the same line: Domain-0 0 478 8 r----- 357306.0> Does your dom0 memory get ballooned (too much) down? Check the amount of > dom0 memory aswell before and after 14th domU. > Anything in dom0 logs? dmesg? /var/log/messages file?A dmesg is interesting: ... ADDRCONF(NETDEV_CHANGE): vif55.0: link becomes ready xenbr0: port 14(vif55.0) entering learning state xenbr0: topology change detected, propagating xenbr0: port 14(vif55.0) entering forwarding state printk: 126 messages suppressed. xen_net: Memory squeeze in netback driver. printk: 4 messages suppressed. xen_net: Memory squeeze in netback driver. printk: 4 messages suppressed. ... xenbr0: port 14(vif55.0) entering disabled state xenbr0: port 14(vif55.0) entering disabled state device vif55.0 left promiscuous mode This is from start to end of 14th domU. So i guess there is a problem with the network configuration. In xend-config I have "(dom0-min-mem 0)" Shoud I set dom0 memory via boot-parameter? I found that solution on the net. Which value whould be best then? Thanks! Hanno -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Sep 15, 2009 at 12:09:10PM +0200, hbh@gmx.de wrote:> Hi, > > thanks for the hints. > > > What does "xm info" say about free memory before and after starting the > > 14th domU? > > It is the same line: > > Domain-0 0 478 8 r----- 357306.0 > > > Does your dom0 memory get ballooned (too much) down? Check the amount of > > dom0 memory aswell before and after 14th domU. > > Anything in dom0 logs? dmesg? /var/log/messages file? > > A dmesg is interesting: > > ... > ADDRCONF(NETDEV_CHANGE): vif55.0: link becomes ready > xenbr0: port 14(vif55.0) entering learning state > xenbr0: topology change detected, propagating > xenbr0: port 14(vif55.0) entering forwarding state > printk: 126 messages suppressed. > xen_net: Memory squeeze in netback driver. > printk: 4 messages suppressed. > xen_net: Memory squeeze in netback driver. > printk: 4 messages suppressed. > ... > xenbr0: port 14(vif55.0) entering disabled state > xenbr0: port 14(vif55.0) entering disabled state > device vif55.0 left promiscuous mode > > This is from start to end of 14th domU. So i guess there is a problem with the network configuration. > In xend-config I have "(dom0-min-mem 0)" > Shoud I set dom0 memory via boot-parameter? I found that solution on the net. Which value whould be best then? >I always set dom0_mem boot parameter for Xen hypervisor, so dom0 gets allocated dedicated amount of memory. And I make sure the other guests only use the free/available memory, so there''s no need to balloon down dom0 memory. Sometimes you might get problems if during the dom0 boot you have full amount of memory visible to dom0, and the dom0 kernel network etc parameters are calculated based on that memory amount - and then later dom0 memory gets ballooned way down from the original amount when you create the guests - but the dom0 kernel parameters are still for the original big amount of memory.. Dunno if that''s the problem here, but could be. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Pasi, That did the trick! I added "dom0_mem=256M" to the kernel, stopped all 13 domU, rebooted, 13domUs up again... Then I started the 14th - without any problems. And the annoying 3-4 second pause when starting a domU is gone also. Thank you very much for this fast help! Hanno -------- Original-Nachricht --------> Datum: Tue, 15 Sep 2009 13:17:18 +0300 > Von: "Pasi Kärkkäinen" <pasik@iki.fi> > An: hbh@gmx.de > CC: xen-users@lists.xensource.com > Betreff: Re: [Xen-users] Strange Network behaviour> On Tue, Sep 15, 2009 at 12:09:10PM +0200, hbh@gmx.de wrote: > > Hi, > > > > thanks for the hints. > > > > > What does "xm info" say about free memory before and after starting > the > > > 14th domU? > > > > It is the same line: > > > > Domain-0 0 478 8 r----- 357306.0 > > > > > Does your dom0 memory get ballooned (too much) down? Check the amount > of > > > dom0 memory aswell before and after 14th domU. > > > Anything in dom0 logs? dmesg? /var/log/messages file? > > > > A dmesg is interesting: > > > > ... > > ADDRCONF(NETDEV_CHANGE): vif55.0: link becomes ready > > xenbr0: port 14(vif55.0) entering learning state > > xenbr0: topology change detected, propagating > > xenbr0: port 14(vif55.0) entering forwarding state > > printk: 126 messages suppressed. > > xen_net: Memory squeeze in netback driver. > > printk: 4 messages suppressed. > > xen_net: Memory squeeze in netback driver. > > printk: 4 messages suppressed. > > ... > > xenbr0: port 14(vif55.0) entering disabled state > > xenbr0: port 14(vif55.0) entering disabled state > > device vif55.0 left promiscuous mode > > > > This is from start to end of 14th domU. So i guess there is a problem > with the network configuration. > > In xend-config I have "(dom0-min-mem 0)" > > Shoud I set dom0 memory via boot-parameter? I found that solution on the > net. Which value whould be best then? > > > > I always set dom0_mem boot parameter for Xen hypervisor, so dom0 gets > allocated dedicated amount of memory. And I make sure the other guests > only use the free/available memory, so there''s no need to balloon down > dom0 memory. > > Sometimes you might get problems if during the dom0 boot you have full > amount of memory visible to dom0, and the dom0 kernel network etc > parameters are calculated based on that memory amount - and then later > dom0 memory gets ballooned way down from the original amount when you > create the guests - but the dom0 kernel parameters are still for the > original > big amount of memory.. > > Dunno if that''s the problem here, but could be. > > -- Pasi > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users