Bug 756944 - can't boot guest with "-readconfig" option using config file
Summary: can't boot guest with "-readconfig" option using config file
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.2
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-25 09:10 UTC by daiwei
Modified: 2013-01-10 00:33 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-08 11:17:26 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description daiwei 2011-11-25 09:10:20 UTC
Description of problem:

create a configure file with "-writeconfig" option in qemu-kvm command line,then boot guest use the same configure file and with "-readconfig" option,guest boot failed.


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

2.6.32-220.el6.x86_64
qemu-kvm-0.12.1.2-2.209.el6.x86_64

How reproducible:
3/3

Steps to Reproduce:
1.boot a guest with "-writeconfig" option and with "-monitor stdio" in qemu-kvm command line

e.g.
# /usr/libexec/qemu-kvm ... -monitor stdio -writeconfig /home/test.cfg

2.boot a guest with "-readconfig" option and use test.cfg

e.g.
# /usr/libexec/qemu-kvm ... -readconfig /home/test.cfg
3.
  
Actual results:
boot guest failed and prompt:

qemu-kvm: Duplicate ID 'monitor' for chardev
parse error: vc:80Cx24C



Expected results:

guest start without any error.

Additional info:

without "-monitor stdio" in qemu-kvm command line no this error.

Comment 1 Suqin Huang 2011-11-25 10:03:00 UTC
try to add -nodefconfig

Comment 2 Dor Laor 2011-12-08 11:17:26 UTC
(In reply to comment #1)
> try to add -nodefconfig

Please retest w/ it

Comment 3 daiwei 2011-12-08 14:20:49 UTC
I'm sorry for updating late.

when boot guest,add -nodeconfig -nodefaults to qemu-kvm command line no this problem.


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