All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Amin <amino7@yahoo.com>, xen-devel@lists.xensource.com
Subject: Re: hvm save twice fails
Date: Mon, 19 Mar 2007 16:01:14 +0000	[thread overview]
Message-ID: <C224644A.BD05%keir@xensource.com> (raw)
In-Reply-To: <pan.2007.03.19.14.31.20@yahoo.com>

On 19/3/07 14:31, "Amin" <amino7@yahoo.com> wrote:

> I'm running changeset 14422 on 64bit.
> I did a full compile and reinstall from scratch.
> 
> I can successfully xm save and restore a win 2003 VM - but just once. The
> second save fails, nothing happens and the domain is still running. I see
> the following file sizes:
> -rwxr-xr-x 1 root root 546181260 Mar 19 15:26 snapshot
> -rwxr-xr-x 1 root root      1345 Mar 19 15:26 snapshot2
> 
> as you see the second snapshot file is almost empty.
> Any ideas?
> 
> Below is what I see in xend.log.

An odd failure. But in any case save/restore of shared_info mapping is not
required for HVM guests. I'll strip that out.

 -- Keir

      reply	other threads:[~2007-03-19 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19 14:31 hvm save twice fails Amin
2007-03-19 16:01 ` Keir Fraser [this message]

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=C224644A.BD05%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=amino7@yahoo.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.