Xen users - Nov 2007 - 3.0.3-fc6 bridging madness / Memory squeeze

Good day,

We''re using the FC6-branch of 3.0.3 on some of our machines. On nodes  
with broadcom-based network interfaces this works just fine, but on  
those with intel e1000-based interface cards, about once a week I''m  
seeing a lot of this:

Nov 30 19:02:02 yankee kernel: printk: 4 messages suppressed.
Nov 30 19:02:02 yankee kernel: xen_net: Memory squeeze in netback  
driver.
Nov 30 19:02:07 yankee kernel: printk: 4 messages suppressed.
Nov 30 19:02:07 yankee kernel: xen_net: Memory squeeze in netback  
driver.
Nov 30 19:02:12 yankee kernel: printk: 4 messages suppressed.

All vifs become unreachable, until I stop or restart one guest, then  
everything comes back to normal. Is this a known problem?

Cheers,
Pim


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

This has been known to happen when dom0 is initially allocated all free memory 
and then shrunk by a substantial amount using xm mem-set in order to make 
space for domUs.

You may well find that you can fix it by moving to a static allocation of 
memory for dom0.

Alter /etc/xen/xend-config.sxp to set dom0-min-mem to 0 (this disables 
automatic resizing of dom0 by Xend).  Edit /boot/grub/menu.lst and add 
dom0_mem=256M (or whatever size you want) to Xen''s commandline.

Reboot and enjoy.  I''ve known this fix the problem for others on
similar
versions of Xen, so I''m quite hopeful that this will solve your
problem.
Please complain at us if it doesn''t!

Cheers,
Mark

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Dec 2, 2007, at 6:51 , Mark Williamson wrote:
> This has been known to happen when dom0 is initially allocated all  
> free memory
> and then shrunk by a substantial amount using xm mem-set in order to  
> make
> space for domUs.
>
> You may well find that you can fix it by moving to a static  
> allocation of
> memory for dom0.
>
> Alter /etc/xen/xend-config.sxp to set dom0-min-mem to 0 (this disables
> automatic resizing of dom0 by Xend).  Edit /boot/grub/menu.lst and add
> dom0_mem=256M (or whatever size you want) to Xen''s commandline.
>
> Reboot and enjoy.  I''ve known this fix the problem for others on  
> similar
> versions of Xen, so I''m quite hopeful that this will solve your  
> problem.
> Please complain at us if it doesn''t!
Makes sense, let me try that out.

Cheers,
Pim


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users