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.

Bug 849461

Summary: Using virtio-console causes hard guest lockup
Product: Red Hat Enterprise Linux 6 Reporter: Enrico Scholz <rh-bugzilla>
Component: qemu-kvmAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3CC: acathrow, amit.shah, bsarathy, dwmw2, dyasny, juzhang, lkundrak, mkenneth, virt-maint, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-22 04:42:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Enrico Scholz 2012-08-19 16:14:08 UTC 
Description of problem:

Having a guest with

    <console type='pty'>
      <target type='virtio' port='0'/>
    </console>

causes the guest to hang when /dev/hvc0 is accessed (e.g. when console is
started by '/sbin/mingetty /dev/hvc0'). E.g. when console is accessed,
spice/vnc video does not respond anymore and guest can not be reached
over network either.

Things work fine when

    <type arch='x86_64' machine='rhel6.0.0'>hvm</type>

is specified; rhel6.1.0 machine type and above cause the seen lockup.

I am using a RHEL6.3 guest on a RHEL6.3 host.


Guest is started by

LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.3.0 -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -name upnor -uuid 8650828c-2927-62eb-8295-181b0dd7f8bc -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/upnor.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=/dev/vg00/virt-upnor,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/dev/vg00/virt-upnor-cache,if=none,id=drive-virtio-disk1,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=virtio-disk1 -drive file=/dev/vg00/virt-upnor-data,if=none,id=drive-virtio-disk2,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk2,id=virtio-disk2 -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=54:52:00:50:08:05,bus=pci.0,addr=0x3 -chardev pty,id=charconsole0 -device virtconsole,chardev=charconsole0,id=console0 -vnc 127.0.0.1:3105 -k en-us -vga cirrus -device i6300esb,id=watchdog0,bus=pci.0,addr=0x9 -watchdog-action reset -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8
char device redirected to /dev/pts/2


Guest system has

| ACTIVE_CONSOLES="$ACTIVE_CONSOLES /dev/hvc0"

in /etc/sysconfig/init to autostart console.



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

kernel-2.6.32-279.5.1.el6.x86_64
qemu-kvm-0.12.1.2-2.295.el6_3.1.x86_64



How reproducible:

100%
Comment 2 Amit Shah 2012-08-20 06:49:46 UTC 
Most likely a dup of bug 839156
Comment 3 Amit Shah 2012-08-20 06:50:28 UTC 
Can you use a different chardev backend, like unix or tcp, to confirm if it's a dup of the earlier bug?
Comment 4 Enrico Scholz 2012-08-21 17:27:35 UTC 
I can not reproduce it with

    <console type='unix'>
      <source mode='bind' path='/tmp/foo'/>
      <target type='virtio' port='0'/>
    </console>

(but 'virsh console' does not work with this setting).
Comment 5 Amit Shah 2012-08-22 04:42:37 UTC 
(In reply to comment #4)
> I can not reproduce it with
> 
>     <console type='unix'>
>       <source mode='bind' path='/tmp/foo'/>
>       <target type='virtio' port='0'/>
>     </console>

Thanks for confirming; I'm marking this as a dup of the other bug.

> (but 'virsh console' does not work with this setting).

Not sure why this happens, need to confirm with libvirt developers.

*** This bug has been marked as a duplicate of bug 839156 ***