Date: Fri, 22 Aug 2014 13:45:26 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Craig Rodrigues <rodrigc@freebsd.org> Cc: freebsd-current Current <freebsd-current@freebsd.org> Subject: Re: mkimg used to create gpt image, problem booting Message-ID: <853B0396-2C19-49DF-A8E8-8EB43D107597@xcllnt.net> In-Reply-To: <CAG=rPVeucq%2BsMxe_NPe3Og939o=Sg4WGfYL7PjA1uXGU8uL=8g@mail.gmail.com> References: <CAG=rPVeucq%2BsMxe_NPe3Og939o=Sg4WGfYL7PjA1uXGU8uL=8g@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Aug 22, 2014, at 9:49 AM, Craig Rodrigues <rodrigc@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@xcllnt.net [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlP3q+YACgkQpgWlLWHuifaVtACZAQb8lsBLWhd2gf3eUQRHaazu EjQAn08QJPUlK3klu06C7PSFwog3mkkO =PXbQ -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?853B0396-2C19-49DF-A8E8-8EB43D107597>