From: "Peter Teoh" <htmldeveloper@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Mount errors in QEMU
Date: Sun, 1 Jun 2008 08:09:13 +0800 [thread overview]
Message-ID: <804dabb00805311709ha5abdbdj62aa63159747d89f@mail.gmail.com> (raw)
In-Reply-To: <f284c33d0805310651l751315c9nbf05cdb5018fcd6f@mail.gmail.com>
On 5/31/08, Mulyadi Santosa <mulyadi.santosa@gmail.com> wrote:
> Hi...
>
> maybe your "root=' needs to point to the LVM volume instead of real
> partition. ANd just make sure your kernel already included LVM
> support...be it LVM version 1 or 2.
>
> regards,
>
>
> Mulyadi.
>
>
Thanks for the reply. As shown in "df", the root is not at the vg
level, as vg is just for storing a different set of data.
But I did try anyway. Let me try again...
Thanks Mulyadi..
>
--
Regards,
Peter Teoh
prev parent reply other threads:[~2008-06-01 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 8:22 [Qemu-devel] Mount errors in QEMU Peter Teoh
2008-05-31 13:51 ` Mulyadi Santosa
2008-06-01 0:09 ` Peter Teoh [this message]
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=804dabb00805311709ha5abdbdj62aa63159747d89f@mail.gmail.com \
--to=htmldeveloper@gmail.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).