[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11635
Hi Yongkang, This issue was found in Cset#10875. But the rate of reproducing is low. --------------------------------------------------------------- [root@tiger156 xen]# xm info (snip) xen_changeset : Mon Jul 31 15:14:47 2006 -0600 10875:00dd5eb7adc1 (snip) [root@tiger156 xen]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1004 3 r----- 5598.9 [root@tiger156 xen]# (xm create rhel4.test1 &);xm create rhel4.test2 & [1] 7801 [root@tiger156 xen]# Using config file "rhel4.test1". Using config file "rhel4.test2". Started domain rhel4.DomU-1 Started domain rhel4.DomU-2 [1]+ Done xm create rhel4.test2 [root@tiger156 xen]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1004 3 r----- 5706.0 Zombie-rhel4.DomU-1 5 1024 1 ----cd 5.7 Zombie-rhel4.DomU-2 6 1024 1 ----cd 5.6 rhel4.DomU-1 8 1024 1 r----- 0.0 [root@tiger156 xen]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1004 3 r----- 5731.6 Zombie-rhel4.DomU-1 5 1024 1 ----cd 5.7 Zombie-rhel4.DomU-1 8 1024 1 ----cd 0.1 Zombie-rhel4.DomU-2 6 1024 1 ----cd 5.6 [root@tiger156 xen]# xend restart [root@tiger156 xen]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1004 3 r----- 5812.2 [root@tiger156 xen]# xm create rhel4.test2 Using config file "rhel4.test2". Started domain rhel4.DomU-2 [root@tiger156 xen]# xm list Error: Device 0 not connected [root@tiger156 xen]# xm list Error: Device 769 not connected [root@tiger156 xen]# xend restart [root@tiger156 xen]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1004 3 r----- 5973.6 [root@tiger156 xen]# xm create rhel4.test1 Using config file "rhel4.test1". Started domain rhel4.DomU-1 [root@tiger156 xen]# xm list Error: Device 0 not connected [root@tiger156 xen]# xm list Error: Device 769 not connected [root@tiger156 xen]# xend restart [root@tiger156 xen]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1004 3 r----- 6090.2 --------------------------------------------------------------- Best Regards, Katase----- Original Message ----- From: "You, Yongkang" <yongkang.you@xxxxxxxxx> To: "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>; <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx> Sent: Thursday, September 28, 2006 3:43 PM Subject: RE: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11635 Hi Tristan, We found it for a long time. This issue also can be easily reproduced in latest changeset 11635. I guess it might be the common issue with IA32 side. But IA32 xenU didn't meet the problem with the same operations. Sorry for the wrong subject 11609, I send out yesterday. It should be 11635. Best Regards, Yongkang (Kangkang) 永康 -----Original Message----- From: Tristan Gingold [mailto:Tristan.Gingold@xxxxxxxx] Sent: 2006年9月28日 14:41 To: You, Yongkang; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx Subject: Re: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11609 Le Mercredi 27 Septembre 2006 12:05, You, Yongkang a écrit :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=747Hi, Is it a recent bug ? According to the bugzilla date it seems so (Aug 29). Could you try to find the changeset from which this bug appears ? Tristan. _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-ia64-devel _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-ia64-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |