WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xen-unstable on OL6 (RHEL6 clone) problems

To: "Fajar A. Nugraha" <list@xxxxxxxxx>
Subject: Re: [Xen-devel] xen-unstable on OL6 (RHEL6 clone) problems
From: Todd Deshane <deshantm@xxxxxxxxx>
Date: Wed, 9 Feb 2011 21:15:10 -0500
Cc: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, keir@xxxxxxx
Delivery-date: Wed, 09 Feb 2011 18:16:22 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=XipD2aiLZ38iWHHH1kKeubQ/s6rTAvYfSjodJ4OB/u8=; b=Zz/rdlRmJSZ3RGJfaALGyogjNqtK1/kLH14N764+cX1/AnHiMEuw7W/kMfUJk8RQf9 45bZr9LEpn2WHIzdzXGZHJ3BZoWdaxYXmRTo8D2jl5GDhncZk3T+nf9aQbOmTZf8QJ51 aGqLTfijWiI4NxLd0ulS1wXyZ0bUDncpz5ML0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; b=NqcV1e7FiBOW2gbJvMG8WrnLSt0yBPSCg5LvrDhorHJmorObwDbckAQFibjRPTg5vH dpxOUoTRstG/euxQGRPcbW7uLFK9qfytoY6cKw1bXliG8zRaY6Lq96Ik1bn905evCaDq o3BVXNWwJ6JKWV0IhVhj9Jw/6EDqQ4om7sbI4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTinfW61ueoytoKatNtm9913J8=7c4XtnLkctQ0aU@xxxxxxxxxxxxxx>
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: <f16717d5-28ae-4c2f-bb80-f0cae1c4b4e1@default> <a00a492b-24c6-486f-a602-2d33142fc20e@default> <AANLkTik+wjewTzKKNS6EOP0T3xfqGxaS7rSyh38c3ZXB@xxxxxxxxxxxxxx> <AANLkTinfW61ueoytoKatNtm9913J8=7c4XtnLkctQ0aU@xxxxxxxxxxxxxx>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Feb 9, 2011 at 8:54 PM, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
> On Thu, Feb 10, 2011 at 8:38 AM, Todd Deshane <deshantm@xxxxxxxxx> wrote:
>> On Wed, Feb 9, 2011 at 7:22 PM, Dan Magenheimer
>> <dan.magenheimer@xxxxxxxxxx> wrote:
>>> Wait... I just realized... this means that there is NO backwards
>>> compatibility of domU config files between 4.0 and 4.1?  EVERY
>>> vm.cfg file MUST be changed when upgrading from 4.0 to 4.1?
>>>
>>> If this is true, /me raises a red flag on 4.1.
>>>
>>
>> There is almost full compatibility, with the exception of being able
>> to have arbitrary python code embedded. Most should work directly.
>> Name the bridge the same as before and it is likely to completely work
>> with most built to work with Xen 4.0
>>
>> I'll be sure to clarify that a bit on the wiki page.
>
> Reading the wiki, isn't the change only required when using xl?
> Shouldn't xm and xend work just as it has always been?

xm and xend are still available (for now), but using xl and libxl is preferred.

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