similar to: Suspend fails, "not managed by Xend lifecycle support"

Hello, I have a problem using xm suspend and xm save. When I use "xm suspend ts" (ts is the name of my DomU) I get the error-message "Error: Domain is not managed by Xend lifecycle support." In /var/log/xen/xend.log there is no output about the error. I found this question in the internet but there were no replies and I did not find any information about configuring

Xend lifecycle changes -- basic functionality. xend/XendDomain.py | 287 ++++++++++++++++++++++++++++++++++---------- xend/XendDomainInfo.py | 203 +++++++++++++++++++++++-------- xend/XendRoot.py | 8 + xend/server/XMLRPCServer.py | 2 xm/create.py | 4 xm/main.py | 29 +++- xm/new.py | 68 ++++++++++ 7

Hi all I get problem here when I try resume a vm. I do this: xm new VM xm start VM xm suspend VM Everything normal. No errors. But when I try resume the VM: xm resume VM I get this error: [2010-05-06 12:29:59 2040] ERROR (XendCheckpoint:357) /usr/lib/xen/bin/xc_restore 28 2 3 4 1 1 1 0 failed Traceback (most recent call last): File

Hi all I get problem here when I try resume a vm. I do this: xm new VM xm start VM xm suspend VM Everything normal. No errors. But when I try resume the VM: xm resume VM I get this error: [2010-05-06 12:29:59 2040] ERROR (XendCheckpoint:357) /usr/lib/xen/bin/xc_restore 28 2 3 4 1 1 1 0 failed Traceback (most recent call last): File

Hi, This patch fixes a error message of xm suspend command for Domain-0. Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com> Best regards, Kan diff -r 2a8eaba24bf0 tools/python/xen/xend/XendDomain.py --- a/tools/python/xen/xend/XendDomain.py Tue Feb 26 15:11:51 2008 +0000 +++ b/tools/python/xen/xend/XendDomain.py Thu Feb 28 14:23:39 2008 +0900 @@ -865,7 +865,7 @@

Recent xen uses xenbus to suspend PV-on-HVM guest domain. The related code in the xen-unstable tree will fall into infinite loop when guest domain failed on suspending one or more devices. The patch attached changes the logic, and raises an XendError after 1 minute waiting. The patch also makes use of "control/shutdown" entry in xenstore, allows guest kernel report the failure of the

[Patch 4/4]: Xend interface for HVM S3 - extend "xm resume <domid>" to be able to S3 resume HVM domain. - when user issue "xm resume" command for HVM domain, xend will use xc lib API to call HVMOP_s3_resume hypercall. Note: it may not appropriate use xm resume for HVM s3, since xm resume is originally designed for save/restor purpose. It will be fine that

Hello, When I snapshot a vm( hvm centos ) the first time, it succeed. There is a snapshot file on disk and the vm is running. But when I do it the second time, it fail for timeout. what''s wrong with 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:

Hello, When I snapshot a vm( hvm centos ) the first time, it succeed. There is a snapshot file on disk and the vm is running. But when I do it the second time, it fail for timeout. what''s wrong with 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:

At least from the ''xm'' commands'' interface, it looks like domU''s just disappear after an ''xm destroy'', which I''ve been using to cut turn off the virtual power switches of domU''s. Is this by design? I''m trying to think of a good way to identify a domU throughout its lifecycle, which for me goes all the way from

Hi, all, When working on adding PM support to xen, we realized that some enhancements are required to suspend/resume domU. Following is some background and thoughts, and welcome on comments. :-) Currently we use a simple approach (pause/unpause) for domU when ready to pull whole platform into a power save state, saying a S3. Because pause/unpause is out of domU''s knowledge, domU

On 12/22/2011 01:37 AM, Mike McClurg wrote: > Hi Thomas, Jon, > > I was hoping that you could both comment on this github pull request: > > https://github.com/jonludlam/xen-api/pull/12 > > Mike > In Debian, /etc/default/xen is there to select xm vs xl. So we could do: if ! [ -f /etc/default/xen ] ; then TOOLSTACK=xm else . /etc/default/xen if ! [

Starting about 2 weeks ago Xend has started to fall over a lot doing what should be normal actions, so much so that our xm-test suite more or less fails all the tests as it keeps apparently knocking over xend on relatively simple operations like create, and list. What is most bizarre now is this "no such process" error generated by Xend. Here is a segment of our xm-test results that

The following patches implement XML-RPC for Xend. The first patch just adds a new server for Xend that exposes the same functions exposed by the S-Expression/HTTP server expect by XML-RPC. There is no change to the code paths taken for any xm commands so it''s a rather safe patch to include. The second patch changes XendClient to use XML-RPC and makes a few subsequent changes to xm

Hi folks, we (the company i am working for) are running several dozens of virtualisation servers using CentOS 6 + Xen4CentOS as the virtualisation infrastructure. With the latest versions of all packages installed [1], we see failures in live-migration of stock-CentOS6 HVM guests, leaving a "Domain-unnamed" on the source host, while the migrated guest runs fine on the target host.

I am seeing a strange issue while running Mini-OS on the changeset 9906:a95e677073c1. This is on both i386 and x86_64. The only difference being on i386 if I stop printing to the console, this issue is not manifested. But with x86_64 it happens all the time. Bringing up Mini-OS for the first time causes xm to hang on certain commands like "list, destroy". Other commands like

Hello, I''ve noticed that if I try to restart Xend via "/etc/init.d/xend stop" then "/etc/init.d/xend start", I won''t receive any errors but then when trying to execute "xm" commands after the restart I get error asking if Xend is started. Is there anything else I need to make sure gets stopped/started with Xend? Another question ... domU reboots

Hi, I tried to test a wrong operation on purpose again. When I tried xm sysrq command to a inactive managed domain, I saw the following error message. The error message did not have a message text behind "Error:". And I found an AssertionError message in xend.log. # xm list PVdomain.1 Name ID Mem VCPUs State Time(s) PVdomain.1

Processing commands for control at bugs.debian.org: > retitle 655301 xend shouldn't start if TOOLSTACK is not xm Bug #655301 [xcp-xapi] xcp-xapi fails to start Changed Bug title to 'xend shouldn't start if TOOLSTACK is not xm' from 'xcp-xapi fails to start' > reassign 655301 xen-utils-common Bug #655301 [xcp-xapi] xend shouldn't start if TOOLSTACK is not xm Bug

thanks for help, xend start is OK but xm list failed as follows How to fix it ?? I am look forward to your directions [root@tgh Twisted-1.3.0]# xend start [root@tgh Twisted-1.3.0]# xm list (111, ''Connection refused'') Error: Error connecting to xend, is xend running? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com