Red Hat Bugzilla – Bug 643982
Internal error reading console log output. vm won't start
Last modified: 2010-10-19 18:58:20 EDT
Description of problem:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 878, in run_domain
File "/usr/share/virt-manager/virtManager/domain.py", line 1321, in startup
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 333, 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.13)
pc-0.13 Standard PC (default)
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
Version-Release number of selected component (if applicable):
Attempting to start an old F13 vm. This happened after bug 638457 was fixed.
Yeah, this is a known bug. Unfortunately we made a mistake in Fedora 13 and added a "fedora13" machine type that never should have existed.
There are two ways to get around it:
1) Update your packages qemu-0.13.0-0.6.rc1.fc14 or later, which should contain a backwards compatible fix for this.
2) Edit your domain XML (virsh edit <domain>), remove the part of the XML that says "machine='fedora-13'", and save the guest. libvirt will fill in the "correct" machine type going forward, and this shouldn't happen again.
*** This bug has been marked as a duplicate of bug 623957 ***
1) Can you push the latest qemu into rawhide? It currently only seems to be updated in f14, not f15
2) virsh 0.8.4 checks for a bad machine time and doesn't allow the change.
error: unknown OS type no OS type