From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, james.harper@bendigoit.com.au,
bastian@waldi.eu.org, JBeulich@novell.com
Cc: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [Bug 1612] Can't start VM when vif set and udev version is greater than 151
Date: Tue, 6 Jul 2010 11:10:23 -0400 [thread overview]
Message-ID: <20100706151023.GA25263@phenom.dumpdata.com> (raw)
In-Reply-To: <201007051720.o65HKsI6030388@bugzilla.xensource.com>
> ------- Comment #28 from silversens@gmail.com 2010-07-05 10:20 -------
> (In reply to comment #26)
> > (In reply to comment #25)
> > > Great,
> > >
> > > Will it be applyed in every xen kernel, or only from 2.6.32 ?
> > >
> > The policy is to stick bug-fixes in xen/next which are then pulled in
> > xen/stable-2.6.32.x. But this being such a serious issue, and a small patch
> > that I think Jeremy would stick it in 2.6.31 once it has passed review.
> >
>
> Its been a few weeks now, do you know when this patch will be included in
> jeremy's repository ? If not can you paste a link here to this patch ?
>
Soooo.. the last I remember it was that the patch for this was not
appropiate. But I don't remember the details - is there a forthcoming
patch that can fix the outstanding issue?
Or is the patch ready and we forgot about it?
next parent reply other threads:[~2010-07-06 15:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-1612-1575@http.bugzilla.xensource.com/bugzilla/>
[not found] ` <201007051720.o65HKsI6030388@bugzilla.xensource.com>
2010-07-06 15:10 ` Konrad Rzeszutek Wilk [this message]
2010-07-06 15:36 ` [Bug 1612] Can't start VM when vif set and udev version is greater than 151 Jan Beulich
2010-07-06 16:46 ` Konrad Rzeszutek Wilk
2010-07-07 7:30 ` Jan Beulich
2010-07-07 14:48 ` Konrad Rzeszutek Wilk
2010-07-07 15:26 ` Jeremy Fitzhardinge
2010-07-07 17:18 ` Konrad Rzeszutek Wilk
2010-07-07 17:34 ` Jeremy Fitzhardinge
2010-07-07 17:57 ` Set up bridging under Xen 4.1-unstable ( 2.6.31.15 pvops) on top of Ubuntu 10.04 Server Boris Derzhavets
2010-07-07 18:21 ` Sander Eikelenboom
2010-07-07 19:11 ` Boris Derzhavets
2010-07-08 9:11 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100706151023.GA25263@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@novell.com \
--cc=bastian@waldi.eu.org \
--cc=james.harper@bendigoit.com.au \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.