[OASIS Issue Tracker] (VIRTIO-146) add advice on transition from legacy interfaces

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/VIRTIO-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael S. Tsirkin updated VIRTIO-146:
--------------------------------------

      Assignee: Michael S. Tsirkin
    Resolution: 
    Accepted by electronic ballot:
    https://www.oasis-open.org/apps/org/workgroup/virtio/ballot.php?id=2866

Fixed in:

    git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio/branches/v1.0@548 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652


> add advice on transition from legacy interfaces
> -----------------------------------------------
>
>                 Key: VIRTIO-146
>                 URL: https://issues.oasis-open.org/browse/VIRTIO-146
>             Project: OASIS Virtual I/O Device (VIRTIO) TC
>          Issue Type: New Feature
>    Affects Versions: virtio 1.0 cs03
>         Environment: Michael S. Tsirkin <mst@redhat.com>
>            Reporter: Michael S. Tsirkin
>            Assignee: Michael S. Tsirkin
>            Priority: Minor
>             Fix For: virtio 1.0 cs04
>
>
> Given someone with a legacy implementation,
> how does one approach updating to virtio 1?
> Offer some advice to implementations.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)