similar to: Bug#744163: xenstore problems

*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

I am running xen 3.2-1 (Debian 3.2.1-2) on Debian Lenny (2.6.26-2-xen-amd64 #1 SMP Wed Mar 10) on two identical production systems. This morning on one of the systems, xentop stopped displaying. Running xentop results in: unable to open xenstore : Connection refused Failed to initialize xenstat library xm list: Error: (9, ''Bad file descriptor'') xm dmseg: Error: Subcommand

Dom0 = centos 5 (32bit), 4GB Ram DomU = centos 5 (PV) (32bit) xen 3.1.2 rc1, compiled using XEN_TARGET_X86_PAE=Y kernel 2.6.18, modified to load areca card drivers initrd image created using the following command mkinitrd -v -f --with=aacraid --with=arcmsr --with=sd_mod --with=scsi_mod initrd-2.6.18-xen.img 2.6.18-xen When i issue xm create for a domU which was working earlier i get the

Package: xen-utils-common Version: 3.0.3-0-2 Severity: important I have installed all the packages I can think of to get Xen going and it still fails with the following : /var/log/xen/xend-debug.log: Exception starting xend: (111, 'Connection refused') er.py", line 463, in process_request_thread self.finish_request(request, client_address) File "SocketServer.py",

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

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

Package: xen-utils-4.1 Version: 4.1.1-3 I have an HVM domU which was created with xen-utils-4.0 (and Xen 4.0 hypervisor of course). Recently I've upgraded to Xen 4.1 and xen-utils-4.1, but after a reboot I was unable to do anything with it: "xm start" caused "Domain is already running" error, while "xm shutdown" simply hadn't printed any error messages, only

Package: xen-utils-common Version: 3.3.1-1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh

I am seeing xend error on OpenSUSE 11.4, Has anyone else seen this ? Thanks Ranjith #uname -a Linux linux-ws7h 2.6.37.6-0.7-xen #1 SMP 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux #/var/log/xen/xend.log 2011-08-09 14:36:38 21111] ERROR (SrvDaemon:349) Exception starting xend ((111, ''Connection refused'')) Traceback (most recent call last): File

Package: xen-utils-common Version: 3.3.1-1 ck-a800:/home/kkadmin# /etc/init.d/xend start Starting XEN control daemon: xenstored xenconsoled xendFATAL: Failed to initialize dom0 state: Invalid argument . failed! xend.log [2009-07-12 06:55:40 15120] INFO (SrvDaemon:331) Xend Daemon started

Hi, I have recompiled xen-3_3.4.3~rc3-1 in Lenny, together with the 2.6.32-10 kernel. While my dom0 boots without issue under Xen, xend refuses to start. I have cut/past my xend.log is bellow. Is there any reason why a backport of this version of Xen wouldn't work in Lenny? Should I try the already compiled SID binaries in Lenny without trying to build myself? Cheers, Thomas When I start

Package: xen-utils-3.0 Version: 3.0.2+hg9656-1 Severity: grave Justification: renders package unusable When xend starts: [2006-05-22 22:07:18 xend] INFO (SrvDaemon:278) Xend Daemon started [2006-05-22 22:07:18 xend] INFO (SrvDaemon:282) Xend changeset: Thu Apr 27 09:58 :50 2006 +0100 . [2006-05-22 22:07:18 xend] ERROR (SrvDaemon:292) Exception starting xend ((111,

Hi there. I cannot start xen, I''m getting this error System: Linux netwarrior 2.6.31.13 #5 SMP Wed Jun 30 13:25:47 ART 2010 x86_64 AMD Athlon(tm) II X4 630 Processor AuthenticAMD GNU/Linux xend.log le "/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xstransact.py", line 355, in Mkdir complete(path, lambda t: t.mkdir(*args)) File

Hey everyone, I''m trying to write a simple python program in dom0 that registers a watch on the xenstore to determine when a domU has shutdown. Is there a particular token I should use? Looking through the tools/python/xen/*.py code, I''ve come across the ''control/shutdown'' token... seems promising? My code is attached below. As is, if fails to call the

Hi all, This is my first post to the list. My first real major issue with xen. I started on 3.4.2 and upgraded to 4.0.1 without issues. Now I just attempted to go to 4.1.0 and I got the following errors in my log. # cat /var/log/xen/xend-debug.log Xend started at Fri Apr 1 13:51:15 2011. cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat:

Xen Version: 4.2.0 Linux Kernel Version: 3.2.30 OS: Debian 6.0 Sometimes when trying to reboot a VM, the reboot fails with the following message in xend.log: Has anyone experienced this issue before, know the cause and/or fix? This is an HVM VM. Device model is set in the configuration file device_model = ''/usr/lib/xen/bin/qemu-dm'' We use the same configuration file with

Hi Orazio, Is "NoneType object is unsubscriptable" the full and complete error message? I'd have expected some sort of accompanying backtrace, if not on the console then in /var/log/xen/* Is this issue by any chance fixed by installing the xen-qemu-dm-4.0 package? Lastly, does this happen with the packages from Wheezy? Thanks, Ian.

Hello: I just gave 3 tries at compiling a xen kernel. I managed to get the networking in the host to work ok on the third try, unfortuately xend gives me the following errors in my xend.log and will not start. Any ideas? It fails to start with the following error ---------------------------------------------------- /usr/sbin/xend [root@localhost ~]# /usr/sbin/xend start Traceback (most recent

Hi all, I''m a total xen-newbie ... I''ve installed xen-3.0-testing from source. (http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-3.0-testing-src.tgz). I''ve followed the intruction for the installation, dom0 work fine and domU start up without problem !!! Now, I''ve tryed to migrate the domU to another dom0 machine but I receive this error on the

Package: xen-utils-3.2-1 Severity: important Hello! When using xenapi.PBD.create() the following error occurs: xen.xm.XenAPI.Failure: Internal error: global name 'genuuid' is not defined. (Attached you can find the logging of the remote host.) This (and other syntax errors) are already fixed in the xen-unstable.hg (see http://xenbits.xensource.com/xen-unstable.hg?rev/7fd49c55c0b0).