Hans van Kranenburg
2012-Dec-09 23:02 UTC
[Pkg-xen-devel] Bug#631102: #631102 and #679533.. related?
Kevin, Would you mind taking a look at #679533 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679533) and give some feedback about how similar this issue is to your report in #631102 here? There was a hint 631102 might be similar, but from the text in this bug report it's not clear to me if this is about the same issue. Maybe you could comment on it. First results of a big shoot-out session (reproducing and isolating the bug) last week is that we found out disabling hyperthreading in the server bios made our issue go away. Knowing that... we now see, looking back, that after we switched on HT together with the lenny->squeeze (xen 3->4) upgrade, this issues started to pop up weeks later in production. The obscure bug did not bite during upgrade-testing. :| Thanks, -- Hans van Kranenburg - System / Network Engineer T +31 (0)10 2760434 | hans.van.kranenburg at mendix.com | www.mendix.com
Kevin Bowling
2012-Dec-09 23:10 UTC
[Pkg-xen-devel] Bug#631102: #631102 and #679533.. related?
I skimmed through this but cannot say. I no longer have access to the hardware. My solution was to switch the entire company to kvm. On Sun, Dec 9, 2012 at 4:02 PM, Hans van Kranenburg < hans.van.kranenburg at mendix.com> wrote:> Kevin, > > Would you mind taking a look at #679533 > (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679533) and give some > feedback about how similar this issue is to your report in #631102 here? > > There was a hint 631102 might be similar, but from the text in this bug > report it's not clear to me if this is about the same issue. Maybe you > could comment on it. > > First results of a big shoot-out session (reproducing and isolating the > bug) last week is that we found out disabling hyperthreading in the > server bios made our issue go away. Knowing that... we now see, looking > back, that after we switched on HT together with the lenny->squeeze (xen > 3->4) upgrade, this issues started to pop up weeks later in production. > The obscure bug did not bite during upgrade-testing. :| > > Thanks, > > -- > Hans van Kranenburg - System / Network Engineer > T +31 (0)10 2760434 | hans.van.kranenburg at mendix.com | www.mendix.com >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20121209/6d408d27/attachment.html>
Hans van Kranenburg
2012-Dec-09 23:13 UTC
[Pkg-xen-devel] Bug#631102: #631102 and #679533.. related?
On 12/10/2012 12:10 AM, Kevin Bowling wrote:> I skimmed through this but cannot say. I no longer have access to the > hardware.Ok.> My solution was to switch the entire company to kvm.Haha :-) You might consider closing the bug report although, if the issue is not relevant any more. Thanks, -- Hans van Kranenburg - System / Network Engineer T +31 (0)10 2760434 | hans.van.kranenburg at mendix.com | www.mendix.com
Kevin Bowling
2012-Dec-09 23:17 UTC
[Pkg-xen-devel] Bug#631102: #631102 and #679533.. related?
Bug 631102 I suggest closing as cannot reproduce if it has not been seen in the wild. I do not have access to the hardware anymore. On Sun, Dec 9, 2012 at 4:13 PM, Hans van Kranenburg < hans.van.kranenburg at mendix.com> wrote:> On 12/10/2012 12:10 AM, Kevin Bowling wrote: > > I skimmed through this but cannot say. I no longer have access to the > > hardware. > > Ok. > > > My solution was to switch the entire company to kvm. > > Haha :-) > > You might consider closing the bug report although, if the issue is not > relevant any more. > > Thanks, > > -- > Hans van Kranenburg - System / Network Engineer > T +31 (0)10 2760434 | hans.van.kranenburg at mendix.com | www.mendix.com >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20121209/dac91172/attachment.html>
Apparently Analagous Threads
- Bug#631102: xen: Xen guests on Squeeze lose networking randomly
- Bug#679533: Traffic forwarding issue between Xen domU/dom0 and ovs
- Bug#658305: Prevent silently failing on duplicate vifname
- Bug#679533: Traffic forwarding issue between Xen domU/dom0
- Bug#658305: Whoops, fixed patch.