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

Re: [Xen-users] Error: The privileged domain did not balloon! afterreboo

To: xen-users@xxxxxxxxxxxxxxxxxxx, dk@xxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Error: The privileged domain did not balloon! afterreboot of Dom0, it just works
From: "Sebastian Reitenbach" <sebastia@xxxxxxxxxxxxxxxxxxxx>
Date: Tue, 13 Nov 2007 16:23:31 +0100
Delivery-date: Tue, 13 Nov 2007 07:24:20 -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>
Organization: L00 bugdead prods.
Reply-to: Sebastian Reitenbach <sebastia@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

Dominik Klein <dk@xxxxxxxxxxxxxxxx> wrote: 
> Sebastian Reitenbach wrote:
> > Hi,
> > 
> > I try to setup a linux ha based cluster, managing virtual Xen domU 
> > resources. When the cluster is up for e.g. a day or two, and then I want 
to 
> > move the Xen domU's from one host to another, I get the following errors 
in 
> > the logfile:
> > 
> > lrmd[9971]: 2007/11/12_11:20:53 info: RA output: (NFS_SW:start:stderr) 
> > Error: The privileged domain did not balloon!
> > 
> > This also happens when I then try to start the domU instance via 
> > xm create
> > When I then reboot the dom0, then xm create works fine again without 
> > problems. So this behaviour is useless, when it comes to a fail-over in 
the 
> > cluster after a week or so. When both cluster nodes started up, the 
> > migration of the resources from one host to another work well. 
> > 
> > Is there a way to prevent this failure, sth. I can do?
> 
> Try limiting dom0s memory so it does not have to balloon. This is done 
> in your boot manager:
> /boot/grub/menu.lst
> ...
> title XEN3.1.0
> root (hd0,0)
> kernel /boot/xen-3.1.0.gz dom0_mem=256M dom0_vcpus_pin
>                            ^^^^^^^^^^^^^
Ah, that sounds a bit like working on fixing the symptoms, instead of 
working on the real cause of the problem. Nevertheless, I'll add that 
parameter and will see whether it helps.
After adding the parameter, does that mean that the dom0 will stop 
ballooning at all? 

kind regards
Sebastian

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


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

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