mkimg used to create gpt image, problem booting

Craig Rodrigues rodrigc at
Fri Aug 22 16:49:17 UTC 2014


I did the following:

(1)  Created a chroot from a src checkout/build with:
         make installworld DESTDIR=/opt2/branches/test1
         make installkernel DESTDIR=/opt2/branches/test1
         make distribution DESTDIR=/opt2/branches/test1

(2)  Created a UFS image, /tmp/file.img using makefs based on the
contents of /opt2/branches/test1

(3)  Verified with bhyve that the UFS image booted properly.

(4)  Created an image with:
cd /opt2/branches
mkimg -v -s gpt -b test1/boot/pmbr -p freebsd-boot:=test1/boot/gptboot
-p freebsd-ufs:=/tmp/file.img  -o /tmp/foo1.img

(5)  Tried to boot the image with qemu:

qemu-system-x86_64 -m 2048 -hda /tmp/foo1.img

SeaBIOS (version

     iPXE ( 00:03.0 C900 PCI2.10 PnP
PMM+7FFC6110+7FF26110 C900

     Booting from Hard Disk...

     BTX loader 1.00  BTX version is 1.02
     Consoles: internal video/keyboard
     BIOS drive A: is disk0
     BIOS drive C: is disk1
     BIOS 639kB/2096120kB available memory

     FreeBSD/x86 bootstrap loader, Revision 1.1
     (root at, Wed Aug 20 21:58:27 PDT 2014)

     can't load 'kernel'

     Type '?' for a list of commands, 'help' for more detailed help.

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?



More information about the freebsd-current mailing list