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-bugs

[Xen-bugs] [Bug 1042] New: xm list, xm console, xm destroy hanging

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1042] New: xm list, xm console, xm destroy hanging
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 14 Aug 2007 01:06:18 -0700
Delivery-date: Tue, 14 Aug 2007 01:06:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1042

           Summary: xm list, xm console, xm destroy  hanging
           Product: Xen
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: dchepishev@xxxxxxxxxxx


Hi,
after about 21 days of work, xen starte acting strange.
xm list
xm console domainname
xm destroy domainname
just do nothing. They just hang with no response.

The system is with 4G memory
xen 3.1 - PAE
OS- CentOS 4.5
glibc: glibc-2.3.4-2.36.i686  manually compiled with
BuildFlags="-mno-tls-direct-seg-refs -march=%{_target_cpu}"

Here is some info about xen:
[root@vhost01 ~]# xm info
host                   : vhost01
release                : 2.6.18-xen
version                : #1 SMP Tue May 22 16:10:41 EEST 2007
machine                : i686
nr_cpus                : 2
nr_nodes               : 1
sockets_per_node       : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 1862
hw_caps                :
bfebfbff:20000000:00000000:00000140:0000e3bd:00000000:00000001
total_memory           : 4094
free_memory            : 2513
xen_major              : 3
xen_minor              : 1
xen_extra              : .0
xen_caps               : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xf5800000
xen_changeset          : unavailable
cc_compiler            : gcc version 3.4.6 20060404 (Red Hat 3.4.6-8)
cc_compile_by          : root
cc_compile_domain      :
cc_compile_date        : Tue May 22 16:02:18 EEST 2007
xend_config_format     : 4
[root@vhost01 ~]# uptime
 10:56:00 up 21 days, 12:02,  3 users,  load average: 0.41, 0.51, 0.40

xentop is still working with the following output:

xentop - 10:58:24   Xen 3.1.0
8 domains: 1 running, 6 blocked, 0 paused, 0 crashed, 1 dying, 0 shutdown
Mem: 4192760k total, 1618572k used, 2574188k free    CPUs: 2 @ 1862MHz
      NAME  STATE   CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k) MAXMEM(%)
VCPUS NETS NETTX(k) NETRX(k) VBDS   VBD_OO   VBD_RD   VBD_WR SSID
    xxxx1 --b---      32082    0.0     262144    6.3    1048576      25.0     2
   1   582306  3292209    2     1224   645002  2266538    0
  Domain-0 -----r      44262    0.0     262144    6.3   no limit       n/a    
2    4  2982238   521976    0        0        0        0    0
   xxxx2 --b---       5737    0.0     262144    6.3     524288      12.5     2 
  1   399804   898883    2      363   751582  2069488    0
    xxxx3 --b---       2725    0.0     262144    6.3     524288      12.5     2
   1  1178669   278467    2      107  1448520   823117    0
   xxxx4 --b---      22047    0.0     131072    3.1     262144       6.3     2 
  1  3778972  3537269    2     1650   427442  1715428    0
   xxxx5 --b---        149    0.0     131072    3.1     262144       6.3     2 
  1      137    87192    2        0     1742     1232    0
   xxxx6 d-----       9169    0.0         16    0.0     524288      12.5     2 
  1   755552   128825    2       99   739782   697372    0
   xxxx7 --b---      13417    0.0     262144    6.3    1048576      25.0     2 
  1  2483238  2605217    2      561  1662281  1745793    0

The domain xxxx6 is in dying state and I cant do anything about it. No destroy
working no nothing.
I will try rebooting the dom0 machine after the work hours and will see what
will happen.

If you need more information, please let me know.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

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