|
Should the TC accept changes listed in the description to resolve issue 14,
for inclusion in specification version(s) "virtio-v1.1-cs01", and future versions of the specification?
Please vote Yes if you agree with all of the following.
If you disagree, please vote No.
If you don't have an opinion, please vote Abstain.
I move that:
The TC agrees to resolve the following specification issue:
Issue #14: Enhance device requirements for feature bits
--------------------------------------
Some guests might not resume properly from suspend a feature changes under their feet.
This applies to Linux guests and the SRIOV feature, offloads for the networking
device and highly likely to more devices and features.
Forbid devices from changing features even across a reset but keep
the door open for white-listing specific feature bits where we will know
what we are doing (e.g. the specific feature bit is re-sampled each time,
failure to resume is the intended behaviour etc).
https://lists.oasis-open.org/archives/virtio-dev/201806/msg00098.html
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-dev/201806/msg00098.html
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio-v1.1-cs01", and future versions of the
specification.
--------------------------------------
Reminder: A Voting Member must be active in a TC to maintain voting rights. As
the Virtio TC has adopted a standing rule to conduct business only by
electronic ballot, without Meetings, a Voting Member who fails to cast a ballot
in two consecutive Work Product Ballots loses his or her voting rights at the
close of the second ballot missed.
--------------------------------------
|
