Hide Forgot
This bug has been copied from bug #1286492 and has been proposed to be backported to 7.2 z-stream (EUS).
Fix included in qemu-kvm-rhev-2.3.0-31.el7_2.9
I cannot reproduce this problem with lastest 7.2.z qemu-kvm-rhev + libvirt steps: 1. # rpm -q libvirt libvirt-1.2.17-13.el7_2.4.x86_64 # rpm -q qemu-kvm-rhev qemu-kvm-rhev-2.3.0-31.el7_2.10.x86_64 # numactl --har available: 2 nodes (0-1) node 0 cpus: 0 1 2 3 4 5 6 7 16 17 18 19 20 21 22 23 node 0 size: 16362 MB node 0 free: 4320 MB node 1 cpus: 8 9 10 11 12 13 14 15 24 25 26 27 28 29 30 31 node 1 size: 16384 MB node 1 free: 3084 MB node distances: node 0 1 0: 10 11 1: 11 10 2. # cat /sys/devices/system/node/node1/hugepages/hugepages-2048kB/free_hugepages 3995 # cat /sys/devices/system/node/node0/hugepages/hugepages-2048kB/free_hugepages 4000 3. # cat run-slirp.sh #!/bin/sh -x /usr/libexec/qemu-kvm -enable-kvm \ -net none \ -net socket,vlan=0,udp=localhost:4444,localaddr=localhost:5555 \ -net user,vlan=0 # ./vhost-user-bridge -l localhost:4444 -r localhost:5555 -u /tmp/vubr.sock & # chown qemu:qemu /tmp/vubr.sock 4. # virsh dumpxml rhel7.0-rhel <memoryBacking> <hugepages> <page size='2048' unit='KiB'/> </hugepages> </memoryBacking> ... <cpu> <numa> <cell id='0' cpus='0-1,4-6,10-12' memory='1048576' unit='KiB' memAccess='shared'/> <cell id='1' cpus='2-3' memory='1048576' unit='KiB' memAccess='shared'/> <cell id='2' cpus='7' memory='1048576' unit='KiB' memAccess='shared'/> <cell id='3' cpus='8-9' memory='1048576' unit='KiB' memAccess='shared'/> <cell id='4' cpus='13-31' memory='1048576' unit='KiB' memAccess='shared'/> </numa> </cpu> ... <interface type='vhostuser'> <mac address='54:52:00:ee:2c:01'/> <source type='unix' path='/tmp/vubr.sock' mode='client'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </interface> 5. # virsh start rhel7.0-rhel Domain rhel7.0-rhel started 6. LOGIN guest: # dhclient -d and that interface can get ip in guest.
According to comment5, comment8 and comment9, set this issue as verified.
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. https://access.redhat.com/errata/RHBA-2016:0587