memory dump file still opened after vm restore

memory dump file still opened after vm restore

[Nikola Ciprich]

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?
thanks in advance for reply
regards
nik

-- 
-------------------------------------
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
-------------------------------------

Re: memory dump file still opened after vm restore

[Daniel P. Berrange]

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 :|