From: Chegu Vinod <chegu_vinod@hp.com>
To: kvm@vger.kernel.org
Subject: Large sized guest taking for ever to boot...
Date: Fri, 8 Jun 2012 16:29:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20120608T181832-528@post.gmane.org> (raw)
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
next reply other threads:[~2012-06-08 16:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 16:29 Chegu Vinod [this message]
2012-06-08 16:46 ` Large sized guest taking for ever to boot Alex Williamson
2012-06-08 17:10 ` Chegu Vinod
2012-06-08 17:42 ` Alex Williamson
2012-06-08 17:57 ` Chegu Vinod
2012-06-08 18:08 ` Jan Kiszka
2012-06-08 18:20 ` Chegu Vinod
2012-06-08 18:37 ` Jan Kiszka
2012-06-12 15:33 ` Chegu Vinod
2012-06-12 15:39 ` Gleb Natapov
2012-06-12 18:44 ` Chegu Vinod
2012-06-13 7:12 ` Gleb Natapov
2012-06-13 8:14 ` Avi Kivity
2012-06-10 9:30 ` Gleb Natapov
2012-06-10 13:29 ` Chegu Vinod
2012-06-08 17:51 ` Chegu Vinod
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20120608T181832-528@post.gmane.org \
--to=chegu_vinod@hp.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox