similar to: Loss of hypervisor control - xm, xentop

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

*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

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

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

This patch fixes the problem with xentop where it returns an exit code of 0 when passing it invalid options when it should return 1. The issue comes from getopt() returning ''?'' and the case from switch matching it. The solution was to remove the case ''?'' so that the default match could be triggered. Quote from `man 3 getopt` "If getopt() does not

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

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

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,

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

Hardware: blade HS20 on RHEL4 U1 base kernel. # hg tip changeset: 6811:a8edb2655c5d220b1bbf2b8d8415aae0ac136da3 tag: tip user: cl349@firebug.cl.cam.ac.uk date: Wed Sep 14 10:47:48 2005 summary: Add methods to read/write Vm/Domain store entries. I created domU and got the messages: # xm create -c vm2.cfg Using config file "vm2.cfg". Started domain

Hello, I noticed that the CPU% reported by xentop appears to be too high. With dom0 idle xentop is reporting between 14-17% CPU utilization while at the same time top in dom0 is reporting 1-4% CPU utilization. I see that the TODO for xentop includes a task to make CPU% more accurate but looking at the code for xentop and libxenstat I''m not sure how to go about this. Assuming the CPU

# HG changeset patch # User john.levon@sun.com # Date 1172534164 28800 # Node ID 37fce3c0c10baee370ecc39b6a50fed8b232bd69 # Parent 4998793aa87729fbe8a582faa3a22c9ecfefe13c Fix for Solaris compile/output for VBDs in xentop. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/xenstat/xentop/xentop.c b/tools/xenstat/xentop/xentop.c --- a/tools/xenstat/xentop/xentop.c +++

This patch make xentop output statistics about both blkback and blktap. And, xentop also display back-end driver type in detail view mode. # HG changeset patch # User s-uchida@ap.jp.nec.com # Date 1180665749 -32400 # Node ID 1b36d6f6c7a98728382de93ee23c8c97b0b95dbd # Parent 1768a89bb87824249827d935d7803d8193bdeb05 XENTOP: Displaying blktap information. Signed-off-by: Satoshi UCHIDA

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

Package: xen-utils-common Version: 3.0.3-0-2 Severity: wishlist Tags: patch Currently when hostnames are wider than 10 chars, the xentop output is messed up. Please add the following patch to support up to 20 chars, or better yet, allow the columns to auto size :) #! /bin/sh /usr/share/dpatch/dpatch-run ## xentop-name-width.dpatch by <apeeters@lashout.net> ## ## All lines beginning with