Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Verified this issue on qemu-kvm-rhev-2.1.2-19.el7
Steps same as comment#0
Actual Results:
1.memory size has value,but some are still unknown
e.g.
[root@dhcp-66-106-173 ~]# dmidecode -t 17
# dmidecode 2.12
SMBIOS 2.8 present.
Handle 0x1100, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: 16384 MB
Form Factor: DIMM
Set: None
Locator: DIMM 0
Bank Locator: Not Specified
Type: RAM
Type Detail: Other
Speed: Unknown
Manufacturer: Red Hat
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Rank: Unknown
Configured Clock Speed: Unknown
Minimum Voltage: Unknown
Maximum Voltage: Unknown
Configured Voltage: Unknown
2.the expect result is like the following which set guest's machine type with "-M pc-i440fx-rhel7.0.0"
e.g.
[root@dhcp-66-106-173 ~]# dmidecode -t 17
# dmidecode 2.12
SMBIOS 2.4 present.
Handle 0x1100, DMI type 17, 21 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: 0x0000
Total Width: 64 bits
Data Width: 64 bits
Size: 16384 MB
Form Factor: DIMM
Set: None
Locator: DIMM 0
Bank Locator: Not Specified
Type: RAM
Type Detail: None
Based on above ,this issue has not been fixed.
thanks,
xiagao
(In reply to xiagao from comment #4)
> Actual Results:
> 1.memory size has value,but some are still unknown
That means the bug is fixed.
> 2.the expect result is like the following which set guest's machine type
> with "-M pc-i440fx-rhel7.0.0"
The SMBIOS data on rhel7.1.0 doesn't need to match exactly what was on rhel7.0.0. Can you explain what exactly is incorrect?
(In reply to Eduardo Habkost from comment #5)
> The SMBIOS data on rhel7.1.0 doesn't need to match exactly what was on
> rhel7.0.0. Can you explain what exactly is incorrect?
If the SMBIOS data on rhel7.1.0 doesn't need to match exactly what was on rhel7.0.0, I think it's fine for me.
thanks，
xiagao
Description of problem: bootup rhel6.6.i386 guest,can't check the memory size with cmd 'dmidecode -t 17' in guest Version-Release number of selected component (if applicable): qemu-kvm-rhev-2.1.2-17.el7.x86_64 seabios-1.7.5-6.el7.x86_64 kernel-3.10.0-219.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.In RHEL7.1 host bootup rhel6.6.386 guest. 2.Chek guest memory size with cmd dmidecode. # dmidecode -t 17 3. Actual results: Handle 0x1100, DMI type 17, 40 bytes Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: DIMM Set: None Locator: DIMM 0 Bank Locator: Not Specified Type: RAM Type Detail: Other Speed: Unknown Manufacturer: Red Hat Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Rank: Unknown Configured Clock Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Expected results: Additional info: 1.CLI /bin/qemu-kvm \ -S \ -name 'virt-tests-vm1' \ -sandbox off \ -M pc \ -nodefaults \ -vga cirrus \ -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20150106-155015-N5nD7PK8,server,nowait \ -mon chardev=qmp_id_qmpmonitor1,mode=control \ -chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0-20150106-155015-N5nD7PK8,server,nowait \ -device isa-serial,chardev=serial_id_serial0 \ -chardev socket,id=seabioslog_id_20150106-155015-N5nD7PK8,path=/tmp/seabios-20150106-155015-N5nD7PK8,server,nowait \ -device isa-debugcon,chardev=seabioslog_id_20150106-155015-N5nD7PK8,iobase=0x402 \ -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=03 \ -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,file=/mnt/nfs_images/RHEL-Server-6.6-32-virtio.qcow2 \ -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,serial=1-n8\+\\\<,bus=pci.0,addr=04 \ -device e1000,mac=9a:4d:4e:4f:50:51,id=idX3dzMc,netdev=idEStUAr,bus=pci.0,addr=05 \ -netdev tap,id=idEStUAr,fd=22 \ -m 16384 \ -smp 16,maxcpus=16,cores=4,threads=2,sockets=2 \ -cpu 'Westmere',+kvm_pv_unhalt \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -vnc :0 \ -rtc base=utc,clock=host,driftfix=slew \ -boot order=cdn,once=c,menu=off,strict=off \ -enable-kvm 2.host cpu info processor : 15 vendor_id : GenuineIntel cpu family : 6 model : 44 model name : Westmere E56xx/L56xx/X56xx (Nehalem-C) stepping : 1 microcode : 1 cpu MHz : 2666.760 cache size : 4096 KB physical id : 1 siblings : 8 core id : 3 cpu cores : 4 3.other test 1)change machine type with '-M pc-i440fx-rhel7.0.0',the result passed. 2)downgrade qemu-kvm-rhev version to 'qemu-kvm-rhev-2.1.2-16.el7.x86_64',it still failed. 3)downgrade seabios version to 'seabios-1.7.5-6.el7.x86_64',it still failed.