From: Uri Lublin <uril-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Daniel P. Berrange" <berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: kvm+virtmanager can't save machine state?
Date: Mon, 02 Jul 2007 10:59:20 +0300 [thread overview]
Message-ID: <4688B058.70508@qumranet.com> (raw)
In-Reply-To: <20070629110414.GA31592-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Actually, although not intended (and was not tested), KVM's migration
capability enables save/restore of non-qcow images.
I used it to debug the migration code.
Please look at the bottom of http://kvm.qumranet.com/kvmwiki/Migration
("savevm/loadvm to an external state file").
BTW, my little trick also works for "live" savevm/loadvm (kids don't try
this at home).
Hope that helps,
Uri.
Daniel P. Berrange wrote:
> On Fri, Jun 29, 2007 at 04:05:22PM +0800, youhongyu wrote:
>
>> hi all,
>>
>> i use: fc7, built in xen, kvm.
>> i boot my machine into normal kernal and install a guest os by vir-manager,
>> and i encounter a strange situation .... the "save" command from virtual-
>> manager menu failed! it pop out a small windows seem want to tell me
>> something, but it quickly disappeared. what's thing happens?
>>
>
> The window shouldn't have disappeared like that - it should have told
> you that this isn't supported....
>
> We can't support save/restore of KVM guests in virt-manager at this
> time. QEMU 0.9.0 was really very unhelpful and removed the ability specify
> a filename for saving VM state, assuming that everyone happens to be using
> a qcow file :-( Not much use if you are using raw files, or physical volumes,
> or LVM which are the primary storage types used in virt-manager currently.
>
> Dan.
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-07-02 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 8:05 kvm+virtmanager can't save machine state? youhongyu
[not found] ` <014e01c7ba24$3df1e340$64191fac-SWKJ/EET2QEN0771rzroLI9Bucmsk37m@public.gmane.org>
2007-06-29 11:04 ` Daniel P. Berrange
[not found] ` <20070629110414.GA31592-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-07-02 7:59 ` Uri Lublin [this message]
[not found] ` <4688B058.70508-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-03 0:41 ` Anthony Liguori
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=4688B058.70508@qumranet.com \
--to=uril-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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