similar to: Bug#404078: "/etc/init.d/xend" wrongly shows /etc/init.d/xen-utils

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal There should be a clean and clearly defined way to restart all the Xen daemons in the case of error. If the file /var/lib/xenstored/tdb is corrupt then you must stop xenstored, rm the file, and then restart it. Currently there is no defined way of doing this so the solution is to kill -9 the process, rm the file, and then reboot. --

Package: xen-utils-3.4 Version: 3.4.0-2 Severity: normal Hi, the variable $DAEMON in /etc/init.d/xend is not set and thus the init.d/-script is not usable. I think it's supposed to be $XEND. Any ideas on that one? regards, Patrick -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux

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: 3.4.2-1 Severity: important File: /etc/init.d/xend Tags: patch Hello, /etc/init.d/xend assume xenfs is present and doesn't start xend if not. This dirty patch makes xend start and XEN being operationnal with old flavour xen kernels. I use 2.6.31.5 with forwarded ported Xen 2.6.18 dom0 kernel patch but it should work with debian's 2.6.26 ---

More details : I noticed that every start of xend is adding the POSTROUTING masquerade iptables rule, and nothing is done at stop time. This should bi fixed, at least. -- Olivier BERGER <olivier.berger at int-edu.eu> (ATTENTION : new address) Ing?nieur Recherche - Dept INF GET/INT at Evry (http://www.int-edu.eu/) OpenPGP-Id: 1024D/6B829EEC

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

Package: xen-utils-common Version: 3.3.1-2 Tags: patch xend_stop currently fails because the script defines $XEND rather than $DAEMON. --- xen-common/debian/xen-utils-common.xend.init +++ xen-common/debian/xen-utils-common.xend.init @@ -49,8 +49,8 @@ xend_start() xend_stop() { - $DAEMON status || return 0 - $DAEMON stop || return 1 + $XEND status || return 0 + $XEND stop || return 1 }

Package: xen-utils-common Version: 4.0.0-1 Severity: normal A strange issue, when deploying Xen using Puppet, /etc/udev/rules.d/xend.rules and /etc/udev/rules.d/xen-backend.rules files are empty. Specifically, the symlinks point to ../xend.rules and ../xen-backend.rules respectively in /etc/udev, but neither of those files exist. Manually copying those files from another host that was not

Package: xen-utils-common Version: 3.0.3-0-2 Severity: important patch I ran into this problem when using xen on Debian/Etch. I have several virtual xen instanses, and I name them using their fully qualified DNS domain name. These machines have failed to start automatically when I booted the host machine, and I just recently found out why. During shutdown, I was messages like this: Error:

Package: xen-utils-common Version: 4.0.0-1 Severity: important When xen domUs are saved by running /etc/init.d/xendomains stop the memory images are saved world readable, so that every user on the system can read the memory dumps. The default mode of /var/lib/xen/save is 755, vm images are saved with mode 755. At least the save directory shoudn't be world readable. -- System Information:

Subject: xen-utils-common: /etc/init.d/xen restart fails when using network-bridge if netdev does not match eth[0-9+] Package: xen-utils-common Version: 3.1.0-1 Severity: normal *** Please type your report below this line *** On a machine where the NICs are named something other than ethN, and using (network-script 'network-bridge netdev=XXX') (where XXX is the name of one of these

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-common Version: 3.2.0-1~bpo4+1 Severity: minor I use the version from backports, but it's still present in sid. In /etc/xen/xend-config-sxp : #(xen-tcp-xmlrpc-server-address 'localhost') #(xen-tcp-xmlrpc-server-port 8006) should be #(xend-tcp-xmlrpc-server-address 'localhost') #(xend-tcp-xmlrpc-server-port 8006) Small typo in a commented line, but

I have a disk image file that was created using dd, makereiserfs dance, operating system files copied in directly with cp -ax (vi a temporary mount, and then dismounted). My domU configuration is as follows: -------------------------------- kernel = "/RAID/data/xen/bootsles10/vmlinuz-xen" ramdisk = "/RAID/data/xen/bootsles10/initrd-xen" memory = 2048 name =

Is anybody using dovecot on RHEL 3? I'd sure appreciate an init script for it. Thanks! Ben

I have another problem, but I have found a work around. However, I don't know why it works. I was hoping someone could help. With some help from some previous people on the list, I have my CentOS 4 install to work. I had some previous problems with PCMCIA freezing which was caused by my video card. The next thing to freeze was /etc/rc.d/init.d/xfs. My first work around was to linux

I have been stepping into pand. There is nothing I can find on this list about getting pand working. There are some instructions on wifi.bluez.org that seem to be redhatish, but.... I have edited /etc/sysconfig/pand: PANDARGS='--listen --role GN --master' I have created a /etc/sysconfig/network-scripts/ifcfg-bnep0: DEVICE=bnep0 BOOTPROTO=none ONBOOT=no IPADDR=192.168.201.101

Any hope to have it fixed soon? This bug messes up the boot and shutdown sequence for those using dependency based boot sequencing.

Hello, Upon trying to install 3.0.2, after executing install.sh, all of the system''s /etc/init.d/* scripts are gone. Only /etc/init.d/xend and /etc/init.d/xendomains remain. Thanks, Brian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This tripped me up recently too, but i found i needed a different patch: 0 aesop:~# diff -u /etc/init.d/xendomains{.orig,} - --- /etc/init.d/xendomains.orig 2007-04-18 12:04:04.000000000 -0400 +++ /etc/init.d/xendomains 2007-04-18 13:00:28.000000000 -0400 @@ -128,9 +128,9 @@ parseln() { - - name=`echo "$1" | cut -c0-17` +