| commit | 0311e5bb22b330fd9cc84397d5d994385c1b6114 | |
| author | Anthony Liguori <aliguori@us.ibm.com> | |
| Sun, 17 May 2009 15:43:14 +0000 (17 10:43 -0500) | ||
| committer | Avi Kivity <avi@redhat.com> | |
| Thu, 21 May 2009 09:04:58 +0000 (21 12:04 +0300) | ||
| tree | aa5eaeb14483ccc1e96fcd953c0a2917109e22f2 | treesnapshot (tar.gz zip) |
| parent | b5eca4097db990dafbb153ee5d8ab200c10eeb8c | commitdiff |
Increment virtio-net savevm version to avoid conflict with upstream QEMU.
When TAP_VNET_HDR eventually merges into upstream QEMU, it cannot change the
format of the version 6 savevm data. This means that we're going to have to
bump the version up to 7. I'm happy to reserve version 7 as having TAP_VNET_HDR
support to allow time to include this support in upstream QEMU.
For those shipping products based on KVM though, it's important that we do not
conflict with upstream QEMU versioning or else it's going to result in breakage
of backwards compatibility.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
When TAP_VNET_HDR eventually merges into upstream QEMU, it cannot change the
format of the version 6 savevm data. This means that we're going to have to
bump the version up to 7. I'm happy to reserve version 7 as having TAP_VNET_HDR
support to allow time to include this support in upstream QEMU.
For those shipping products based on KVM though, it's important that we do not
conflict with upstream QEMU versioning or else it's going to result in breakage
of backwards compatibility.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
| hw/virtio-net.c | diffblobblamehistory |