similar to: RFC: making the xen startup integrate better with distros

*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

Package: xen-utils-common Version: 4.4.1-2 Severity: normal For correct operation under SE Linux the start script needs to assign correct security labels to firectories it creates. Note that restorcon doesn't cause any problems if run twice. If it's executable then you can safely run it. Below is a patch that demonstrates how to solve this problem. --- xen.old 2014-10-12

Package: xen-utils-common Version: 4.0.0-1 Severity: important After running modules_setup you need to have the following line: [ -x /sbin/restorecon ] && /sbin/restorecon -R /dev/xen The reason is that the module load causes the kernel to create device nodes in the devtmpfs. This bypasses the udev code for labelling the device node and results in xenstored being unable to access

Package: xen-utils-common Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 Severity: important Please modify the init scripts in a manner similar to the following to give the correct SE Linux labels. Failing to correctly label them may result in Xen not working correctly when SE Linux is enabled. --- /etc/init.d/xen.orig 2012-06-24 10:29:04.000000000 +1000 +++ /etc/init.d/xen 2012-06-24

Package: xen-utils-common Version: 4.3.0-3 Severity: normal Dear Maintainer, * What led up to the situation? I upgraded my server from squeeze to wheezy and then to jessie. Server is Intel S3200SHV m/b with Intel(R) Core(TM)2 Quad CPU. I'm pretty sure that before that it was running whatever came before squeeze, I forget the name. I was trying to get xen_pciback to work, so I

Package: xen-utils-3.4 Version: 3.4.3~rc6-1 Severity: important blktapctrl isn't started by default. If blktapctrl isn't started then none of the tap: disks (eg tap:aio) work. This functionality has been removed in tools-misc-xend-startup.diff @@ -120,24 +86,14 @@ if not sys.argv[1:]: print 'usage: %s {start|stop|reload|restart}' % sys.argv[0] elif

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1336153082 -7200 # Node ID 9a430b7e2df2893f7f4f75d10e66d52bdffa7efa # Parent 113fd57259b91af06a5352404dd94b484a98d2bc tools/hotplug: remove 4 from default runlevel in xen-watchdog, xend and xendomains Similar to what changeset 24847:0900b1c905f1 does in xencommons, remove runlevel 4 from the other runlevel scripts. LSB defines

Hi all, I have some serious problems making Xen run. I have spent a couple of days looking in Google and trying a lot of different things, but none of them has worked. I hope you can help me... First of all: xen was running smoothly on my machine, but suddenly (I think I haven''t changed any configuration) it doesn''t work anymore. I am using a Debian 4.0 with Xen 3. When

Processing commands for control at bugs.debian.org: > reassign 628912 xen-utils-common 4.0.1-2 Bug #628912 [xen-utils-4.0] xenconsoled and xenstored stopping unhandled by init script Bug reassigned from package 'xen-utils-4.0' to 'xen-utils-common'. No longer marked as found in versions xen/4.0.1-2. Ignoring request to alter fixed versions of bug #628912 to the same values

Package: xen-utils-4.0 Version: 4.0.1-2 Hi, When you change XENCONSOLED_ARGS in /etc/default/xend, there's no normal way to apply it. Even if you do '/etc/init.d/xend stop', that doesn't stop xenconsoled, despite the fact the analogous 'start' action did start it. There isn't even a separate init script action to stop it, it has to be killed manually. Same goes for

As any other daemon, I''d assume it should be possible to restart xenstored (i.e. if it crashed or if, during development, a fix was made to it that needs to be tested). However, as I learned after over a day of digging, things don''t work anymore after doing so: Since the watches are transient, they''re lost with the daemon going away. Right now I specifically need this in

This fast-track covers the SMF-related changes for dom0. This is a final draft, so any comments by the end of the week please... Man pages are attached. thanks john SMF services for Xen 1. Introduction This case introduces the SMF services used by a Solaris-based domain 0 when running on Xen, or a Xen-compatible hypervisor. All of these services only run on domain 0 when booted

hi, > xm list Error: Unable to connect to xend: Connection refused. Is xend running? > xend restart <complete''s with no complaints> however in /var/log/messages I get Apr 14 16:18:42 tiger BLKTAPCTRL[6058]: xs_daemon_open failed -- is xenstore running? > xenstored FATAL: Failed to initialize dom0 state: Invalid argument full talloc report on

Hi All I am using xen 3.3.0 version and I want to start network virtual interface on Dom U by using the following command # xend start *************************************************************** *************************************************************** ** WARNING: Currently emulating unsupported memory accesses ** ** in /lib/tls glibc libraries. The emulation is

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Hi, # ps awux | grep /usr/lib/xen <nothing> # /etc/init.d/xend start Starting XEN control daemon: xend. # /etc/init.d/xend stop Stopping XEN control daemon: xend. # ps awux | grep /usr/lib/xen root 29826 0.2 0.1 2160 848 ? S 09:37 0:00 /usr/lib/xen-3.2-1/bin/xenstored --pid-file /var/run/xenstore.pid root

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

hello all, it''s my first time ever with xen (or even virtualization in general). I installed Xen 3.2 on top of a Debian Lenny kernel 2.6.26-2-686 via apt-get. Boot options are: title Xen 3.2-1-i386 / Debian GNU/Linux, kernel 2.6.26-2-xen-686 root (hd0,0) kernel /xen-3.2-1-i386.gz dom0_mem=512000 module /vmlinuz-2.6.26-2-xen-686 root=/dev/mapper/athena-root ro console=tty0 module

Package: xen-utils-3.0 Version: 3.0.2+hg9697-2 Severity: wishlist Hi, it would be nice to run xend under the supervision of runit. xenconsoled and xenstored already provide relevant switches (-i and --no-fork). Thanks Andras -- Andras Korn <korn at chardonnay.math.bme.hu> <http://chardonnay.math.bme.hu/~korn/> QOTD: Paranoid: someone

-------- Исходное сообщение -------- Тема: Fwd: bug on create domain0 Дата: Mon, 04 Apr 2011 14:54:13 +0600 От: net administrator Отвечать: tkpiuk@gmail.com Кому: xen-devel@lists.xensource.com -------- Исходное сообщение -------- Тема: bug on create domain0