similar to: Bug#706876: xen-utils-common: network-bridge assigns addresses, breaking ifup

Package: xen-utils-common Version: 4.1.4-3 Severity: important Dear Maintainer, Executive summary: dist-upgrade - squeeze to wheezy. Rebooted machine; no default route on network interface eth0. Commented 'transfer_addrs' function in network-bridge produced a machine which worked after reboot. We're using network-bridge as our xen networking configuration. After rebooting the

Package: xen-utils-common Version: 4.0.0-1 Severity: important Tags: patch --- Please enter the report below this line. --- when you use "hardware" virtual machine (with qemu) with xen configured for bridging the network script treates a tap interface and then /etc/xen/scripts/qemu-ifup adds it to the bridge. That would be ok but tap interfaces have a random mac address and the bridge

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

I have seen those documents, I did not see anything that indicates how _automatic_ bridge configuration could be enabled with xl. For my specific set up I have two bridges (xenbr0 -> peth0 & xenbr1 -> peth1). If I have to configure this manually with ifcfg scripts I will, but if an automatic method is provided or is possible with xl I'd prefer to use that. -Gene On Thu, Jan 29,

Package: xen-utils-common Followup-For: Bug #691734 There is some more information in #709103 which I have just merged, however it only shows: Setting up xen-utils-common (4.1.4-3+deb7u1) ... [warn] Starting Xen daemons: (warning). invoke-rc.d: initscript xen, action "start" failed. dpkg: error processing xen-utils-common (--configure): subprocess installed post-installation

Hi folks I forgot to move qemu-ifup to xen-utils-common. So this needs to be done now. Plan. - Upload xen-common today. xen-utils-common includes the qemu-ifup script and replaces xen-utils-3.0-unstable and xen-utils-3.0.2-1 with versions <= current. - Wait five days so both xen-unstable and xen-common can migrate to testing. - Upload xen-unstable and xen-3.0. The utils packages depends

Source: xen Version: 4.4.1-1 Severity: serious Justification: FTBFS Hello, Your package fails to build from source on Debian autobuilder network. Please check your package build logs at: <https://buildd.debian.org/status/package.php?p=xen&suite=sid> install: cannot stat 'debian/xen-utils-4.4.lintian-overrides': No such file or directory debian/rules.real:201: recipe

Package: xen-utils-common Version: 3.0+hg11624-1 Severity: normal Hi, the executable /usr/sbin/xm refers to the man pages xm(1) and xmdomain.cfg(5). As far as I can see, Debian doesn't ship the respective upstream man pages available at http://xensource.com/ . Since Debian packages should ship man pages for executables, it would be a good idea to include those. Thanks, bye, Roland --

Package: xen-utils-3.2-1 Version: 3.2.0-4 Severity: important Tags: patch pygrub uses tools/libfsimage to read a guest filesystem. Unfortunately the grub derived code does not support 256 byte inodes. Grub itself has been patched (see #463236 and #463123) and this patch has now been applied to the upstream Xen tree. See <http://xenbits.xensource.com/staging/xen-unstable.hg?rev/c777e572a467>

Gene, I think you should find the answers in * http://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt (bottom of page) * http://wiki.xenproject.org/wiki/Migration_Guide_To_Xen4.1%2B * http://wiki.xenproject.org/wiki/Network_Configuration_Examples_%28Xen_4.1%2B%29 * http://wiki.xenproject.org/wiki/XL_vs_Xend_Feature_Comparison may also be relevant If not, circle back to the list and I am sure

Package: xen-utils-common Version: 4.1.3-8 Severity: important When antispoof is set to 'on', the vif-common script does not create an ALLOW firewall rule for the emulated vif devices. This means that HVM nodes, unless a Xen PV driver is installed and running, cannot access the external network. The vif-common script creates an ACCEPT entry for the normal vif device (e.g. vif4.0) but not

Package: xen-utils-common Version: 4.3.0-3 Severity: normal Dear Maintainer, I've just set up a fresh Jessie system using the installer dated 2014-03-05, then installed and enabled Xen 4.3. I've done this quite a few times before using Wheezy and 4.1. I set up xenbr0, then created a test domU using xen-create-image, which completed without issue. However I was unable to start the new

Package: xen-utils-common Version: 4.1.3-2 Severity: important IMPORTANT NOTE: This bug has been generated using reportbug run from a debian stable system. The affected debian testing systems are isolated in a lab and do not have internet access. The issue is wholly reproducible on several different debian testing installations. xen-utils-common fails to install if xen cannot be started.

Package: xen-utils-common Severity: normal When setting (network-script network-bridge) in the xen config, restarting xen will result in error messages like: /etc/xen/scripts/network-bridge: line 219: brctl: command not found /etc/xen/scripts/network-bridge is part of xen-utils-common which doesnt depend or recommend the bridge-utils package which contains brctl.

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Hi guys, Just a couple of things I noticed running through /usr/share/doc/xcp-xapi/README.Debian.gz as referenced by http://wiki.debian.org/XCP In "4/ Configuring Xen and XCP": sed -i "s/TOOLSTACK=/TOOLSTACK=xapi/" /etc/default/xen should be sed -i "s/TOOLSTACK=.*/TOOLSTACK=xapi/" /etc/default/xen Otherwise

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal Tags: squeeze I have 3 VM running. I have upgraded debian squeeze to 6.0.1 (new kernel package 2.6.32-31) and restarted my server. VM were still running. After reboot I could not start xend service (from init.d). I got following errors: kern.log: Mar 22 15:07:30 router kernel: [53888.212756] xenstored[7232]: segfault at 7fff056b5ff8 ip

Control: tag -1 +patch (experimenting with http://www.donarmstrong.com/posts/control_at_submit/ ...) Hi Thomas, I think it is as simple as the following, which works for me with xl and xm. Does it work as you expect/want with xe? Ian. >From 88f10bc8dbf96dd2c32f12259249f8be70fd01a4 Mon Sep 17 00:00:00 2001 From: Ian Campbell <ijc at hellion.org.uk> Date: Thu, 19 Jul 2012 16:19:09

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)

Source: xen Version: 4.5.1~rc1-1 Severity: wishlist Tags: patch http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2015-June/006206.html suggests that we are prone to "loosing" bugs as the package versions change since they include the Xen version. To avoid this we can ship a reportbug control file to redirect those bugs to src:xen, which the attached patch does. I went with