Bug 753783
| Summary: | Supported machines are: pc Standard PC (alias of pc-0.14) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||
| Component: | libvirt | Assignee: | Fedora Virtualization Maintainers <virt-maint> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 16 | CC: | berrange, clalancette, crobinso, dougsland, itamar, jforbes, laine, veillard, virt-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-11-15 21:54:13 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Created attachment 533529 [details]
broken VM definition file
gpxe-roms-qemu-1.0.1-4.fc16.noarch qemu-common-0.15.1-2.fc16.x86_64 qemu-system-x86-0.15.1-2.fc16.x86_64 qemu-kvm-0.15.1-2.fc16.x86_64 qemu-img-0.15.1-2.fc16.x86_64 This bug may be same as bug 750881. (In reply to comment #3) > This bug may be same as bug 750881. It's similar to that, in that qemu spits out the same message due to a machine type that's unknown by qemu, but in the case of that bug it's because ovirt incorrectly assumes that the nodes will be running RHEL but your node is running Fedora (which doesn't understand the rhelx.x.x machine types). In your case, your guest was almost surely created when your host was running Fedora 13 and thus got the machine type 'fedora-13'. qemu retained this machine type through F14 and F15, but forgot to put it into F16, which is what's causing the problems now. Since 748218 was the first report filed for this problem, that's the one that will be consolidating all the reports and tracking the fix (to add fedora-13 back into the list of qemu machine types). *** This bug has been marked as a duplicate of bug 748218 *** |
Description of problem: After upgrade from F15 to F16 some of my virtual machines can no longer be started. I receive this error: Error starting domain: internal error Process exited while reading console log output: 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 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1050, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 510, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error Process exited while reading console log output: 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 Other machines can be started. Version-Release number of selected component (if applicable): libvirt-client-0.9.6-2.fc16.x86_64 libvirt-0.9.6-2.fc16.x86_64 libvirt-python-0.9.6-2.fc16.x86_64 virt-manager-common-0.9.0-7.fc16.noarch virt-manager-0.9.0-7.fc16.noarch