Bug 795661

Summary: Qemu monitor prompt missing after boot
Product: Red Hat Enterprise Linux 6 Reporter: Shaolong Hu <shu>
Component: qemu-kvmAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 6.3CC: acathrow, bsarathy, juzhang, kwolf, michen, mkenneth, virt-maint
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-21 09:10:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Shaolong Hu 2012-02-21 08:12:52 UTC 
Description of problem:
---------------------------
Qemu monitor prompt missing:
#qemu-kvm
QEMU 0.12.1 monitor - type 'help' for more information
(qemu)

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
qemu-kvm-0.12.1.2-2.228.el6.x86_64.rpm and later version

How reproducible:
-----------------
100%

Steps to Reproduce:
--------------------
1.boot guest, used to have prompt:
QEMU 0.12.1 monitor - type 'help' for more information
(qemu)

2.now nothing, after press "ENTER", only:
(qemu)

Additional info:
-----------------
Not sure whether this is a bug nor worth fixing, probably caused by the patch set: Backport corountine-based block layer.
Comment 2 Shaolong Hu 2012-02-21 08:58:02 UTC 
Additional info:
-----------------
Need add at least one block device to trigger this, eg:

/usr/libexec/qemu-kvm -drive file=nfs/win2008r2-64-virtio.qcow2,cache=none,if=none,rerror=stop,werror=stop,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,drive=drive-virtio-disk0,id=device-virtio-disk0 -monitor stdio
Comment 4 Kevin Wolf 2012-02-21 09:10:10 UTC 

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