OASIS Virtual I/O Device (VIRTIO) TC Public Documents

Number of Documents Show last documents per workgroup
Document Descriptions
OASIS Virtual I/O Device (VIRTIO) TC   (Showing 10 of 288)
Document Name # Size State Submitter Date Action
0
15K
Draft
Michael S. Tsirkin
2023-01-27
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 #147: should clarify VLAN tagging requirement with or without VIRTIO_NET_F_CTRL_VLAN -------------------------------------- The software virtio implementation in QEMU differentiates VLAN tagging disposition subject to the presence of VIRTIO_NET_F_CTRL_VLAN feature: - when VIRTIO_NET_F_CTRL_VLAN is negotiated, the device starts with all VLANs filtered (meaning only untagged traffic can be received, and traffic with VLAN tag will be dropped). - when VIRTIO_NET_F_CTRL_VLAN is not negotiated, all traffic including untagged and tagged can be received. It is essential to capture this expectation in the spec. Otherwise live migraiton between different virtio implemenations won't work, either from software to vDPA, or cross different vDPA vendors. See the discussion thread in: https://lists.oasis-open.org/archives/virtio-dev/202301/msg00231.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-dev/202301/msg00231.html -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-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. --------------------------------------
0
16K
Draft
Michael S. Tsirkin
2023-01-25
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 #154: virtio-network: Avoid confusion between a card and a device -------------------------------------- Problem statement: Ethernet card is a relatively vague term in context of virtio network device specification. A Ethernet card in the industry has one to multiple ports, one to multiple PCI functions. Historically virtio network device is documented as a Ethernet card. However it is usually just a single virtual Ethernet device. Solution: Hence, avoid this confusing term 'card' and align the specification to adhere to widely used specification term as 'device' used for all virtio device types. Solution patch: https://lists.oasis-open.org/archives/virtio-dev/202301/msg00230.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-dev/202301/msg00230.html -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-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. --------------------------------------
0
14K
Draft
Michael S. Tsirkin
2023-01-24
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 #153: Split individual virtio device spec to its own file -------------------------------------- Problem statement: Several of the relatively recent device specifications are maintained in their own specification file. Such separate files enable better maintenance of the specification overall. However, several of the initial virtio device specifications are located in single file. Current specification is maintained as mixed mode. Solution: Hence follow the modular approach practice of individual files for all devices. This also make maintainance easier by keeping devices and conformance clause lists together i.e. in the same directory. Patches: https://lists.oasis-open.org/archives/virtio-dev/202301/msg00210.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-dev/202301/msg00210.html -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-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. --------------------------------------
0
14K
Draft
Cornelia Huck
2022-12-07
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 #150: reserve device ID 44 for ISM device -------------------------------------- The virtio-ism device provides the ability to share memory between different guests on a host. A guest's memory got from ism device can be shared with multiple peers at the same time. This shared relationship can be dynamically created and released. The shared memory obtained from the device is divided into multiple ism regions for share. ISM device provides a mechanism to notify other ism region referrers of content update events. https://lists.oasis-open.org/archives/virtio-dev/202211/msg00198.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-dev/202211/msg00198.html -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-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. --------------------------------------
0
15K
Draft
Cornelia Huck
2022-12-05
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 #143: virtio-blk: add zoned block device specification -------------------------------------- Introduce support for Zoned Block Devices (ZBDs) to virtio. The virtio protocol for block devices (virtio-blk) is not aware of ZBDs but it allows the guest to successfully scan a host-managed zoned drive provided by as a virtio-blk device. As the result, the host-managed drive appears at the virtio-blk driver as a regular drive that will operate erroneously under the most common write workloads. Host-aware ZBDs are currently usable, but their performance is not optimal because the driver can only recoginze them as non-zoned block devices. To properly support ZBDs, the virtio-blk protocol needs to be extended to add the capabilities to convey the zone characteristics of ZBDs to the driver and to provide the support for ZBD-specific commands. The patch linked below extends the virtio-blk section of virtio specification with the minimum set of requirements that are necessary to support ZBDs. [https://lists.oasis-open.org/archives/virtio-comment/202211/msg00002.html](https://lists.oasis-open.org/archives/virtio-comment/202211/msg00002.html) The patch series to implement this spec extension in Linux kernel virtio-blk driver code has been posted to linux-block mailing list - [https://lore.kernel.org/linux-block/20221110053952.3378990-1-dmitry.fomichev@wdc.com/](https://lore.kernel.org/linux-block/20221110053952.3378990-1-dmitry.fomichev@wdc.com/) The patch series to add ZBD support to QEMU virtio codebase by Sam Li that follow this spec are in review at the QEMU mailing list - [https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg05195.html](https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg05195.html) [https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg05205.html](https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg05205.html) [https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg05896.html](https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg05896.html) -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202211/msg00002.html](https://lists.oasis-open.org/archives/virtio-comment/202211/msg00002.html) -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-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. --------------------------------------
0
13K
Draft
Cornelia Huck
2022-11-14
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 #148: Reserve device ID 43 for Camera Device -------------------------------------- Please reserve device ID 43 for the Camera device as requested in https://lists.oasis-open.org/archives/virtio-dev/202210/msg00021.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-dev/202210/msg00021.html -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-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. --------------------------------------
0
14K
Draft
Cornelia Huck
2022-08-02
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 #142: virtio-vsock: add VIRTIO_VSOCK_F_NO_IMPLIED_STREAM feature bit -------------------------------------- Initially virtio-vsock only supported the stream type, which is why there was no feature. Later we added the seqpacket type and in the future we may have other types (e.g. datagram). seqpacket is an extension of stream, so it might be implied that if seqpacket is supported, stream is too, but this might not be true for other types. As we discussed [here](http://markmail.org/message/2s3qd74drgjxkvte) should be better to add a new VIRTIO_VSOCK_F_NO_IMPLIED_STREAM feature bit to avoid this implication. Let's also add normative sections to better define the behavior when VIRTIO_VSOCK_F_NO_IMPLIED_STREAM is negotiated or not. Latest patch sent: https://lists.oasis-open.org/archives/virtio-comment/202207/msg00034.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202207/msg00034.html -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-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. --------------------------------------
0
13K
Draft
Cornelia Huck
2022-08-01
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 #129: Crypto: introduce akcipher service -------------------------------------- Support a new class of crypto service "AKCIPHER", include serval asymmetric algorithms. The latest patch: https://lists.oasis-open.org/archives/virtio-comment/202206/msg00066.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202206/msg00066.html -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-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. --------------------------------------
0
15K
Draft
Cornelia Huck
2022-07-11
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 #141: virtio-net: interrupt coalescing feature -------------------------------------- This patch adds a new interrupt coalescing feature for a VirtIO net device: VIRTIO_NET_F_NOTF_COAL(53). A device that negotiates this feature can receive VIRTIO_NET_CTRL_NOTF_COAL commands through the control virtqueue. - VIRTIO_NET_CTRL_NOTF_COAL_TX_SET: set tx_usecs and tx_max_packets parameters. - VIRTIO_NET_CTRL_NOTF_COAL_RX_SET: set rx_usecs and rx_max_packets parameters. spec patch: https://lists.oasis-open.org/archives/virtio-comment/202206/msg00100.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202206/msg00100.html -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-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. --------------------------------------
0
13K
Draft
Chet Ensign
2022-07-01
Virtual I/O Device (VIRTIO) Version 1.2 [1] has had Non-Material Changes since the work's last public review [2]. This ballot requires a Special Majority Vote [3]. The TC roster currently lists 8 voting members. In order to pass, at least 6 members have to vote Yes and no more than 1 members may vote No. [1] URI for the specification https://github.com/oasis-tcs/virtio-docs/blob/master/virtio-v1.2-cs01.zipd [2] The Working Draft for this Committee Specification contains changes made since its last public review. The changes made are documented in https://www.oasis-open.org/committees/ballot.php?id=3705. The TC judges these changes to be Non-Material Changes in accordance with the definition in the OASIS TC Process (https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22/#dNonmaterialChange). [3] https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22/#dSpecialMajority