From: Jim Fehlig <jfehlig@suse.com>
To: erin.balid@inoutbox.com
Cc: "Roger Pau Monné" <roger.pau@entel.upc.edu>,
xen-devel@lists.xensource.com
Subject: Re: After switching from "xm" to "xl" toolstack, can't get Guest networking to work.
Date: Tue, 24 Jan 2012 16:13:39 -0700 [thread overview]
Message-ID: <4F1F3B23.60304@suse.com> (raw)
In-Reply-To: <1327254854.9185.140661026566721@webmail.messagingengine.com>
erin.balid@inoutbox.com wrote:
> I found this post from a year ago by an OpenSuse Xen developer -
>
> http://lists.opensuse.org/opensuse-features/2011-03/msg00212.html
>
A mailing list to discuss openSUSE features, not an authoritative
resource on functionality in any given openSUSE release...
> "Xen 4.1.0 (due February 2011) will be the first release in which thenew
> xl/libxl (aka libxenlight [1]) toolstack will be the default,preferred
> tool set. Although still included in the release, the legacyxm/xend
> toolstack will be disabled and in process of deprecation."
>
> That was for 4.1.0. The current version is 4.1.2. The post reads then
> like we already should be using xl in OpenSuse.
That talks about upstream xen, not xen packaging in openSUSE. xl/libxl
is the default, preferred toolstack in upstream Xen 4.1.x.
> Looks like the author
> posts on this list too. I'll CC him directly on just this email. Maybe
> he can participate here a bit and has some ideas.
>
Well, our plan was to switch to xl/libxl in openSUSE12.1, but we
switched back to the legacy toolstack before 12.1 released. In the end,
we didn't have time to ensure xl/libxl was baked enough serve as a
replacement for xm/xend, let alone ensuring the tools consuming libxl
(e.g. libvirt) were feature parity with the legacy toolstack
counterparts. Hopefully we will have time to do this during
openSUSE12.2 development cycle.
BTW, I can reproduce your problem and will take a look as time permits.
Regards,
Jim
next prev parent reply other threads:[~2012-01-24 23:13 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 [this message]
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
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=4F1F3B23.60304@suse.com \
--to=jfehlig@suse.com \
--cc=erin.balid@inoutbox.com \
--cc=roger.pau@entel.upc.edu \
--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.