similar to: Bug#588888: create fails

Package: xen-utils-common Version: 4.0.0-1 Severity: wishlist Tags: patch I am not a gawk/mawk expert, but I looked carefully at the few uses of gawk that I saw in /etc/xen/scripts/vtpm-common.sh and network-bridge, and I did not see anything that was gawk-specific. It would be nice if they could be changed to awk and the dependency on gawk removed. base-files is Essential: yes and it

Package: xen-utils-common Version: 4.0.0-1 Severity: normal This is an offshoot of Bug#588888, but is really a separate issue. It appears that with hvmloader, the disk device names presented to the vm must by from a specific set that hvmloader knows how to emulate. Names like hd[a-c] and sd[a-c] work, but sr0 does not. While this makes sense, when you think about what hvmloader is doing, it is

Package: xen-utils-common Version: 4.0.0-1 Severity: normal Tags: patch do_ifup() in network-bridge exits badly, if the interface doesn't have a default gateway. Since it's wrapped in xen's locking script it causes it to be retied 100 times and sleep for 95 seconds before it continues. In my setup this amounts to: 16 vlans without a default gateway * 95 secs / bridge = 25 minutes

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: 4.0.0-1 Severity: important The xm utility requires python-xml but the package does not depend on it. # xm new --help_vars Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-4.0/bin/xm", line 8, in <module>

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

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

Fix config file parsing for VMX domains. If we define "vif" in the config file, image.py will raise error "vmx: missing vbd configuration". The reason is "vif" is dealt with as a "vbd" device. This patch fixes this issue by dealing with "vbd" and "vif " separately, removing "macaddr" arg and parsing mac address from

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: important When Xen is configured in routed mode, restarting xend fails because the script hotplugpath.sh is missing. Please see below for more information. *** root at eliott:~# /etc/init.d/xend restart Restarting Xen daemons: xend/etc/xen/scripts/network-route: line 20: /etc/xen/scripts/hotplugpath.sh: No such file or directory

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: important If using ethernet bonding and network-bridge with xen the network-bridge scripts breaks the network. I have run through the commands manually in irder to establish the culprit. In the op_start function (Starting on line 214) everything is fine up until line 251. At this point the bridge has been created, devices renamed and the

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: 4.0.0-1 Severity: normal After upgrading xen-utils-common from 3.4.2-4 to 4.0.0-1, I could not create a guest domain defined with a DRBD file type. The xm create command would fail with "Error: Device 51713 (vbd) could not be connected. Hotplug scripts not working.". After some research I realized the /etc/xen/scripts/block-drbd helper script was

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

Device model path cleanup. Remove bochsrc which is no longer needed. Signed-off-by: Arun Sharma <arun.sharma@intel.com> --- a/tools/examples/xmexample.vmx Thu Jun 30 18:41:11 2005 +++ b/tools/examples/xmexample.vmx Thu Jun 30 18:59:08 2005 @@ -89,10 +89,10 @@ # New stuff -device_model = ''/usr/bin/qemu-dm'' +device_model = ''/usr/lib/xen/bin/qemu-dm''

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal I cannot find a use the network-nat and vif-nat provided in the general case, where I'd like to NAT between vifx.0 and ethx interfaces. I have setup the following in /etc/xen/xend-config.sxp : ## Use the following if network traffic is routed with NAT, as an alternative # to the settings for bridged networking given above.