This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Upgrade to xen unstable, what changes are needed?

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Upgrade to xen unstable, what changes are needed?
From: Bruce Edge <bruce.edge@xxxxxxxxx>
Date: Mon, 20 Sep 2010 08:56:42 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 20 Sep 2010 08:57:50 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Sm4g4egL0FLeD8EJGSoPKUeqlvyZ5kFf/jIOnIN66rU=; b=rW98Yd5rtvhHxCfdkX0V3mSV/K//SZuygwRzEHh89yHjrsc9vyjjT/edsOXcwkepUM u7Yg7xLKv2LObrKkM8KSs6ZYsLz1wyvmd5kzjl+gP3CRIwUvKWZav/F4NoRAt8eMbyTS 11IS85nqLO2ZRsaYNpKDrxOZ6r8z2+DZ6aEpM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=NLrWj9ilwKMmFNLgixyD2f3kAdR+JDKCbLzXG81o2fd6q6OdfmLU4c0z7B/7bJpkdR mmg54RlMNvFwgbpTwqCeV88FXJCra0QVx/UZm/Zzk3cgRxDYMCQMYkw7ak/phXq6zzeZ KlUfJuWfTSWy7f16VoLAn69Beqh968ic4qeOg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100920153821.GA15129@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTikbt=C2ct98ABohDsj1hfkFp8yzxdJQAVo1S1A_@xxxxxxxxxxxxxx> <20100911101552.GY2804@xxxxxxxxxxx> <AANLkTim+q6bZkC7z7T-EFshrLK35YwUrqRNJeuUVU_Mz@xxxxxxxxxxxxxx> <20100920153821.GA15129@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, Sep 20, 2010 at 8:38 AM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> On Mon, Sep 13, 2010 at 12:12:55PM -0700, Bruce Edge wrote:
>> On Sat, Sep 11, 2010 at 3:15 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
>> > 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.
> Is the xen backend device loaded or built in? Is the tap/tun device loaded?

Turned out to be some missing modules. The xen udev rules were not
loading the modules.
Once I fixed that (packaging problems), most other problems went away.

The final problems were related to the VM's VIF line. I had to change it from:
    vif         = [ 'mac = ' + mac + ',vifname = vif-dpm' ]
    vif         = [ 'mac = ' + mac  ]

For whatever reason I can't specify the VIF name with unstable.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>