From: Ritu kaur <ritu.kaur.us@gmail.com>
To: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: [Xen-users] pci passthrough and Xenserver
Date: Tue, 9 Mar 2010 17:29:47 -0800 [thread overview]
Message-ID: <29b32d341003091729p6d43407eu79acc3b2f90b3b6e@mail.gmail.com> (raw)
In-Reply-To: <29b32d341003091707y4f1fee12ucf50f4228e74007a@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2128 bytes --]
Hi,
I had additional questions(I re-read the Assign_hardware...), and I don't
quite follow it completely. The config given is for dom0, it doesn't have
any information as to what domU will get access to this pci device? Do I
need to change config in domU as well, document doesn't say anything about
it. Furthermore, in the document I see references to "xm
pci-list-assignable-devices" cli's, however, XCP comes with xe tool-stack,
does it come with similar pci commands? I am yet to install XCP, but wanted
to check.
Thanks
On Tue, Mar 9, 2010 at 5:07 PM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:
> Hi,
>
> I did go through vmops.ml and I really didn't get much information on
> what config file it is reading or what changes are needed. I looked at
> http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_modulefrom the link given by Dullor, not sure whether those changes suffice XCP
> for pci passthrough hence thought of checking. Any inputs?
>
> Thanks
>
> On Mon, Mar 8, 2010 at 2:37 PM, James Troup <james@linuxterminal.com>wrote:
>
>> No PCI passthrough for XenServer AFAIK.
>> You need XCP for that and then it is still very experimental with NO
>> documentation except what is in the code.
>> Line 483+
>> http://xenbits.xen.org/xapi/xen-api.hg?file/a8decf9d3bee/ocaml/xapi/vmops.ml
>>
>>
>> ----- Original Message -----
>> From: "Ritu kaur" <ritu.kaur.us@gmail.com>
>> To: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
>> Sent: Tuesday, 9 March, 2010 6:29:49 AM
>> Subject: [Xen-users] pci passthrough and Xenserver
>>
>> Hi,
>>
>> We are running Citrix Xenserver 5.5(dom0) and PV guests(domU). Since VT-d
>> support is not required for PV guests has anyone tried pci passthrough with
>> Citrix Xenserver? If yes what config file changes are required in domU and
>> dom0? I looked at Citrix forums and xen.org/xen-users archives, not
>> getting useful information from it. Inputs much appreciated.
>>
>> Thanks
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>
>
[-- Attachment #1.2: Type: text/html, Size: 3628 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-03-10 1:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 19:59 pci passthrough and Xenserver Ritu kaur
2010-03-08 21:00 ` Dulloor
[not found] ` <15863915.27.1268087855741.JavaMail.root@zimbra5>
2010-03-10 1:07 ` [Xen-users] " Ritu kaur
2010-03-10 1:29 ` Ritu kaur [this message]
2010-03-10 16:05 ` Ian Campbell
2010-03-10 17:48 ` [Xen-devel] " Ritu kaur
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=29b32d341003091729p6d43407eu79acc3b2f90b3b6e@mail.gmail.com \
--to=ritu.kaur.us@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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).