From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: suspending in kvm and resuming in qemu Date: Thu, 27 Jan 2011 16:06:20 +0200 Message-ID: <4D417BDC.1040704@redhat.com> References: <404700.23849.qm@web39308.mail.mud.yahoo.com> <20110120161159.GE5996@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mehul Chadha , kvm@vger.kernel.org To: Marcelo Tosatti Return-path: Received: from mx1.redhat.com ([209.132.183.28]:37603 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750921Ab1A0OGY (ORCPT ); Thu, 27 Jan 2011 09:06:24 -0500 In-Reply-To: <20110120161159.GE5996@amt.cnet> Sender: kvm-owner@vger.kernel.org List-ID: On 01/20/2011 06:11 PM, Marcelo Tosatti wrote: > On Tue, Jan 18, 2011 at 04:08:33AM -0800, Mehul Chadha wrote: > > Hi, > > > > I have been trying to get suspending and resuming done across kvm and qemu. > > While resuming a suspended state in kvm, an error was generated saying "unknown section kvmclock" . I modified loadvm in qemu to neglect the kvmclock section. > > > > Now, when I suspend and resume, qemu screen just stalls at the suspended state and it seems nothing is executing. > > > > Pls give any inputs or help, where should I start looking at?? > > > > Thanks, > > Mehul > > The guest relies on kvmclock support, which is not implemented by qemu > alone. So you'd have to disable kvmclock support (with no-kvmclock > kernel boot option) in the guest. > Or with -cpu qemu64,-kvmclock on the qemu command line. -- error compiling committee.c: too many arguments to function