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.
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:
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
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: