Bug 795661 - Qemu monitor prompt missing after boot
Summary: Qemu monitor prompt missing after boot
Keywords:
Status: CLOSED DUPLICATE of bug 791200
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.3
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-21 08:12 UTC by Shaolong Hu
Modified: 2012-02-21 09:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-21 09:10:10 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.