From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Magenheimer Subject: RE: xen-unstable on OL6 (RHEL6 clone) problems Date: Wed, 9 Feb 2011 16:22:42 -0800 (PST) Message-ID: References: <69bf887a-89de-46fc-a04e-7653255620e5@default AANLkTinrsyGwGhga_r+r-mcpMZnxw2Ekst4pVbjwh2M9@mail.gmail.com f16717d5-28ae-4c2f-bb80-f0cae1c4b4e1@default> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Todd Deshane , keir@xen.org Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > > > Any clues? =A0I'm guessing that I have to manually set up some > > > network bridges that I never had to deal with before, but > > > don't have any idea how to do that. > > > > > > > Disable bridging in the xend config and set up a xen bridge like > this: > > http://wiki.libvirt.org/page/Networking#Fedora.2FRHEL_Bridging > > > > Then, just make sure your domU config files use the same bridge name > > you created. 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.