From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: pv_ops dom0 USB fixed Date: Thu, 11 Dec 2008 14:38:52 -0800 Message-ID: <4941967C.2020801@goop.org> References: <4940210C.1060401@goop.org> <1e16a9ed0812110850odff8f56h836b7187ad0c64b0@mail.gmail.com> <49415945.3030508@goop.org> <1e16a9ed0812111147h3416cbb5uc11a8b9f5f0d0e80@mail.gmail.com> <1229025794.2770.32.camel@localhost.localdomain> <1e16a9ed0812111220h40e62ee1ma27f48c5207bc735@mail.gmail.com> <49417755.4050703@goop.org> <1e16a9ed0812111312p2547884cgf4020eb9ea92ddde@mail.gmail.com> <1229030361.2770.36.camel@localhost.localdomain> <1e16a9ed0812111323k60f4404ekd367f3d24f8b2bc2@mail.gmail.com> <1e16a9ed0812111339rd084ed7md1e6d9e7346ab18f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1e16a9ed0812111339rd084ed7md1e6d9e7346ab18f@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: deshantm@gmail.com Cc: Xen-devel , Aviv Grafi , Ian Campbell List-Id: xen-devel@lists.xenproject.org Todd Deshane wrote: > disk only, took out vif and dhcp options. > > Still didn't boot, same error. > > Log attached. > > Also changing for 20 to 256 memory gave problems. > > Looks like some sort of memory problem too. > Hm, seems to be trying to shrink dom0 too much. What's your domain config file? mem=3G is probably overkill. There's no problem in Xen using all your memory, but you should set dom0_mem=1G or something (less than 3G, but you probably don't need all that much). How much memory does your system have? > Also, it looks like I am getting a number of errors in > xend-debug.log to do with scsi commands. > > I will try to track down potentially missing packages. > > Any idea on what dependencies there might be? > Looks like you're missing lsscsi and udev (though I would have thought Ubuntu would be using udev). BTW, I just pushed up a patch which should clear up the warnings in your boot messages (they could potentially result in a system-locking deadlock, so its probably worthwhile). J