Hi Jamie,
Nice to see that you are playing with NUMA. :)
On Thu, Nov 19, 2015 at 11:40 AM, Martin Sivak <msivak(a)redhat.com> wrote:
Hi Jamie,
you might be hitting a but we have
https://bugzilla.redhat.com/show_bug.cgi?id=1256716 and we might already
have a fix for that
https://gerrit.ovirt.org/#/c/48721/6
I am adding Roman to see if he has more information.
Regards
Martin
On Wed, Nov 18, 2015 at 11:11 PM, Jamie Lawrence <
jlawrence(a)squaretrade.com> wrote:
> Hello,
>
> Continuing my experimentation, I’m on to making VMs. I defined a toy
> instance, mainly to work through connecting to our DHCP/PXE setup, but it
> won’t start due to the error in the subject line.
>
> Google only tuned up apparently unrelated bugs and architecture docs, and
> it appears searching for ‘NUMA’ in the admin guide turns up nothing. I
> found a GUI config screen (Hosts -> Numa Support), but it wants me to drag
> nonexistent things around for pinning, and I can’t tell if that is broken
> or irrelevant. Or both.
>
> Anyone know what this is about?
>
> Thanks,
>
> -j
>
> Log:
>
> 2015-11-18 21:41:17.254+0000: starting up
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
> QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name sfo-vm-test-1 -S -machine
> pc-i440fx-rhel7.2.0,accel=kvm,usb=off -cpu SandyBridge -m 2048 -realtime
> mlock=off -smp 1,maxcpus=16,sockets=16,cores=1,threads=1 -numa
> node,nodeid=0,cpus=0,mem=2048 -uuid 778b05d9-0c97-438c-966d-010312a4e56f
> -smbios type=1,manufacturer=oVirt,product=oVirt
>
Node,version=7-1.1503.el7.centos.2.8,serial=4C4C4544-0054-4810-8036-C7C04F393432,uuid=778b05d9-0c97-438c-966d-010312a4e56f
> -no-user-config -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/sfo-vm-test-1.monitor,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control -rtc
> base=2015-11-18T21:41:16,driftfix=slew -global
> kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on
> -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
> virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -drive
> if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device
> ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
>
file=/rhev/data-center/8eb96c8d-de23-495e-9ddf-8f02935241fb/2df37968-10cb-40a9-a116-59eb6d0bf83e/images/e2fab53b-c716-4265-8a12-bc73f8373a3f/b2520e43-eb61-4882-a9c0-ff1c010a92ca,if=none,id=drive-virtio-disk0,format=raw,serial=e2fab53b-c716-4265-8a12-bc73f8373a3f,cache=none,werror=stop,rerror=stop,aio=threads
> -device
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0
> -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device
>
virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:16:01:51,bus=pci.0,addr=0x3,bootindex=1
> -netdev tap,fd=28,id=hostnet1,vhost=on,vhostfd=29 -device
>
virtio-net-pci,netdev=hostnet1,id=net1,mac=00:1a:4a:16:01:52,bus=pci.0,addr=0x4,bootindex=2
> -chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/778b05d9-0c97-438c-966d-010312a4e56f.com.redhat.rhevm.vdsm,server,nowait
> -device
>
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
> -chardev
>
socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/778b05d9-0c97-438c-966d-010312a4e56f.org.qemu.guest_agent.0,server,nowait
> -device
>
virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
> -device usb-tablet,id=input0 -vnc 10.180.202.13:0,password -device
> cirrus-vga,id=video0,bus=pci.0,addr=0x2 -msg timestamp=on
> 2015-11-18T21:41:17.283493Z qemu-kvm: warning: CPU(s) not present in any
> NUMA nodes: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
> 2015-11-18T21:41:17.283542Z qemu-kvm: warning: All CPU(s) up to maxcpus
> should be described in NUMA config
>
>
Did you create virtual numa nodes for sfo-test-1? Did you pin the CPUs or
the virtual numa nodes to a specific host?
Could you share your /var/log/vdsm/vdsm.log on local_host, that I can see
what the actual configuration of the VM looks like?
>
>
>
>
Am I right that sfo-test-1 is not pinned to local_host? If it is not pinned
then you are hitting a bug which is fixed in
https://gerrit.ovirt.org/#/c/48721/6.
You should not see the vm in this window at all when it is not pinned to
this host.
_______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
>
Thanks,
Roman