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.
Bug 1293042 - [virtio-win][vioser] Extra '-' (dash) in serial driver name
Summary: [virtio-win][vioser] Extra '-' (dash) in serial driver name
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Ladi Prosek
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-19 15:26 UTC by Ladi Prosek
Modified: 2016-11-04 08:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
NO_DOCS
Clone Of:
Environment:
Last Closed: 2016-11-04 08:49:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2609 0 normal SHIPPED_LIVE virtio-win bug fix and enhancement update 2016-11-03 15:27:12 UTC

Description Ladi Prosek 2015-12-19 15:26:48 UTC
Description of problem:
The name of the serial driver is not consistent with the rest of virtio-win.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install drivers
2. Open Device Manager, look at device names

Actual results:
VirtIO-Serial Driver

Expected results:
VirtIO Serial Driver

Additional info:

Comment 3 Yu Wang 2016-03-23 08:02:42 UTC
Reproduced this issue on virtio-win-prewhql-112 version
Verified this issue on virtio-win-prewhql-115 version
  
Steps same as comment#0

Actual Results:

on virtio-win-prewhql-112 (un-fixed version), the issue can be reproduced as comment#0
on virtio-win-prewhql-115 (fix version), Open Device Manager,device names is "VirtIO Serial Driver"
  
Base on above, this issue has been fixed already.

Thanks
wyu

Comment 4 Mike McCune 2016-03-28 22:57:02 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 5 Ladi Prosek 2016-05-23 08:58:30 UTC
Yu Wang, based on comment #3 should this BZ have VERIFIED status? Thanks!

Comment 6 Yu Wang 2016-05-23 09:37:45 UTC
(In reply to Ladi Prosek from comment #5)
> Yu Wang, based on comment #3 should this BZ have VERIFIED status? Thanks!

Verify this bug according comment#3

Thanks
wyu

Comment 7 Yu Wang 2016-05-23 09:39:33 UTC
(In reply to Ladi Prosek from comment #5)
> Yu Wang, based on comment #3 should this BZ have VERIFIED status? Thanks!

Hi,

I have verified this bug, but there is no "devel_ack" for this bug.

Thanks
wyu

Comment 10 errata-xmlrpc 2016-11-04 08:49:36 UTC
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/RHBA-2016-2609.html


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