< Home | Return to Ballot listing

Ballot Details    TC Member Ballot View
Resolve Issue #27: vsock: add vsock device

Should the TC accept changes listed in the description to resolve issue 27, 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 #27: vsock: add vsock device
--------------------------------------
The virtio vsock device is a zero-configuration socket communications
device. It is designed as a guesthost management channel suitable
for communicating with guest agents.

vsock is designed with the sockets API in mind and the driver is
typically implemented as an address family (at the same level as
AF_INET). Applications written for the sockets API can be ported with
minimal changes (similar amount of effort as adding IPv6 support to an
IPv4 application).

Unlike the existing console device, which is also used for guesthost
communication, multiple clients can connect to a server at the same time
over vsock. This limitation requires console-based users to arbitrate
access through a single client. In vsock they can connect directly and
do not have to synchronize with each other.

Unlike network devices, no configuration is necessary because the device
comes with its address in the configuration space.

The vsock device was prototyped by Gerd Hoffmann and Asias He. I picked
the code and design up from them.
--------------------------------------

The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-dev/201811/msg00145.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.

--------------------------------------

 [ ]  Yes
 [ ]  No
 [ ]  Abstain
Opening:   Friday, 30 November 2018 @ 08:45 am EST
Closing:   Friday, 7 December 2018 @ 08:45 am EST
Group:   OASIS Virtual I/O Device (VIRTIO) TC
Ballot has closed.

Referenced Items
Name Type Date Action
Document
2018-12-07

Voting Details

Voting Summary

Options with highest number of votes are bold

Option # Votes % of Total
Yes 6 100%
No 0 0%
Abstain 0
Eligible members who have voted: 6 of 6 100%
Eligible members who have abstained: 0 of 6 0%
Eligible members who have not voted: 0 of 6 0%

Voting Details

Voter Company VoteReference Document and/or Comment
Halil Pasic
IBM
Yes
 
Mihai Carabas
Oracle
Yes
 
Michael S. Tsirkin
Red Hat
Yes
 
Stefan Hajnoczi
Red Hat
Yes
 
Cornelia Huck
Red Hat
Yes
 
Jan Kiszka
Siemens AG
Yes