From nobody Thu May 18 20:04:46 2023 X-Original-To: freebsd-emulation@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 4QMgtj3WCpz4ByKp; Thu, 18 May 2023 20:05:01 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 4QMgtj33Xmz3qpR; Thu, 18 May 2023 20:05:01 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-9659f452148so463203366b.1; Thu, 18 May 2023 13:05:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684440298; x=1687032298; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=G4dM1ngXWxsqCgO+4PUpcAO+4Gs9dWR5OuucCsS11L0=; b=HESOmDyidmmrgimBiCm2jmovhqshKh6SGvvQQgpDcd9L8XulR7HEu/Akad0AThUn8i xFI7x1cTDae4DyyLumebjs2j+XGw5bqtMcd3/25pM2qN9eUHKofmqKekVUsaucoMjVmc UnaPuXTLMIcbNUn6LkPGOmucs4XTtGDVGVTwUmrH8kwg94huuJpRqVGhNFk8QgJjoRan NiWN9Wk18UUybqwwXipv5Jx0JcTWmT+euCYv58jNHxJSNUUIzDFhWVFln0/ZR3sVrkbA paf8CzImU7r2Z6jYqerwmyCPvhY99OCDUXSXyKNFicUUXSskjqp3u4ee9l6siAKuoSpB GKIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684440298; x=1687032298; h=content-transfer-encoding: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=G4dM1ngXWxsqCgO+4PUpcAO+4Gs9dWR5OuucCsS11L0=; b=SvuROU+tShe8E9LFfax9+Oxbc6FykU7P2uaD23PxCsSy62kO6QLwlQ/Yz+f55KGOBt ItRHSdBXDf78jYfaB4imMsSFB60tsp4ujInwkEfDAFA+RWLxYhlN004BV5ikJBROvNR/ N4DmsJD1mRvf7k7QrKahIekow08P8Zmmo5qBgisU3vSb+s8ti1A8ORSWSowRq5zfYFkc 66mkCPmWG39iXumEUpV1PwG13lu5gDVqY+LYsMLzD3K3qtzodsz4juESujYxYhbuqKoy r8Vop2JqzGh+N4p1l+hN8fKQo68ECt7asMO7f51mqoXBG0aKPaisi7nXKQGS5CG+h3Ru GXsQ== X-Gm-Message-State: AC+VfDxxI2RZUMRre2UsUxuqw0fc/1G6RTF7YHOpxiIiRYmbhZwlD0QN C2eXIlfGO3g673yGQEg8Y17iJqWpUMwNoX79JspB+h+A X-Google-Smtp-Source: ACHHUZ7lGeNvtWkiHU7yWyrbe+ASz6qB9NnGfRyqWArXA9lfrFFEQNTFRElYb+dtWW6HOHd3h35TtAeQdUFbKfwRxWo= X-Received: by 2002:a17:907:9705:b0:957:943e:7416 with SMTP id jg5-20020a170907970500b00957943e7416mr367037ejc.15.1684440297933; Thu, 18 May 2023 13:04:57 -0700 (PDT) List-Id: Development of Emulators of other operating systems List-Archive: https://lists.freebsd.org/archives/freebsd-emulation List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-emulation@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Aryeh Friedman Date: Thu, 18 May 2023 16:04:46 -0400 Message-ID: Subject: Re: How is this possible To: Tomek CEDRO Cc: FreeBSD Mailing List , freebsd-emulation@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4QMgtj33Xmz3qpR 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 On Thu, May 18, 2023 at 3:03=E2=80=AFPM Tomek CEDRO wrot= e: > > On Thu, May 18, 2023 at 8:51=E2=80=AFPM Aryeh Friedmanwrote: > > On Thu, May 18, 2023 at 2:48=E2=80=AFPM Tomek CEDRO wrote: > > > If you create a ramdisk and build there it will be even faster.. > > > assuming space is enough (kernel should go, not sure about world).. I > > > have tried with 128GB RAM and it works quite well on older hardware.. > > > similar to newer hardware with 32GB RAM and nvme disk :-) > > > > See other replies two identical SSD's (same model number and capacity) > > backing both the physical OS and VM's OS (each on a different drive). > > As to NVM I still don't trust it even though it has been around for 7 > > or 8 years now (too much experience with OS wackiness with high end > > storage networking) > > True :-) I have additional nvme pci-e controller and fast nvme drive > as my OS storage.. on an older machine.. it really blows my sock off > (faster than SATA SSD).. but the raidz2 uses WD RED Pro 4x4TB HDD for > more important stuff and zfs stripe on WD RED 2x2TB as scratchpad :-P See below for ZFS problems... we purposely decided to not do anything fancier then mirroring and only then so one the drives can safely be backed up > > It would be good to know the VM (bhyve?) and host fs (ZFS?) and the vm > fs (UFS?) :-) I have noticed after switching to ZFS that my raid was a > lot faster on UFS.. but I had consistency errors on crash which now I > do not have with ZFS and I have really nice features now for instance > snapshots and amazingly flexible pools allocation :-) The machine this is replacing (hard crashed a few days ago) was ZFS and frankly ZFS posed more of a problem then a solution for restoring at the virtual drive level (zpool scrub cleared the error but corrupted the virtual drive then once I get the OS reinstalled it started spontaniously rebooting while doing a make -j12 DESTDIR=3D/ and thus the new machine).... due to problems with ZFS I decided to use UFS this time and rely of more traditional backups the ZFS as primary backups --=20 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org