From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Xen List <xen-users@lists.xensource.com>,
"'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
Dave Scott <Dave.Scott@eu.citrix.com>,
"xen-api@lists.xensource.com" <xen-api@lists.xensource.com>
Subject: Re: RE: XCP: first unstable snapshot available
Date: Sat, 17 Jul 2010 11:10:04 +0100 [thread overview]
Message-ID: <1279361404.13417.49.camel@localhost.localdomain> (raw)
In-Reply-To: <54B2EB610B7F1340BB6A0D4CA04A4F10A17FA65E@orsmsx505.amr.corp.intel.com>
On Fri, 2010-07-16 at 21:18 +0100, Nakajima, Jun wrote:
> Dave Scott wrote on Tue, 13 Jul 2010 at 10:31:00:
>
> > Hi,
> >
> > I've built a snapshot of XCP unstable and uploaded it here:
> >
> > http://www.xen.org/files/XenCloud/Software/unstable/
> >
> > The goal is to create snapshots weekly, do some limited tests and
> > automatically upload them to the website. This particular snapshot
> > hasn't been tested at all so be careful :-)
> >
>
> Looks like Open vSwitch is not there (unlike XCP 0.5)?
I haven't installed this particular build but I can see the vswitch bits
in the root filesystem tarball and the default set in the installer is
to use vswitch.
Are you getting no networking at all or is it just using Linux bridging?
What does /etc/xensource/network.conf contain?
What does "rpm -q openvswitch" say?
What about "chkconfig --list openvswitch"?
Ian.
next prev parent reply other threads:[~2010-07-17 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 17:31 XCP: first unstable snapshot available Dave Scott
2010-07-16 20:18 ` Nakajima, Jun
2010-07-17 10:10 ` Ian Campbell [this message]
[not found] ` <1279361404.13417.49.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-07-17 17:55 ` [Xen-devel] " Nakajima, Jun
2010-07-17 19:00 ` Ian Campbell
2010-07-19 11:58 ` [Xen-devel] " Pasi Kärkkäinen
2010-07-20 10:00 ` Dave Scott
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=1279361404.13417.49.camel@localhost.localdomain \
--to=ian.campbell@citrix.com \
--cc=Dave.Scott@eu.citrix.com \
--cc=jun.nakajima@intel.com \
--cc=xen-api@lists.xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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.