From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nikola Ciprich Subject: Re: [libvirt] qemu-kvm-0.10.5, kvm-kmod-2.6.30, libvirt-0.6.4 - save/restore still unreliable Date: Sat, 13 Jun 2009 08:32:18 +0200 Message-ID: <20090613063218.GA5018@nik-comp.linuxbox.cz> References: <20090612140109.GA18926@develbox.linuxbox.cz> <20090612201043.GA4852@nik-comp.linuxbox.cz> <4A32B7CE.20004@messageone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org, nikola.ciprich@linuxbox.cz To: Charles Duffy Return-path: Received: from gwu.lbox.cz ([62.245.111.132]:43259 "EHLO gwu.lbox.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751382AbZFMGc3 (ORCPT ); Sat, 13 Jun 2009 02:32:29 -0400 Content-Disposition: inline In-Reply-To: <4A32B7CE.20004@messageone.com> Sender: kvm-owner@vger.kernel.org List-ID: Hmm, I just noticed that dump file saved using virsh contains some libvirt related headers, so I guess I can't just feed it directly to qemu-kvm. So I guess best way to test save/restore without libvirt is to save vm state using monitor and then restore it again. But I can't find any clear documentation on how to do this. Could anyone give me a hint? thanks a lot! nik On Fri, Jun 12, 2009 at 03:17:18PM -0500, Charles Duffy wrote: > That may well be a guest issue rather than a qemu migration problem -- > I've seen similar difficulties for guests being resumed via incoming > migration when using guest kernels with TSC as their clocksource. > > You might try interrogating the monitor to see your guest's state. > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- ------------------------------------- Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: servis@linuxbox.cz -------------------------------------