From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: memory dump file still opened after vm restore Date: Thu, 29 Jan 2009 15:33:00 +0000 Message-ID: <20090129153300.GN22110@redhat.com> References: <20090128192421.GB28568@nik-comp.linuxbox.cz> Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org, nikola.ciprich@linuxbox.cz To: Nikola Ciprich Return-path: Received: from mx1.redhat.com ([66.187.233.31]:36914 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751782AbZA2PdK (ORCPT ); Thu, 29 Jan 2009 10:33:10 -0500 Content-Disposition: inline In-Reply-To: <20090128192421.GB28568@nik-comp.linuxbox.cz> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Jan 28, 2009 at 08:24:21PM +0100, Nikola Ciprich wrote: > Hello, > with latest libvirt + small patch, I've finally managed to have save/restore working again > (at least for kernels without paravirtualisation enabled), but I've noticed one small glitch. > when vm is restored, the image is deleted, but kvm process keeps it opened, so it's not really deleted. > is this somehow intended, or is it a bug? I have reproduced this problems - its not a KVM bug really - its just an artifact of the way we tried to use '-incoming exec' in libvirt. This is not really satisfactory, so I'm going to try and find another way todo this Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|