Bug 1655039

Summary: VMs with OS type Windows are not booting due to NUMA config error
Product: Red Hat Enterprise Virtualization Manager Reporter: Jaroslav Spanko <jspanko>
Component: vdsmAssignee: Steven Rosenberg <srosenbe>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: lsurette, michal.skrivanek, rbarry, srevivo, ycui
Target Milestone: ovirt-4.3.0   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-03 09:50:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine log
none
vdsm log none

Description Jaroslav Spanko 2018-11-30 11:58:47 UTC
Description of problem:
Installed RHV 4.3 alpha to start testing, once i setup VM with OS type Windows the VM does not boot, once i change OS type to Other/Linux VM is booting fine. It's not related to one VM, but all which i setup.

Version-Release number of selected component (if applicable):
rhvm-4.3.0-0.5.alpha1.el7.noarch
vdsm-4.30.3-1.el7ev.x86_64
libvirt-4.5.0-10.el7_6.3.x86_64
qemu-kvm-rhev-2.12.0-18.el7_6.1.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Setup VM with OS type Windows
2. Start VM
3. VM fails to start with NUMA error

Actual results:
VM fails booting with OS Type Windows
libvirtError: internal error: qemu unexpectedly closed the monitor: 2018-11-30T11:27:23.122281Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config, ability to start up with partial NUMA mappings is obsoleted and will be removed in future

Expected results:
VM boots properly with OS Type Windows

Additional info:
Tried on 3 different hosts, only affected is OS type Windows. 
-----------------------
2018-11-30 12:44:19,456+0100 ERROR (vm/82b90871) [virt.vm] (vmId='82b90871-3521-46c7-8812-570a8dd796c3') The vm start process failed (vm:934)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 863, in _startUnderlyingVm
    self._run()
  File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2840, in _run
    dom.createWithFlags(flags)
  File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in wrapper
    return func(inst, *args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1110, in createWithFlags
    if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
libvirtError: internal error: qemu unexpectedly closed the monitor: 2018-11-30T11:44:18.985229Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config, ability to start up with partial NUMA mappings is obsoleted and will be removed in future
2018-11-30T11:44:18.985640Z qemu-kvm: can't apply global Haswell-noTSX-x86_64-cpu.hv-synic=on: Property '.hv-synic' not found
2018-11-30 12:44:19,456+0100 INFO  (vm/82b90871) [virt.vm] (vmId='82b90871-3521-46c7-8812-570a8dd796c3') Changed state to Down: internal error: qemu unexpectedly closed the monitor: 2018-11-30T11:44:18.985229Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config, ability to start up with partial NUMA mappings is obsoleted and will be removed in future
----------------------------
I will attach all logs, also have live system if will be needed.
Thanks !

Comment 1 Jaroslav Spanko 2018-11-30 12:01:11 UTC
Created attachment 1510116 [details]
engine log

Comment 2 Jaroslav Spanko 2018-11-30 12:01:39 UTC
Created attachment 1510118 [details]
vdsm log

Comment 3 Ryan Barry 2018-12-01 14:09:57 UTC
The error is not Nina, but HyperV enlightenments missing. This is a known issue until the next platform batch update, unfortunately.

Comment 4 Michal Skrivanek 2018-12-03 09:50:18 UTC

*** This bug has been marked as a duplicate of bug 1644693 ***