similar to: Processed: #599161 not fixed in Debian stable

Displaying 20 results from an estimated 20000 matches similar to: "Processed: #599161 not fixed in Debian stable"

2012 Dec 11
0
Bug#674907: closed by Bastian Blank <waldi@debian.org> (Bug#599161: fixed in xen 4.1.3-7)
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
2012 Oct 01
0
Processed: reassign 674907 to src:linux-2.6, forcibly merging 599161 674907
Processing commands for control at bugs.debian.org: > reassign 674907 src:linux-2.6 Bug #674907 [xen] shifts the clock by 50 minutes unexplicably under a Xen dom0 Bug reassigned from package 'xen' to 'src:linux-2.6'. No longer marked as found in versions 4.0.1-5.4. Ignoring request to alter fixed versions of bug #674907 to the same values previously set > forcemerge 599161
2012 Sep 26
0
Processed: this affects more than OpenNTPd, probably all of Xen 4.0 on Debian
Processing commands for control at bugs.debian.org: > reassign 674907 xen Bug #674907 [openntpd] shifts the clock by 50 minutes unexplicably under a Xen dom0 Bug reassigned from package 'openntpd' to 'xen'. No longer marked as found in versions 3.9p1+debian-8~bpo60+1. Ignoring request to alter fixed versions of bug #674907 to the same values previously set > found 674907
2012 Dec 10
0
Processed: Re: [Xen-devel] #599161: Xen debug patch for the "clock shifts by 50 minutes" bug.
Processing commands for control at bugs.debian.org: > reassign 599161 src:xen Bug #599161 [src:linux-2.6] xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart Bug #674907 [src:linux-2.6] shifts the clock by 50 minutes unexplicably under a Xen dom0 Bug reassigned from package 'src:linux-2.6' to 'src:xen'. Bug reassigned from package
2013 Jan 30
0
Processed: Re: [experimental] boot fails as xen domU: xc_dom_find_loader: no loader found
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.
2012 Jan 09
0
Processed: Re: Bug#649141 closed by Bastian Blank <waldi@debian.org> (no bug)
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:
2012 Sep 26
0
Processed: severity of 674907 is normal
Processing commands for control at bugs.debian.org: > severity 674907 normal Bug #674907 [xen] shifts the clock by 50 minutes unexplicably under a Xen dom0 Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 674907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674907 Debian Bug Tracking System Contact
2012 May 10
0
Processed: fixed 571634 in 4.1.0~rc6-1
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
2012 Aug 24
0
Processed: reassign 666135 to src:xen-common
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
2012 Jul 02
0
Processed: fixed 677221 in 4.0.1-5.2
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
2006 Sep 14
0
Bug#387238: closed by Bastian Blank <waldi@debian.org> (fixed)
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
2012 May 06
0
Processed (with 1 errors): forcibly merging 570066 596765
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
2012 May 06
0
Processed (with 1 errors): forcibly merging 644390 668641
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)',
2010 May 28
0
Bug#583283: marked as done (udev - Weird behaviour with device names including a slash)
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
2010 Mar 20
0
Processed: reassign 555902 to xen-utils-common, forcibly merging 555902 538073
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
2011 Jan 16
0
No subject
xm save lenny3 /tmp/lenny3.save The guest console says: Suspending xenbus... and detaches. Restore the guest (paused to attach its console before continuing): xm restore -p /tmp/lenny3.save xm console lenny3 xm unpause lenny3 The console starts spewing out "BUG: recent printk recursion" and the domain spins until destroyed. The same thing happens on (live or not) migration. The
2012 May 06
0
Processed: forcibly merging 417243 409926
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
2011 Dec 10
0
Bug#649141: marked as done (xen-hypervisor-4.0-amd64: live migration fails with invalid opcode due to nonstop_tsc)
Your message dated Sat, 10 Dec 2011 20:00:59 +0100 with message-id <20111210190059.GG15557 at wavehammer.waldi.eu.org> and subject line no bug has caused the Debian Bug report #649141, regarding xen-hypervisor-4.0-amd64: live migration fails with invalid opcode due to nonstop_tsc to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it
2012 Apr 14
0
Bug#606589: marked as done (xen-linux-system-2.6.32-5-xen-amd64 doesn't upgrade from xen-linux-system-2.6.26-2-xen-amd64)
Your message dated Sat, 14 Apr 2012 19:24:04 +0200 with message-id <20120414172403.GA25566 at wavehammer.waldi.eu.org> and subject line meta-packages available has caused the Debian Bug report #606589, regarding xen-linux-system-2.6.32-5-xen-amd64 doesn't upgrade from xen-linux-system-2.6.26-2-xen-amd64 to be marked as done. This means that you claim that the problem has been dealt
2014 Aug 29
0
Bug#728295: marked as done (xen: Issues with Networking on virtual hosts with Xen.3.0.3-1)
Your message dated Fri, 29 Aug 2014 13:26:07 +0000 with message-id <20140829132607.GD4202 at shell.waldi.eu.org> and subject line Xen 3.0 unsupported has caused the Debian Bug report #728295, regarding xen: Issues with Networking on virtual hosts with Xen.3.0.3-1 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