similar to: xend and xen-tool crashed after intensive operation

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

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important When starting (or migrating in) a domain, sometimes I get the following exception: [2014-04-01 10:58:08 4821] ERROR (XendDomainInfo:2927) XendDomainInfo.initDomain: exception occurred Traceback (most recent call last): File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2914, in _initDomain

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

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

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-4.0 Version: 4.0.1~rc6-1 Severity: important Issue confirmed with xen-utils-4.0 (4.0.1~rc6-1) in Debian Squeeze AMD64. Trace of error while using xm-debian.cfg (attached): [2010-09-02 00:53:21 1407] ERROR (xmlrpclib2:178) Internal error handling xend.domain.create Traceback (most recent call last): File "/usr/lib/xen-4.0/lib/python/xen/util/xmlrpclib2.py",

Hi all, I just compiled an installed the Xen Hypervisor, Tools and a new Kernel from the 3.1 source. The dom0 is running without problem and the xm seems to work fine, too (tried xm info, xm list, xm dmesg). Unforunately on creation of a domU I always get an error using a config file and a domU image that is definitley working (at least with 3.0.4): Using config file

Hi, I have set up an ubuntu edgy guest domain on a fiesty host domain. The installation was successful but on running xm create -c baseimage, I get the following error message: Error: (22, ''Invalid argument'') The problem seems very similar to the one here: http://lists.xensource.com/archives/html/xen-users/2007-07/msg00361.html but I''m not able to figure out what the

Hello, I''m using Xen (installed from source - "hg clone http://xenbits.xen.org/xen-4.0-testing.hg") on Debian Lenny. Dom0 kernel is 2.6.32-bpo.5-xen-686. Until now I have successfully ran the Lucid Ubuntu as domU guest, defining disks as (and also as file:): disk = [''tap2:aio:/home/xen/domains/lucid/disk.img,xvda1,w'',

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).

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

When a domain is in the process of shutting down there is a small window when the domain is known to XenD, but it will be unable to form an SXPR for it due it being in the middle of device hot-unplug. This causes the ''xm list'' command to totally fail with an error like # xm list Error: Device 0 not connected Usage: xm list [options] [Domain, ...] List information about all/some

Hello, i have two xen hosts servers configured to support migration of domus, but when i try to migrate, the command never ends, i can see on the remote server the machine with xm list but the machine is not accesible, and on the own server i see migrating-{machine_name} and i have access to it. Every server have one nic, with public ip (that is using with xenbr0), and i have a virbr0 configured

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

Hi all, I downloaded the xen 3.3.0 and now testing the pci pass-through with the NIC. Using late binding, the pci slot 0000:08:01.0 is assigned to pciback. But pci related xm commands are not working. For eg: linux-242:/home/xen-3.3.0 # xm pci-list-assignable-devices Unexpected error: <type ''exceptions.OSError''> Please report to

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

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

Hi, I have a problem that I can't solve it: the hvm-guest don't start (same image works under Xen 4.01 on another machines). Further I'm confust, because I had to use xm instad of xl. A PV-guest works fine. I start it with 'xm create jessie'. Some data you can see down. What further information do you need? vg. ------------------------------------------------- call with