From KVM
Contents |
[edit]
Stable Guest ABI
Allow guest virtual machines to be presented with the same ABI across QEMU upgrades.
[edit]
Detailed
[edit]
Why is it useful?
Changing guest ABI can confuse or break guests.
This is particularly relevant for Windows guests where a guest ABI change may require Windows installs to be reactivated.
[edit]
How to run
libvirt takes care of it.
[edit]
How to test
Requirement: At least one guest image installed before executing this case.
1) Edit an existing guests configuration using virsh edit 2) Set the machine attribute to pc e.g.
<os>
<type arch='x86_64' machine='pc'>hvm</type>
3) Check the newly saved configuration using virsh dumpxml 4) Verify the machine attribute is now pc-0.11 e.g.
<os>
<type arch='x86_64' machine='pc-0.11'>hvm</type>
5) Start the guest and verify that it boots correctly as before.
[edit]
Potential migration issues
[edit]
Backward/forward compatibility issues
[edit]
Specific issues with some releases
[edit]
Test cases
[edit]
Links
For additional information, see Features/KVM Stable Guest ABI and Features/KVM Stable PCI Addresses on the Fedora Project Wiki.

