From: Jun Koi <junkoi2004@gmail.com>
To: "Xu, Dongxiao" <dongxiao.xu@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Failed to create a domain with xen-unstable (Error 22: Invalid argument)
Date: Thu, 14 Jan 2010 16:40:51 +0900 [thread overview]
Message-ID: <fdaac4d51001132340vd2112abv6f12a1a771263afb@mail.gmail.com> (raw)
In-Reply-To: <6CADD16F56BC954D8E28F3836FA7ED7112A7932ED8@shzsmsx501.ccr.corp.intel.com>
On Thu, Jan 14, 2010 at 4:29 PM, Xu, Dongxiao <dongxiao.xu@intel.com> wrote:
> Yes, one VM could own maxium 128 vcpus.
> The failure you meet should be a regression. I am looking into it.
Thanks! Let me know if you need more information.
Anyway, I am wondering how a simple bug like this can evade the
auto-testing process??
Jun
prev parent reply other threads:[~2010-01-14 7:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 3:57 Failed to create a domain with xen-unstable (Error 22: Invalid argument) Jun Koi
2010-01-14 5:06 ` qingbo yuan
2010-01-14 7:29 ` Xu, Dongxiao
2010-01-14 7:40 ` Jun Koi [this message]
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=fdaac4d51001132340vd2112abv6f12a1a771263afb@mail.gmail.com \
--to=junkoi2004@gmail.com \
--cc=dongxiao.xu@intel.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).