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

[Xen-devel] FV-VM hangs after long time running.

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] FV-VM hangs after long time running.
From: 宋伟 <james.song@xxxxxxxxxxxxxx>
Date: Wed, 8 Sep 2010 15:35:16 +0800
Delivery-date: Wed, 08 Sep 2010 00:37:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: ActPKGBQSnWoMwiQRMSSOvWWO+xQ4w==

Hi,

 

      I always met a FV-VM(redhat-5.4) hangs after about 48 or more hours run on xen4.0.0 + Pvops dom0 kernels 2.6.32, besides, some workload also run on dom0. Unfortunately I can only connect the VM with vnc and no reponse with console. From “vcpu-list” found that there are two vcpu with that VM but one have no state.  After rebooting the Vm, I got the message in Guest OS like:

 

Jul 22 18:43:31 sun-test9 kernel: BUG: soft lockup - CPU#0 stuck for 10s! [events/0:11]

Jul 22 18:43:31 sun-test9 kernel: CPU 0:

Jul 22 18:43:31 sun-test9 kernel: Modules linked in: nls_utf8 autofs4 hidp rfcomm l2cap bluetooth lockd sunrpc ip_conntrack_ftp ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack nfnetlink iptable_filter ip_tables ip6t_REJECT xt_tcpudp ip6table_filter ip6_tables x_tables dm_mirror dm_multipath scsi_dh video hwmon backlight sbs i2c_ec button battery asus_acpi acpi_memhotplug ac ipv6 xfrm_nalgo crypto_api parport_pc lp parport floppy joydev ide_cd cdrom i2c_piix4 pcspkr serio_raw i2c_core xen_vnif xen_balloon dm_raid45 dm_message dm_region_hash dm_log dm_mod dm_mem_cache ata_piix libata sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd xen_vbd xen_platform_pci

Jul 22 18:43:31 sun-test9 kernel: Pid: 11, comm: events/0 Not tainted 2.6.18-164.el5 #1

Jul 22 18:43:31 sun-test9 kernel: RIP: 0010:[<ffffffff80075c12>]  [<ffffffff80075c12>] __smp_call_function+0x6a/0x8b

Jul 22 18:43:31 sun-test9 kernel: RSP: 0018:ffff810037f49d90  EFLAGS: 00000297

Jul 22 18:43:31 sun-test9 kernel: RAX: 0000000000000001 RBX: 0000000000000000 RCX: 0000000000000000

Jul 22 18:43:31 sun-test9 kernel: RDX: 00000000000000ff RSI: 00000000000000ff RDI: 00000000000000c0

Jul 22 18:43:31 sun-test9 kernel: RBP: 0000000000000000 R08: 0000000000000003 R09: 000000000000003d

Jul 22 18:43:31 sun-test9 kernel: R10: ffff810037f49cf0 R11: 0000000000000000 R12: 0000000000000000

Jul 22 18:43:31 sun-test9 kernel: R13: 0000000000000000 R14: 0000000000000006 R15: 0000000000000286

Jul 22 18:43:31 sun-test9 kernel: FS:  0000000000000000(0000) GS:ffffffff803c0000(0000) knlGS:0000000000000000

Jul 22 18:43:31 sun-test9 kernel: CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b

Jul 22 18:43:31 sun-test9 kernel: CR2: 00000000f7699430 CR3: 00000000275bf000 CR4: 00000000000006e0

Jul 22 18:43:31 sun-test9 kernel:

Jul 22 18:43:31 sun-test9 kernel: Call Trace:

Jul 22 18:43:31 sun-test9 kernel:  [<ffffffff80072404>] mcheck_check_cpu+0x0/0x2f

Jul 22 18:43:31 sun-test9 kernel:  [<ffffffff80075d40>] smp_call_function+0x32/0x47

Jul 22 18:43:31 sun-test9 kernel:  [<ffffffff80072404>] mcheck_check_cpu+0x0/0x2f

Jul 22 18:43:31 sun-test9 kernel:  [<ffffffff8009359a>] on_each_cpu+0x10/0x22

Jul 22 18:43:31 sun-test9 kernel:  [<ffffffff8007172f>] mcheck_timer+0x1c/0x6c

Jul 22 18:43:31 sun-test9 kernel:  [<ffffffff8004d80a>] run_workqueue+0x94/0xe4

Jul 22 18:43:31 sun-test9 kernel:  [<ffffffff8004a052>] worker_thread+0x0/0x122

Jul 22 18:43:31 sun-test9 kernel:  [<ffffffff8004a142>] worker_thread+0xf0/0x122

Jul 22 18:43:31 sun-test9 kernel:  [<ffffffff8008be71>] default_wake_function+0x0/0xe

Jul 22 18:43:31 sun-test9 kernel:  [<ffffffff8003298b>] kthread+0xfe/0x132

Jul 22 18:43:31 sun-test9 kernel:  [<ffffffff8005dfb1>] child_rip+0xa/0x11

Jul 22 18:43:31 sun-test9 kernel:  [<ffffffff8003288d>] kthread+0x0/0x132

Jul 22 18:43:31 sun-test9 kernel:  [<ffffffff8005dfa7>] child_rip+0x0/0x11

Jul 22 18:43:31 sun-test9 kernel:

 

Someone could give some hint what cause vm hang or how to get more information? Thanks in advance!

 

-James Song

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] FV-VM hangs after long time running., 宋伟 <=