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-ia64-devel

Re: [Xen-ia64-devel] Create 2nd XenU fail after destroy 1st one

To: "You, Yongkang" <yongkang.you@xxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] Create 2nd XenU fail after destroy 1st one
From: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Date: Thu, 16 Mar 2006 11:02:22 +0100
Delivery-date: Thu, 16 Mar 2006 09:59:23 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <16A54BF5D6E14E4D916CE26C9AD30575044A200C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <16A54BF5D6E14E4D916CE26C9AD30575044A200C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
Le Jeudi 16 Mars 2006 10:48, You, Yongkang a écrit :
> >-----Original Message-----
>
> From: Tristan Gingold [mailto:Tristan.Gingold@xxxxxxxx]
>
> >Sent: 2006年3月16日 17:33
> >To: You, Yongkang; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >Subject: Re: [Xen-ia64-devel] Create 2nd XenU fail after destroy 1st one
> >
> >Le Jeudi 16 Mars 2006 10:19, You, Yongkang a écrit :
> >> Hi all,
> >>
> >> I am very glad to see xm destroy xenU will release memory.
> >> But when I try this feature, I found I couldn't create 2nd xenU
> >> successfully.
> >>
> >> I do the following steps:
> >> 1. boot Xen0
> >> 2. create XenU
> >> 3. After xenU boot up, use poweroff in xenU to kill xenU.
> >> 4. create 2nd XenU
> >> 5. when 2nd XenU boot up to "start udev", xenU stop to boot and serial
> >> port kept reporting "bad hyperprivop". (please see the attachment)
> >>
> >> If I destroy the 2nd xenU, the whole system seems hang. I catch this
> >> issue in Cset 9268.
> >
> >Hi,
> >
> >this is a very good catch.
> >I hope you can easily reproduce this bug, but I can't.
>
> Meet this issue every time. Could you give more information about your
> steps about creating and destroying? :)
I don't use RHEL4 usually.  I will install it.

Thank you for the details.

Tristan.


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