From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alex Williamson <alex.williamson@redhat.com>
Subject: Re: Large sized guest taking for ever to boot...
Date: Fri, 08 Jun 2012 10:46:06 -0600
Message-ID: <1339173966.26976.95.camel@ul30vt>
References: <loom.20120608T181832-528@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Chegu Vinod <chegu_vinod@hp.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:7736 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751931Ab2FHQqM (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 8 Jun 2012 12:46:12 -0400
In-Reply-To: <loom.20120608T181832-528@post.gmane.org>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Fri, 2012-06-08 at 16:29 +0000, Chegu Vinod wrote:
> Hello,
> 
> I picked up a recent version of the qemu (1.0.92 with some fixes) and tried it 
> on x86_64 server (with host and the guest running 3.4.1 kernel). 
> 
> While trying to boot a large guest (80 vcpus + 512GB) I observed that the guest 
> took for ever to boot up...  ~1 hr or even more. [This wasn't the case when I 
> was using RHEL 6.x related bits]

Was either case using device assignment?  Device assignment will map and
pin each page of guest memory before startup, which can be a noticeable
pause on smallish (<16GB) guests.  That should be linear scaling though
and if you're using qemu and not qemu-kvm, not related.  Thanks,

Alex