From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: RE: xen 4.2 unstable; HVM; 2.6.39.3; HD/Network card error
Date: Mon, 25 Jul 2011 17:50:36 +0100
Message-ID: <alpine.DEB.2.00.1107251748160.12963@kaball-desktop>
References: <!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAAI32k8eIVQhMgLM5AGCb128BAAAAAA==@gmail.com>
	<alpine.DEB.2.00.1107181242270.12963@kaball-desktop>
	<!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAAE0cphS4zTVFjzXOjWNB7uwBAAAAAA==@gmail.com>
	<alpine.DEB.2.00.1107201238440.12963@kaball-desktop>
	<!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAAIMchHuG/6dIqtJ7GgPrsOEBAAAAAA==@gmail.com>
	<!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAAAKIP0TTIelKl7OMHw7/aSQBAAAAAA==@gmail.com>
	<alpine.DEB.2.00.1107251142270.12963@kaball-desktop>
	<!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAAICr5HMuz3FOpEbmgui+XxgBAAAAAA==@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAAICr5HMuz3FOpEbmgui+XxgBAAAAAA==@gmail.com>
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: Walter Robert Ditzler <ditwal001@gmail.com>
Cc: "xen-users@lists.xensource.com" <xen-users@lists.xensource.com>, "konrad.wilk@oracle.com" <konrad.wilk@oracle.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Mon, 25 Jul 2011, Walter Robert Ditzler wrote:
> hi stefanao,
> 
> i have you added loglevel=9 in grub
> 
> ***
> ### BEGIN /etc/grub.d/08_xen ###
> menuentry "Xen 4.2 Unstable / Debian Squeeze kernel 3.0.0" {
>         insmod ext2
>         insmod multiboot2
>         insmod lvm
>         insmod part_msdos
>         insmod raid
>         insmod mdraid
>         set root='(md/1)'
>         search --no-floppy --fs-uuid --set
> 8809ff98-9ce8-472a-9ae9-74b821fe5285
>         echo 'Loading multiboot kernel ...'
>         multiboot (md/1)/boot/xen.gz placeholder dom0_mem=1024M loglevel=9
>         echo 'Loading initial kernel ...'
>         module (md/1)/boot/vmlinuz-3.0.0 placeholder
> root=UUID=8809ff98-9ce8-472a-9ae9-74b821fe5285 ro quiet console=tty0
> nomodeset
>         echo 'Loading initial ramdisk ...'
>         module (md/1)/boot/initrd.img-3.0.0
> }
> ### END /etc/grub.d/08_xen ###
> ***
> 
> and several log files attached to this email.

I need the output of the guest kernel stuck during boot in order to
understand the problem. It shouldn't be difficult to get if you enable
logging over the serial in the guest kernel.