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:
"virsh start" succeeds even if a nonexistent serial type (e.g. 'xyz') is
specified in an xml file. If invalid serial types are specified, virsh uses the "null" serial type. Instead it should report and error message to that effect and fail to start the guest.
Version-Release number of selected component:
Red Hat Enterprise Linux Version Number: 6
Release Number: snapshot13
Architecture: x86_64
Kernel Version: kernel-2.6.32-70.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. Add an invalid serial type and port number to the configuration file.
Eg,
<serial type='xyz'>
<target port='0'/>
</serial>
2. Start the guest
# virsh start rhel6
Domain rhel6 started
3.
# virsh dumpxml rhel6 | grep serial
<serial type='null'> -----------------------------------It's this one
<alias name='serial0'/>
</serial>
<serial type='dev'>
<alias name='serial1'/>
</serial>
<alias name='serial0'/>
The invalid serial type specified has been converted to "null". Instead it should fail to start the guest and report the error.
Actual results:
Guest successfully starts with virsh even while specifying an invalid serial type.
Expected results:
Guest should fail to start using virsh if an invalid serial type is specified.
Additional info:
Verified. Pass.
Test environment:
libvirt-0.8.7-3.el6
qemu-kvm-0.12.1.2-2.128.el6
kernel-2.6.32-94.el6
Steps:
1. Edit a domain "serial" part in xml file with the invaild serial types.
The error message can be reported and domain still keeps the original serial type.
# virsh edit cc
error: XML description for unknown type presented to host for character device: # is not well formed or invalid
# virsh edit cc
error: XML description for unknown type presented to host for character device: abcdfafa is not well formed or invalid
# virsh edit cc
error: XML description for unknown type presented to host for character device: .... is not well formed or invalid
# virsh edit cc
error: XML description for unknown type presented to host for character device: pty1 is not well formed or invalid
2. Edit a domain "serial" part in xml file with the vaild serial types.
The serial type can be changed to the specified type.
# virsh edit cc
Domain cc XML configuration edited.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0596.html
Description of problem: "virsh start" succeeds even if a nonexistent serial type (e.g. 'xyz') is specified in an xml file. If invalid serial types are specified, virsh uses the "null" serial type. Instead it should report and error message to that effect and fail to start the guest. Version-Release number of selected component: Red Hat Enterprise Linux Version Number: 6 Release Number: snapshot13 Architecture: x86_64 Kernel Version: kernel-2.6.32-70.el6.x86_64 How reproducible: always Steps to Reproduce: 1. Add an invalid serial type and port number to the configuration file. Eg, <serial type='xyz'> <target port='0'/> </serial> 2. Start the guest # virsh start rhel6 Domain rhel6 started 3. # virsh dumpxml rhel6 | grep serial <serial type='null'> -----------------------------------It's this one <alias name='serial0'/> </serial> <serial type='dev'> <alias name='serial1'/> </serial> <alias name='serial0'/> The invalid serial type specified has been converted to "null". Instead it should fail to start the guest and report the error. Actual results: Guest successfully starts with virsh even while specifying an invalid serial type. Expected results: Guest should fail to start using virsh if an invalid serial type is specified. Additional info: