|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Upgrade to xen unstable, what changes are needed?
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' ]
to
vif = [ 'mac = ' + mac ]
For whatever reason I can't specify the VIF name with unstable.
-Bruce
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|