From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: kvm@vger.kernel.org
Cc: nikola.ciprich@linuxbox.cz
Subject: memory dump file still opened after vm restore
Date: Wed, 28 Jan 2009 20:24:21 +0100 [thread overview]
Message-ID: <20090128192421.GB28568@nik-comp.linuxbox.cz> (raw)
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
-------------------------------------
next reply other threads:[~2009-01-28 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 19:24 Nikola Ciprich [this message]
2009-01-29 15:33 ` memory dump file still opened after vm restore Daniel P. Berrange
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090128192421.GB28568@nik-comp.linuxbox.cz \
--to=extmaillist@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox