RE: [Xen-devel] VMX status report 11536:041be3f6b38e

["Yu, Ping Y" <ping.y.yu@xxxxxxxxx>]

Thanks for the fix, and we will verify it in later testing.

Ping

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Roland 
>Paterson-Jones
>Sent: 2006年9月20日 14:54
>To: Yu, Ping Y
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] VMX status report 11536:041be3f6b38e
>
>Yu, Ping Y wrote:
>
>>2).Create eight VMX domains simultaneously, usually, not all four VMX
>>domains can start successfully. only part of them can start, but two or
>>one will failed with the following messages " Error: Device 768 (vbd)
>>could not be connected. Hotplug scripts not working." or "Error: Device
>>5632 (vbd) could not be connected. Hotplug scripts not working."or "
>>Error: Device 0 (vif) could not be connected. Hotplug scripts not
>>working.".
>>
>>
>We have seen this caused by time-outs due to a very busy dom-0.
>
>Try increasing the timeout in
>./tools/python/xen/xend/server/DevController.py, for example:
>
>--- ./tools/python/xen/xend/server/DevController.py     2006-04-13
>19:48:39.000000000 +0200
>+++ ../xen-3.0.2-2patched/tools/python/xen/xend/server/DevController.py
>2006-06-07 13:17:45.000000000 +0200
>@@ -25,7 +25,7 @@
> from xen.xend.xenstore.xstransact import xstransact, complete
> from xen.xend.xenstore.xswatch import xswatch
>
>-DEVICE_CREATE_TIMEOUT = 10
>+DEVICE_CREATE_TIMEOUT = 3600
> HOTPLUG_STATUS_NODE = "hotplug-status"
> HOTPLUG_ERROR_NODE  = "hotplug-error"
> HOTPLUG_STATUS_ERROR = "error"
>
>Roland
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel