From: topperxin <topperxin@126.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Problem about SRIOV and the vCpu number
Date: Wed, 9 Apr 2014 20:58:18 +0800 (CST) [thread overview]
Message-ID: <39077d80.14edc.14546914d4c.Coremail.topperxin@126.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 592 bytes --]
Hi list
I'm using Intel 82599 NIC for the SRIOV function.
At the same time, I would like to assign more vCpu to the VM who already configured SRIOV NIC.
My host platform has 32 physical CPUs. and xenserver 6.2
What make me curious is when the vcpu number is less 15, all the things work well.
While when the vcpu number assigned to the VM more than 15, such as 20, the VM can not work normally.
Anyone who have ever met this problem? Is it same on XEN?
Any replies are welcome, thanks a lot.
Lixin.
[-- Attachment #1.2: Type: text/html, Size: 1090 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2014-04-09 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 12:58 topperxin [this message]
2014-04-10 15:31 ` Problem about SRIOV and the vCpu number George Dunlap
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=39077d80.14edc.14546914d4c.Coremail.topperxin@126.com \
--to=topperxin@126.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).