WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] memory issues with FC5.2200 kernels

To: fedora-xen@xxxxxxxxxx
Subject: [Xen-users] memory issues with FC5.2200 kernels
From: Adrian Chadd <adrian@xxxxxxxxxxxxxxx>
Date: Tue, 7 Nov 2006 21:37:03 +0800
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 07 Nov 2006 05:33:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
hiya,

I've just upgraded a production Xen to FC5.2200 + the Xen userspace
stuff and its exhibiting some nasty problems. A couple of hours uptime
is followed by all domU networking stopping.

Here's dmesg in dom0:

xen_net: Memory squeeze in netback driver.
printk: 4 messages suppressed.
xen_net: Memory squeeze in netback driver.
printk: 4 messages suppressed.

And xm dmesg:

(XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 
memflags=0 (0 of 63)
(XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 
memflags=0 (0 of 63)
(XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 
memflags=0 (0 of 63)
(XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 
memflags=0 (0 of 63)
(XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 
memflags=0 (0 of 63)

Googling has shown inconclusive results - a couple of possible fixes but no 
explanation
why (and no consistent fix.)

Any ideas?

Thanks,


Adrian


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

<Prev in Thread] Current Thread [Next in Thread>