Comment 19 for bug 1291321

After trying a few more things and discussing with upstream, I'm afraid the answer will be to mark this as unsupported in the release notes. Because users could be using -m pc-1.0 in raring+, we cannot simply use the old qemu-kvm values for pc-1.0 and lower machines, as that would fix users from newer releases.

The one possibility which would remain, would be to publish an alternate qemu package (perhaps in ppa) which uses the older values, and advise users needing to migrate images from precise to install that package. Key to this would be to make sure that users use a higher machine type when starting new VMs so that they could be migrated to the new qemu values for subsequent releases.

In order to make sure that this is not an issue after trusty, we will define a trusty-specific machine type.