search for: checkpointfile

...tc/xen/auto for autostart/autostop, but when shutdown the dom0 or stop the guests os with the xendomains script this happens: [root@xenhost ~]# service xendomains stop Shutting down Xen domains: centos4.4(save)Error: /usr/lib64/xen/bin/xc_save 17 16 0 0 0 failed Usage: xm save <Domain> <CheckpointFile> Save a domain state to restore later. .!(shut).Domain 16 terminated .All domains terminated /etc/init.d/xendomains: line 299: 8235 Terminated watchdog_xm save /etc/init.d/xendomains: line 188: 8249 Terminated watchdog_xm shutdown fc6(save)/etc/init.d/xendomains:...

I recently used the Xen virtual machine backup tools, such as ''xm save'' command. And I found that before this tool save the memory and CPU state, it first pauses the VM. Do Xen have same tools for online backup the VMs? If it do not have one, can I saty that Xen don''t support VM online backup? -- View this message in context:

...em, though a workaround or at least a warning in xen's documentation (man page, xm help, or something like that) would be great. - Saving of a HVM domU does not work either: # xm save 5 foobar Error: /usr/lib/xen-3.0.3-1/bin/xc_save 17 5 0 0 0 failed Usage: xm save <Domain> <CheckpointFile> Save a domain state to restore later. - When running "man xm" I always get these messages in less: /tmp/zmankxWh5l:643: warning: can't find numbered character 160 /tmp/zmankxWh5l:651: warning: can't find numbered character 160 /tmp/zmankxWh5l:652: warning: can't f...

...ith it? This error happened when I used xen-4.0.1-rc5 and kernel-2.6.31.13. Today I update to xen-4.0.1 and kernel-2.6.32.25, it is with the same wrong. Error message: [root@localhost ~]# xm save -c 2 snap1 Error: Timeout waiting for domain 2 to suspend Usage: xm save [-c] <Domain> <CheckpointFile> Save a domain state to restore later. -c, --checkpoint Leave domain running after creating snapshot xend.log : [2010-11-26 15:39:48 5411] DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib64/xen/bin/xc_save 4 2 0 0 4 [2010-11-26 15:39:48 5411...

...ith it? This error happened when I used xen-4.0.1-rc5 and kernel-2.6.31.13. Today I update to xen-4.0.1 and kernel-2.6.32.25, it is with the same wrong. Error message: [root@localhost ~]# xm save -c 2 snap1 Error: Timeout waiting for domain 2 to suspend Usage: xm save [-c] <Domain> <CheckpointFile> Save a domain state to restore later. -c, --checkpoint Leave domain running after creating snapshot xend.log : [2010-11-26 15:39:48 5411] DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib64/xen/bin/xc_save 4 2 0 0 4 [2010-11-26 15:39:48 5411...

Changes since v1: - Removed libxl vncviewer related dependencies - The vncviewer function was modified to accept a domid instead of domspec; - main_vncviewer was updated to reflect the new use. - A domain_create structure is now passed to the parse_config_data where required/feasible (NULL otherwise) - xl restore now have long options for vncviewer/vncviewer-autopass; docs updated. - Updated

Hello everybody, after saving a virtual machine I wanted to restore it so I gave the command #xm restore xen1.sav where xen1.sav is the file obtained with xm save. It didn''t work though and I had this response: Error: Restore failed Usage: xm restore <CheckpointFile> Restore a domain from a saved state. Well, xen1.sav is a saved state, so why doesn''t it work? Thanks in advance. Molly _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...err("%s" % ex.faultString) AttributeError: error instance has no attribute ''faultString'' This patch fixes the bugs. Test results are as follows. # touch /tmp/dummy # xm restore /tmp/dummy Error: not a valid guest state file: signature read Usage: xm restore <CheckpointFile> [-p] Restore a domain from a saved state. -p, --paused Do not unpause domain after restoring it # echo $? 1 # xend stop # xm restore /xen/save.vm1 Error: Unable to connect to xend: Connection refused. Is xend running? Signed-off-by: Masaki Kanno <kanno.masaki@jp.fu...

...I name them using their fully qualified DNS domain name. These machines have failed to start automatically when I booted the host machine, and I just recently found out why. During shutdown, I was messages like this: Error: Domain 'o' does not exist. Usage: xm save <Domain> <CheckpointFile> Save a domain state to restore later. By running '/etc/init.d/xendomains stop' manually using bash -x, I discovered why. The code to extract the domain name is only looking at the first 17 characters of the result reported by 'xm list', and this is too short to get the enti...

...@ struct cmd_spec cmd_table[] = { "--vncviewer-autopass (consistency alias for --autopass)" }, { "save", - &main_save, 0, + &main_save, 0, 1, "Save a domain state to restore later", "[options] <Domain> <CheckpointFile> [<ConfigFile>]", "-h Print this help.\n" "-c Leave domain running after creating the snapshot." }, { "migrate", - &main_migrate, 0, + &main_migrate, 0, 1, "Save a domain state to restore later"...

This is v3 of my disk series. What were previously patches 01-06 have been applied. These are the tested and updated remainder, addressing the previous comments. 1 Preparatory work. 2-4 The new parser and its documentation. 5-6 Replace old parsers with calls to the new one. 7-8 Two features, one of them essential. 9 Basic test suite for disk string parsing, as adhoc script.

The following series flushes my documentation queue and replaces previous postings of those patches. The main difference is that the xl cfg file is now formatted using POD instead of markdown and presented as a manpage. I have setup a cron job to build docs/html and publish it at http://xenbits.xen.org/docs/unstable/ (it''s a bit bare right now). The motivation for some of these patches