From: Valdis.Kletnieks@vt.edu
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: Re: [PATCH] xen: wait up to 5 minutes for device connection
Date: Sat, 04 Jul 2009 11:15:30 -0400 [thread overview]
Message-ID: <15093.1246720530@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 03 Jul 2009 23:21:35 +0200." <4A4E765F.4000501@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Fri, 03 Jul 2009 23:21:35 +0200, Gerd Hoffmann said:
> Usually it is *much* faster, but when the host is quite loaded it can
> take a unusual long time. With 10 seconds it happends in practice now
> and then that a virtual machine fails to boot just because the virtual
> root disk didn't show up fast enough.
Are people actually trying to boot a guest on a host machine so loaded that
disks take that long to show up - and expect things to work in any sane
matter?
I'm tempted to suggest that booting under conditions like that is almost
deserving of its own kernel Tainted flag. If devices aren't showing up in
a timely manner, we probably need to be leery of any other kernel timeout
values as well...
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2009-07-04 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 13:12 Paolo Bonzini
2009-07-03 13:28 ` Ian Campbell
2009-07-03 16:00 ` Christoph Hellwig
2009-07-03 21:21 ` Gerd Hoffmann
2009-07-04 15:15 ` Valdis.Kletnieks [this message]
2009-07-06 7:43 ` Gerd Hoffmann
2009-07-06 21:54 ` Jeremy Fitzhardinge
2009-07-08 10:27 ` [PATCH 1/3 v2] xen: fix is_disconnected_device/exists_disconnected_device Paolo Bonzini
2009-07-08 10:27 ` [PATCH 2/3 v2] xen: improvement to wait_for_devices() Paolo Bonzini
2009-07-08 10:27 ` [PATCH 3/3 v2] xen: wait up to 5 minutes for device connetion Paolo Bonzini
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=15093.1246720530@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=hch@infradead.org \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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
Powered by JetHome