PIC


Virtual I/O Device (VIRTIO) Version 1.0

Working Draft

05 Nov 2013

Technical Committee:
OASIS Virtual I/O Device (VIRTIO) TC

Chair:
Rusty Russell (rusty@au.ibm.com), IBM

Editors:
Michael S. Tsirkin (mst@redhat.com), Red Hat
Cornelia Huck (cornelia.huck@de.ibm.com), IBM
Pawel Moll (pawel.moll@arm.com), ARM Limited

Additional artifacts:
This prose specification is one component of a Work Product which also includes:

Related work:
This specification replaces or supersedes:

This specification is related to:

Declared XML namespaces:

Abstract:
Summary of the technical purpose of the specification

Status:
This Working Draft (WD) has been produced by one or more TC Members; it has not yet been voted on by the TC or approved as a Committee Draft (Committee Specification Draft or a Committee Note Draft). The OASIS document Approval Process begins officially with a TC vote to approve a WD as a Committee Draft. A TC may approve a Working Draft, revise it, and re-approve it any number of times as a Committee Draft.

Technical Committee members should send comments on this specification to the Technical Committee’s mailing list. Others should send comments to the Technical Committee by sending mail to the virtio-comment public mailing list or using the "Send A Comment" button on the Technical Committee’s web page at https://www.oasis-open.org/committees/virtio/.

Initial URI pattern

http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/virtio-v1.0-csd01.odt
(Managed by OASIS TC Administration; please don’t modify.)
http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/virtio-v1.0-csd01.pdf (Authoritative)
http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/virtio-v1.0-csd01.html

Notices

Copyright © OASIS Open 2013. All Rights Reserved.

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS’ procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

The name "OASIS" is a trademark of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see https://www.oasis-open.org/policies-guidelines/trademark for above guidance.

__________________________________________________________________

Table of Contents

1 Introduction
 1.1 Terminology
 1.2 Normative References
 1.3 Non-Normative References
 1.4 Section
  1.4.1 Second level heading
2 Conformance
A Acknowledgements
B Example Title
 B.1 subsiduary appendix
  B.1.1 Sub-subsiduary appendix
C Revision History


1 Introduction

1.1 Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

1.2 Normative References

[RFC2119]

S. Bradner, Key words for use in RFCs to Indicate Requirement Levels,
http://www.ietf.org/rfc/rfc2119.txt, March 1997

1.3 Non-Normative References

1.4 Section

1.4.1 Second level heading

1.4.1.1 Third level heading
1.4.1.1.1 Fourth level heading
1.4.1.1.1.1 Fifth level heading


2 Conformance

The last numbered section in the specification must be the Conformance section. Conformance Statements/Clauses go here.

Appendix A. Acknowledgements

The following individuals have participated in the creation of this specification and are gratefully acknowledged:

Participants:
[ Participant Name, Affiliation | Individual Member ]

Appendix B. Example Title

demonstrating appendix numbering

B.1 subsiduary appendix

text

B.1.1 Sub-subsiduary appendix

text

Appendix C. Revision History





Revision Date Editor Changes Made




[Rev number ] [Rev Date ] [Modified By ] [Summary of Changes ]