From: Stefan Bader <stefan.bader@canonical.com>
To: Fantu <fantonifabio@tiscali.it>
Cc: xen-devel@lists.xensource.com
Subject: Re: Unable to start Precise domU PV on xen-unstable with xl
Date: Mon, 13 Feb 2012 16:41:57 +0100 [thread overview]
Message-ID: <4F392F45.3000903@canonical.com> (raw)
In-Reply-To: <1329146007080-5479529.post@n5.nabble.com>
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
next prev parent reply other threads:[~2012-02-13 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 14:38 Unable to start Precise domU PV on xen-unstable with xl Fantu
2012-02-13 14:53 ` Stefan Bader
2012-02-13 15:13 ` Fantu
2012-02-13 15:41 ` Stefan Bader [this message]
2012-02-14 9:19 ` Fantu
2012-02-14 11:16 ` Stefan Bader
2012-02-14 9:21 ` Fantu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F392F45.3000903@canonical.com \
--to=stefan.bader@canonical.com \
--cc=fantonifabio@tiscali.it \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.