This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] about hot plug issue

To: "Yu, Ping Y" <ping.y.yu@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] about hot plug issue
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 26 Sep 2006 08:41:48 +0100
Cc: sos22@xxxxxxxxx, Steven Hand <steven.hand@xxxxxxxxxxxx>, Christian.Limpach@xxxxxxxxxxxxx
Delivery-date: Tue, 26 Sep 2006 00:52:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <8C834404208B254EAD4E532C9485986901408B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbhPoDCejFEsZRAQd24zSmg/cIN+wAALgcs
Thread-topic: [Xen-devel] about hot plug issue
User-agent: Microsoft-Entourage/

On 26/9/06 8:36 am, "Yu, Ping Y" <ping.y.yu@xxxxxxxxx> wrote:

> 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.

How long do the creation commands appear to hang before timing out? With the
new timeouts it ought to be at least a minute, which ought to be plenty of
time to create a dozen domains.

> 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.

Perhaps we need a single polling daemon that can demux kb/mouse events to
all qemu instances in a way that can be select()ed on. That would avoid
unscalable polling overheads.

 -- Keir

Xen-devel mailing list