From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: VMware disk image type
Date: Mon, 04 Apr 2011 15:56:50 +0200 [thread overview]
Message-ID: <incin3$3vi$1@dough.gmane.org> (raw)
In-Reply-To: <BANLkTik=S6Ui--WVgGMZO0XiUoGsaQxU0g@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04-04-11 13:21, Mickael Chazaux wrote:
> Hi,
>
> 2011/2/23 Tom Rini <tom_rini@mentor.com>:
>> On 02/23/2011 05:48 AM, Mickael Chazaux wrote:
>>>
>>> Hi,
>>>
>>> I see there is a vmware.conf in conf/machine, but it does not generate
>>> vmdk (vmware virtual disk files) files. Here are the steps I take to
>>> do that:
>>>
>>> - create an empty file the size wanted (with dd),
>>> - format it to ext3 (mkfs.ext3 myfile)
>>> - mount it loopback (mount -o loop myfile /mnt)
>>> - untar the OE-generated rootfs in /mnt
>>> - create a /boot/extlinux.conf [1],
>>> - install extlinux in /boot (extlinux -i /mnt/boot)
>>> - umount,
>>> - convert to vmdk (using qemu-img -O vmdk myfile myfile.vmdk)
>>> - boot it in vmware.
>>>
>>> Is it possible to add a "vmdk" image to openembedded to do this
>>> automatically?
>>
>> Yes, patches would be welcome. This would reside in conf/bitbake.conf. See
>> the ubi/ubifs image examples for how to generate slightly complex images
>> like this. And I would recommend adding vmdk.ext[234] as the image names
>> (and supply at least one of them, someone else might step up and do the
>> regex for the others if you don't). Thanks!
>>
>
> The problem is the loopback mount, which requires root privileges, and
> is required by extlinux for its installation. Is there another method?
If your user is in the 'disk' group it should also work. Narcissus runs
as 'www-data' and generated OMAP SD images with loopmounts, adding
'www-data' to 'disks' fixed the weird problems we were seeing (vfat loop
mounts worked, ext3 didn't0.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNmc4iMkyGM64RGpERAuygAKCk1FXClMR8xQZU99Cu7d4ZIVsXhgCeP89h
XQPhqxENu/aE+9LsE9g1R88=
=J9PL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-04-04 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 12:48 VMware disk image type Mickael Chazaux
2011-02-23 21:42 ` Tom Rini
2011-04-04 11:21 ` Mickael Chazaux
2011-04-04 13:56 ` Koen Kooi [this message]
2011-04-04 14:00 ` Mike Westerhof
2011-04-04 14:07 ` Phil Blundell
2011-04-04 14:46 ` Tom Rini
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='incin3$3vi$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.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