From nobody Fri Jul 14 18:08:19 2023 X-Original-To: virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4R2fZp2Qtqz4mbHc for ; Fri, 14 Jul 2023 18:07:30 +0000 (UTC) (envelope-from rob.fx907@gmail.com) Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R2fZp0Vb9z49hh for ; Fri, 14 Jul 2023 18:07:30 +0000 (UTC) (envelope-from rob.fx907@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-x132.google.com with SMTP id 2adb3069b0e04-4fbe5161fbeso666496e87.0 for ; Fri, 14 Jul 2023 11:07:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689358048; x=1691950048; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ib+JAyGnvAg06chNZ3/vUgNLYUzuYvjPXwnC+7XvDaU=; b=JfK8FpmXwpS2CiJ5Db7coxVTLQUV/lD6mmnZIVBilirHajOoGi7mJowWhxdlfoRnkS OaWpZTKHOvv7Z6NRwAVg8r7GKqJ0pMC78a0JIZbggLAlJltI5ZDy88FP1PY6e5EAPJ2q jrnfYtefYeiSH/j5HNvgvdwaKrAMxHk4UWZ1p6LUBok7X9VwlHwbl2eXweOzGr87a90U dVnr6LTdUUnNsBTmLZHIKqGZp5jpLYgbJuzDLUllroFL/2rcA6DiZqciHcEVcs5p7p37 tNSi3n2FF0bQjJAPgKLxyBtyM4EH8fU1V6nVv/CtvvUfRrR0s8+yzW5eyFYWEd5MVPll EDDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689358048; x=1691950048; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ib+JAyGnvAg06chNZ3/vUgNLYUzuYvjPXwnC+7XvDaU=; b=OHIazIOYAPVTXdGoiwZ9SJS4yPrC5DxrNDrMcj3e8CPNyXtcZSPloe0AhwiDABpgtX kks0D8B2JFI4yn1vt8s7XtkTnZLHEbMDiwgLsXcjK83DuztC5L6k+ejo6bOLs10uXhlV IWQgGvB1FvBVtORH5CgzWK4xb7R8k+JMGURHqm7kIgJk4cAQ9ChI7aqUsa4A+AuT1TZS /+8rxC5OC2nPPAmTE07QjXxM38kZnnzRIvB6+LY1R6KD/AQ8ALtW8YQX8+MKlDoTftWZ iaZDJXYDIYGQiZyET93F5fMOpesq/AqTtnCruPlRMy/n3G+uHPqyNne58TqUOaVFBFO9 T1bg== X-Gm-Message-State: ABy/qLZiDrqQpv0Hm2r7rcyVp0yUExc0mg4aZnlWHI4cbvG/MZql8NXJ noOcOikLV8DJIp3byNazL7rZRWtzn+Xlad9a9Tk= X-Google-Smtp-Source: APBJJlGlObGf3razMdBjC/eWnxv5NMETfu5/PxfdoUFs55PUOOOr1Q/COOLBTAHm2IODwOcNmDbkTb+WpvFm/7ecPc4= X-Received: by 2002:a2e:9016:0:b0:2b6:cd7f:5ea8 with SMTP id h22-20020a2e9016000000b002b6cd7f5ea8mr3423641ljg.1.1689358047628; Fri, 14 Jul 2023 11:07:27 -0700 (PDT) List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org MIME-Version: 1.0 References: <67FDC8A8-86A6-4AE4-85F0-FF7BEF9F2F06@gmail.com> <6b98da58a5bd8e83bc466efa20b5a900298210aa.camel@FreeBSD.org> <8387AC83-6667-48E5-A3FA-11475EA96A5F@gmail.com> <986A83D8-E0E0-4030-9369-A5B3500E27C6@gmail.com> <79fabe94-b800-c713-48ea-518da1f74e4d@shrew.net> In-Reply-To: <79fabe94-b800-c713-48ea-518da1f74e4d@shrew.net> From: Rob Wing Date: Fri, 14 Jul 2023 10:08:19 -0800 Message-ID: Subject: Re: BHYVE SNAPSHOT image format proposal To: Matthew Grooms Cc: virtualization@freebsd.org Content-Type: multipart/alternative; boundary="00000000000053d1c006007652af" X-Rspamd-Queue-Id: 4R2fZp0Vb9z49hh X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000053d1c006007652af Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jul 14, 2023 at 9:40=E2=80=AFAM Matthew Grooms = wrote: > > I see a need to define a format for bhyve so it's possible to mix > different sections and encodings inside a unified stream. But all the > data in your nvlist example above can be easily be represented as text. > We already have JSON, YAML, XML, etc ... By adopting an preexisting > format, we could retain the snapshot structure instead of lifting it up > into the stream format. Even if we decide to break the structure up into > different nvlist stream sections, using a common format would allow > other tools to more easily parse and validate the structure inside these > sections. Isn't that a good thing? Is there a reason we're trying to > reinvent the wheel here? > Does JSON support storing binary data? I'm under the impression that it does not. --00000000000053d1c006007652af Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Jul 14, 2023 at 9:= 40=E2=80=AFAM Matthew Grooms <mgroo= ms@shrew.net> wrote:

I see a need to define a format for bhyve so it's possible to mix
different sections and encodings inside a unified stream. But all the
data in your nvlist example above can be easily be represented as text. We already have JSON, YAML, XML, etc ... By adopting an preexisting
format, we could retain the snapshot structure instead of lifting it up into the stream format. Even if we decide to break the structure up into different nvlist stream sections, using a common format would allow
other tools to more easily parse and validate the structure inside these sections. Isn't that a good thing? Is there a reason we're trying t= o
reinvent the wheel here?

Does JSON supp= ort storing binary data? I'm under the impression that it does not.
=
--00000000000053d1c006007652af--