On Fri, Nov 4, 2011 at 2:26 PM, Wen Congyang <we...@cn.fujitsu.com> wrote: > At 11/04/2011 10:48 AM, Zhi Yong Wu Write: >> On Fri, Nov 4, 2011 at 10:45 AM, Wen Congyang <we...@cn.fujitsu.com> wrote: >>> >>> We disable vm_clock when pausing all vcpus, but we forget to >>> reenable it when resuming all vcpus. It will cause that the >>> guest can not be rebooted. >> Actually i also met this issue when rebooting the guest. When the >> guest is rebooted, it will crash. > > When I reboot the guest, it will hang. > > Does this patch solve your problem? Yeah, it can work for my guest now.
BTW: If the patch is not applied, when guest is rebooted, fedora guest will crash, while rh6.1 guest will hang up. Tested-by: Zhi Yong Wu <zwu.ker...@gmai.com> > >> >>> >>> Signed-off-by: Wen Congyang <we...@cn.fujitsu.com> >>> >>> --- >>> cpus.c | 1 + >>> 1 files changed, 1 insertions(+), 0 deletions(-) >>> >>> diff --git a/cpus.c b/cpus.c >>> index 6aff425..82530c4 100644 >>> --- a/cpus.c >>> +++ b/cpus.c >>> @@ -891,6 +891,7 @@ void resume_all_vcpus(void) >>> { >>> CPUState *penv = first_cpu; >>> >>> + qemu_clock_enable(vm_clock, true); >>> while (penv) { >>> penv->stop = 0; >>> penv->stopped = 0; >>> -- >>> 1.7.1 >>> >> >> >> >> -- >> Regards, >> >> Zhi Yong Wu >> > > -- Regards, Zhi Yong Wu