From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: wei.liu2@citrix.com, stefano.stabellini@eu.citrix.com,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
ian.campbell@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 1/2] libxl: Wait until QEMU removed the device before tearing it down
Date: Fri, 14 Nov 2014 16:38:11 -0500 [thread overview]
Message-ID: <54667643.7010008@oracle.com> (raw)
In-Reply-To: <1106502345.20141114222039@eikelenboom.it>
On 11/14/2014 04:20 PM, Sander Eikelenboom wrote:
> Friday, November 14, 2014, 10:09:04 PM, you wrote:
>
>
>> I don't know about detach but I apparently can't even properly attach a
>> second device --- I get complaints about it already being in xenstore.
>> But device does show up in the guest.
>> And then I can't remove it because, well, it's not in xenstore.
>> Maybe it has something to do with the fact that both devices are virtual
>> functions of the same physical device. I might look at this sometime
>> next week.
> Ah .. virtual function as in virtual functions of a SR-IOV NIC ?
> or the functions of a multi-function device (the later ends up as separate devices
> in a HVM guest (assuming you use qemu-xen and not qemu-traditional)).
Virtual functions of an SR-IOV NIC. I'd think they should show up as separate devices in xenstore. (And they do show up as separate devices in the guest)
And qemu-xen.
-boris
next prev parent reply other threads:[~2014-11-14 21:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 23:16 [PATCH 0/2] Two fixes for libxl's PCI detach operation Boris Ostrovsky
2014-11-10 23:16 ` [PATCH 1/2] libxl: Wait until QEMU removed the device before tearing it down Boris Ostrovsky
2014-11-14 14:41 ` Ian Jackson
2014-11-14 15:30 ` Boris Ostrovsky
2014-11-14 16:01 ` Ian Jackson
2014-11-14 16:24 ` Boris Ostrovsky
2014-11-14 16:31 ` Ian Jackson
2014-11-14 16:37 ` Boris Ostrovsky
2014-11-14 16:36 ` Ian Jackson
2014-11-14 16:58 ` Boris Ostrovsky
2014-11-14 17:45 ` Sander Eikelenboom
2014-11-14 18:07 ` Ian Jackson
2014-11-14 19:24 ` Sander Eikelenboom
2014-11-14 21:09 ` Boris Ostrovsky
2014-11-14 21:20 ` Sander Eikelenboom
2014-11-14 21:38 ` Boris Ostrovsky [this message]
2014-11-14 21:50 ` Sander Eikelenboom
2014-11-14 16:19 ` Ian Jackson
2014-11-14 17:09 ` Boris Ostrovsky
2014-11-14 17:33 ` Ian Jackson
2014-11-10 23:16 ` [PATCH 2/2] libxl: Simplify cleanup in do_pci_remove() Boris Ostrovsky
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=54667643.7010008@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=linux@eikelenboom.it \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.