From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Detail on 2.6.32.11 pv_ops not boot Date: Thu, 22 Apr 2010 16:08:12 -0700 Message-ID: <4BD0D6DC.5020502@goop.org> References: <28287956.post@talk.nabble.com> <28326903.post@talk.nabble.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <28326903.post@talk.nabble.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: Fantu Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 04/22/2010 03:17 AM, Fantu wrote: > Here the full output of SOL with full debug option: > http://old.nabble.com/file/p28326903/xenboot-sol.log xenboot-sol.log > Thanks for that. Does it always hang at the same place? Your screenshot shows it apparently hanging at ata_piix, whereas the sol log shows a hang near serial setup (which doesn't seem to overlap with the screenshot at all). What does booting the same kernel natively show? Thanks, J > > Fantu wrote: > >> S.O. is Lenny 64 bit >> Dom0 is xen 4 from hg-testing4.0 >> Kernel is 2.6.32.11 pv_ops update with this config: >> http://old.nabble.com/file/p28287956/.config .config >> Server is Dell T610 with bios 2.0.13 >> >> I have start with all debug option found: >> menuentry "Xen 4 hg-4.0-testing, linux 2.6.32.11 DEBUG" { >> set root=(hd0,1) >> multiboot /boot/xen-4.gz dom0_mem=1024M loglvl=all guest_loglvl=all >> lapic=debug apic_verbosity=debug apic=debug iommu=off >> module /boot/vmlinuz-2.6.32.11 root=LABEL=root-raid ro nomodeset >> earlyprintk=xen nomodeset initcall_debug debug loglevel=10 >> module /boot/initrd.img-2.6.32.11 >> } >> >> The result is block here: >> http://old.nabble.com/file/p28287956/2.6.32.11_pv_ops_screen.jpg >> 2.6.32.11_pv_ops_screen.jpg >> >> Thanks in advantages for any help >> >> >