From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: "qemu-devel" <qemu-devel@nongnu.org>, "kvm" <kvm@vger.kernel.org>
Subject: [questions] about using vfio to assign sr-iov vf to vm
Date: Thu, 14 Aug 2014 16:22:26 +0800 [thread overview]
Message-ID: <201408141622244965425@sangfor.com> (raw)
Hi, all
I'm using VFIO to assign intel 82599 VF to VM, now I encounter a problem,
82599 PF and its VFs belong to the same iommu_group, but I only want to assign some VFs to one VM, and some other VFs to another VM, ...,
so how to only unbind (part of) the VFs but PF?
I read the kernel doc vfio.txt, I'm not sure should I unbind all of the devices which belong to one iommu_group?
If so, because PF and its VFs belong to the same iommu_group, if I unbind the PF, its VFs also diappeared.
I think I misunderstand someting,
any advises?
Thanks,
Zhang Haoyu
WARNING: multiple messages have this Message-ID (diff)
From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: [Qemu-devel] [questions] about using vfio to assign sr-iov vf to vm
Date: Thu, 14 Aug 2014 16:22:26 +0800 [thread overview]
Message-ID: <201408141622244965425@sangfor.com> (raw)
Hi, all
I'm using VFIO to assign intel 82599 VF to VM, now I encounter a problem,
82599 PF and its VFs belong to the same iommu_group, but I only want to assign some VFs to one VM, and some other VFs to another VM, ...,
so how to only unbind (part of) the VFs but PF?
I read the kernel doc vfio.txt, I'm not sure should I unbind all of the devices which belong to one iommu_group?
If so, because PF and its VFs belong to the same iommu_group, if I unbind the PF, its VFs also diappeared.
I think I misunderstand someting,
any advises?
Thanks,
Zhang Haoyu
next reply other threads:[~2014-08-14 8:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 8:22 Zhang Haoyu [this message]
2014-08-14 8:22 ` [Qemu-devel] [questions] about using vfio to assign sr-iov vf to vm Zhang Haoyu
2014-08-14 12:44 ` Alex Williamson
2014-08-14 12:44 ` [Qemu-devel] " Alex Williamson
2014-08-16 6:48 ` Zhang Haoyu
2014-08-16 6:48 ` [Qemu-devel] " Zhang Haoyu
2014-08-16 13:29 ` Alex Williamson
2014-08-16 13:29 ` [Qemu-devel] " Alex Williamson
2014-08-18 1:00 ` Zhang Haoyu
2014-08-18 1:00 ` [Qemu-devel] " Zhang Haoyu
2014-08-18 1:14 ` Alex Williamson
2014-08-18 1:14 ` [Qemu-devel] " Alex Williamson
2014-08-18 8:46 ` Zhang Haoyu
2014-08-18 8:46 ` [Qemu-devel] " Zhang Haoyu
2014-08-18 9:49 ` Zhang Haoyu
2014-08-18 9:49 ` [Qemu-devel] " Zhang Haoyu
2014-08-18 12:53 ` Alex Williamson
2014-08-18 12:53 ` [Qemu-devel] " Alex Williamson
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=201408141622244965425@sangfor.com \
--to=zhanghy@sangfor.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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.