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/
Home Products Support Community News


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

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Error: The privileged domain did not balloon! after reboot of Dom0, it just works
From: Dominik Klein <dk@xxxxxxxxxxxxxxxx>
Date: Tue, 13 Nov 2007 13:42:33 +0100
Delivery-date: Tue, 13 Nov 2007 04:43:19 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071113122938.29408460A7@xxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <20071113122938.29408460A7@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20071008)
Sebastian Reitenbach wrote:

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:
title XEN3.1.0
root (hd0,0)
kernel /boot/xen-3.1.0.gz dom0_mem=256M dom0_vcpus_pin
module /boot/vmlinuz-2.6.18-xen root=/dev/sda1
module /boot/initrd-2.6.18-xen


Xen-users mailing list

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