From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chegu Vinod Subject: Large sized guest taking for ever to boot... Date: Fri, 8 Jun 2012 16:29:05 +0000 (UTC) Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from plane.gmane.org ([80.91.229.3]:50474 "EHLO plane.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756885Ab2FHQ3W (ORCPT ); Fri, 8 Jun 2012 12:29:22 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Sd23q-00022L-N8 for kvm@vger.kernel.org; Fri, 08 Jun 2012 18:29:19 +0200 Received: from zccy01cs103.houston.hp.com ([15.211.201.83]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 08 Jun 2012 18:29:18 +0200 Received: from chegu_vinod by zccy01cs103.houston.hp.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 08 Jun 2012 18:29:18 +0200 Sender: kvm-owner@vger.kernel.org List-ID: 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] Lots of the following type of errors show up on the console... ... udevd [886] : worker: [7321] unexpectedly returned with status 0x0100 udevd [886] : worker: [7321] failed while handling '/devices/system/memory/memory1351' udevd [886] : worker: [7371] unexpectedly returned with status 0x0100 udevd [886] : worker: [7371] failed while handling '/devices/system/memory/memory1352' .... Wondering if this is due to some very basic configuration issue on my side? or if I am using an in-comptible version of the qemu with host and guest kernel.. Vinod