| commit | 13f5545daa8b4d12221bc69287c6a5d87962e115 | |
| author | Juan Quintela <quintela@redhat.com> | |
| Wed, 9 Sep 2009 07:46:57 +0000 (9 09:46 +0200) | ||
| committer | Anthony Liguori <aliguori@us.ibm.com> | |
| Wed, 9 Sep 2009 23:20:58 +0000 (9 18:20 -0500) | ||
| tree | a23eacea53af260d9e40f552291f00172a792bd8 | treesnapshot (tar.gz zip) |
| parent | 733318ea9c6d846a6a047b87619e7d9d6e9707d1 | commitdiff |
Fix VMSTATE_PCI_DEVICE version
PCI device entries have to have a default version, not 2, because they are
used in the midle of other structures that can have _any_ version number.
We can't use proper versioning here until we have SubSections support.
Why we didn't noticed before? Because in a PC, the only device ported with
a version less that 2 is piix_pm, and for that one, default pci values are
right. If you use a virtio-console, you will see that its state it is not
loaded back.
Thanks to Amit Shah for reporting the problem and help debug the fix.
Signed-off-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
PCI device entries have to have a default version, not 2, because they are
used in the midle of other structures that can have _any_ version number.
We can't use proper versioning here until we have SubSections support.
Why we didn't noticed before? Because in a PC, the only device ported with
a version less that 2 is piix_pm, and for that one, default pci values are
right. If you use a virtio-console, you will see that its state it is not
loaded back.
Thanks to Amit Shah for reporting the problem and help debug the fix.
Signed-off-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
| hw/hw.h | diffblobblamehistory |