On 08/21/2012 01:57 PM, Qingtang Zhou wrote:
* On 2012-08-21 07:42:31 +0200, Gerd Hoffmann (kra...@redhat.com) wrote:
On 08/21/12 06:49, Amos Kong wrote:
On 20/08/12 22:18, Lucas Meneghel Rodrigues wrote:
On Mon, 2012-08-20 at 08:24 +0200, Gerd Hoffmann wrote:
On 08/20/12 07:57, yunzh...@redhat.com wrote:
From: Yunping Zheng<yunzh...@redhat.com>
we can config whether or not qemu to start in stopped state (via -S),
then start the guest via cont monitor command.
What do you need this for?
CPU is always frozen at startup. Yunping's patch makes this configurable.
I don't think it should be configurable and try to understand why you
want it.
me2, All the patches leaves this "freeze_cpu" parameter to 'yes'.
Yunping, could you give us some example of the situation which this
parameter should be 'no'?
Here I just have a different opinion. As this is a framework to test
qemu-kvm we should provide more choice for the people who is not working
in the same environment as us. And make it configurable will make things
more flexible which is good and harmless.
-----------------------
{'execute': 'cont'}
{
"error": {
"class": "MigrationExpected",
"desc": "An incoming migration is expected before this command
can be executed"
}
}
-----------------------
(qemu) cont
An incoming migration is expected before this command can be executed
-----------------------
Ok. That is clearly a bug which should be fixed. Working around by
adding a new config option isn't a good idea IMHO.
I guest we can check guest status here.
"""
# qemu-kvm -S -incoming tcp:0:1234 -monitor stdio -vnc :0
QEMU 1.1.50 monitor - type 'help' for more information
(qemu) info status
VM status: paused (inmigrate)
(qemu) cont
An incoming migration is expected before this command can be executed
(qemu) q
# qemu-kvm -S -monitor stdio -vnc :0
QEMU 1.1.50 monitor - type 'help' for more information
(qemu) info status
VM status: paused (prelaunch)
(qemu) cont
(qemu)
"""
This method only works in the new version of qemu. But in RHEL5 it only
will shows as paused or running. So this will not work.
Plan B is just ignore this error msg, if autotest gets this error msg
from monitor, just return directly.
We have another choice that don't send cont when the guest is the dst in
migrate.
cheers,
Gerd
_______________________________________________
Autotest-kernel mailing list
Autotest-kernel@redhat.com
https://www.redhat.com/mailman/listinfo/autotest-kernel
_______________________________________________
Autotest-kernel mailing list
Autotest-kernel@redhat.com
https://www.redhat.com/mailman/listinfo/autotest-kernel
_______________________________________________
Autotest-kernel mailing list
Autotest-kernel@redhat.com
https://www.redhat.com/mailman/listinfo/autotest-kernel
