mkimg used to create gpt image, problem booting

[Marcel Moolenaar]

On Aug 22, 2014, at 9:49 AM, Craig Rodrigues <rodrigc at freebsd.org> wrote:

> 
> (5)  Tried to boot the image with qemu:
> 
> qemu-system-x86_64 -m 2048 -hda /tmp/foo1.img

*snip*

> If I mdconfig the foo1.img disk image, and do a gpart show, I see:
> 
> =>      3  1784944  md0  GPT  (872M)
>        3       32    1  freebsd-boot  (16K)
>       35  1784912    2  freebsd-ufs  (872M)
> 
> Any idea what I am doing wrong?

To the best of my knowledge, qemu is the thing you're
doing wrong :-)

I have so far not been able to boot an image created
by mkimg with a FreeBSD-hosted qemu.
o   VMware and VirtualBox are fine.
o   A non-FreeBSD hosted qemu also works fine.

If your host is running -current, make sure to set
MALLOC_CONF=junk:false. It improves behaviour on
FreeBSD for boot0/boo1.

HTH (probably not),

-- 
Marcel Moolenaar
marcel at xcllnt.net


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20140822/7b00c344/attachment.sig>