[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Upgrade to xl


  • To: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
  • From: Todd Deshane <todd.deshane@xxxxxxx>
  • Date: Thu, 9 Jun 2011 20:58:47 -0400
  • Cc: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 09 Jun 2011 18:03:40 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=WtBUyqRBDQqVjBUH4xNa6l9jtyhIxktmoQsf38d0H8gpIUBY+RLJaWKac6zugkoEOQ fgyDnu9cUHErasYb5dIzyYEM3pDtp3bwwouNsio4ayPZzNEDtuDAa8y/KOL/rAD1q3HJ cDsPVk0pdMr48eS/TrNU7iJzQLlFzR64cVyBw=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Thu, Jun 9, 2011 at 7:31 AM, Jonathan Tripathy <jonnyt@xxxxxxxxxxx> wrote:
> Hi Everyone,
>
> I'm setting up a couple of new servers and have a question regarding moving
> to xl from xm.
>
> For fresh install servers, assuming that I have installed 4.1.0 first, can I
> ignore the xl upgrade list in the release notes?

For the most part things should just work well. A notable exception is
that arbitrary python code is not accepted. (For example calls to the
system to get the arch and the like)

> Specifically, what does
> "Disable xend startup script" mean?
>

xend is the backend daemon that xm relies on. I don't think you
shouldn't need to worry about this on a fresh 4.1 install.

Thanks,
Todd

> Thanks
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>



-- 
Todd Deshane
http://www.linkedin.com/in/deshantm
http://www.xen.org/products/cloudxen.html
http://runningxen.com/

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.