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] zombie opensolaris domU

To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Subject: Re: [Xen-users] zombie opensolaris domU
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Wed, 9 Apr 2008 14:26:09 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 09 Apr 2008 06:27:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47FC37ED.7070007@xxxxxxxxx>
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: <47FC37ED.7070007@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Wed, Apr 09, 2008 at 10:28:45AM +0700, Fajar A. Nugraha wrote:

> I'm using RHEL5.1, bundled xen (3.1). I have setup setup opensolaris 
> domU (b75a and b79b) guests, and it works fine for the most part, but 
> every time the domU restarted a zombie appear.
> # xm list
> Name                                      ID Mem(MiB) VCPUs State   Time(s)
> Domain-0                                   0     1967     2 r-----    116.0
> Zombie-sol_pv                              2     1024     1 ---s-d     46.6
> Zombie-sol_pv                              6     1024     1 ---s-d     32.8
> sol_pv                                     7     1024     1 r-----      1.7
> Any idea how to fix this? Will upgrading to 3.2 fix this issue?
> Relevant entry from domU config file :

It's a bug in 3.1, updating to a more recent version of Xen 3.1 will fix
it (but of course, this will completely trash RHEL's mutant version of


Xen-users mailing list

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