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] Xen/IA64 Healthiness Report -Cset#11609

To: "You, Yongkang" <yongkang.you@xxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11609
From: "Yoshinori Katase" <y_katase@xxxxxxxxxxxxxxxx>
Date: Thu, 28 Sep 2006 17:46:54 +0900
Delivery-date: Thu, 28 Sep 2006 01:47:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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: <094BCE01AFBE9646AF220B0B3F367AAB589042@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Yongkang,

I confirmed the phenomenon you reported.(11635:f34e37d0742d)
It is very easy to reproduce.
But not have to reboot machine to recover.
----------------------------------------------------------------
[root@tiger156 ~]# xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      988     3 r-----    45.3
[root@tiger156 xen]# (xm create rhel4.cs11609 &);xm create rhel4.cs11609-2 &
[1] 6045
[root@tiger156 xen]# Using config file "rhel4.cs11609-2".
Using config file "rhel4.cs11609".
Started domain rhel4.cs11609
Started domain rhel4.cs11609-2

[1]+  Done                    xm create rhel4.cs11609-2
[root@tiger156 xen]# xm list
Error: Device 0 not connected
[root@tiger156 xen]# xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      988     3 r-----    69.5
Zombie-rhel4.cs11609               2     1024     1 ----cd     6.1
Zombie-rhel4.cs11609               4     1024     1 ----cd     0.0
Zombie-rhel4.cs11609-2             1     1024     1 ----cd     6.1
Zombie-rhel4.cs11609-2             3     1024     1 ----cd     0.1
[root@tiger156 xen]# xend stop
[root@tiger156 xen]# xend start
[root@tiger156 xen]# xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      988     3 r-----    80.0
[root@tiger156 xen]# (xm create rhel4.cs11609 &);xm create rhel4.cs11609-2 &
[1] 7978
[root@tiger156 xen]# Using config file "rhel4.cs11609".
Using config file "rhel4.cs11609-2".
Started domain rhel4.cs11609
Started domain rhel4.cs11609-2

[1]+  Done                    xm create rhel4.cs11609-2
[root@tiger156 xen]# xm list
Error: Device 0 not connected
[root@tiger156 xen]# xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      988     3 r-----    98.9
Zombie-rhel4.cs11609               5     1024     1 ----cd     0.1
Zombie-rhel4.cs11609               7     1024     1 ----cd     0.1
Zombie-rhel4.cs11609-2             8     1024     1 ----cd     0.1
Zombie-rhel4.cs11609-2             6     1024     1 ----cd     0.4
----------------------------------------------------------------

Best Regards,
Katase

----- Original Message ----- From: "You, Yongkang" <yongkang.you@xxxxxxxxx>
To: "You, Yongkang" <yongkang.you@xxxxxxxxx>; 
<xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, September 27, 2006 7:05 PM
Subject: RE: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11609


The 2 XenU coexisting testing is easy to fail.

I try 3 times to create 2 XenU domains at the same time "(xm create config1 &) ; xm create config2 &" . The first 2 times are pass. But the 3rd time. XenU creating failed.
After that, "xm list" can not list domains and will report "Error: Device 768 not 
connected"

Use "xend stop and xend start" could recover "xm list".
But if try to create 2 XenU domains again, there will be 4 Zombie-Domains in "xm 
list".

It is same with the bug 
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=747

Best Regards,
Yongkang (Kangkang) 永康

-----Original Message-----
From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of You,
Yongkang
Sent: 2006年9月27日 15:05
To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11609

Xen/IA64 Healthiness Report

2 XenU coexisting case failed.
If try to create 2 XenU at the same time, Xend will be broken, e.g. "xm list" 
just
show "xm help" information. Have to reboot machine to recover. We will report
a
new bug for this.

Testing Environment:
----------------------------
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
PAL version: 8.15
Service OS: RHEL4u3 IA64 SMP with 2 VCPUs
VTI Guest OS: RHEL4u2 & RHEL4u3
XenU Guest OS: RHEL4u2
Xen IA64 Unstable tree: 11635:f34e37d0742d
Xen Schedule: credit
VTI Guest Firmware MD5: ea1815932b91e5a6481bb64468e50254

Summary Test Report:
-----------------------------
 Total cases: 16
 Passed:    15
 Failed:     1

Detailed test cases info:
-----------------------------
1. One_VTI_without_vif                pass
2. One_VTI                           pass
3. One_XenU                         pass
4. Two_VTI_Coexist                   pass
5. One_VTI_and_One_XenU           pass
6. Two_XenU_Coexist                 __FAIL__
7. One_VTI_4096M                   pass
8. VTI_Network                       pass
9. XenU_Network                     pass
10. One_SMP_XenU                  pass
11. One_SMP_VTI                    pass
12. UP_VTI_LTP                      pass
13. VTI_Kernel_Build                  pass
14. Four_VTI_Coexist                  pass
15. VTI_Windows                     pass
16. VTI_Win_Linux_XenU_Coexist      pass

Notes:
-----------------------------

The last stable changeset:
-----------------------------
11609:7b250cf49e50

Best Regards,
Yongkang (Kangkang) 永康




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