All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Bruce Edge <bruce.edge@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Upgrade to xen unstable, what changes are needed?
Date: Sat, 11 Sep 2010 13:15:52 +0300	[thread overview]
Message-ID: <20100911101552.GY2804@reaktio.net> (raw)
In-Reply-To: <AANLkTikbt=C2ct98ABohDsj1hfkFp8yzxdJQAVo1S1A_@mail.gmail.com>

On Fri, Sep 10, 2010 at 04:26:12PM -0700, Bruce Edge wrote:
> It's obvious that some config changes are needed to move from testing
> to unstable. Is this documented anywhere?
> I diff'd the docs dir in the xen-testing and xen-unstable branches and
> the only change of note is Stefano's
> xen-unstable.hg/docs/misc/console.txt doc.
> Is there a wiki/README/man page on what a user needs to fix after
> upgrading to unstable?
> 
> Aside from obvious things like xencommons and xend needing to be
> manually started, what else is there?
> 
> I do have a bridge still: (that was one of the complaints I saw from some users)
> #> brctl show
> bridge name     bridge id               STP enabled     interfaces
> eth0            8000.002481e8a51c       no              peth0
> 
> Here's the error I'm getting trying to start an Ubuntu pv-ops VM that
> was working fine with testing:
> 
> xenconsole: Could not read tty from store: No such file or directory
> #> Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
> 

try reading "xm log" to figure out why vif hotplug doesn't work.

-- Pasi

  reply	other threads:[~2010-09-11 10:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 23:26 Upgrade to xen unstable, what changes are needed? Bruce Edge
2010-09-11 10:15 ` Pasi Kärkkäinen [this message]
2010-09-13 19:12   ` Bruce Edge
2010-09-20 15:38     ` Konrad Rzeszutek Wilk
2010-09-20 15:56       ` Bruce Edge

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=20100911101552.GY2804@reaktio.net \
    --to=pasik@iki.fi \
    --cc=bruce.edge@gmail.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 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.