Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

qemu-configs: update disable_vhost_net description #2197

Merged
merged 1 commit into from
Nov 14, 2019

Conversation

egernst
Copy link
Member

@egernst egernst commented Nov 13, 2019

I think we should consider disable vhost-net for QEMU configuration in 1.10, though I'd like to get feedback from users/community here.

In the meantime, let's clarify what this configuration does.

Fixes: ###

Signed-off-by: Eric Ernst [email protected]

@egernst
Copy link
Member Author

egernst commented Nov 13, 2019

/test

Updated to better clarify this configuration option. Currently in QEMU
pre 1.9 release of Kata, vhost-net is used for the virtio-net backend.
This results in efficient network I/O performance, but does rely on the
backend running in ring0 (host kernel). Update comment to clarify this
trade-off for end-users.

Fixes: kata-containers#2198

Signed-off-by: Eric Ernst <[email protected]>
Copy link

@sboeuf sboeuf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Way better comment than the one we had before :)
LGTM

@codecov
Copy link

codecov bot commented Nov 14, 2019

Codecov Report

❗ No coverage uploaded for pull request base (master@75d149c). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #2197   +/-   ##
=========================================
  Coverage          ?   51.18%           
=========================================
  Files             ?      110           
  Lines             ?    15082           
  Branches          ?        0           
=========================================
  Hits              ?     7720           
  Misses            ?     6406           
  Partials          ?      956

@egernst egernst merged commit f2bbcf4 into kata-containers:master Nov 14, 2019
@egernst egernst deleted the disable-vhost-comment branch June 26, 2020 05:33
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants