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 08:55:40 -0700 [thread overview]
Message-ID: <4F2025FC.7060407@suse.com> (raw)
In-Reply-To: <1327456894.17114.140661027646361@webmail.messagingengine.com>
erin.balid@inoutbox.com wrote:
> Hi Jim.
>
> Thanks for chiming in.
>
> On Tue, Jan 24, 2012, at 04:13 PM, Jim Fehlig wrote:
>
>>> 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...
>>
>
> It's been a big challenge finding anything that IS "an authoritative
> resource on functionality" for Xen in Opensuse.
>
> Where is the Opensuse-specific and Up-to-Date Xen documentation? I
> guess we cant rely on xen.org docs for Opensuse's Xen? Is it not really
> closely tied to the xen-devel project then?
>
Generally speaking, xen.org documentation applies to the xen packages in
openSUSE. In the case of toolstacks, openSUSE still enables the legacy
toolstack by default, and all upstream documentation wrt the legacy
toolstack applies. You can use the new toolstack as well, in which case
the upstream xl/libxl documentation applies - including recommendation
that the toolstacks should not be used in parallel.
What you have described in this thread is a bug in openSUSE12.1. You
followed the documentation and it didn't work :-).
> That leaves me back at my earlier question -- What are good docs for Xen
> on Opensuse? I've wasted a lot of time - mine and other people's -
> doing what I was told (RTFM!) just to find out that 'real' Xen manual is
> the wrong one.
>
I'm not sure what the problem is with the manual. You've hit a bug I
introduced in openSUSE.
Regards,
Jim
next prev parent reply other threads:[~2012-01-25 15:55 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 [this message]
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=4F2025FC.7060407@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).