xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: 马磊 <aware.why@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: [BUG]: when using `xl restore`,xc_evtchn_alloc_unbound will raise this error
Date: Wed, 26 Dec 2012 18:19:36 +0800	[thread overview]
Message-ID: <CA+ePHTAcFUrPC3rUiBTps0JZ6PdBxUZfsZSgnn4Mym=po+NDpg@mail.gmail.com> (raw)
In-Reply-To: <CA+ePHTBx8iJaAz7PCzeM-jFcs9e_Cx2qAR3cZTSavbZs0hhEoA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1711 bytes --]

On Wed, Dec 26, 2012 at 6:03 PM, 马磊 <aware.why@gmail.com> wrote:

> Hi,
>     I got xen source code from
> http://www.xen.org/download/index_4.1.2.html .
>     when using `xl restore`,xc_evtchn_alloc_unbound will raise this error: xc:
> error: do_evtchn_op: HYPERVISOR_event_channel_op failed: -1 (3 = No such
> process): Internal error.
>   what does this mean and what does such process refer to?
>     Looking forward to your reply.
>     Thanks.
>

The error exactly occurs at  this point: (tools/libxl/libxl_dom.c)
67-int libxl__build_pre(libxl_ctx *ctx, uint32_t domid,



 68              libxl_domain_build_info *info, libxl_domain_build_state
*state)


 69{



 70    xc_domain_max_vcpus(ctx->xch, domid, info->max_vcpus);



 71    xc_domain_setmaxmem(ctx->xch, domid, info->target_memkb +
LIBXL_MAXMEM_CONSTANT);


 72    xc_domain_set_memmap_limit(ctx->xch, domid,



 73            (info->hvm) ? info->max_memkb :



 74            (info->max_memkb + info->u.pv.slack_memkb));



 75    xc_domain_set_tsc_info(ctx->xch, domid, info->tsc_mode, 0, 0, 0);



 76    if ( info->disable_migrate )



 77        xc_domain_disable_migrate(ctx->xch, domid);



 78



 79    if (info->hvm) {



 80        unsigned long shadow;



 81        shadow = (info->shadow_memkb + 1023) / 1024;



 82        xc_shadow_control(ctx->xch, domid,
XEN_DOMCTL_SHADOW_OP_SET_ALLOCATION, NULL, 0, &shadow, 0, NULL);


 83    }



 84



 85    state->store_port = xc_evtchn_alloc_unbound(ctx->xch, domid, 0);



 86    state->console_port = xc_evtchn_alloc_unbound(ctx->xch, domid, 0);



 87    return 0;



 88}

[-- Attachment #1.2: Type: text/html, Size: 9031 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-12-26 10:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26 10:03 [BUG]: when using `xl restore`,xc_evtchn_alloc_unbound will raise this error 马磊
2012-12-26 10:19 ` 马磊 [this message]
2012-12-26 13:41   ` Wei Liu
2012-12-26 14:45     ` 马磊
2012-12-26 19:33       ` Wei Liu
2012-12-27  2:12         ` 马磊
2012-12-27 12:41           ` Wei Liu
2012-12-28  3:13             ` 马磊
2012-12-28 10:46               ` Wei Liu
2012-12-31  3:10                 ` 马磊
2012-12-31 12:03                   ` Wei Liu
2013-01-04  3:23                     ` 马磊
2013-01-04  6:27                       ` 马磊
2013-01-04  9:20                         ` Ian Campbell
2013-01-04 11:34                           ` 马磊
2013-01-04 11:42                             ` Ian Campbell
2013-01-05  4:03                               ` 马磊
2013-01-05  6:44                       ` 马磊

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='CA+ePHTAcFUrPC3rUiBTps0JZ6PdBxUZfsZSgnn4Mym=po+NDpg@mail.gmail.com' \
    --to=aware.why@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).