xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@suse.com>
To: erin.balid@inoutbox.com
Cc: xen-devel@lists.xensource.com
Subject: Re: After switching from "xm" to "xl" toolstack, can't get Guest networking to work.
Date: Wed, 25 Jan 2012 09:47:22 -0700	[thread overview]
Message-ID: <4F20321A.9090204@suse.com> (raw)
In-Reply-To: <1327508820.28123.140661027898793@webmail.messagingengine.com>

erin.balid@inoutbox.com wrote:
> Hi Jim.
>
> On Wed, Jan 25, 2012, at 08:55 AM, Jim Fehlig wrote:
>   
>> Generally speaking, xen.org documentation applies to the xen packages in openSUSE.
>>     
>
> Okay then.  That simplifies life.  Thanks.
>
> What will be the best place to track fixes to this issue in
> Opensuse-land?  Xen-users list?  Opensuse-virtual list?

bugzilla.novell.com

>  I'd like to get
> off _this_ list if possible.  I don't really fit here.  Unless it really
> is the right forum to follow.
>   

Yes, let's stop this thread here :-).  This is a downstream issue.

> I got your comment that you'd look for fixes in the Opensuse 12.2
> time-frame.  As I read the openSUSE Roadmap, the scheduled release date
> for openSUSE 12.2 is July 2012.
>
> We won't switch to a new OS release until after it's in production.  We
> _are_ willing to use a few non-production repositories for key packages.
>  Xen's one of them.
>
> Should we plan to see these Xen fixes in a shorter timeframe in a repo
> built for use with 12.1 release/kernel prior to that 12.2 release date?

We do maintenance on virtualization packages in openSUSE, so a fix for
this could be delivered to the openSUSE12.1 update repository.  But the
process starts with a bugzilla entry...

Regards,
Jim

  reply	other threads:[~2012-01-25 16:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21 20:06 After switching from "xm" to "xl" toolstack, can't get Guest networking to work erin.balid
2012-01-21 22:57 ` Roger Pau Monné
2012-01-21 23:04   ` erin.balid
2012-01-22  0:54     ` erin.balid
2012-01-22 11:08     ` Roger Pau Monné
2012-01-22 17:11       ` erin.balid
2012-01-22 17:28         ` Roger Pau Monné
2012-01-22 17:54           ` erin.balid
2012-01-24 23:13             ` Jim Fehlig
2012-01-25  2:01               ` erin.balid
2012-01-25 15:55                 ` Jim Fehlig
2012-01-25 16:27                   ` erin.balid
2012-01-25 16:47                     ` Jim Fehlig [this message]
2012-01-22 15:49 ` djmagee
2012-01-23 11:27 ` Ian Campbell
2012-01-23 15:28   ` erin.balid
2012-01-24 14:26     ` Ian Campbell
2012-01-24 15:56       ` erin.balid
2012-01-24 16:41         ` Ian Campbell
2012-01-24 17:10           ` erin.balid
2012-01-24 18:05             ` erin.balid
2012-01-24 18:19               ` erin.balid
2012-01-24 21:20                 ` Ian Campbell
2012-01-24 21:20               ` Ian Campbell
2012-01-24 21:44                 ` erin.balid
2012-01-25  3:59                   ` erin.balid
2012-01-25  9:35                   ` Ian Campbell
2012-01-25 16:19                 ` Jim Fehlig
2012-01-25 16:32                   ` Ian Campbell
     [not found] <mailman.1527.1327510060.1471.xen-devel@lists.xensource.com>
2012-01-25 17:06 ` John McDermott CIV
2012-01-25 17:16   ` Ian Campbell
2012-01-25 17:22     ` John McDermott CIV
2012-01-25 17:33     ` Jim Fehlig
2012-01-25 17:39       ` John McDermott CIV
2012-01-25 18:02         ` Jim Fehlig
2012-01-25 19:20           ` John McDermott CIV
2012-01-25 21:16             ` Jim Fehlig

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=4F20321A.9090204@suse.com \
    --to=jfehlig@suse.com \
    --cc=erin.balid@inoutbox.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).