From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:44058) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RAoso-0007w7-1z for qemu-devel@nongnu.org; Mon, 03 Oct 2011 16:13:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RAosn-0005l1-1O for qemu-devel@nongnu.org; Mon, 03 Oct 2011 16:13:01 -0400 Received: from ihemail1.lucent.com ([135.245.0.33]:49995) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RAosm-0005kp-R1 for qemu-devel@nongnu.org; Mon, 03 Oct 2011 16:13:01 -0400 Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p93KCw89008334 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 3 Oct 2011 15:12:58 -0500 (CDT) Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p93KCu8O003142 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 3 Oct 2011 15:12:57 -0500 Received: from [135.185.92.148] (cabiness01-c1.ih.lucent.com [135.185.92.148]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p93KCuAK009535 for ; Mon, 3 Oct 2011 15:12:56 -0500 (CDT) Message-ID: <4E8A1741.9020208@alcatel-lucent.com> Date: Mon, 03 Oct 2011 15:12:49 -0500 From: Kenton Cabiness MIME-Version: 1.0 References: <4E89FD03.3030404@alcatel-lucent.com> In-Reply-To: <4E89FD03.3030404@alcatel-lucent.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Slow linux (RH5.6) guest reboot? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org One thing I forgot to mention is that this same guest image has no problem when installed bare metal. Kenton On 10/3/2011 1:20 PM, Kenton Cabiness wrote: > In general, we have seen that during a reboot of a > running guest (by issuing a 'reboot' command in the > guest), the guest goes down normally, but when coming > back up, during the udev phase, it takes anywhere from > a few seconds to a few hours to complete that part of the > boot. Then the guest seems to behave itself after that. > If the guest is powered off (virsh destroy guest), then > restarted (virsh create guest), then udev returns to a > speedy few seconds. It seems that the longer the guest > is up, the longer it takes udev (the +2 hour udev window > was on a guest up for 6 days) during a guest reboot. > It's always fast after a destroy/create. > > Does anyone have any idea what could be causing the slowness > in boot and the variability of the time spent in udev? Any > suggestions on where we should look? > > Thanks, > Kenton > > Specifics: > =========== > Host OS: > - RHEL 6.1 x64: (2.6.32-131.6.1.el6.x86_64) > - qemu-kvm: qemu-kvm-0.12.1.2-2.160.el6_1.2.x86_64.rpm > - libvirt: libvirt-0.8.7-18.el6.x86_64.rpm > > Guest OS: > - RHEL 5.6: (2.6.18-238.19.1.el5) > > VM details: > - 1 VM/guest on the host > - VM size is 32GB ram and 10 cores (host has > 36GB and 12 cores total) > - virtual disk drive is a local file on a RAID 1 disk > - cpu pinning set to force each virtual core to > a unique core (hyperthreading is turned on) > - virtio for storage and network devices > - have 16 ethernet devices tied to 16 bridges > mapped to 2 NICS on the host > - Use of iPXE and SGA bios for VM. > >