Red Hat Bugzilla – Bug 754772
Convert all uses of "fedora-13" machine type into "pc-0.14"
Last modified: 2016-04-26 09:56:42 EDT
Description of problem:
qemu removed support for the fedora-13 machine type in F16, with the result that VMs created with older toolchains fail to boot after the host is upgraded to F16.
Steps to Reproduce:
1. Create a VM with the "fedora-13" machine type on a F15 host
2. Upgrade the host to F16
3. Attempt to boot the VM
VM fails to boot with the message:
error: Failed to start domain foo
error: internal error process exited while connecting to monitor: Supported machines are:
pc Standard PC (alias of pc-0.14)
pc-0.14 Standard PC (default)
pc-0.13 Standard PC
pc-0.12 Standard PC
pc-0.11 Standard PC, qemu 0.11
pc-0.10 Standard PC, qemu 0.10
isapc ISA-only PC
Libvirt detects and reports that the user has specified a machine type that qemu does not understand, showing both the user specified value and the list of values that qemu supports.
IMO this needs to be fixed immediately as it has already resulted in 3 BZs filed against libvirt for non-booting VMs.
After further discussions, we decided to reinstate support for the fedora-13 machine type in F16 qemu (to be removed for good with the release of F17) - see Bug 748218, while at the same time adding a Fedora-specific patch to libvirt that will catch uses of that machine as they pass by and convert them to "pc-0.13" (which to the best of our knowledge is exactly equivalent to "fedora-13") while logging a warning to indicate what was done. This patch will be carried at least through Fedora 17, possibly into Fedora 18. By that time, hopefully all uses of fedora-13 will have disappeared; for those that manage to sneak through, the change will be release-noted.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Is there any progress on this? I'm running rawhide and all of my old VMs won't start.
I'm happy to test a patch, or apply some sort of manual fix to convert the machine types.
Never mind, I see the manual workaround description in 748218.
Last night I posted a potential patch for this to email@example.com. There are still a couple things to clean up before including it in Fedora builds:
libvirt-0.9.6-4.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libvirt-0.9.6-4.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
libvirt-0.9.6-4.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
libvirt-0.9.10-2.fc17 has been submitted as an update for Fedora 17.
libvirt-0.9.10-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.