similar to: VDS not accessible due to some issue with xend service

xen-3.0.3-64.el5_2.1 Here's the scenario: Name ID Uptime Domain-0 0 128 days, 17:31:11 piranga_xen01 1 128 days, 17:30:13 piranga_xen02 39 96 days, 15:47:10 piranga_xen03 35 96 days, 16:39:52 piranga_xen04 59 16 days, 17:30:35 3 hours ago, xen04 stopped

Dear Xen Users, at first, sorry for my bad english and in fact my post is wrong here, please light me the way to the right board. My Xen Host runs since two years without a problem. As of today, some v-servers was not reachable anymore. I did a short xm top and got dozen of erros. I did a reboot of the Host. Thereafter i get the same error messages when trying to start xend (/etc/init.d/xend

Hi all, All of a sudden my xend is crashing, when i do "xm create domu" due to which the domains are created in paused state. Iam using minios as domU kernel, but the problem occurs even for linux-2.6.18.1 pv kernel as domu kernel. xend.log shows [2008-07-31 03:00:54 14821] CRITICAL (SrvDaemon:231) Xend died due to signal 11! Restarting it.... after doing some preliminary

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 compile and install  xen 4.1.2 source after that compile kernel 3.0.21 source and install it. after I boot system then I install a DOMU HVM guest in my system  xm list  command show DOM0 and DOMU -two item- but when I want run these command root@pc# service xend start root@pc# ------------------------ root@pc# service xend start libvirtd: unrecognized service root@pc# please guide me

*After running intensively (i.e. running >10 guests and migrating them all into other machines etc.) , I wasn''t able to * *run xen tools as the following messages show. * ** ># xm list Error: (9, ''Bad file descriptor'') Usage: xm list [options] [Domain, ...] List information about all/some domains. -l, --long Output all VM details in SXP

Hi all, I am trying the pci-passthrough on xen 3.3.0. I binded the pci slot to pciback using late binding. But xend fails to allocate this slot to domU. linux-242:/home/xen-3.3.0 # xm create -c pci=08:01.0 /etc/xen/xen3.3_guest1 Using config file "/etc/xen/xen3.3_guest1". Error: [Errno 2] No such file or directory: ''/sys/bus/pci/devices/0000:06:00.0/config''

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

Short:     Which package do I need to install to get "auto/I18N/Langinfo/autosplit.ix"? Long: The problem I have was discussed almost a year ago (see this thread), but the resolution was not complete... I''m using Mark Johnson''s slim.py script (package list below), against repo=http://pkg.opensolaris.org/dev, followed by `pkg install xvm-gui` and `svcadm enable

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

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 ! [

Hi, I am posting this message because past 36 hours have been nightmare for me. I finally have solved the problem I by temporarily moving put the xml files from /var/lib/xend directories reboot then xend started. And DomU''s were failing to start the above xml files I kept back and got all DomU''s back. I am very very surprised.I do not have any logical answer to this some one

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

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

I installed Xen on Debian Lenny, server is Power Edge R710 Dell by the method mentioned here http://www.howtoforge.com/virtualization-with-xen-on-debian-lenny-amd64 every thing seemed to go fine. It rebooted to a kernel 2.6.26-1-xen-amd64 but there is no output of following commands openworld:~# /etc/init.d/xend status openworld:~# /etc/init.d/xend stop openworld:~# /etc/init.d/xend start I

I''ve migrated my Dom0 host to Xen 4.2.0 + xl toolstack. With ''xm'' toolstack, configs in /etc/xen/auto are autostarted, assuming xend/xendomains services are started. IIUC, when using xl toolstack, those services are not to be started; and, afaict, the installation process for 4.2 has them disabled by default. Now, the configs in /etc/xen/auto are simply ignored. I

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

I end up with the same error after building and running xen-stable 3.2-rc4 on both Ubuntu 7.10 and Fedora Core 6. I am using AMD64 builds. I have carefully followed the instruction on the xenbits.xensource.com on building Xen unstable. After booting with the new Xen and dom0 kernel, I cannot use any Xen tools (such as xm) from Dom0. I have tried restarting Xend but it fails with the same errors.

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

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal Tags: squeeze I have 3 VM running. I have upgraded debian squeeze to 6.0.1 (new kernel package 2.6.32-31) and restarted my server. VM were still running. After reboot I could not start xend service (from init.d). I got following errors: kern.log: Mar 22 15:07:30 router kernel: [53888.212756] xenstored[7232]: segfault at 7fff056b5ff8 ip