similar to: Processed: fixed 571634 in 4.1.0~rc6-1

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: > reassign 666135 src:xen-common 4.0.0-1 Bug #666135 {Done: Bastian Blank <waldi at debian.org>} [xen-hypervisor-4.0-amd64] Multiple "Domain-0", slow libvirt Bug reassigned from package 'xen-hypervisor-4.0-amd64' to 'src:xen-common'. No longer marked as found in versions xen/4.0.1-4. No longer marked as fixed

Processing commands for control at bugs.debian.org: > found 599161 4.0.1-5.5 Bug #599161 {Done: Bastian Blank <waldi at debian.org>} [src:xen] xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart Bug #674907 {Done: Bastian Blank <waldi at debian.org>} [src:xen] shifts the clock by 50 minutes unexplicably under a Xen dom0 Marked as found

Package: xen-utils-common Version: 4.0.0-1 Hello guys, Ik running Debian stable (squeeze). This appeared in the messages when i started and stopped a DomU: root at dom0:~# cat messages Aug 31 22:04:52 dom0 kernel: [ 775.569937] device vif6.0 entered promiscuous mode Aug 31 22:04:52 dom0 kernel: [ 775.575993] br_lan: port 2(vif6.0) entering forwarding state Aug 31 22:04:52 dom0 kernel: [

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

Processing commands for control at bugs.debian.org: > reassign 699381 src:xen 4.0.1-5.5 Bug #699381 {Done: Julien Cristau <jcristau at debian.org>} [src:linux] linux-image-3.7-trunk-amd64: boot fails as xen domU: xc_dom_find_loader: no loader found Bug reassigned from package 'src:linux' to 'src:xen'. No longer marked as found in versions linux/3.7.3-1~experimental.1.

Processing commands for control at bugs.debian.org: > unarchive 649141 Bug #649141 {Done: Bastian Blank <waldi at debian.org>} [xen-hypervisor-4.0-amd64] xen-hypervisor-4.0-amd64: live migration fails with invalid opcode due to nonstop_tsc Unarchived Bug 649141 > End of message, stopping processing here. Please contact me if you need assistance. -- 649141:

Processing commands for control at bugs.debian.org: > forcemerge 570066 596765 Bug #570066 [xen-utils-common] xen-utils-4.1: should depend on python-lxml Bug #593741 [xen-utils-common] xen-utils-4.1: should depend on python-lxml Bug #641934 [xen-utils-common] xen-utils-common: missing python-lxml dependancy Unable to merge bugs because: package of #596765 is 'xen' not

On Wednesday 13 September 2006 16:48, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > #387238: xen-hypervisor: Xen hypervisor reboots when scrubbing ram message > is reached: confirmed on AMD64 and i386, which was filed against the > xen-hypervisor-3.0.2-1-i386 package. Hi Bastian, My conclusion is the same. I think xen-hypervisor

Processing commands for control at bugs.debian.org: > forcemerge 644390 668641 Bug #644390 [libxen-dev] Please make it possible to link a against libxlutil Unable to merge bugs because: package of #668641 is 'xen' not 'libxen-dev' Failed to forcibly merge 644390: Did not alter merged bugs Debbugs::Control::set_merged('transcript', 'GLOB(0x25f5b28)',

FYI: The status of the xen-common source package in Debian's testing distribution has changed. Previous version: 4.0.0-1 Current version: 4.1.0~rc6-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more

Processing commands for control at bugs.debian.org: > fixed 677221 4.0.1-5.2 Bug #677221 {Done: Bastian Blank <waldi at debian.org>} [src:xen] xen: Xen PV privilege escalation (CVE-2012-0217) Marked as fixed in versions xen/4.0.1-5.2. > thanks Stopping processing here. Please contact me if you need assistance. -- 677221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677221 Debian

Your message dated Fri, 28 May 2010 10:02:57 +0000 with message-id <E1OHwP3-0007aW-JR at ries.debian.org> and subject line Bug#583283: fixed in xen-3 3.4.3-1 has caused the Debian Bug report #583283, regarding udev - Weird behaviour with device names including a slash to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Hi, I'm not sure but I think I suffer under the same problem with a bit different setup with squeeze testing and xen 4.0rc5. In fact I'm using bridges in the dom0 and the connections to the domU get lost sporadically. In don't see where's a solution to the problem... Is it now a bug? When it's an iptables bug, where's the corresponding bug in the iptables bugtracker

Processing commands for control at bugs.debian.org: > reassign 555902 xen-utils-common 3.3.1-2 Bug #555902 {Done: Bastian Blank <waldi at debian.org>} [xen-utils-3.4] xen-utils-3.4: /etc/init.d/xend - $DAEMON variable at xend_stop() Bug reassigned from package 'xen-utils-3.4' to 'xen-utils-common'. Bug No longer marked as found in versions xen-3/3.4.0-2. Bug No longer

libxen-dev_4.1.0~rc6-1_amd64.deb to main/x/xen/libxen-dev_4.1.0~rc6-1_amd64.deb libxenstore3.0_4.1.0~rc6-1_amd64.deb to main/x/xen/libxenstore3.0_4.1.0~rc6-1_amd64.deb (new) xen-docs-4.1_4.1.0~rc6-1_all.deb optional doc Documentation for Xen This package contains all the large documentation files for Xen. This includes a description interface (both the API, and a nice explanation of how

Processing commands for control at bugs.debian.org: > forcemerge 417243 409926 Bug #417243 {Done: Bastian Blank <waldi at debian.org>} [xen-utils-common] xen-utils-common: Should display a usable error message when there is a config file error Bug #409926 [xen-utils-common] xen-utils-common: Please clarify error messages: ie when disk is not found Severity set to 'normal' from

retitle 571634 xen-utils-common vif-common.sh still using --physdev-out, --state found 571634 4.0.0-1 thanks Hi, That link to upstream patch in the last message is apparently broken, a working one is: http://xenbits.xen.org/hg/xen-unstable.hg/rev/b0fe8260cefa but also more importantly for the current stable package: http://xenbits.xen.org/hg/xen-4.0-testing.hg/rev/af7110f4f803 Because the

On 2012-12-11, Debian Bug Tracking System wrote: > #674907: shifts the clock by 50 minutes unexplicably under a Xen dom0 > > It has been closed by Bastian Blank <waldi at debian.org>. What about us poor users on Debian squeeze? Or worse, about the upcoming wheezy release? Is there the possibility to backport this fix to s-p-u? Should I ask release.debian.org for a freeze

Processing commands for control at bugs.debian.org: > close 587090 4.1.0~rc6-1 Bug #587090 [xen-utils-4.0] xen-utils-4.0: Exception starting xend ('NoneType' object has no attribute 'rfind') There is no source info for the package 'xen-utils-4.0' at version '4.1.0~rc6-1' with architecture '' Unable to make a source version for version