Bug 1180879

Summary: Can't get memory size of rhel6.6 guest with cmd 'dmidecode -t 17'
Product: Red Hat Enterprise Linux 7 Reporter: xiagao
Component: qemu-kvm-rhevAssignee: Eduardo Habkost <ehabkost>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.1CC: coli, hhuang, juzhang, meyang, michen, scui, shuang, virt-maint, xiagao, yaxue
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-13 16:21:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description xiagao 2015-01-11 12:18:48 UTC
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.

Comment 2 Gerd Hoffmann 2015-01-13 09:23:57 UTC
http://patchwork.ozlabs.org/patch/426350/

Comment 3 Eduardo Habkost 2015-01-13 16:21:51 UTC

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

Comment 4 xiagao 2015-01-14 08:38:17 UTC
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

Comment 5 Eduardo Habkost 2015-01-14 14:23:20 UTC
(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?

Comment 6 xiagao 2015-01-15 02:58:50 UTC
(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