From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: Large sized guest taking for ever to boot... Date: Sun, 10 Jun 2012 12:30:57 +0300 Message-ID: <20120610093057.GL580@redhat.com> References: <1339173966.26976.95.camel@ul30vt> <4FD23221.5090208@hp.com> <1339177340.26976.111.camel@ul30vt> <4FD23CF9.5000203@hp.com> <4FD23FA0.6060202@siemens.com> <4FD24285.1060702@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jan Kiszka , Alex Williamson , qemu-devel , kvm@vger.kernel.org To: Chegu Vinod Return-path: Content-Disposition: inline In-Reply-To: <4FD24285.1060702@hp.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org On Fri, Jun 08, 2012 at 11:20:53AM -0700, Chegu Vinod wrote: > On 6/8/2012 11:08 AM, Jan Kiszka wrote: > BTW, another data point ...if I try to boot a the RHEL6.3 kernel in > the guest (with the latest qemu.git and the 3.4.1 on the host) it > boots just fine.... > > So something to do with the 3.4.1 kernel in the guest and the > existing udev... Need to dig > deeper. > How many CPUs do you have on the host? RHEL6.3 uses unfair spinlock when it runs as a guest. -- Gleb.