From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Jiri Denemark <jdenemar@redhat.com>, xen-devel@lists.xensource.com
Subject: Re: [RFC][PATCH] Increase hotplug timeout
Date: Thu, 16 Apr 2009 11:59:07 +0100 [thread overview]
Message-ID: <20090416105906.GB4787@redhat.com> (raw)
In-Reply-To: <18919.3354.673265.359229@mariner.uk.xensource.com>
On Thu, Apr 16, 2009 at 11:48:58AM +0100, Ian Jackson wrote:
> Jiri Denemark writes ("[Xen-devel] [RFC][PATCH] Increase hotplug timeout"):
> > When a process in dom0 is writing huge amount of data to a disk in
> > parallel to creating new domain, it may take quite a lot of time
> > until all hotplug scripts finish. For example, on my system it takes
> > almost 5 minutes to start all hotplug scripts.
>
> That's a very long time. All of that for just one domain ?
>
> > So it seems 100 seconds is not enough for such scenarios as xend
> > would give up waiting for hotplug scripts too early. What do you
> > think about the attached patch, which increases the timeout to 10
> > minutes? Of course, the dark side of this change is that it would
> > take ages to recognize hotplug scripts are not really working.
>
> I think very few people have configurations like yours.
It is a problem that gets more common as you add more devices. eg if
you have lots of disks or nics then it becomes much more likely to
occur. Add in a 2nd guest which is doing alot of I/O at the same time
you are trying to start this guest and it gets worse again, because
xenstored I/O performance starts to hurt. Having xenstored on tmpfs
should make it happen less. Having a fully in memory xenstored without
any need for tmpfs at all, would be even better.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2009-04-16 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 14:41 [RFC][PATCH] Increase hotplug timeout Jiri Denemark
2009-04-16 10:48 ` Ian Jackson
2009-04-16 10:59 ` Daniel P. Berrange [this message]
2009-04-16 11:40 ` Jiri Denemark
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=20090416105906.GB4787@redhat.com \
--to=berrange@redhat.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jdenemar@redhat.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.