|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-devel
Re: [Xen-devel] vmx status report against cset 15072 - one	blocker issue
 
Hang in domain_kill() because the VMX domain is not getting descheduled for
some reason. The backtraces would be much easier to read if you use a debug
build of Xen. Also we'll have a go at reproducing this issue.
 -- Keir
On 16/5/07 09:16, "Zhao, Yunfeng" <yunfeng.zhao@xxxxxxxxx> wrote:
> Attached the serial output
> 
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Zhao, Yunfeng
> Sent: 2007年5月16日 12:45
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] vmx status report against cset 15072 - one blocker issue
> 
> Today's testing is blocked by the issue below:
> xen0 hang when destroy VMX guest
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=981
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 
 |   
 
 | 
    | 
  
  
    |   | 
    |