similar to: Bug#571634: correct link to patch, another tangled issue in current stable

tags 571634 +fixed-upstream thanks A fix was committed to xen-unstable: http://xenbits.xensource.com/xen-unstable.hg?rev/b0fe8260cefa Anders

Processing commands for control at bugs.debian.org: > forcemerge 571634 639942 Bug #571634 [xen-utils-common] xen-utils-common vif-common.sh still using --physdev-out, --state Bug #639942 [xen-utils-common] Xen "non-bridged traffic is not supported anymore" with bridges Severity set to 'serious' from 'normal' Marked as found in versions xen-common/3.4.2-2 and

Processing commands for control at bugs.debian.org: > fixed 571634 4.1.0~rc6-1 Bug #571634 {Done: Bastian Blank <waldi at debian.org>} [xen-utils-common] xen-utils-common vif-common.sh still using --physdev-out, --state Bug #639942 {Done: Bastian Blank <waldi at debian.org>} [xen-utils-common] Xen "non-bridged traffic is not supported anymore" with bridges Marked as fixed

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

Agreed, I have the the same problem after upgrading from Lenny to Squeeze and the only option for me is tu use routing networking for xen. Among this there are another bug in /etc/xen/scripts/vif-common.sh which trigger a kernel error regarding routing for which exist a patch at http://xenbits.xensource.com/xen-unstable.hg?rev/b0fe8260cefa This is very annoying because debian multimedia

Hello List, I have been using Sweave for my homework this last quarter and have been very impressed at how much time and effort it saves me. I, however, have run up against a problem which I have not been able to solve using any of the Sweave/LaTeX tricks I know. I work through my homework one problem at a time, typesetting equations and writing R code, etc. and occasionally use

Hi! Someone asked me in private if I had found a solution to my problem with forwarding in DomUs. [1] In fact I did and I've just filled a new bug report [2] and will try to work it out. Just dropping this here in case someone else is interested. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571634#10 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592780 -- Sebasti?n Cruz

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

What is the correct combination of packages to configure and manage VMs via virt-manager undet CentOS-5.4? If I use qemu then while virt-manager works I obtain SELinux alerts with respect to the real-time clock. If instead of qemu I use kvm-qemu-img then virt-manager simply does not work. It starts but it does not find any form of qemu and the selection boxes are all greyed out. Further, do I

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20061225/6b78e0ae/attachment-0002.pgp

retitle 119396 flac: Decoded raw data does not match original raw data thanks On Tue, Nov 13, 2001 at 02:38:32AM +0000, Adam M. Costello wrote: > Matt Zimmerman <mdz@debian.org> wrote: > > > Based on a few quick tests, this kind of problem seems to occur with > > any file smaller than 4k (at least when using 44100Hz/16bps/2chan). > > I don't think the problem

Source: xen Severity: wishlist Hi, xendomains init and default files in debian folder is not updated from upstream onesfor some years. Some parameters are missed. The more useful parameters when mainly windows domUs are used is XENDOMAINS_CREATE_USLEEP that I setted to 30 or 40 seconds on my systems to decrease the "overload" caused by windows startup (even if pv drivers are installed).

Source: xen Severity: important Tags: security Hi, please see http://xenbits.xen.org/xsa/advisory-116.html for details and a patch. Cheers, Moritz

Package: logcheck-database Version: 1.2.43a Severity: minor Since last weekend's upgrade of logcheck-database from 1.2.42 to 1.2.43a, logcheck stopped ignoring routine SpamAssassin messages of the form Feb 20 21:36:16 tux64 spamd[4665]: spamd: checking message <20060220190721.0E0B41C5207 at llwb563.servidoresdns.net> for amu:7286 Could you please edit the second pattern in

retitle 925358 qemu-user-static: mis-emulates something to do with process/signal handling (m68k, s390x, ?) affects 925358 klibc-dev thanks This still happens. (And retitling because I almost filed a bug against klibc again? oops?) Look for ?mtest-external? (second occurrence) in: https://buildd.debian.org/status/fetch.php?pkg=mksh&arch=m68k&ver=59c-16&stamp=1643675884&raw=0

Package: xenstore-utils Version: 4.17.0+74-g3eac216e6e-1 Severity: serious User: debian-qa at lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink: 0m15.9s ERROR: FAIL: Broken symlinks: /usr/bin/xenstore-control -> ../lib/xen-common/bin/xen-utils-wrapper (xenstore-utils) cheers, Andreas

retitle 593741 xen-utils-common: python-xml is not marked as a dependency and xm errors without it reassign 593741 xen-utils-common kthxbye Hi, Tyler wrote: > Package: xen-tools > Version: 3.9-4 > Severity: important > > When you start building a basic xen box: > > apt-get install xen-linux-system-2.6.26-2-xen-amd64 xen-tools > > You eventually get to: > >

Package: xen-utils-common Version: 3.4.2-3 --- Please enter the report below this line. --- After several tests and many hours of investigation I found out that this is not a bug. The iptables rules that triggers the message is found in /etc/xen/scripts/vif-common.sh [1], but as the syslog message clearly indicates this rule works perfectly when the traffic is bridged. Moreover, those rules are

(copying debian-kernel for reasons which will hopefully become obvious) On Mon, 8 Jul 2013 18:10:58 +0200 =?UTF-8?Q?Moritz_M=C3=BChlenhoff?= <jmm at inutil.org> wrote: > In current Debian kernel there's no special Xen dom0 kernel image and depending > on irqbalance in the kernel package would be overkill. Would it? I thought irqbalance is actually required even for native with

Package: logcheck Version: 1.2.34 Severity: normal the patterns for pure-ftpd in ignore.d.server are not matching a user with a trailing whitespace. here a some examples: Feb 18 13:02:33 web1 pure-ftpd: (stupid-pure-ftpd @84.56.131.73) [NOTICE] /example/example.txt downloaded (5908 bytes, 152196.03KB/sec) Feb 18 13:16:14 web1 pure-ftpd: (stupid-pure-ftpd @84.56.131.73) [INFO] Logout. every