From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: FW: [Xen-users] xen 4+ jeremy 2.6.32 pvops kernel
	boot error
Date: Mon, 2 May 2011 10:17:06 -0400
Message-ID: <20110502141706.GD13192@dumpdata.com>
References: <BLU164-w82B6C67269032AF82F13CB1AA0@phx.gbl>
	<BLU164-w619CA3CED027601033B0F7B1AA0@phx.gbl>
	<BLU164-w1178A83720D01C436820E0B1930@phx.gbl>
	<BLU164-w26402FB25A30A722CF4767B1950@phx.gbl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <BLU164-w26402FB25A30A722CF4767B1950@phx.gbl>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: linbao <girl111_2002@hotmail.com>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On Fri, Apr 22, 2011 at 01:50:44AM +0000, linbao wrote:
> 
> 
> any one reply for this?

Do not top post.

.. snip..
> megaraid_sas 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> megaraid_sas 0000:01:00.scsi4 : LSI SAS based MegaRAID driver
> shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
> init used greatest stack depth: 3992 bytes left
> Kernel panic - not syncing: Attempted to kill init!
> Pid: 1, comm: init Not tainted 2.6.32.36 #3
> Call Trace:
>  [<ffffffff8105bc77>] panic+0xa5/0x169
>  [<ffffffff8100f351>] ? xen_force_evtchn_callback+0xd/0xf
>  [<ffffffff8100fabf>] ? xen_restore_fl_direct_end+0x0/0x1
>  [<ffffffff814b55d8>] ? _write_unlock_irq+0x30/0x3c
>  [<ffffffff8108d1de>] ? trace_hardirqs_on_caller+0x110/0x134
>  [<ffffffff8108d20f>] ? trace_hardirqs_on+0xd/0xf
>  [<ffffffff814b55df>] ? _write_unlock_irq+0x37/0x3c
>  [<ffffffff8105f549>] do_exit+0x7e/0x712
>  [<ffffffff8105fc79>] sys_exit_group+0x0/0x1b
>  [<ffffffff8105fc90>] sys_exit_group+0x17/0x1b
>  [<ffffffff81012db2>] system_call_fastpath+0x16/0x1b
> (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
> (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.

And there are no messages about a disk drive being detected. It looks
as so:

[    2.652264] sd 0:0:0:0: [sda] 1464640512 512-byte hardware sectors (749896 MB)
[    2.652375] sd 0:0:0:0: [sda] Write Protect is off
[    2.652448] sd 0:0:0:0: [sda] Mode Sense: 06 00 00 00
[    2.652515] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.654013] sd 0:0:0:0: [sda] 1464640512 512-byte hardware sectors (749896 MB)

So somehow you either don't have the drive for it, or you are missing
the SCSI_WAIT option (not sure of the name).