similar to: Xend docs

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

Missed this in the [patch] state. If we are gonna do this can we get a timestamp on every open? or every message? -JX On Oct 25, 2006, at 5:30 AM, Xen staging patchbot-unstable wrote: > # HG changeset patch > # User kfraser@localhost.localdomain > # Date 1161768423 -3600 > # Node ID 0c7923eb6b9846c92f1c15486e06ee9745bcf676 > # Parent 410df40afc014555ce7bfcad2852de9e6d0425f0

Hi I tried building xen on my IA64 machine. It builds and installs smoothly. But I have not been able to start xend. I get the error in /var/log/xen/xend.log as below: [2007-06-14 05:02:01 xend 26504] WARNING (XendAuthSessions:27) python-pam is required for XenAPI support. [2007-06-14 05:02:01 xend 26520] INFO (SrvDaemon:322) Xend Daemon started [2007-06-14 05:02:01 xend 26520] INFO

Hi all, I can''t get xend to start and could do with some help. this is the stock 30.2 release. it was working fine on ubuntu breezy, and since I''ve updated to dapper it''s boned... The odd thing is, if I run the installer, I can start xend ok. but when I reboot it''s broken again. I''m guessing a directory is being deleted by ubuntu at reboot time - is

Error:Unable to connect to xend:No such file or directory.Is xend running ?" When i tried to start up  xend i am getting the  error message like this "Error:Unable to connect to xend:No such file or directory.Is xend running ?" When i check the file /var/log/xen/xend.log i am getting the  follwing log messages. How should i fix this problem ? ExpatError: no element found: line

Comparing my last know working configuration with the current one, it appears to be gagging on the new localhost\.localdomain that is in the configuration file. I don''t know if this got added by my machine when compiling. diff -ur xen-3.0-testing.hg/install/etc/xen/xend-config.sxp xen-unstable.hg/install/etc/xen/xend-config.sxp --- xen-3.0-testing.hg/install/etc/xen/xend-config.sxp

On Thu, 2007-11-08 at 15:34 +0000, Xen staging patchbot-unstable wrote: > # HG changeset patch > # User Keir Fraser <keir@xensource.com> > # Date 1194535934 0 > # Node ID 0ebac857649591de0e1b57605b054552afb03297 > # Parent c0bdfda5183d5e9dca5c9bc7a68a6cf40e3f6c58 > xend: Allow for non-existent xen-python-path binary. > On Solaris, xen-python-path is unnecessary.

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 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''

Hi, every one: I had problem creating domU on diskless device by using xen-unstable. Following, please find out details. BTW, the same configuration works fine on device with hard disk (1) Xen, dom0 kernel and dom0 root file system are loaded/mounted over via eth0 (2) DomU root file system is created in a file-backed virtual block device(VBD). The file-backed VBD locates at some directory on

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

After a recent power cycle of our building, I discovered that the xend pyc files have full paths to the install directory where I built the xen tools. Turns out the xend python process calls stat() on these pyc filenames. In this case, the automounter was broken so the stat() hung and xend failed to start. I was very suprised to see the full path to the dist/install *.py files in the strace

With changeset 6869, I can _not_ start xend. Did anybody else meet the same issue? [root@xin ~]# xend start Traceback (most recent call last): File "/usr/sbin/xend", line 32, in ? from xen.xend.server import SrvDaemon File "/home/xin/work/xmp/xen32-smp/dist/install/usr/lib/python/xen/xend/serve r/SrvDaemon.py", line 30, in ? File

Resent of mail sent on 28.04. xend: fix bug in option parsing If you enable legacy tcp xmlrpc in xend''s config but omit to enable ssl the following backtrace is generated when starting xend: [2010-04-28 16:09:04 15754] ERROR (SrvDaemon:349) Exception starting xend (''NoneType'' object has no attribute ''rfind'') Traceback (most recent call last): File

I''ll step back to Xen stable, because of my network probs with Xen unstable. So I configured and compiled Xen 2.0.6, but I came to the following error after starting Xend: Exception starting xend: ''module'' object has no attribute ''VIRQ_DOM_EXC'' Traceback (most recent call last): File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 302,

Hi there I get the same error, only /usr/lib/python/xen/lowlevel/xu.so does -not- exist I see a dir named /usr/lib/python/site-packages/xen/lowlevel with just one file in it: __init__.pyc even if I do a find -name xu.* from / I get nothing I run Suse 9.3 and kernel 2.6.8-24.14, which seems to be the only way to get Dom0 up under Suse 9.3 for the time being Hints most welcome! Chris

Hi, I am able to get Xend running on Fedora 8 but when I try to create any VM it fails. The xm create osc.cfg throws following error - [root@asds174 vm_images]# xm create osc.cfg Modified arg=osc.cfg stop3 Using config file "./osc.cfg". group_id=None [''create'', ''osc.cfg''] Stop 1 None [''vm'', [''name'',

delete xend entry when destroying pv usb host controller of a guest os which has no pv-frontend driver loaded. -James (Song Wei) Signed-off-by: James (Song Wei) <jsong@novell.com> diff -r f42ff98a2cdc tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py Thu Mar 25 09:32:21 2010 +0000 +++ b/tools/python/xen/xend/XendDomainInfo.py Fri Mar 26 13:27:25

xend: fix LinuxImageHandler debugging output Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r c2472ded5c7c tools/python/xen/xend/image.py --- a/tools/python/xen/xend/image.py Tue Aug 26 15:16:57 2008 +0100 +++ b/tools/python/xen/xend/image.py Tue Aug 26 17:06:09 2008 +0100 @@ -637,8 +637,9 @@ class LinuxImageHandler(ImageHandler): log.debug("ramdisk

After changeset 18030 and 18064 were checked in, I found some issues when creating HVM domains with devices assigned: In XendDomainInfo.py, we have the call trace: the global function create() => vm.start() => _constructDomain(). In _constructDomain(), we invoke xc.test_assign_device() and when the function fails (maybe because iommu=1 is not specified in grub entry since iommu is 0 by