Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1190580

Summary: Failed to run vm with NUMA under RHEL7.1
Product: Red Hat Enterprise Virtualization Manager Reporter: Artyom <alukiano>
Component: ovirt-engineAssignee: Roy Golan <rgolan>
Status: CLOSED CURRENTRELEASE QA Contact: Artyom <alukiano>
Severity: urgent Docs Contact:
Priority: low    
Version: 3.5.0CC: alukiano, dfediuck, ecohen, eedri, gklein, istein, lpeer, lsurette, mavital, michal.skrivanek, rbalakri, rgolan, Rhev-m-bugs, sherold, yeylon
Target Milestone: ovirt-3.5.7Keywords: Triaged
Target Release: 3.5.7   
Hardware: x86_64   
OS: Linux   
Whiteboard: sla
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-26 08:25:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1191567, 1191617    
Bug Blocks:    
Attachments:
Description Flags
engine and vdsm logs
none
qemu log none

Description Artyom 2015-02-09 08:23:44 UTC
Created attachment 989565 [details]
engine and vdsm logs

Description of problem:
Failed to run vm with NUMA under RHEL7.1

Version-Release number of selected component (if applicable):
vdsm-4.16.8.1-6.el7ev.x86_64
rhevm-3.5.0-0.31.el6ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create vm and pinned it to host with NUMA architecture
2. Create numa nodes on vm
3. Run vm

Actual results:
Vm failed to run with error under vdsm log:
Traceback (most recent call last):
  File "/usr/share/vdsm/virt/vm.py", line 2264, in _startUnderlyingVm
    self._run()
  File "/usr/share/vdsm/virt/vm.py", line 3323, in _run
    self._connection.createXML(domxml, flags),
  File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 111, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3424, in createXML
    if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
libvirtError: internal error: early end of file from monitor: possible problem:
2015-02-09T08:17:58.028331Z qemu-kvm: -numa memdev is not supported by machine rhel6.5.0


Expected results:
Vm success to run

Additional info:

Comment 1 Artyom 2015-02-09 08:32:38 UTC
Additional information about versions:
3.10.0-227.el7.x86_64
Red Hat Enterprise Linux Server release 7.1 (Maipo)
libvirt-1.2.8-16.el7.x86_64

Comment 2 Michal Skrivanek 2015-02-09 13:01:49 UTC
how is this relevant to 3.5 GA on an unsupported RHEL release of 7.1?
Results on libvirt&qemu from the latest 7.0.z?

Comment 3 Artyom 2015-02-09 13:33:38 UTC
Gil ask from me to check feature on RHEL 7.1, I checked it and open bug for version where I checked it.
About reasons you can ask Gil

Comment 4 Michal Skrivanek 2015-02-09 13:35:57 UTC
it's cool to test against 7.1 as it's going out soon and we should be ready. But first and foremost you should test on 7.0

please doublecheck the libvirt version as there was a recent 7.0.z libvirt fix

Comment 5 Michal Skrivanek 2015-02-09 13:39:30 UTC
can you please attach the corresponding qemu.log?

Comment 6 Artyom 2015-02-09 16:02:07 UTC
Created attachment 989764 [details]
qemu log

I wrote libvirt version above, so you can say me if fix already in.

Comment 7 Michal Skrivanek 2015-02-10 09:12:37 UTC
it may be a regression in libvirt behavior, memdev devices are not supported in rhel_6.5.0 machine type

Comment 8 Doron Fediuck 2015-02-10 21:30:51 UTC
1. Removing blocker flag since there's no regression here in functionality. NUMA pinning (strict mode) is not a common use case in RHEL 7.x (unlike 6.x where we have numad).

2. Functionality wise, interleaved mode should be used if pinning (strict) does not work, and no need for special settings since autonuma is being used.

3. Agree with Michal 7.0.z should be verified first. Please use 1.1.1-29+ as you did with cpu qos.

4. Looking into vdsm logs show we're using rhel6.5.0:

Thread-150::DEBUG::2015-02-09 10:10:36,931::__init__::469::jsonrpc.JsonRpcServer::(_serveRequest) Calling 'VM.create' in bridge with {u'vmParams': {u'acpiEnable': u'true', u'emulatedMachine': u'rhel6.5.0', 

and we should check if we should change it or indeed a libvirt regression
which will require a libvirt fix.

Comment 9 Eyal Edri 2015-02-11 12:55:26 UTC
removing 3.5.0 flag to allow to move to async release.
still needs 3.5.z flag.

Comment 10 Doron Fediuck 2015-10-19 10:45:07 UTC
Can you please check if still relevant in RHEV 3.5.5?

Comment 11 Artyom 2015-10-25 11:39:17 UTC
Checked on rhevm-3.5.5-0.1.el6ev.noarch.
Vm with numa succeed to run, also I see difference in qemu command:
-numa node,nodeid=0,cpus=0-1,mem=1024
instead of
-numa node,nodeid=0,cpus=0-1,memdev=ram-node0
So I believe we can close this bug.

Comment 12 Artyom 2015-10-25 11:42:34 UTC
Host version:
Red Hat Enterprise Linux Server release 7.1 (Maipo) 3.10.0-229.20.1.el7.x86_64
vdsm-4.16.27-1.el7ev.x86_64
libvirt-1.2.8-16.el7_1.5.x86_64

Comment 13 Doron Fediuck 2015-10-26 08:25:23 UTC
Closing based on comment 11.