From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: pvops Domain 0 Creased when boot Xen-unstable on
	Ubuntu10.04
Date: Tue, 17 May 2011 10:44:21 -0400
Message-ID: <20110517144421.GA7597@dumpdata.com>
References: <BANLkTimALuDSgaw_UeuC4vf+Vyfd7+Sufg@mail.gmail.com>
	<20110516175320.GA5722@dumpdata.com>
	<BANLkTi=sQ0TCSG7ky2pj3QB=Heq-biuERw@mail.gmail.com>
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: <BANLkTi=sQ0TCSG7ky2pj3QB=Heq-biuERw@mail.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: Bei Guan <gbtju85@gmail.com>
Cc: Xen Devel <xen-devel@lists.xensource.com>, Andrei Warkentin <andreiw@motorola.com>
List-Id: xen-devel@lists.xenproject.org

> menuentry "Ubuntu_Xen 4.2 (2.6.32.28)" {
> recordfail
> insmod ext2
> set root='(hd0,9)'
> search --no-floppy --fs-uuid --set 59c64afa-47a8-4a5f-a4cf-dbe3be20cc15
>         multiboot /boot/xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all
> sync_console console_to_ring com1=115200,8n1 console=com1 lapic=debug
> apic_verbosity=debug apic=debug iommu=off
> module /boot/vmlinuz-2.6.32.28 nopat
> root=UUID=59c64afa-47a8-4a5f-a4cf-dbe3be20cc15 ro console=tty0
> console=ttyS0,115200n8 console=hvc0 earlyprintk=xen nomodeset initcall_debug
> debug loglevel=10
> module /boot/initrd.img-2.6.32.28
> }
> 
> In the debug, there is message like this:
> 
> Loading, please wait...
> mount: mounting none on /dev failed: No such device


So your /dev/sda is being seen. Not sure why the UUID hasn't been read, but
you could do 'root=/dev/sdaX' where X is the correct root partition.

This would replace the 'UUID=59...'.