Description of problem: 1. In virt-who man config file. #man virt-who 4. RHEV-M ^^^^^^^ 4 # virt-who --rhevm --rhevm-owner=RHEVM_OWNER --rhevm-env=RHEVM_ENV --rhevm-server=RHEVM_SERVER --rhevm-username=RHEVM_USERNAME --rhevm-password=RHEVM_PASSWORD Use RHEV-M as virtualization backend and specify option required to connect to RHEV-M server. 4. Hyper-V ^^^^^^^^ 4 # virt-who --hyperv --hyperv-owner=HYPERV_OWNER --hyperv-env=HYPERV_ENV --hyperv-server=HYPERV_SERVER --hyperv-user- name=HYPERV_USERNAME --hyperv-password=HYPERV_PASSWORD Use Hyper-V as virtualization backend and specify option required to connect to Hyper-V server. 2. About RHEV-M backend, "virt-who --help" --rhevm-server=SERVER URL of the RHEV-M server to connect to ^^^^^^^^^^^^^^There are two URL can connect to RHEVM manager, http://$IP:port1, https://$IP:port2(security) Actually, virt-who support secure URL should be $ip:port2. Pls provide suitable notice to the customer. --rhevm-username=USERNAME Username for connecting to RHEV-M ^^^^^^^^^^^^^^Actually, the USERNAME should be $username@domain of RHEV-M manager, pls add suitable notice. Version-Release number of selected component (if applicable): virt-who-0.8-2 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: As the description Expected results: 1. 4. Hyper-V ^^^^^^^^ 5. Hyper-V 2. Give suitable descriptions of --rhevm-server=SERVER and --rhevm-username=USERNAME Additional info:
This bug has been fixed in virt-who-0.8-4.el6.
Verified the bug, the result is PASS. version: virt-who-0.8-4.el6.noarch.rpm Moving the status to VERIFIED
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. http://rhn.redhat.com/errata/RHBA-2013-0374.html