From owner-freebsd-bugs@FreeBSD.ORG  Sat May  9 10:24:52 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CAC22E7E
 for <freebsd-bugs@FreeBSD.org>; Sat,  9 May 2015 10:24:52 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B4910151E
 for <freebsd-bugs@FreeBSD.org>; Sat,  9 May 2015 10:24:52 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t49AOqdL005919
 for <freebsd-bugs@FreeBSD.org>; Sat, 9 May 2015 10:24:52 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 200068] release/scripts/mk-vmimage.sh producing incorrect vmdk
 format vm-images
Date: Sat, 09 May 2015 10:24:52 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: ishmaeljx@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
 attachments.created
Message-ID: <bug-200068-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 09 May 2015 10:24:52 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200068

            Bug ID: 200068
           Summary: release/scripts/mk-vmimage.sh producing incorrect vmdk
                    format vm-images
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: ishmaeljx@gmail.com

Created attachment 156554
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=156554&action=edit
Possible fix to mkimg invocation

amd64 vmdk images for 10.1-STABLE and 11.0-CURRENT as found on ftp.freebsd.org
are not actually vmdk format files, but instead appear to be miscreated raw
image files.

Examining release/tools/vmimage.subr for both -head and -stable svn branches,
it appears that the mkimg invocation lost the passing of the -f argument during
a rewrite a few months ago.

Probably need to change all the mkimg invocations in vmimage.subr to include a
"-f ${VMFORMAT}" argument (see attached for possible fix).

-- 
You are receiving this mail because:
You are the assignee for the bug.