From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ted Kaczmarek Subject: Re: cannot boot domU Date: Mon, 17 Oct 2005 08:17:45 -0400 Message-ID: <1129551465.3496.75.camel@pluto.linsolutions.com> References: <983B408465C04C49B0344D51FA21C7553E7567@trudi.intra.bpm.ch> <2b6116b30510170330l6c9bb023m14bd1f254f6a03c0@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-reply-to: <2b6116b30510170330l6c9bb023m14bd1f254f6a03c0@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Xen Devs , Nicholas Lee List-Id: xen-devel@lists.xenproject.org On Mon, 2005-10-17 at 23:30 +1300, Nicholas Lee wrote: > On 10/17/05, Stephan B=C3=B6ni wrote: > > # xm console inhouse > > Linux version 2.6.12.6-xenU (root@xen1) (gcc version 4.0.2 200509= 01 > > (prerelease) > > (SUSE Linux)) #1 SMP Sun Oct 16 15:40:12 CEST 2005 >=20 >=20 > I've not heard if Xen works with gcc 4.0. That might be worth check= ing. Unstable works as well for me with gcc 4.0.1 as 3.4.3. >=20 > Otherwise I suggest sending though logs from xm dmesg, vgdisplay an= d > anything else that might be useful. >=20 > Not sure what else I can suggest, pretty much told you everything I= 've > figured out so far. :) xen_changeset : Sun Oct 16 12:25:15 2005 +0100 7396:9b51e763767 This changeset appears to have less issues with respect to creating t= he disk device for the domU, but I am having lots of problems with vifs being mapped to the bridges, manually mapping them doesn't help. This may be specific to the present setup I am using, eth0 is used for the domU's and eth1 is the egress interface.=20 Regards, Ted >=20 > -- > Nicholas Lee > http://stateless.geek.nz > gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C