Fix included in qemu-kvm-0.12.1.2-2.415.el6_5.10

[root@dhcp-9-130 home]# rpm -q libvirt qemu-kvm-rhev
libvirt-0.10.2-29.el6_5.7.x86_64
qemu-kvm-rhev-0.12.1.2-2.415.el6_5.10.x86_64

with components above, qemu cmd has been generated by libvirt correctly.


[root@dhcp-9-130 home]# ps aux | grep -i smp --color
qemu      5671 84.4  0.4 1774120 35320 ?       Sl   14:20   0:23 /usr/libexec/qemu-kvm -name smp6 -S -M rhel6.5.0 -enable-kvm -m 1024 -realtime mlock=off -smp 6,sockets=2,cores=3,threads=1 -uuid e5447184-ede7-4884-07d8-59c3b0ce9202 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/smp6.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/home/test.qcow2,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:69:c3:7c,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
root      5737  0.0  0.0 103252   856 pts/0    S+   14:20   0:00 grep -i smp --color

snip of xml used in C#5

  <vcpu placement='static'>6</vcpu>
  <os>
    <type arch='x86_64' machine='rhel6.5.0'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <cpu>
    <topology sockets='2' cores='3' threads='1'/>
  </cpu>

define a smp6 vm in virt-manager, and config the cpu to 2 sockets, each has 3 cores
then boot it.

As not error like https://bugzilla.redhat.com/show_bug.cgi?id=1099599#c0 found, 
this bug is fixed.

libvirt-0.10.2-29.el6_5.7.x86_64
qemu-kvm-rhev-0.12.1.2-2.415.el6_5.10.x86_64

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2014-0743.html