Bug 810078

Summary:	Nice to add an warning message about "virsh schedinfo <domain> --cap 65535" when use virsh connect to KVM hypervisor.
Product:	[Community] Virtualization Tools	Reporter:	lei wang <leiwan>
Component:	libvirt	Assignee:	Martin Kletzander <mkletzan>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	acathrow, dallan, dyasny, dyuan, gsun, mzhan, rwu, whuang
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-30 08:17:21 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 lei wang 2012-04-05 05:19:37 UTC

Description of problem:
If cap option isn't supported on KVM host, it's nice to add an warning message about "schedinfo <domain> --cap 65535" when use virsh connect to KVM hypervisor.

Version-Release number of selected component (if applicable):
kernel-2.6.32-251.el6
libvirt-0.9.10-6.el6
netcf-0.1.9-2.el6
qemu-kvm-0.12.1.2-2.251.el6

How reproducible:
always

Steps to Reproduce:
Connect KVM host with virsh.
1.#virsh schedinfo rhel6w
Scheduler      : posix
cpu_shares     : 0
vcpu_period    : 0
vcpu_quota     : 0

2.#virsh schedinfo rhel6w --cap 65536
Scheduler      : posix
cpu_shares     : 0
vcpu_period    : 0
vcpu_quota     : 0

==> Nice to add an warning message to prompt user that is not supported.

Actual results:
Nothing to prompt user what happened or which option is changed.

Expected results:
Add an warning message to prompt user what happened.

Comment 5 Martin Kletzander 2013-04-03 06:52:38 UTC

Moving to POST:

commit e7cd2844ca2b0d716a520667eff286713963e2ec
Author: Martin Kletzander <mkletzan>
Date:   Fri Mar 15 14:42:42 2013 +0100

    Allow multiple parameters for schedinfo