From nobody Tue May 02 16:04:02 2023 X-Original-To: freebsd-hackers@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 4Q9lJK5rZdz496fl; Tue, 2 May 2023 16:04:17 +0000 (UTC) (envelope-from gusev.vitaliy@gmail.com) Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 4Q9lJJ6PW3z4LP8; Tue, 2 May 2023 16:04:16 +0000 (UTC) (envelope-from gusev.vitaliy@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=OcmOsu+W; spf=pass (mx1.freebsd.org: domain of gusev.vitaliy@gmail.com designates 2a00:1450:4864:20::22b as permitted sender) smtp.mailfrom=gusev.vitaliy@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-lj1-x22b.google.com with SMTP id 38308e7fff4ca-2aa39ce5d26so40035301fa.1; Tue, 02 May 2023 09:04:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683043454; x=1685635454; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=QU8tYAy4WZ9pbgxX9JzfnrW1kukUjmYcxtPRSGSst5I=; b=OcmOsu+WBcaN6sJt5MPJWkCvXdQnYfaKKZMtdOwFEuitSQivYBliqWYFt0xL7YwPNO rfs+nCnMI6lvHb8v0bGPCDpNzQigv29EWubYdbaWrPILVSKTLH24jlVZ9Tsu8AW6OrlD w2XNK445Gl+DpDHpnEZLILu9RwDNxahtL96X2VZcFV/t4z9obUfgB0let5FBx10qdnAA RMrTJKKnSAC0IJnFO8us2mdVzP62r9BwhzdaN8JcLakefeDn0VSTdOKcYEwLqpBhbLpU YDIhrA3WpmMznkSQpc8tAZ9RoZNdnP+DYGsubijHddtcbuqse6crVppJOklN8e433Kyt joPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683043454; x=1685635454; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=QU8tYAy4WZ9pbgxX9JzfnrW1kukUjmYcxtPRSGSst5I=; b=DUGskCo+1Uz6EUgXlUgpV68jKjOVOZ9VJmYbnzqL3+u57aB1YzLKxGhZhFAnvtCPDT o0dPwIDmtJUcdupS0sgAISHqu5khgq6XYOSfHKo1VuNpdF/bdQ71CvFWiKVGcn8HizMO OuZaXtb7GlKCsg+Q7i2XaD/t7V6RR/xu3xfWNvKkIgkk1cOwad3cTlowfuXQbr47qc1U qitUNuaXbtGbtlMs0+nAbMlLbo8vh4pJOdi+v+HbXf7b/IRnn2kmz9fZ48ndUQ3347wi ulzLbHnpI/wTDWX9k8a9SRTvfHzktTd9UpfhWFISdLn8HbfZC3Aat6Ox4+6YJqMtnoDj ZpkA== X-Gm-Message-State: AC+VfDxLa5MRlRcNtG2cFSjX2Pc3J4LjY+R5yUYfQ7zQISEYgxfjTxVZ Y5ehXkcql1JmwUESsNKj210= X-Google-Smtp-Source: ACHHUZ6CfOOyQ4QngnjYymTo/zwri0JCT4wG0UEAwWeNTXtVmnU7rHrHeuhlbi2HNO0Xa08UZF96rw== X-Received: by 2002:a2e:98c5:0:b0:2a8:e6f8:301e with SMTP id s5-20020a2e98c5000000b002a8e6f8301emr4595615ljj.28.1683043454199; Tue, 02 May 2023 09:04:14 -0700 (PDT) Received: from smtpclient.apple ([188.187.60.230]) by smtp.gmail.com with ESMTPSA id w4-20020ac25d44000000b004eb0c51780bsm5443260lfd.29.2023.05.02.09.04.13 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 May 2023 09:04:13 -0700 (PDT) From: Vitaliy Gusev Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_07C1A3F1-22E1-41CC-8145-2FE0D588B957" List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\)) Subject: Re: BHYVE_SNAPSHOT Date: Tue, 2 May 2023 19:04:02 +0300 In-Reply-To: Cc: =?utf-8?Q?Corvin_K=C3=B6hne?= , Matthew Grooms , freebsd-hackers@freebsd.org, freebsd-virtualization@freebsd.org, Elena Mihailescu , Mihai Carabas To: Rob Wing References: <89c84bd7-a925-02f4-acbe-12c3000e7007@shrew.net> <3ab4e6d94fb0153fb6ff4a53ac6f53b2eaae0cf7.camel@FreeBSD.org> X-Mailer: Apple Mail (2.3731.500.231) X-Spamd-Result: default: False [-2.44 / 15.00]; SUBJ_ALL_CAPS(1.05)[14]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.990]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MV_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TAGGED_RCPT(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::22b:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,freebsd-virtualization@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; TAGGED_FROM(0.00)[]; RCPT_COUNT_SEVEN(0.00)[7]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_TO(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_CC(0.00)[freebsd.org,shrew.net,gmail.com] X-Rspamd-Queue-Id: 4Q9lJJ6PW3z4LP8 X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_07C1A3F1-22E1-41CC-8145-2FE0D588B957 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 2 May 2023, at 18:38, Rob Wing wrote: >=20 > Do you plan on saving the guest memory into the nvlist? If I have VM = with 8 gigs of memory, will the nvlist implementation allocate 8 gigs of = memory for the nvlist then write it out to disk? Or..? >=20 > All the bullet points look good to me. >=20 > -Rob Of course no. Guest memory should be saved as is. As possible = improvement - only dirty memory/pages.=20 I was taking about saving with nvlist: device=E2=80=99s variables, = registers, internal data, etc.=20 Overall description will be provided shortly. =E2=80=94=E2=80=94=E2=80=94 Vitaliy Gusev --Apple-Mail=_07C1A3F1-22E1-41CC-8145-2FE0D588B957 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On 2 May = 2023, at 18:38, Rob Wing <rob.fx907@gmail.com> = wrote:

Do you plan on saving the = guest memory into the nvlist? If I have VM with 8 gigs of memory, will = the nvlist implementation allocate 8 gigs of memory for the nvlist then = write it out to disk? Or..?

All the bullet points look good to = me.

-Rob


Of course no. Guest memory should be saved as is. As possible = improvement  -  only dirty = memory/pages. 

I was taking about saving = with nvlist: device=E2=80=99s variables, registers, internal data, = etc. 

Overall description will be provided = shortly.

=E2=80=94=E2=80=94=E2=80=94
Vi= taliy Gusev


= --Apple-Mail=_07C1A3F1-22E1-41CC-8145-2FE0D588B957--