Hide Forgot
Description of problem: kernel panic when boot guest with -numa ...cpus=0... -numa ...cpus=1-3 Version-Release number of selected component (if applicable): qemu-kvm-0.12.1.2-2.209.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. cmd: -smp 4,cores=2,threads=1,sockets=2 \ -numa node,mem=1024,cpus=0,nodeid=0 \ -numa node,mem=1024,cpus=1-3,nodeid=1 \ -m 2048 2. 3. Actual results: Expected results: Additional info: 1. boot guest successfully with -numa node,mem=1024,cpus=0-1,nodeid=0 \ -numa node,mem=1024,cpus=2-3,nodeid=1 \ 2. full cmd /usr/libexec/qemu-kvm -monitor stdio -chardev socket,id=serial_id_shuang,path=/tmp/serial-shuang,server,nowait -device isa-serial,chardev=serial_id_shuang -drive file='/home/Auto/autotest-devel/client/tests/kvm/images/RHEL-Server-6.1-64-virtio.qcow2',index=0,if=none,id=drive-virtio-disk1,media=disk,cache=none,format=qcow2,aio=native -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk1,id=virtio-disk1 -device virtio-net-pci,netdev=idRn6Pb1,mac=9a:ce:d8:b5:ea:15,id=ndev00idRn6Pb1,bus=pci.0,addr=0x3 -netdev tap,id=idRn6Pb1,vhost=on,script=/home/Auto/autotest-devel/client/tests/kvm/scripts/qemu-ifup-switch -cpu cpu64-rhel6,+sse2,+x2apic -vnc :0 -rtc base=utc,clock=host,driftfix=slew -boot order=cdn,once=c,menu=off -no-kvm-pit-reinjection -M rhel6.2.0 -usb -device usb-tablet -enable-kvm -smp 4,cores=2,threads=1,sockets=2 -numa node,mem=1024,cpus=0,nodeid=0 -numa node,mem=1024,cpus=1-3,nodeid=1 -m 2048 3. host cpuinfo [root@amd-2427-32-1 staf-kvm-devel]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 12 On-line CPU(s) list: 0-11 Thread(s) per core: 1 Core(s) per socket: 6 CPU socket(s): 2 NUMA node(s): 2 Vendor ID: AuthenticAMD CPU family: 16 Model: 8 Stepping: 0 CPU MHz: 800.000 BogoMIPS: 4399.63 Virtualization: AMD-V L1d cache: 64K L1i cache: 64K L2 cache: 512K L3 cache: 6144K NUMA node0 CPU(s): 0,2,4,6,8,10 NUMA node1 CPU(s): 1,3,5,7,9,11
Created attachment 534720 [details] kernel panic
can boot up with -smp 4,cores=1,threads=1,sockets=4 -numa node,mem=1024,cpus=0,nodeid=0 -numa node,mem=1024,cpus=1-3,nodeid=1 it should be my cmd issue, the cores with same socket can not be separated to two nodes.
(In reply to comment #2) > can boot up with > -smp 4,cores=1,threads=1,sockets=4 -numa node,mem=1024,cpus=0,nodeid=0 -numa > node,mem=1024,cpus=1-3,nodeid=1 > > it should be my cmd issue, the cores with same socket can not be separated to > two nodes. You should only be allowed to mimic a topology like the physical world. In theory you're right but it is too low in our priority list.