Bug 1292678 – Qemu should report error when cmdline set threads=2 in amd host

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1292678 - Qemu should report error when cmdline set threads=2 in amd host

Summary:	Qemu should report error when cmdline set threads=2 in amd host

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	qemu-kvm (Show other bugs)
Sub Component:
Version:	6.8
Hardware:	x86_64 Linux

Priority	high Severity low
Target Milestone:	rc
Target Release:	---
Assigned To:	Wei Huang
QA Contact:	Virtualization Bugs
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1359965
	Show dependency tree / graph

Reported:	2015-12-17 22:09 EST by Yumei Huang
Modified:	2017-03-21 05:35 EDT (History)
CC List:	19 users (show)

See Also:
Fixed In Version:	qemu-kvm-0.12.1.2-2.495.el6
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-03-21 05:35:46 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:0621	normal	SHIPPED_LIVE	Moderate: qemu-kvm security and bug fix update	2017-03-21 08:28:31 EDT

Groups: None (edit)

Description Yumei Huang 2015-12-17 22:09:17 EST

Description of problem:
In amd host, when qemu cmdline set threads=2, qemu should report " AMD CPU doesn't support hyperthreading", just like rhel7.2. 

Version-Release number of selected component (if applicable):
kernel: 2.6.32-593.el6.x86_64
qemu: qemu-kvm-0.12.1.2-2.481.el6

How reproducible:
always

Steps to Reproduce:
1.  start a qemu process with threads=2
  /usr/libexec/qemu-kvm -name win10 -m 6G -smp 2,threads=2,cores=1,sockets=1 -numa node -numa node  -monitor stdio

2. 
3.

Actual results:
Qemu report nothing.


Expected results:
Qemu should report error, just like rhel7.2:
qemu-kvm: AMD CPU doesn't support hyperthreading. Please configure -smp options properly.

Additional info:

Comment 2 Wei Huang 2015-12-21 11:04:49 EST

See https://bugzilla.redhat.com/show_bug.cgi?id=1135772.

I will get a patch for 6.8. Please assign it to me.

-Wei

Comment 3 Jeff Nelson 2016-01-18 16:51:47 EST

Fix included in qemu-kvm-0.12.1.2-2.484.el6

Comment 5 Guo, Zhiyi 2016-01-20 00:31:39 EST

Test on qemu-kvm version:qemu-kvm-0.12.1.2-2.482.el6.x86_64
No warning output after lunch qemu-kvm:
# /usr/libexec/qemu-kvm -name win10 -m 6G -smp 2,threads=2,cores=1,sockets=1
VNC server running on `::1:5900'
Verified on qemu-kvm version:qemu-img-0.12.1.2-2.484.el6.x86_64:
Warning output after lunch qemu-kvm:
# /usr/libexec/qemu-kvm -name win10 -m 6G -smp 2,threads=2,cores=1,sockets=1
qemu-kvm: AMD CPU doesn't support hyperthreading. Please configure -smp options properly.

Comment 14 Yash Mankad 2016-10-27 16:32:41 EDT

Fix included in qemu-kvm-0.12.1.2-2.495.el6

Comment 16 Yiqian Wei 2016-10-28 05:19:42 EDT

Reproduce:
host version:
  kernel-2.6.32-642.el6.x86_64
  qemu-kvm-0.12.1.2-2.494.el6.x86_64
Steps to Reproduce:
1.start a qemu process with threads=2 
# /usr/libexec/qemu-kvm -name win10 -m 6G -smp 2,threads=2,cores=1,sockets=1
VNC server running on `::1:5900'

Actual results:
Qemu report nothing.

------------------------------------

Verify this bug on "qemu-kvm-0.12.1.2-2.495.el6.x86_64" as same steps above.

Test results:Qemu report error
# /usr/libexec/qemu-kvm -name win10 -m 6G -smp 2,threads=2,cores=1,sockets=1
qemu-kvm: AMD CPU doesn't support hyperthreading. Please configure -smp options properly.

According to result above,this bug has been fixed.

Comment 19 errata-xmlrpc 2017-03-21 05:35:46 EDT

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://rhn.redhat.com/errata/RHSA-2017-0621.html

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