On Wed, Mar 18, 2015 at 01:35:15PM +, Ian Campbell wrote:
> On Fri, 2015-03-13 at 10:34 +, Wei Liu wrote:
> > Watch /local/domain/$dm_domid/device-model/$domid/state, wait until
> > state turns "running" then unpause guest.
> >
> > LIBXL_STUBDOM_START_TIMEOUT is the timeout used wait for s
On Fri, 2015-03-13 at 10:34 +, Wei Liu wrote:
> Watch /local/domain/$dm_domid/device-model/$domid/state, wait until
> state turns "running" then unpause guest.
>
> LIBXL_STUBDOM_START_TIMEOUT is the timeout used wait for stubdom to be
> ready. My test on a very old machine (Core 2 6400) showed
On Fri, Mar 13, 2015 at 10:34:34AM +, Wei Liu wrote:
> Watch /local/domain/$dm_domid/device-model/$domid/state, wait until
> state turns "running" then unpause guest.
>
> LIBXL_STUBDOM_START_TIMEOUT is the timeout used wait for stubdom to be
> ready. My test on a very old machine (Core 2 6400)
Watch /local/domain/$dm_domid/device-model/$domid/state, wait until
state turns "running" then unpause guest.
LIBXL_STUBDOM_START_TIMEOUT is the timeout used wait for stubdom to be
ready. My test on a very old machine (Core 2 6400) showed that it might
need more than 20s before the stubdom is read