similar to: Bug#390927: xen-hypervisor-3.0.2-1-i386: Xen kernel panics when booting

Package: xen-3.0 Version: 3.0.2-3+hg9762-1 Severity: wishlist There was an error while trying to autobuild your package: > Automatic build of xen-3.0_3.0.2-3+hg9762-1 on caballero by sbuild/ia64 85 > Build started at 20060922-0812 [...] > ** Using build dependencies supplied by package: > Build-Depends: debhelper (>= 5.0.37.2), libcurl3-dev | libcurl-dev, python-dev, python

Package: xen-hypervisor-3.0.2-1-i386 Version: 3.0.2-3+hg9762-1 Severity: normal xm fails to find xen-utils, the error apears with other parameters, such as xm create. The error also apears when running "/usr/lib/xen-common/bin/xen-utils-version". Best Regards /Lars Staun Knudsen #xm list WARING! Can't find version 3.0.2-3-1 of xen utils, fallback to default version! Name

Package: xen Severity: important Tags: security Justification: user security hole Hi, This issue is still unfixed in Wheezy: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-2625 Patch: http://xenbits.xensource.com/hg/xen-unstable.hg/rev/60f09d1ab1fe Cheers, Moritz

Package: xen-utils-common Version: 3.4.2-2 Severity: important The network setup uses not longer supported iptables operations: | physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. -- Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, "Day of the Dove", stardate

Package: xen-hypervisor-3.0-unstable-1-i386-pae Version: 3.0-unstable+hg11561-1 It's great having a pae hypervisor packaged for debian, but it'd be a lot more useful with a pae kernel seph

Package: xen-docs-3.0 Version: 3.0.3-0-2 The PDF's are gzipped. As there is no PDF reader that can open such files, the process to get to read the docs is quite complicated. I doubt this package is useful that way. Then it's faster to lookup the docs on the net. To make it useful, please don't zip the files. Henning

Package: xen-utils-common Version: 3.2.0-2 In network bridge, IP addresses of ${netdev} are correctly transferred to ${tdev} which later is renamed to ${bridge} (by default = ${netdev}). But then there is ifup ${bridge} which sets up again the network configuration for ${bdrige}/${netdev} and aliases (e.g. eth0:1 defined in /etc/network/interfaces) are loosed. Regards, Ognyan Kulev

package: xen-3 version: 3.4.2-2 severity: important tags: security hi, your package embeds source code from both qemu, which makes security updates very cumbersome, difficult, and potentially error-prone. please update your package to make use of the existing packages if possible. thanks for your attention on this matter. best wishes, mike

package: xen-unstable version: 3.3-unstable+hg17961-1 severity: important tags: security hi, your package embeds source code from both qemu, which makes security updates very cumbersome, difficult, and potentially error-prone. please update your package to make use of the existing packages if possible. thanks for your attention on this matter. best wishes, mike

Package: xen Severity: grave Tags: security Justification: user security hole Please see the following links: http://www.openwall.com/lists/oss-security/2012/09/05/11 http://www.openwall.com/lists/oss-security/2012/09/05/10 http://www.openwall.com/lists/oss-security/2012/09/05/9 http://www.openwall.com/lists/oss-security/2012/09/05/8 http://www.openwall.com/lists/oss-security/2012/09/05/7

Package: xen-utils-3.2-1 Version: 3.2.0-3~bpo4+2 Severity: normal Hi, pygrub has problems parsing block devices partitioned with Lenny Beta 2 and ext3 on paravirt guests: # /usr/lib/xen-3.2-1/bin/pygrub /var/lib/xen/images/test2.img Traceback (most recent call last): File "/usr/lib/xen-3.2-1/bin/pygrub", line 653, in ? chosencfg = run_grub(file, entry, fs) File

Package: xen Version: 4.0.1-1 Severity: serious User: debian-python at lists.debian.org Usertag: python2.6 The package build-depends on python2.5-dev, which is not the default python version for squeeze. The package should be rebuilt with python2.6, either build-depending on python-dev (recommended) or python2.6-dev.

Source: xen-unstable Version: 3.0-unstable+hg11561-1 Severity: grave Tags: security Hi, the following CVE (Common Vulnerabilities & Exposures) id was published for xen-unstable. CVE-2007-3919[0]: | (1) xenbaked and (2) xenmon.py in Xen 3.1 and earlier allow local | users to truncate arbitrary files via a symlink attack on | /tmp/xenq-shm. If you fix this vulnerability please also include

Package: xen-hypervisor-3.0.2-1-i386 Version: 3.0.2-3+hg9762-1 Followup-For: Bug #385934 Hello! For me, the new upload of xen-hypervisor-3.0.2-1-i386, version 3.0.2-3+hg9762-1, does _not_ fix this issue. I'm still seeing the same problem as it was originally reported in this very bug report. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900,

Package: xen-hypervisor-3.2-1-i386 Version: 3.2.0-4 Severity: important in etch there was an automated generated entry in the menu-list of grub in this version the grub-menu is not updated also found following links: http://lists.xensource.com/archives/html/xen-users/2007-09/msg00328.html -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500,

Package: xen-utils-common Version: 4.0.0-1 Hello guys, Ik running Debian stable (squeeze). I run a virtual pfsense firwall in a DomU. I created multiple bridges. The interfaces itself (except eth2 (connected to br_lan)) itself don't have a IP assigned. I use them to connect to other devices. grep my-network /etc/xen/xend-config.sxp (network-script my-network-script) root at

Package: libxen-4.2 Version: 4.2.0-1 Severity: normal Hello, in xen 4.1 Debian packagers removed blktap uselessly as is documenteted in the blktap bug. in xen 4.2 qemu-dm is removed. This removes any reasonable way to access disks and reserves Debian Xen for diskless DomU use. Essentially Debian Xen packages are now useless. -- System Information: Debian Release: wheezy/sid APT prefers

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal While reviewing the contents of /etc/init.d/xendomains, I noticed that the script sets a variable named WDOG_PID but later references an uninitialized variable named WDOG_PIG. I'm not sure how much this impairs the behavior of Xen, so I left the severity at "normal". See below for a simple patch: --- xendomains.orig

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