From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Bader Subject: Re: Unable to start Precise domU PV on xen-unstable with xl Date: Mon, 13 Feb 2012 16:41:57 +0100 Message-ID: <4F392F45.3000903@canonical.com> References: <1329143937594-5479428.post@n5.nabble.com> <4F3923D6.2000502@canonical.com> <1329146007080-5479529.post@n5.nabble.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1329146007080-5479529.post@n5.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 13.02.2012 16:13, Fantu wrote: > Thanks for reply, test system have already dom0 kernel with > bugfix...2.6.32-5-xen-amd64 version 2.6.32-41 > linux-2.6 (2.6.32-40) stable; urgency=high > .... > * xen: blkback: don't fail empty barrier requests (Closes: #637234) > > http://packages.debian.org/changelogs/pool/main/l/linux-2.6/linux-2.6_2.6.32-41/changelog > > blkid is already on log file attached in first post > > mounting image on dom0 is right uuid and working: > mount -o loop /mnt/vm/disks/PRECISE.disk1.xm /mnt/tmp/ > mount > ... > /dev/loop0 on /mnt/tmp type ext4 (rw) > blkid > /dev/loop0: UUID="b58257ed-87ed-480f-86dc-9d06cefb2267" TYPE="ext4" > Ok, so that looks ok. The /proc/partitions output looks like xvda1 is present (at least ot the kernel). When you fall into the emergency shell, is there a /dev/xvda1, and then as the next piece in that chain an entry in /dev/disk-by-uuid/ ? -Stefan > -- > View this message in context: http://xen.1045712.n5.nabble.com/Unable-to-start-Precise-domU-PV-on-xen-unstable-with-xl-tp5479428p5479529.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel