Hi On Thu, Nov 26, 2015 at 11:33 AM, Michael S. Tsirkin <m...@redhat.com> wrote: > I'm still not sure users actually need this. I am inclined to think we > should teach guests to respond to NEED_RESET status. Then to handle > disconnect, we would > - deactivate the disconnected backend > - stop VM, and wait for a reconnect > - set NEED_RESET status, and re-activate the backend > after guest reset
Sorry your answer came late, so my reply too ;). It may depend on the use case, what I suggest wouldn't need to stop the VM, but merely set the link-down status. Furthermore, how do you disconnect/deactivate the backend cleanly? Having an explicit message for that and document it may make things easier. It has been a while I haven't looked at vhost-user, so I am short of details, but I rebased this series, if there is still interest. I'll send a RFCv2, there are a couple of worthy fixes to pick from that. thanks -- Marc-André Lureau
