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] Error: The privileged domain did not balloon! after reboot o

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Error: The privileged domain did not balloon! after reboot of Dom0, it just works
From: "Sebastian Reitenbach" <sebastia@xxxxxxxxxxxxxxxxxxxx>
Date: Tue, 13 Nov 2007 13:29:37 +0100
Delivery-date: Tue, 13 Nov 2007 04:30:29 -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,

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?

kind regards
Sebastian



xm info
host                   : ppsdb101
release                : 2.6.16.46-0.12-xen
version                : #3 SMP Wed Oct 24 22:07:07 CEST 2007
machine                : x86_64
nr_cpus                : 4
nr_nodes               : 1
sockets_per_node       : 2
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 2205
hw_caps                : 
178bfbff:e3d3fbff:00000000:00000010:00000001:00000000:00000002
total_memory           : 3927
free_memory            : 34
max_free_memory        : 34
max_para_memory        : 30
max_hvm_memory         : 21
xen_major              : 3
xen_minor              : 0
xen_extra              : .4_13138-0.40
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : 13138
cc_compiler            : gcc version 4.1.2 20070115 (prerelease) (SUSE 
Linux)
cc_compile_by          : abuild
cc_compile_domain      : suse.de
cc_compile_date        : Fri May 18 13:26:05 UTC 2007
xend_config_format     : 3


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

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