Description of problem: Libvirt says rhel5.4.0 machine type is supported by kvm even if it is not. As a result kvm guests which do not specify any machine type cannot be created. Version-Release number of selected component (if applicable): libvirt-0.6.3-32.el5 kvm-83-105.el5 How reproducible: 100% Steps to Reproduce: 1. /usr/libexec/qemu-kvm -M ? Supported machines are: pc Standard PC (default) 2. virsh capabilities <capabilities> ... <guest> <os_type>hvm</os_type> <arch name='x86_64'> <wordsize>64</wordsize> <emulator>/usr/libexec/qemu-kvm</emulator> <machine>rhel5.4.0</machine> <machine>pc</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/libexec/qemu-kvm</emulator> </domain> </arch> <features> <acpi default='on' toggle='yes'/> <apic default='on' toggle='no'/> </features> </guest> </capabilities> Actual results: Expected results: Additional info: After an attempt to start such guest, it's log contains: LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin HOME=/ /usr/libexec/qemu-kvm -S -M rhel5.4.0 -m 1024 -smp 1 -name vm1 -uuid ae85fedc-a822-f488-59cb-555ff3e1320d -no-kvm-pit-reinjection -monitor pty -pidfile /var/run/libvirt/qemu//vm1.pid -no-reboot -boot d -drive file=/var/lib/libvirt/images/vm1.img,if=virtio,index=0,cache=none -drive file=/var/lib/libvirt/boot/virtinst-boot.iso.l4vju-,if=ide,media=cdrom,index=2 -net nic,macaddr=54:52:00:7e:5d:68,vlan=0,model=virtio -net tap,fd=16,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -vnc 127.0.0.1:0 -k en-us Supported machines are: pc Standard PC (default)
Hmm, I didn't realize we don't have machine type probing at all in RHEL-5 libvirt. So not sure what we can do about this bug...
Created attachment 397575 [details] Conflict with kvm older than 83-142
Fix built into libvirt-0.6.3-33.el5
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0205.html