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] Re: [Xen-users] pvops dom0 kernel: Unable to locate IOA

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] pvops dom0 kernel: Unable to locate IOAPIC for GSI 2 and 9
From: kishore kumar <bodkekumar@xxxxxxxxx>
Date: Tue, 16 Mar 2010 14:16:22 -0700
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 16 Mar 2010 14:21:59 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=G1FOhGXMJq2QDitMPjo6K4wvaZAUlrtc8BK81UZrfkk=; b=mQgTSToJB+tlOHHFhQ2vpls1fBvAQsxuwWQhFE3hVNDqnkdJG2UioCoYdM/L6BbsCP Cps0Iq6wZpIN2VLBbczDSi+zgO3QrozKimNNZ2UOE5CbQJBzRLBGEpNrtV4jrWWIMdnm YLDNMlWqL6uFffqPFboQD/hW5rSDJvM+iMoL0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=gfeCbeXdocNV3XBYz45H3QoL+XfNJlda8BvYyqeXcRPjolq67YT7+Tj+tVs6shxkoF eiWAywK2luWVcz319arsxL7kPf6s3/ohNwS8KGkgnscmmjDcxU2jFWNvagwFgv1ArBEI 8BV0AdrUzx+1klGJ2mcyyh8RH2N0l1mlmoLpw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100316202056.GZ1878@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <9f975f341003121546m7042e458i67822a037076b828@xxxxxxxxxxxxxx> <20100313001842.GO1878@xxxxxxxxxxx> <9f975f341003121641m17e7398cnd2398a3f50a1c78a@xxxxxxxxxxxxxx> <20100313004730.GR1878@xxxxxxxxxxx> <9f975f341003151701u4e8da890ve2c11f5e66a44a93@xxxxxxxxxxxxxx> <9f975f341003161032p423b5c7cs5bc9bcfb36620033@xxxxxxxxxxxxxx> <20100316194344.GW1878@xxxxxxxxxxx> <20100316194831.GX1878@xxxxxxxxxxx> <4B9FE71C.7070006@xxxxxxxx> <20100316202056.GZ1878@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I did below steps.

 
 I pulled DOM 0 kernel from
 
cd linux-2.6-xen

make clean

cp -a .config .config-old

wget -O .config http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.9-pvops-dom0-xen-stable-x86_64

make oldconfig

make bzImage

make modules

make modules_install

cp -a .config /boot/config-2.6.32.9

cp -a System.map /boot/System.map-2.6.32.9

cp -a arch/x86/boot/bzImage /boot/vmlinuz-2.6.32.9


and modified the grub.conf as below
 

Root(hd0,0)

 kernel /xen.gz console=vga,com1 com1=115200,8n1 msi=1 iommu=1

 module /vmlinuz-2.6.32.9 ro root=/dev/VolGroup01/LogVo100  rhgb quiet

 module /initrd-2.6.32.9.img

 
and rebooted the machine.  Then It booted with some xen messages and stopped.  Those were the messages captured from serial console.
 
Please let me know if I did something wrong here.
 
 

 
On Tue, Mar 16, 2010 at 1:20 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
On Tue, Mar 16, 2010 at 01:16:28PM -0700, Jeremy Fitzhardinge wrote:
> On 03/16/2010 12:48 PM, Pasi Kärkkäinen wrote:
>> On Tue, Mar 16, 2010 at 09:43:44PM +0200, Pasi Kärkkäinen wrote:
>>
>>> On Tue, Mar 16, 2010 at 10:32:17AM -0700, kishore kumar wrote:
>>>
>>>>     Attached is the output captured from serial console.
>>>>
>>>>     Machine does not boot after compiling xen 3.4.3 with pv_ops dom 0 kernel.
>>>>
>>>>     Please let me know what is going wrong here.
>>>>
>>>>
>>> Ok this looks like a bug that is already being sorted out on xen-devel mailinglist.
>>> I added CC to xen-devel.
>>>
>>>
>>
>
> Those messages are not a problem in themselves, but the related problem
> is believed to be fixed in current xen/stable-2.6.32.x.  It looks like
> the output stops there because the Xen console isn't set up properly for
> some reason.
>

Yeah, remove "rhgb quiet" from the options.. the dom0 kernel cmdline should be like this:
ro root=/dev/VolGroup01/LogVol00 console=hvc0 earlyprintk=xen nomodeset

-- Pasi



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>