From: Bai Shuwei <baishuwei@gmail.com>
To: Mulyadi Santosa <mulyadi.santosa@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] diskimage HOWTO
Date: Tue, 25 Aug 2009 16:48:51 +0800 [thread overview]
Message-ID: <f3566d60908250148p45503750qc402b4ce25eb45d4@mail.gmail.com> (raw)
In-Reply-To: <f284c33d0908250041l4973e75amf7357d1c905c31af@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
Hi, Kevin:
I am not familiar the kpartx too. this is the result, I think I should
rebuild my kernel to support device-mapper :(
weslab:/home/baishw/crosscompile/qemu/xtratum# kpartx -l rootfs
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.27 (2008-06-25)(compat) and kernel driver
loop1p1 : 0 128457 /dev/loop1 63
On 8/25/09, Mulyadi Santosa <mulyadi.santosa@gmail.com> wrote:
>
> On Tue, Aug 25, 2009 at 2:37 PM, Kevin Wolf<kwolf@redhat.com> wrote:
>
> > You would use "kpartx -a test.img" which creates devices like
> > /dev/mapper/loop0p1 for each partition. You can work with it like you
> > would do with losetup and afterwards remove it with "kpartx -d test.img".
> >
> > But actually Laurent's solution doesn't look too bad either. Didn't know
> > about it until now.
> >
> > Kevin
> >
>
> Thanks for the kind example, Kevin. Couple nice lessons I got today :)
> Not bad to me too as well
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer
> blog: the-hydra.blogspot.com
>
--
Love other people, as same as love yourself!
Don't think all the time, do it by your hands!
Personal URL: http://dslab.lzu.edu.cn:8080/members/baishw/
E-Mail: baishuwei@gmail.com or baishuwei@dslab.lzu.edu.cn
[-- Attachment #2: Type: text/html, Size: 2240 bytes --]
next prev parent reply other threads:[~2009-08-25 8:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 5:39 [Qemu-devel] diskimage HOWTO Bai Shuwei
2009-08-24 7:48 ` Kevin Wolf
2009-08-24 8:30 ` Bai Shuwei
2009-08-24 17:04 ` Mulyadi Santosa
2009-08-25 3:55 ` Bai Shuwei
2009-08-25 5:03 ` Mulyadi Santosa
2009-08-25 7:06 ` Kevin Wolf
2009-08-25 7:32 ` Mulyadi Santosa
2009-08-25 7:37 ` Kevin Wolf
2009-08-25 7:41 ` Mulyadi Santosa
2009-08-25 8:48 ` Bai Shuwei [this message]
2009-08-25 7:28 ` Laurent Vivier
2009-08-24 18:13 ` [Qemu-devel] Re: [Buildroot] " Steve Calfee
2009-09-11 9:32 ` [Qemu-devel] " Richard W.M. Jones
[not found] ` <87ab11vhza.fsf@macbook.be.48ers.dk>
2009-09-11 11:38 ` Richard W.M. Jones
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=f3566d60908250148p45503750qc402b4ce25eb45d4@mail.gmail.com \
--to=baishuwei@gmail.com \
--cc=kwolf@redhat.com \
--cc=mulyadi.santosa@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).