similar to: Bug#578252: xen-utils-common: documentation/examples contain obsolete and wrong kernels name

Package: xen-utils-common Version: 3.4.2-4 Severity: important File: /usr/lib/xen-common/bin/xen-utils-wrapper xm invoke vtpm-common.sh from /etc/xen/hotplug, wich one call gawk, but gawk is not listed as dependence for xen packages. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux

Package: xen-utils-common Version: 3.2.0-2 Followup-For: Bug #519064 I've experienced the same problem (missing /var/lib/xen/save) on one host, but had no problem on another. Some investigation showed that /var/lib/xen/save gets created on some actions like a reboot whith a suspend/resume cycle. This problem will thus not be reproducable on quite some hosts, but is a real bug. The simplest

Package: xen-utils-common Version: 4.0.0-1 Severity: minor Tags: patch /etc/xen/scripts/block doesn't properly enclose $file in quotes for two out of three stat calls, which causes the script to fail on files which contain special characters (i.e. spaces) in their filename or pathname. See attached for patch. -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT

Package: xen-utils-common Version: 3.2.0-2 Severity: normal When I was trying to migrate (xm migrate) a guest from one host to another, it simply fails. On the source host the virtual machine gets destroyed without any warning message - on the destination host I see the following error message in /var/log/xen/xend.log [2009-03-10 08:01:22 9846] ERROR (XendCheckpoint:52) read_exact: EOF trying

Package: xen-utils-common Version: 3.2.0-2 Followup-For: Bug #511579 My system is a Dell PowerEdge SC1435. As most of the servers of this category, it comes with 2 network interfaces. Both based on a Broadcom Corporation NetXtreme BCM5721 chip, set up via tg3 module. Does multiple NIC's triggers the bug? This link helped me a lot: https://systemausfall.org/wikis/howto/XenUpgrade3.2 --

Package: xen-utils-common Version: 3.4.2-3 Followup-For: Bug #571634 I can confirm that this bug not only exists in the current version but that it makes a DomU which forwards packets unusable. Other "simpler" DomUs which do not forward work perfectly. -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (1000, 'stable'), (100, 'testing')

Package: xen-utils-common Version: 4.0.0-1 Severity: normal Hi, I think would be good to have a note in manpage about this issue. Will save time to many people which will search about xmlproc in squeeze. --- xm.1.orig 2010-08-31 11:02:15.393343178 +0200 +++ xm.1 2010-08-31 11:05:25.978339569 +0200 @@ -466,7 +466,9 @@ .RE .IP "\fBnew\fR \fIconfigfile\fR [\fI\s-1OPTIONS\s0\fR]

Package: xen-utils-common Version: 4.0.0-1 Severity: normal When a qemu hvm with vif=['type=ioemu,bridge=eth0'] is created, xen will successfully create the required vif and tap bridge interfaces, but will create the corresponding iptables filter rules for the vif interface only, not the tap interface. With a FORWARD policy of DROP (e.g. by enabling antispoofing) network traffic from/to

Package: xen-utils-common Version: 4.0.0-1 Severity: important Xen domains should be shutdown before iSCSI if that is installed. This can be accomplished by adding the following to /etc/init.d/xendomains: # Should-Start: iscsi # Should-Stop: iscsi -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64)

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

Package: xen-utils-common Version: 3.4.2-3 Severity: minor Hi, I've just noticed that the xen-utils-common package instals the file xen-backend.rules both under /etc/udev/xen-backend.rules and /lib/udev/rules.d/xen-backend.rules I think the flormer is useless and is installed there by mistake. Kind Regards, Marco -- System Information: Debian Release: squeeze/sid APT prefers unstable

Package: xen-utils-common Version: 4.0.0-1 Severity: important Xen domains should be shutdown before iSCSI if that is installed. This can be accomplished by adding the following to /etc/init.d/xendomains: # Should-Start: iscsi # Should-Stop: iscsi -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64)

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

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:

Package: xen-utils-common Version: 3.2.0-2 Severity: wishlist Hi, It would be very useful it /usr/bin/pygrub was available -- it should be a symlink (or wrapper) that points to the real version in the Xen hypervisor. That would mean that the domain configuration for xen domains could be (relatively) static when upgrades are occuring between hypervisor versions. Thanks, Anand -- System

Package: xen-utils-common Version: 3.2.0-1~bpo4+1 Severity: normal -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-xen-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xen-utils-common depends on: ii lsb-base

Package: xen-utils-common Version: 3.4.2-4 Severity: normal Tags: patch xen-version does not include the "extra" component, only major.minor. This keeps makes /etc/init.d/xend bail out with xen 3.2-1 from lenny. patch attached. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (600, 'testing'), (600, 'stable'), (500,

Package: xen-utils-common Version: 4.0.0-1 Severity: normal Tags: squeeze The host runs (at the time of testing) a single linux-x86 domu (128MB, 1VCPU). When issuing a reboot, everything looks as expected: - domu is saved - xend is stopped - drbd stopped - lvms unmounted - md0..4 stopped and the message "rebooting now" appears, but nothing happens until "INFO: task xenwatch is

Package: xen-utils-common Version: 4.0.0-1 Severity: important The script /etc/xen/scripts/block contains an error in the part which is checking the sharing of the already created loop devices. This error leads in the case of somespecific file inode values to the wrong report of the loop device as being already used and causes then the domain could not be started with such device at all, there

Package: xen-utils-common Version: 4.0.0-1 Severity: normal Hi, On system shutdown the 'xendomains' script appears to detect wrong guests: | Stopping libvirt management daemon: libvirtd. | Clearing ebtables rulesets: filter nat broute done. | Shutting down Xen domains: bev-d6x02(save).Error: Domain '1024' does not exist. | !(shut).Error: Domain '1024' does not exist. |