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 727896 - ACPI description of serial and parallel ports incorrect with -chardev/-device
Summary: ACPI description of serial and parallel ports incorrect with -chardev/-device
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 707130
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-03 14:54 UTC by RHEL Program Management
Modified: 2013-01-10 00:11 UTC (History)
16 users (show)

Fixed In Version: qemu-kvm-0.12.1.2-2.160.el6_1.7
Doc Type: Bug Fix
Doc Text:
When KVM guests were launched with the "-device isa-serial" option instead of the "-serial" option, serial devices created were not visible by Windows guests. This issue arose because QEMU did not expose these devices in the guests' ACPI tables. With this fix, the guest's ACPI Differentiated System Description Table (DSDT) now properly senses the presence of serial devices and Windows guests can now see them properly.
Clone Of:
Environment:
Last Closed: 2011-08-25 08:02:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1211 0 normal SHIPPED_LIVE qemu-kvm bug fix update 2011-08-25 08:02:31 UTC

Description RHEL Program Management 2011-08-03 14:54:30 UTC 
This bug has been copied from bug #707130 and has been proposed
to be backported to 6.1 z-stream (EUS).
Comment 7 Qunfang Zhang 2011-08-12 01:47:40 UTC 
Reproduced on qemu-kvm-0.12.1.2-2.160.el6_1.6 and verified pass on
qemu-kvm-0.12.1.2-2.160.el6_1.8.
Steps:
1. Boot guest A with
-chardev tty,id=serial0,path=/dev/ttyS0 -device isa-serial,chardev=serial0
Inside guest:
#udevadm info --query path --name /dev/ttyS0
#!! --attribute-walk | grep looking

2. Boot guest B with
-serial /dev/ttyS0
Inside guest:
#udevadm info --query path --name /dev/ttyS0
#!! --attribute-walk | grep looking

Results:
For old qemu-kvm version:
Guest A:
[root@virtlab-66-85-138 ~]# udevadm info --query path --name /dev/ttyS0
/devices/platform/serial8250/tty/ttyS0
[root@virtlab-66-85-138 ~]# !! --attribute-walk | grep looking
udevadm info --query path --name /dev/ttyS0 --attribute-walk | grep looking
  looking at device '/devices/platform/serial8250/tty/ttyS0':
  looking at parent device '/devices/platform/serial8250':
  looking at parent device '/devices/platform':

Guest B:
[root@virtlab-66-85-105 ~]#  udevadm info --query path --name /dev/ttyS0
/devices/pnp0/00:06/tty/ttyS0
[root@virtlab-66-85-105 ~]#  !! --attribute-walk | grep looking
  udevadm info --query path --name /dev/ttyS0 --attribute-walk | grep looking
  looking at device '/devices/pnp0/00:06/tty/ttyS0':
  looking at parent device '/devices/pnp0/00:06':
  looking at parent device '/devices/pnp0':

For fixed version:
Guest A and guest B are the same:
[root@virtlab-66-85-138 ~]# !! --attribute-walk | grep looking
udevadm info --query path --name /dev/ttyS0 --attribute-walk | grep looking
  looking at device '/devices/pnp0/00:06/tty/ttyS0':
  looking at parent device '/devices/pnp0/00:06':
  looking at parent device '/devices/pnp0':

So, this bug is fixed.
Comment 9 Miroslav Svoboda 2011-08-23 15:05:24 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When KVM guests were configured with the "-serial" option or the "-device isa-serial" option, serial devices created were displayed incorrectly by the system and were not visible by Windows guests. This issue arose because such devices were described incorrectly in the Advanced Configuration and Power Interface (ACPI) Differentiated System Description Table (DSDT). To fix this issue, the code has been modified to report such serial devices in the PCI IDE ISA Xcelerator 4 (PIIX4) configuration space. The system now shows these serial devices correctly and such devices are now registered by ACPI DSDT so Windows systems can now see these devices properly.
Comment 10 Paolo Bonzini 2011-08-23 16:13:12 UTC 
Fixed and cleaned up the description; the bug only occurs with "-serial", not "-device isa-serial".  I omitted the expansion of ACPI, and avoided mentioning PIIX4 which is just an implementation detail of current versions of QEMU.  In general, if somebody really cares about how the fix works, they should know at least what ACPI is, even though perhaps not that the fix involves the DSDT.
Comment 11 Paolo Bonzini 2011-08-23 16:13:13 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-When KVM guests were configured with the "-serial" option or the "-device isa-serial" option, serial devices created were displayed incorrectly by the system and were not visible by Windows guests. This issue arose because such devices were described incorrectly in the Advanced Configuration and Power Interface (ACPI) Differentiated System Description Table (DSDT). To fix this issue, the code has been modified to report such serial devices in the PCI IDE ISA Xcelerator 4 (PIIX4) configuration space. The system now shows these serial devices correctly and such devices are now registered by ACPI DSDT so Windows systems can now see these devices properly.+When KVM guests were launched with the "-device isa-serial" option instead of the "-serial" option (as libvirt does in Red Hat Enterprise Linux version 6), serial devices created were not visible by Windows guests. This issue arose because QEMU did not expose these devices in the guest's ACPI tables.  With the fix, the ACPI Differentiated System Description Table (DSDT) will properly sense the presence of serial devices and Windows guests will see them properly.
Comment 12 Miroslav Svoboda 2011-08-23 17:33:51 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-When KVM guests were launched with the "-device isa-serial" option instead of the "-serial" option (as libvirt does in Red Hat Enterprise Linux version 6), serial devices created were not visible by Windows guests. This issue arose because QEMU did not expose these devices in the guest's ACPI tables.  With the fix, the ACPI Differentiated System Description Table (DSDT) will properly sense the presence of serial devices and Windows guests will see them properly.+When KVM guests were launched with the "-device isa-serial" option instead of the "-serial" option, serial devices created were not visible by Windows guests. This issue arose because QEMU did not expose these devices in guests' ACPI tables.  With this fix, the guest's ACPI Differentiated System Description Table (DSDT) now properly senses the presence of serial devices and Windows guests can now see them properly.
Comment 13 Miroslav Svoboda 2011-08-23 17:39:50 UTC 
I've done several style corrections and reflected the description to the related advisory.
Comment 14 Miroslav Svoboda 2011-08-24 15:34:30 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-When KVM guests were launched with the "-device isa-serial" option instead of the "-serial" option, serial devices created were not visible by Windows guests. This issue arose because QEMU did not expose these devices in guests' ACPI tables.  With this fix, the guest's ACPI Differentiated System Description Table (DSDT) now properly senses the presence of serial devices and Windows guests can now see them properly.+When KVM guests were launched with the "-device isa-serial" option instead of the "-serial" option, serial devices created were not visible by Windows guests. This issue arose because QEMU did not expose these devices in the guests' ACPI tables.  With this fix, the guest's ACPI Differentiated System Description Table (DSDT) now properly senses the presence of serial devices and Windows guests can now see them properly.
Comment 15 errata-xmlrpc 2011-08-25 08:02:53 UTC 
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-1211.html
Note You need to log in before you can comment on or make changes to this bug.