<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7601.19038"></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt 微软雅黑">
<DIV><BR><BR>>>> Cole Robinson <crobinso@redhat.com> 2017/10/26 星期四 下午 6:08 >>><BR>>On 10/20/2017 11:08 AM, Lin Ma wrote:<BR>>> Signed-off-by: Lin Ma <lma@suse.com><BR>>> ---<BR>>> ui/netlist.ui | 97 ++++++++++++++++++++++++++++++++++++++++++++++++++<BR>>> virtManager/details.py | 9 ++++-<BR>>> virtManager/domain.py | 8 ++++-<BR>>> virtManager/netlist.py | 67 +++++++++++++++++++++++++++++++++-<BR>>> 4 files changed, 178 insertions(+), 3 deletions(-)<BR>><BR>>Can you explain the usecase for vhostuser a bit? I've never used it. Is<BR>>it largely just to facilitate DPDK? If so my feeling is this doesn't<BR>>really need to be in virt-manager UI given it's an advanced feature that<BR>>requires external config to setup in the first place, I'd prefer to just<BR>>point people at virt-xml for editing an existing VM than maintain<BR>>explicit UI for it. But maybe I'm missing something...</DIV>
<DIV>First of all, Thanks to review the patches.</DIV>
<DIV><BR>Yes, it does require external config to setup in the first place.</DIV>
<DIV>e.g: openvswitch creates the relevant vhostuser unix sockets, then</DIV>
<DIV>qemu connects to them as backend of virtual nic to request service.</DIV>
<DIV> </DIV>
<DIV>eventhough it replies on external app to create the unix sockets, But</DIV>
<DIV>what I thought is that the patch provides a convenience way to help</DIV>
<DIV>users to review and configure this kind of virtual nic.</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Lin</DIV></BODY></HTML>