Enable nested KVM for srv16-msk

[Dmitry Kalashnik]

Steps:
cat /sys/module/kvm_intel/parameters/nested

Expected result:
Y

Actual result:
N

----- History -----

Scenario:
            1. Revert snapshot "basic_env_for_numa_cpu_pinning"
            2. Pin maximum CPU for the nova on the first compute
            3. Pin minimun CPU for the nova on the second compute
            4. Verify setting was successfully applied
            5. Deploy cluster
            6. Check new filters are enabled in nova.conf at controller
            7. Check nova.conf contains pinned CPU at compute
            8. Run OSTF <- Failed here
            9. Boot VM with pinned CPU on the first compute
            10. Boot VM with pinned CPU on the second compute

Expected result:
All tests are successful

Actual result:
 Launch instance, create snapshot, launch instance from snapshot failure
 Launch instance with file injection failure
 Launch instance failure
 Check network connectivity from instance via floating IP failure

Libvirt log contains error:
2016-06-23 12:10:11.732+0000: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name instance-0000000f -S -machine pc-i440fx-vivid,accel=kvm,usb=off -m 64 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 48ce32c1-6c2a-4267-8415-4e8df188befe -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=13.0.0,serial=259ff0f0-4ccd-41cf-8771-db75da34cba3,uuid=48ce32c1-6c2a-4267-8415-4e8df188befe,family=Virtual Machine -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0000000f.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,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 -drive file=/var/lib/nova/instances/48ce32c1-6c2a-4267-8415-4e8df188befe/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=directsync -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/nova/instances/48ce32c1-6c2a-4267-8415-4e8df188befe/disk.config,if=none,id=drive-virtio-disk25,format=raw,cache=directsync -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk25,id=virtio-disk25 -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:cc:24:e5,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/var/lib/nova/instances/48ce32c1-6c2a-4267-8415-4e8df188befe/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on
Domain id=6 is tainted: high-privileges
char device redirected to /dev/pts/5 (label charserial1)
kvm version too old
failed to initialize KVM: Inappropriate ioctl for device
2016-06-23 12:10:11.936+0000: shutting down

Versions: http://paste.openstack.org/show/521670/
Failed 2 cases
Blocked 2 cases

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[Timofey Durakov (tdurakov)]

from libvirt logs:
<11>Jun 23 14:36:44 node-4 libvirtd: 15888: error : qemuMonitorOpenUnix:309 : failed to connect to monitor socket: No such process
<11>Jun 23 14:36:44 node-4 libvirtd: 15888: error : qemuProcessWaitForMonitor:2052 : internal error: process exited while connecting to monitor: kvm version too old
failed to initialize KVM: Inappropriate ioctl for device

[Timofey Durakov (tdurakov)]

there was no nested kvm virtualization on env enabled, so kvm initialization fails

[Artur Kaszuba (akaszuba)]

@devops please enable nesting on slaves:
srv14-msk.msk.mirantis.net
srv15-msk.msk.mirantis.net
srv16-msk.msk.mirantis.net
srv17-msk.msk.mirantis.net
srv18-msk.msk.mirantis.net
srv19-msk.msk.mirantis.net
srv20-msk.msk.mirantis.net
srv21-msk.msk.mirantis.net

All slaves are offlined and ready for restarts (if required)

[Aleksandra Fedorova (bookwar)]

For 9.0 we removed slaves from the pool.

Thread https://product-ci.infra.mirantis.net/job/9.0.system_test.ubuntu.numa_cpu_pinning/69/ has finished successfully so I am marking 9.0 part as fix commited

[Andrey Nikitin (heos)]

Nested virtualization was not enabled, because each fresh Jenkins slave should be rebooted before adding it to a Jenkins.

[Andrey Nikitin (heos)]

All the servers were rebooted to enable nested virtualization. Please check and confirm.

[Artur Kaszuba (akaszuba)]

It is ok now