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: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] xen-unstable on OL6 (RHEL6 clone) problems
From: Todd Deshane <todd.deshane@xxxxxxx>
Date: Thu, 10 Feb 2011 15:19:13 +0000
Cc: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "keir@xxxxxxx" <keir@xxxxxxx>
Delivery-date: Thu, 10 Feb 2011 07:20:22 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=XCfur0bDly+l+V/qnJXozE3VVHK+Z1vJZyyglSMuVb8=; b=iaNXGYjia71rw7yKzUqvUAw/ft6iV0Qx38989HmEzKpWSUvGWl86qo9aiYgudlOQCH hla8ScbnghBBtksJbncqDU1uBZRGPKMPsjtBX1ON7/MaJcqQpl5JV2It9l0Wjmrbfv0t jsNP9Ww4aVUQnBBAzYGUprVNkuzIv6wc24ydo=
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 :content-transfer-encoding; b=cHZIwuK5JEitYoFL1HLvV/RkCJruH0RzUK6GNhosKDKmxBW6mcTrljUbtTPfeL1yQh HIT+2OHuJ9fSUQl5m4nJvFxSSy/meAUS0T6bPHqCBYpqkXMzi4mSUFelR4uHk7a0Xfpd OcJXWHQ+iHo0uM4aXzEShUuaPEYSY/2BbpPPw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1297326731.28185.1181.camel@xxxxxxxxxxxxxxxxxxxxxx>
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> <1297326731.28185.1181.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Feb 10, 2011 at 8:32 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Thu, 2011-02-10 at 01:38 +0000, Todd Deshane 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.
>
> Since it is one of the biggest changes it might be worth embedding a
> simple example (i.e. the most basic possible) of the network
> configuration required for each of the distro types, as well as
> referencing the distro documentation.
>
> A hint as to what bridge name(s) to prefer for best xend compatibility
> would also be useful.
>

Thanks. I added this and the other xend-specific note.

Any other comments just let me know (or feel free to make edits)

Thanks,
Todd

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

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