RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1539541 - [kvm][Crystal Ridge]nvml running failed in guest
Summary: [kvm][Crystal Ridge]nvml running failed in guest
Keywords:
Status: CLOSED DUPLICATE of bug 1365721
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Stefan Hajnoczi
QA Contact: Yumei Huang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-29 07:23 UTC by Robert Hoo
Modified: 2018-02-01 08:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-01 08:54:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Robert Hoo 2018-01-29 07:23:34 UTC 
Environment:
KVM/QEMU:qemu-kvm-rhev-2.10.0-17.el7
Base OS: RHEL7.5 BETA
Guest OS: RHEL7.5 BETA
Platform: SKL-2S



Steps to Reproduce:
1.Setup the AEP with 2-1-1 configuration on SKL-2S
2.Install RHEL7.5 BETA on SKL host
3.Replacing the KVM package with the version(qemu-kvm-rhev-2.10.0-17.el7.x86_64)
4.Check the pmem dev via command
[root@cr-rhel ~]# ll /dev/pmem*
brw-rw---- 1 root disk 259, 0 Jan 28 23:54 /dev/pmem4
brw-rw---- 1 root disk 259, 1 Jan 26 02:26 /dev/pmem5
5.Create the guest with "/dev/pmem4" as:
qemu-system-x86_64 -M q35,accel=kvm,nvdimm -smp 8 -cpu host -m 16G,slots=32,maxmem=96G -object memory-backend-file,id=mem1,share,mem-path=/dev/pmem4,size=16G -device nvdimm,memdev=mem1,id=nv1,label-size=128k -device virtio-net-pci,netdev=nic0,mac=52:52:00:66:92:66 -netdev bridge,id=nic0,br=virbr0,helper=/usr/libexec/qemu-bridge-helper -drive file=/opt/rhel7u5.qcow2,if=virtio,id=virtio-disk0,format=qcow2 -daemonize
6.Check the nvdimm device in guest and mount it to /mnt/:
[root@localhost ~]# ll /dev/pmem0
brw-rw----. 1 root disk 259, 0 Jan 29 11:03 /dev/pmem0
[root@localhost mnt]# mkfs.xfs /dev/pmem0
[root@localhost mnt]# mount /dev/pmem0 /mnt/
7.Download the nvml (git clone https://github.com/pmem/nvml)
8.Make nvml test as following:
cd /root/nvml; make; make install

Actual results:
The nvml tools make/make install successful

Expected results:
[root@localhost nvml]# make
src/common.inc:262: *** libndctl(version >= 58.2.37) is missing -- see README.  Stop.

Additional info:
[root@localhost nvml]# rpm -qa | grep ndctl-devel
ndctl-devel-58.2-3.el7.x86_64
[root@localhost nvml]# ndctl --version
58.2
Comment 2 Yumei Huang 2018-01-30 03:24:41 UTC 
How does it have anything to do with qemu-kvm-rhev ? IMHO, it is more about nvml.
Please correct me if I'm wrong. Thanks!
Comment 3 Robert Hoo 2018-02-01 08:14:35 UTC 
(In reply to Yumei Huang from comment #2)
> How does it have anything to do with qemu-kvm-rhev ? IMHO, it is more about
> nvml.
> Please correct me if I'm wrong. Thanks!

Yes you're right.
This is non business with qemu, just about the test tool itself compilation erros/environment requirements. 
We've solved it but some further test still fails, using nvml test tool. We're checking that now, will feed you back on progress. Thanks.
Comment 4 Yumei Huang 2018-02-01 08:33:27 UTC 
(In reply to Robert Hoo from comment #3)
> We've solved it but some further test still fails, using nvml test tool.
> We're checking that now, will feed you back on progress. Thanks.

We have bug1365721 to track the nvml tests. Maybe we should update on that bz ?
Comment 5 Robert Hoo 2018-02-01 08:54:05 UTC 
Yes, the issue we met as the same as bug1365721

Mark bug1539541 as duplicated and track the bug1365721.

--------
.............
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
obj_ctl_prefault/TEST0: PASS                    [00.162 s]
obj_ctl_prefault/TEST0: SETUP (check/pmem/static-debug)
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
obj_ctl_prefault/TEST0: PASS                    [00.465 s]
obj_ctl_prefault/TEST0: SETUP (check/pmem/static-nondebug)
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
obj_ctl_prefault/TEST0: PASS                    [00.154 s]
obj_ctl_prefault/TEST0: SETUP (check/non-pmem/debug)
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
obj_ctl_prefault/TEST0: START: obj_ctl_prefault
RUNTESTS: stopping: obj_ctl_prefault/TEST0 failed, TEST=check FS=non-pmem BUILD=debug---

*** This bug has been marked as a duplicate of bug 1365721 ***
Note You need to log in before you can comment on or make changes to this bug.