WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] xm save while VM is writing once per second?

To: Jeff Blaine <jblaine@xxxxxxxxx>
Subject: Re: [Xen-users] xm save while VM is writing once per second?
From: Daniel Stekloff <dsteklof@xxxxxxxxxx>
Date: Tue, 10 May 2005 15:39:51 -0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 10 May 2005 22:19:19 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <428105B0.4060400@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <428105B0.4060400@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2005-05-10 at 15:04 -0400, Jeff Blaine wrote:
> I must not be understanding something trivial that I cannot
> find in the documentation.
> 
> I am running Xen 2.0.5 with Fedora Core 3 successfully.
> 
> I have a VM (VM4) running a test shell script that loops
> infinitely while writing the date and a counter every
> second (to /tmp/counter).
> 
> The entire VM is using a file-backed VBD for all storage
> (/vm-images/vm-4-disk acting as sda1 to the VM).
> 
> Running 'xm save VM4 /vm-images/vm4.save' from dom0
> never returns (well, I have been staring at it for 5
> minutes now).
> 
> 'xm save VM4 /vm-images/vm4.save' works fine without the
> looping script writing to /tmp/counter every second.
> 
> Somebody clue me in?


This may sound odd, but have you run the save command a second time
after the first time never returned? I have a similar configuration as
you and I just ran xm save command. The first time, it just sat there
and didn't return. I exited it and ran the command again and it worked. 

I'm still figuring out why. But it worked the second time I ran the xm
save command.

I followed up the save with "xm restore" and that worked.

Thanks,

Dan




_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>