Bug 1687664 - qemu-kvm: warning: cap-hpt-max-page-size lower level (16) in incoming stream than on destination (24) pops up but both source and destination have the same value 16M
Summary: qemu-kvm: warning: cap-hpt-max-page-size lower level (16) in incoming stream ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: qemu-kvm
Version: 8.1
Hardware: ppc64le
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.1
Assignee: David Gibson
QA Contact: Min Deng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-12 05:22 UTC by Min Deng
Modified: 2019-11-06 07:14 UTC (History)
10 users (show)

Fixed In Version: qemu-kvm-4.1.0-1.module+el8.1.0+3966+4a23dca1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-06 07:13:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3723 0 None None None 2019-11-06 07:14:05 UTC

Description Min Deng 2019-03-12 05:22:59 UTC
Description of problem:
(qemu) qemu-kvm: warning: cap-hpt-max-page-size lower level (16) in incoming stream than on destination (24)  pops up but both source and destination has the same value 16M

Version-Release number of selected component (if applicable):
kernel-4.18.0-77.el8.ppc64le
qemu-kvm-3.1.0-18.module+el8+2834+fa8bb6e2.ppc64le
guest kernel (rhel7.6le)
kernel-3.10.0-957.11.1.el7.ppc64le

How reproducible:
5/5

Steps to Reproduce:
1.Configure 1G huge page size on host and assign enough nr huge page for the guest

[root@ibm-p9wr-04 kar]# cat /proc/meminfo|grep Huge
AnonHugePages:         0 kB
ShmemHugePages:        0 kB
HugePages_Total:     448
HugePages_Free:      398
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:    1048576 kB
Hugetlb:        471859200 kB

  
2.Boot up a guest on src

2.1.On SRC,boot up a guest 
 /usr/libexec/qemu-kvm -name avocado-vt-vm1 -machine pseries,max-cpu-compat=power8,cap-hpt-max-page-size=16M -nodefaults -device VGA,bus=pci.0,addr=0x2 -chardev socket,id=serial_id_serial0,path=/tmp/5,server,nowait -device spapr-vty,reg=0x30000000,chardev=serial_id_serial0 -device qemu-xhci,id=usb1,bus=pci.0,addr=0x3 -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 -device scsi-hd,id=image1,drive=drive_scsi11,bus=virtio_scsi_pci0.0,channel=0,scsi-id=0,lun=0,bootindex=0 -blockdev driver=file,cache.direct=on,cache.no-flush=off,filename=rhel76-ppc64le-virtio-scsi.qcow2.bak.all.tools.in,node-name=drive_scsi1 -blockdev driver=qcow2,node-name=drive_scsi11,file=drive_scsi1 -m 20G,slots=256,maxmem=2T -mem-path /dev/hugepages1G -smp 2,maxcpus=2,cores=1,threads=1,sockets=2 -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 -vnc :34 -rtc base=utc,clock=host -enable-kvm -monitor stdio -numa node -qmp tcp:0:4445,server,nowait -object memory-backend-file,id=mem1,size=5G,mem-path=/dev/hugepages1G -device pc-dimm,id=dimm1,memdev=mem1 -device virtio-net-pci,mac=9a:4c:4d:4e:4f:60,id=idtniYmJ,vectors=4,netdev=idG7NvsN,bus=pci.0,addr=0x5 -netdev tap,id=idG7NvsN,vhost=on,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown

2.3.Run libhugetlbfs test by "make check".

2.4.On Des,boot up a guest with

 /usr/libexec/qemu-kvm -name avocado-vt-vm1 -machine pseries,max-cpu-compat=power8,cap-hpt-max-page-size=16M -nodefaults -device VGA,bus=pci.0,addr=0x2 -chardev socket,id=serial_id_serial0,path=/tmp/5,server,nowait -device spapr-vty,reg=0x30000000,chardev=serial_id_serial0 -device qemu-xhci,id=usb1,bus=pci.0,addr=0x3 -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 -device scsi-hd,id=image1,drive=drive_scsi11,bus=virtio_scsi_pci0.0,channel=0,scsi-id=0,lun=0,bootindex=0 -blockdev driver=file,cache.direct=on,cache.no-flush=off,filename=rhel76-ppc64le-virtio-scsi.qcow2.bak.all.tools.in,node-name=drive_scsi1 -blockdev driver=qcow2,node-name=drive_scsi11,file=drive_scsi1 -m 20G,slots=256,maxmem=2T -mem-path /dev/hugepages1G -smp 2,maxcpus=2,cores=1,threads=1,sockets=2 -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 -vnc :31 -rtc base=utc,clock=host -enable-kvm -monitor stdio -numa node -qmp tcp:0:4440,server,nowait -object memory-backend-file,id=mem1,size=5G,mem-path=/dev/hugepages1G -device pc-dimm,id=dimm1,memdev=mem1 -device virtio-net-pci,mac=9a:4c:4d:4e:4f:60,id=idtniYmJ,vectors=4,netdev=idG7NvsN,bus=pci.0,addr=0x5 -netdev tap,id=idG7NvsN,vhost=on,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown -incoming tcp:0:1212


3.migrate -d tcp:0:1212 on src


Actual results:
Migrated successfully but the warning was wrong,it shouldn't be there.Because both src and des guest had the same "cap-hpt-max-page-size=16M" value and there wasn't any differences between guests.

"qemu-kvm: warning: cap-hpt-max-page-size lower level (16) in incoming stream than on destination (24)"

Expected results:
No improper warnings and guest works well.

Additional info:
It is a ppc only bug.Thanks.

Comment 1 David Gibson 2019-05-06 05:37:23 UTC
I think this error could occur if you have the 3.1 qemu at the destination but the 2.12 qemu at the source end.

Min, can you double check that this occurs with the fast train (3.1) qemu at *both* ends.  If it does, that's definitely a bug.

Comment 2 Min Deng 2019-05-06 06:00:38 UTC
(In reply to David Gibson from comment #1)
> I think this error could occur if you have the 3.1 qemu at the destination
> but the 2.12 qemu at the source end.
> 
> Min, can you double check that this occurs with the fast train (3.1) qemu at
> *both* ends.  If it does, that's definitely a bug.

Hello David,
  Actually,the bug was initially reported on local host,it meant it only had qemu3.1 installed at both ends,what's more.I re-tested it on my host again,unfortunately,the problem still could be reproducible.So I'm afraid that it's a bug from somewhere.Could you please help to re-check ? Thanks in advance.

Build information
kernel-4.18.0-82.el8.ppc64le
qemu-kvm-3.1.0-24.module+el8.0.1+3132+0c0fb959.ppc64le

On source side,
   /usr/libexec/qemu-kvm -name avocado-vt-vm1 -machine pseries,max-cpu-compat=power8,cap-hpt-max-page-size=16M -nodefaults -device VGA,bus=pci.0,addr=0x2 -chardev socket,id=serial_id_serial0,path=/tmp/5,server,nowait -device spapr-vty,reg=0x30000000,chardev=serial_id_serial0 -device qemu-xhci,id=usb1,bus=pci.0,addr=0x3 -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 -device scsi-hd,id=image1,drive=drive_scsi11,bus=virtio_scsi_pci0.0,channel=0,scsi-id=0,lun=0,bootindex=0 -blockdev driver=file,cache.direct=on,cache.no-flush=off,filename=rhel801-ppc64le-virtio-scsi.qcow2.compatible,node-name=drive_scsi1 -blockdev driver=qcow2,node-name=drive_scsi11,file=drive_scsi1 -m 20G,slots=256,maxmem=2T -mem-path /mnt/hugepages1G -smp 2,maxcpus=2,cores=1,threads=1,sockets=2 -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 -vnc :35 -rtc base=utc,clock=host -enable-kvm -monitor stdio -numa node -qmp tcp:0:4446,server,nowait -object memory-backend-file,id=mem1,size=5G,mem-path=/mnt/hugepages1G -device pc-dimm,id=dimm1,memdev=mem1 -device virtio-net-pci,mac=9a:4c:4d:4e:4f:60,id=idtniYmJ,vectors=4,netdev=idG7NvsN,bus=pci.0,addr=0x5 -netdev tap,id=idG7NvsN,vhost=on,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown -incoming tcp:0:1212
QEMU 3.1.0 monitor - type 'help' for more information
(qemu) qemu-kvm: warning: cap-hpt-max-page-size lower level (16) in incoming stream than on destination (24)

Comment 3 David Gibson 2019-05-16 05:44:13 UTC
I've reproduced the problem, investigating...

Comment 4 David Gibson 2019-05-16 06:05:26 UTC
Problem also exists in upstream.

Comment 5 David Gibson 2019-05-17 04:15:58 UTC
I've located the problem: the maxpagesize property was accidentally omitted from the migration stream.  I've written a draft fix upstream.

Comment 6 David Gibson 2019-05-22 23:33:10 UTC
Draft fix had a problem, but Greg Kurz has posted a fix for that, now pending upstream.

Comment 7 David Gibson 2019-06-04 04:08:57 UTC
Fix is now merged upstream for qemu-4.1, so we'll get it in fast train for RHEL-AV-8.1.

This is essentially cosmetic, so I don't believe there's any point trying to backport the fix to slow train.

Comment 8 Qunfang Zhang 2019-06-10 02:12:21 UTC
(In reply to David Gibson from comment #7)
> Fix is now merged upstream for qemu-4.1, so we'll get it in fast train for
> RHEL-AV-8.1.
> 
> This is essentially cosmetic, so I don't believe there's any point trying to
> backport the fix to slow train.

Thanks David. Would you add Internal Target Release filed too?

Comment 10 Min Deng 2019-08-20 07:09:11 UTC
Verified the bug on the follow build 
qemu-kvm-4.1.0-1.module+el8.1.0+3966+4a23dca1.ppc64le
The original issue has been fixed,thanks.

Comment 12 errata-xmlrpc 2019-11-06 07:13:50 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3723


Note You need to log in before you can comment on or make changes to this bug.