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/
Home Products Support Community News


[Xen-devel] Guest OS boots up slowly

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Guest OS boots up slowly
From: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Date: Mon, 31 Aug 2009 15:50:10 +0900
Delivery-date: Sun, 30 Aug 2009 23:50:50 -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

I tested the latest xen-unstable (changeset: 20128) and the latest 
linux-2.6.18-xen (changeset: 931).  A guest OS is booted up slower 
than before.  And the following messages are shown by the guest OS.

Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
  ** WARNING: Currently emulating unsupported memory accesses  **
  **          in /lib/tls glibc libraries. The emulation is    **
  **          slow. To ensure full performance you should      **
  **          install a 'xen-friendly' (nosegneg) version of   **
  **          the library, or disable tls support by executing **
  **          the following as root:                           **
  **          mv /lib/tls /lib/tls.disabled                    **
  ** Offending process: modprobe (pid=761)                     **
Pausing... 5<3>BUG: soft lockup detected on CPU#0!
 [<c0151205>] softlockup_tick+0xa5/0xd0
 [<c010978a>] timer_interrupt+0x2fa/0x6c0
 [<c011d8c1>] __activate_task+0x21/0x40
 [<c012fed0>] lock_timer_base+0x20/0x50
 [<c0151563>] handle_IRQ_event+0x33/0xa0
 [<c0151678>] __do_IRQ+0xa8/0x120
 [<c01076e1>] do_IRQ+0x31/0x80
 [<c02af6b0>] neigh_periodic_timer+0x0/0x140
 [<c024ced5>] evtchn_do_upcall+0xe5/0x1f0
 [<c0115fb0>] do_fixup_4gb_segment+0x0/0x170
 [<c0105ba3>] hypervisor_callback+0x33/0x3b
 [<c0115fb0>] do_fixup_4gb_segment+0x0/0x170
 [<c01ed68b>] delay_tsc+0xb/0x20
 [<c01ed6d6>] __delay+0x6/0x10
 [<c01160f0>] do_fixup_4gb_segment+0x140/0x170
 [<c0169597>] do_munmap+0x197/0x200
 [<c01ee0a4>] copy_to_user+0x34/0x70
 [<c0105b6b>] error_code+0x2b/0x30

FYI, when I reverted changeset 20122 of xen-unstable, the guest OS 
is booted up as before.

Best regards,

Xen-devel mailing list

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