From: "Steven Hand" <steven.hand@cl.cam.ac.uk>
To: "Yu, Ping Y" <ping.y.yu@intel.com>, xen-devel@lists.xensource.com
Cc: sos22@cam.ac.uk, Christian.Limpach@xensource.com
Subject: Re: about hot plug issue
Date: Tue, 26 Sep 2006 08:47:59 +0100 [thread overview]
Message-ID: <107701c6e140$1645fd80$80cda8c0@Violet> (raw)
In-Reply-To: 8C834404208B254EAD4E532C9485986901408B@pdsmsx412.ccr.corp.intel.com
Any extreme case is going to stress the crap out of the dom0
hotplug subsystem; it's not clear it was designed for the sort
of workloads xen puts on it :-(
BTW, your attachment was stripped, but I think we can probably
work out what it does.
cheers,
S.
----- Original Message -----
From: "Yu, Ping Y" <ping.y.yu@intel.com>
To: <xen-devel@lists.xensource.com>
Cc: <Christian.Limpach@xensource.com>; <sos22@cam.ac.uk>; "Steven Hand"
<steven.hand@cl.cam.ac.uk>
Sent: Tuesday, September 26, 2006 8:36 AM
Subject: about hot plug issue
We found that cs 11554 increases some of timeout to fix
the hot plug issue when starting 4 VMX simultaneously.
Thanks for the quick reponse to nightly status report.
But we found that when in an extremely condition, like
creating 12 VMX domains and 4 XENU domains at the same
time, sometimes we still can meet this bug. Attached is a
demo script to start many domains. So we just wonder changing
the timout value could not resolve this issue completely.
At the same time, we found when main_loop_wait is increased to
100 ms, windows guest's keyboard and mouse response is
significantly slower.
Ping
next prev parent reply other threads:[~2006-09-26 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 7:36 about hot plug issue Yu, Ping Y
2006-09-26 7:41 ` Keir Fraser
2006-09-26 7:47 ` Steven Hand [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-26 7:53 Yu, Ping Y
2006-09-26 8:26 Yu, Ping Y
2006-09-26 9:15 ` Keir Fraser
2006-09-26 10:20 Yu, Ping Y
2006-09-26 10:41 ` Keir Fraser
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='107701c6e140$1645fd80$80cda8c0@Violet' \
--to=steven.hand@cl.cam.ac.uk \
--cc=Christian.Limpach@xensource.com \
--cc=ping.y.yu@intel.com \
--cc=sos22@cam.ac.uk \
--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.