From owner-freebsd-current@FreeBSD.ORG Sat Aug 23 20:49:52 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CE512438 for ; Sat, 23 Aug 2014 20:49:52 +0000 (UTC) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 54E833C55 for ; Sat, 23 Aug 2014 20:49:52 +0000 (UTC) Received: by mail-lb0-f180.google.com with SMTP id v6so10525616lbi.25 for ; Sat, 23 Aug 2014 13:49:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=95XHE47YGDj0pl1ocWOXeAT6eiPVfi+HX8XXo3Otx2Y=; b=hpf00HQQIZiW8mfI2c7CwNDrWZO6/6WHE+vq9Ve645Hzp1Db6Ddlf8ZLtWomps9A/M Pfh08vz3E0ofN+l5B9X+lei75DcoTFrSetec8nF1QUc0k7VvvlEfI/O+FLEU5uQWiDCY 5emvM5RLmsmAnlUbK3OwZpUBYFI5Y2bGX9kdXh2D/8uuOqamEHqbWalOzD8Cc1M9rq9C 6Mq5X9dp/wksbTNz4wI9LeeO2OzGFPQQ/y23xfPrfhHrQiGGXqeWOyKP08lR+iLuHQfZ A46Iz41TXnGpkWv60E1mLmGTFJKebIDcni7OSwUUVWH1AIV1Z+egxRnyUwCKi5sUjPTQ CT1g== MIME-Version: 1.0 X-Received: by 10.112.160.38 with SMTP id xh6mr11203641lbb.21.1408826990150; Sat, 23 Aug 2014 13:49:50 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.197.107 with HTTP; Sat, 23 Aug 2014 13:49:50 -0700 (PDT) In-Reply-To: <7CE168C1-6AF3-4AD2-80DB-192AEC49FD2B@xcllnt.net> References: <853B0396-2C19-49DF-A8E8-8EB43D107597@xcllnt.net> <7CE168C1-6AF3-4AD2-80DB-192AEC49FD2B@xcllnt.net> Date: Sat, 23 Aug 2014 13:49:50 -0700 X-Google-Sender-Auth: u8oImlcMz_TVYNqVES2wGy0w56I Message-ID: Subject: Re: mkimg used to create gpt image, problem booting From: Craig Rodrigues To: Marcel Moolenaar Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Aug 2014 20:49:52 -0000 On Sat, Aug 23, 2014 at 12:11 PM, Marcel Moolenaar wrote: > > Could be. Try the -P option to mkimg. It sets the > underlying (unexposed) physical sector size while > still working with the visible 512 bytes sectors. > The net effect is that for the GPT scheme things > get aligned to the physical sector size and that > it also causes the image size to be rounded. > > You can also try emitting vmdk directly to see if > that makes a difference. vmdk also has the side- > effect of rounding the image to the grain size. I tried the following experiments: mkimg -v -f vmdk -s gpt -b test1/boot/pmbr -p freebsd-boot:=test1/boot/gptboot -p freebsd-ufs:=/tmp/file.img -o /tmp/foo1.vmdk When I tried to boot the image in QEMU, I had the same problem as before. It looks like it started writing the image on block 3, same as before. I also tried adding the -P flag, with different values like 2048 and 4096. I ran into the same problem. Hmm. -- Craig