From nobody Sat Feb 18 14:59:49 2023 X-Original-To: freebsd-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 4PJsLM5DK9z3sbcw for ; Sat, 18 Feb 2023 15:00:27 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (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 4PJsLM0wZ1z3mx0 for ; Sat, 18 Feb 2023 15:00:27 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=T4ygrKTM; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2a00:1450:4864:20::533 as permitted sender) smtp.mailfrom=marietto2008@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x533.google.com with SMTP id dm15so4425526edb.0 for ; Sat, 18 Feb 2023 07:00:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=iyw0ZQjPRhWCAeYSOaHLBw52sfrdssThJcqD1EEpFso=; b=T4ygrKTMuQznc0vY25+tiAA25qTtBNNZW1pjKV83l9dMtqbj1AqPnzhWi+NuDmq8B1 MabKhFcyKR/wUhZo8cu7Yk34KJ5C2KD2TnwZsd1eS3LKdJleAvQiOtkcj/885Ej/Z08b ebpZ4Puee3ZgnEH4PXAD1DJ023gKNi8YikEn2Su+LW3H5hXPip2YRT786bPRhceK4ZA5 ZC1HViyFdxRnNfzqeUZU/NAzMfYZ3u+buo1aZbocZe7hcDuFz8WNRaECai+6qqwFgRp+ y/Xmckv2+hYi/SD1Z9axg3NAtNlW3Ir4u/j6sRUFaQBna99l3DmgKmtnWx4GhbxMIBh2 cuZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=iyw0ZQjPRhWCAeYSOaHLBw52sfrdssThJcqD1EEpFso=; b=PGzB80pNKa2ALJCLHT2ZLjDmu+EaHmZUEX845nyOxpG0g7tOlLpl3AeMqGlaPfWA3P blymBlml1DeIKL+C+ZpZGBKjzHvFH/U7cB4zFgAk2Gl3pTboXRx0+jjiYwBDXrIR9vo+ RoqjzcN7oMVaeFNxHHNm/kgvBJGPmq6pBpxzAKf5OSclmZpkYgXQ8C7fDwChYyXI68XC lR4IAnG5/tLm6fPGY7ZjL9TgEpepu3uMF6ITc0t0zn1qhNUMRtLVBpzIUORbj5SXRTEK 2/IO7g1FNvZcKg46VEfz5Htgc0S2NyaZi4v1w8sqoeO+EdU7rj6e8LODcD6eDhUQQjRD BEGg== X-Gm-Message-State: AO0yUKXtxup4OMVY9WXhU8T3Z484DHaxc+S+vb74JfOILDhUvx9OBCBr Qip+Ah5jliwtZq82NgfC5ICRMM+v8yD/j8MWNSmKOhgCCS50Hw== X-Google-Smtp-Source: AK7set9ZF/8KepWhABsgGuSheI1X/gr7BjPRyQYD1XtWtz3Rp9aECmscEpPAxJ+tUuhm+ISKqmYza0Qxoh3InKZHyoQ= X-Received: by 2002:a50:9fa6:0:b0:4ad:72b2:cf57 with SMTP id c35-20020a509fa6000000b004ad72b2cf57mr136651edf.0.1676732425445; Sat, 18 Feb 2023 07:00:25 -0800 (PST) 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 From: Mario Marietto Date: Sat, 18 Feb 2023 15:59:49 +0100 Message-ID: Subject: Why Blender Cycles is not able to detect my GPU(s) and CUDA within the Ubuntu / Linuxulator To: FreeBSD virtualization Content-Type: multipart/alternative; boundary="0000000000009a26b905f4fab05c" X-Spamd-Result: default: False [-2.06 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.99)[-0.993]; NEURAL_SPAM_SHORT(0.94)[0.937]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::533:from]; DKIM_TRACE(0.00)[gmail.com:+]; RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_FROM(0.00)[gmail.com]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4PJsLM0wZ1z3mx0 X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --0000000000009a26b905f4fab05c Content-Type: text/plain; charset="UTF-8" Hello to everyone. I've just installed Ubuntu 22.10 with the Linuxulator on FreeBSD 13.1-RELEASE p6 as well as these components inside it : 1. nvidia driver Version: 525.78.01 + CUDA 12 2. Blender 3.2.2 The nvidia driver 525.78.1 + CUDA 12 work correctly within the linuxulator : https://ibb.co/8Ps8J81 and Cycles is already able to detect the nvidia driver + CUDA,but only if blender runs on FreeBSD. Give a look at this picture : https://ibb.co/rwZ7q8Q What I want to do is to run Blender and I want to render my projects with cycles using the CUDA libraries and my GPU(s) within the linux emulation layer. Is this supposed to work ? The error that Blender gives when I try to do that are the the following ones : root@marietto:/# blender Read prefs: /root/.config/blender/3.2/config/userpref.blend libGL error: glx: failed to create dri2 screen libGL error: failed to load driver: nouveau could not get a list of mounted file-systems /var/run/user/1001/gvfs/ non-existent directory Saved session recovery to '/tmp/quit.blend' Blender quit why do I use root ? because as a normal user Blender does not start at all. marietto@marietto:~$ blender Unable to open a display Aborted I'm very curious to understand the reason(s) of the errors I see below : libGL error: glx: failed to create dri2 screen libGL error: failed to load driver: nouveau My sensation is that they can be fixed. If I do : cp -r ./blender-3.2.2-linux-x64/3.2/scripts/addons/cycles/lib /compat/ubuntu2210/usr/share/blender/scripts/addons/cycles/ I see this additional error : CUDA cuInit: Unknown error but if I remove the lib directory : rm -r /compat/ubuntu2210/usr/share/blender/scripts/addons/cycles/lib the error "CUDA cuInit: Unknown error" disappears,but the other errors are still there. It seems to me that Blender looks for the nouveau driver and it can't find it. But it should look like the nVidia driver. Since the nouveau driver does not support CUDA,maybe it should be "unlinked" from Blender and Blender should be "linked" to the nvidia driver,in some way. What do you think ? -- Mario. --0000000000009a26b905f4fab05c Content-Type: text/html; charset="UTF-8"
Hello to everyone.

I've just installed Ubuntu 22.10 with the Linuxulator on FreeBSD 13.1-RELEASE p6 as well as these components inside it :

  1. nvidia driver Version: 525.78.01 + CUDA 12
  2. Blender 3.2.2

The nvidia driver 525.78.1 + CUDA 12 work correctly within the linuxulator :

https://ibb.co/8Ps8J81

and Cycles is already able to detect the nvidia driver + CUDA,but only if blender runs on FreeBSD. Give a look at this picture :

https://ibb.co/rwZ7q8Q

What I want to do is to run Blender and I want to render my projects with cycles using the CUDA libraries and my GPU(s) within the linux emulation layer. Is this supposed to work ? The error that Blender gives when I try to do that are the the following ones :

root@marietto:/# blender

Read prefs: /root/.config/blender/3.2/config/userpref.blend
libGL error: glx: failed to create dri2 screen
libGL error: failed to load driver: nouveau
could not get a list of mounted file-systems
/var/run/user/1001/gvfs/ non-existent directory
Saved session recovery to '/tmp/quit.blend'
Blender quit

why do I use root ? because as a normal user Blender does not start at all.

marietto@marietto:~$ blender
Unable to open a display
Aborted

I'm very curious to understand the reason(s) of the errors I see below :

libGL error: glx: failed to create dri2 screen
libGL error: failed to load driver: nouveau

My sensation is that they can be fixed. If I do :

cp -r  ./blender-3.2.2-linux-x64/3.2/scripts/addons/cycles/lib /compat/ubuntu2210/usr/share/blender/scripts/addons/cycles/

I see this additional error :

CUDA cuInit: Unknown error

but if I remove the lib directory :

rm -r /compat/ubuntu2210/usr/share/blender/scripts/addons/cycles/lib

the error "CUDA cuInit: Unknown error" disappears,but the other errors are still there.

It seems to me that Blender looks for the nouveau driver and it can't find it. But it should look like the nVidia driver. Since the nouveau driver does not support CUDA,maybe it should be "unlinked" from Blender and Blender should be "linked" to the nvidia driver,in some way. What do you think ?

--
Mario.
--0000000000009a26b905f4fab05c-- From nobody Sun Feb 19 13:21:14 2023 X-Original-To: freebsd-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 4PKR5W6zLPz3r7dY for ; Sun, 19 Feb 2023 13:21:19 +0000 (UTC) (envelope-from torsten.kaestel@cgnf.net) Received: from smtp.cgnf.net (smtp.cgnf.net [217.91.244.36]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PKR5V5k5cz4St0 for ; Sun, 19 Feb 2023 13:21:18 +0000 (UTC) (envelope-from torsten.kaestel@cgnf.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cgnf.net header.s=mail header.b=BpKVMwND; spf=pass (mx1.freebsd.org: domain of torsten.kaestel@cgnf.net designates 217.91.244.36 as permitted sender) smtp.mailfrom=torsten.kaestel@cgnf.net; dmarc=pass (policy=reject) header.from=cgnf.net Received: from smtp.cgnf.net (localhost [127.0.0.1]) by smtp.cgnf.net (Postfix) with ESMTP id AC9FD202B5 for ; Sun, 19 Feb 2023 14:21:14 +0100 (CET) Content-Type: multipart/alternative; boundary="------------atcRFIVP49Y8OJziJ0w0ACSG" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cgnf.net; s=mail; t=1676812874; bh=aPsb0jKydwUEmrof7qqCiodMv9suXVFx60P8pwXOkvk=; h=Date:To:From:Subject:From; b=BpKVMwND6hQHP+UJJ661dstMN2bMvgee1NCu39qEzAI7CyM4OdPJkvOjEN6ABW5Ph P57XbOGooxKzbGxct8qZWFn8jtIPBcWgPNoKLze6xVx/bmqstwjuAWFZgYfYJlG9ac UGT6jwpS7DBobaT26rUvGcimhT7OtfiIwTM2qLzc= Message-ID: Date: Sun, 19 Feb 2023 14:21:14 +0100 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 To: freebsd-virtualization@freebsd.org Content-Language: de-DE From: =?UTF-8?Q?Torsten_K=c3=a4stel?= Subject: xn_txeof Warning repsonse is -1! X-Antivirus: Avast (VPS 230219-0, 19.2.2023), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: ClamAV using ClamSMTP X-Spamd-Result: default: False [1.05 / 15.00]; URI_COUNT_ODD(1.00)[3]; NEURAL_HAM_SHORT(-0.98)[-0.984]; NEURAL_SPAM_MEDIUM(0.95)[0.948]; R_MIXED_CHARSET(0.71)[subject]; DMARC_POLICY_ALLOW(-0.50)[cgnf.net,reject]; NEURAL_SPAM_LONG(0.37)[0.375]; R_SPF_ALLOW(-0.20)[+ip4:217.91.244.36]; R_DKIM_ALLOW(-0.20)[cgnf.net:s=mail]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ASN(0.00)[asn:3320, ipnet:217.80.0.0/12, country:DE]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_EXCLAIM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[cgnf.net:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4PKR5V5k5cz4St0 X-Spamd-Bar: + X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --------------atcRFIVP49Y8OJziJ0w0ACSG Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hello all, I am running a firewall OPNsense 23.1.1 with FreeBSD 13.1-RELEASE-p6 virtualized on a server with Ubuntu 20.04. After a kernel update in the Ubuntu dom0 to 5.4.0-139 , I repeatedly get the following error message when starting my OPNSense VM in its console xn_txeof: WARNING: response is -1! This means that the firewall is not working.  Also with the hwe kernel 5.15.0-60 of Ubuntu this error occurs. With the Ubuntu kernel 5.4.0-136 the error does not occur. I have tried google but can't find anything to help with this message. Does anyone have any idea where this is coming from or what setting I need to change in freebsd. What setting could I adjust? Many greetings Torsten -- Diese E-Mail wurde von Avast-Antivirussoftware auf Viren geprüft. www.avast.com --------------atcRFIVP49Y8OJziJ0w0ACSG Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Hello all,

I am running a firewall OPNsense 23.1.1 with FreeBSD 13.1-RELEASE-p6 virtualized on a server with Ubuntu 20.04. After a kernel update in the Ubuntu dom0 to 5.4.0-139 , I repeatedly get the following error message when starting my OPNSense VM in its console

xn_txeof: WARNING: response is -1!

This means that the firewall is not working.  Also with the hwe kernel 5.15.0-60 of Ubuntu this error occurs.

With the Ubuntu kernel 5.4.0-136 the error does not occur.  

I have tried google but can't find anything to help with this message. Does anyone have any idea where this is coming from or what setting I need to change in freebsd. What setting could I adjust?

Many greetings
Torsten



Virenfrei.www.avast.com
--------------atcRFIVP49Y8OJziJ0w0ACSG-- From nobody Sun Feb 19 21:00:51 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 4PKdHl5d5cz3s1ZT for ; Sun, 19 Feb 2023 21:00:51 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PKdHl2wPSz4CSm for ; Sun, 19 Feb 2023 21:00:51 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1676840451; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=x9n3otUchXObQElXw17ZXMVm74jEwV1FET6zOxAgzqI=; b=Oq0cfGU60YYU0mqJXLxnNCcVPajAeMM88jiuKcLtwMniJQPcLSROMEgrNYKZ/pCzHjP1LZ q8n4xeWZq+wEU5dT1IrCJbDfr2WahfBkEePWq0jYC/ABp1Zn3XBqy/QH30mQ+k1PVvMdvG UbXeh5gYmcTxO0tfky6Yd38ddGjQ+rQkh9CXU1RZR+kqZdg4voKh2vBTs8sr3W/gBQGF5Z oHAGOlyKb3L+ecH2TL8r2xkmKsCiBfDX+YMe3dfsSAZ+ONXq2jcXUjh/EoZXEb+UON7JxH xLjbKiA5vJ1bpSJFG6W4+dNDSRMXQa1uG3Ch9cabE/wVtHnzPn18UHuJjQd/+g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1676840451; a=rsa-sha256; cv=none; b=v93uyC/15arcW+uNga57VWSCGbm3ZdNB6OWDYW5jkUIFflb9bIzjiwVv6DBABzXpueZUpA fp4qU1ZqVbGOdGB7Q5fsUd5cj7e9Haar/EUqnT7+x02h4vU30OW213CDzxdSJKNHzYEIoR e5ZM+g4gfFosIEPN5wth+O5XlZ+P3F2Gf0znBnZtESWhahMLitfsxaMJqWkrAh7QEkXoGr 9275Rlri0m2wCgIq3vQGayxb+6U6txJafduASHT8Dd1F0Qc/REYulR3SrtDKLJYkefavvB olbM/GxumZQlsdPyeJK575WICzgpqGAud7KeyVdmjxxyikEUQOLG9gZ6zzUP4w== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4PKdHl20bczGW7 for ; Sun, 19 Feb 2023 21:00:51 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 31JL0puY048386 for ; Sun, 19 Feb 2023 21:00:51 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31JL0pTs048385 for virtualization@FreeBSD.org; Sun, 19 Feb 2023 21:00:51 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <202302192100.31JL0pTs048385@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: virtualization@FreeBSD.org Subject: Problem reports for virtualization@FreeBSD.org that need special attention Date: Sun, 19 Feb 2023 21:00:51 +0000 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 Content-Type: multipart/alternative; boundary="16768404511.Ad30E.44161" Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N --16768404511.Ad30E.44161 Date: Sun, 19 Feb 2023 21:00:51 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 247208 | mpt(4): VMWare virtualized LSI controller panics New | 240945 | [hyper-v] [netvsc] hn network driver incorrectly Open | 244838 | "bectl activate -t" does not honor the -t flag in 3 problems total for which you should take action. --16768404511.Ad30E.44161 Date: Sun, 19 Feb 2023 21:00:51 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" 
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status      |    Bug Id | Description
------------+-----------+---------------------------------------------------
In Progress |    247208 | mpt(4): VMWare virtualized LSI controller panics 
New         |    240945 | [hyper-v] [netvsc] hn network driver incorrectly 
Open        |    244838 | "bectl activate -t" does not honor the -t flag in

3 problems total for which you should take action.
--16768404511.Ad30E.44161-- From nobody Mon Feb 20 08:13:22 2023 X-Original-To: freebsd-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 4PKwCn6YFdz3s9bR for ; Mon, 20 Feb 2023 08:13:25 +0000 (UTC) (envelope-from bounces+22773047-b8c4-freebsd-virtualization=freebsd.org@em7125.potemkin.co) Received: from xtrwhcvx.outbound-mail.sendgrid.net (xtrwhcvx.outbound-mail.sendgrid.net [167.89.12.138]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PKwCm3fgqz45Qs for ; Mon, 20 Feb 2023 08:13:24 +0000 (UTC) (envelope-from bounces+22773047-b8c4-freebsd-virtualization=freebsd.org@em7125.potemkin.co) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=potemkin.co header.s=s1 header.b=lKkTIrPY; spf=pass (mx1.freebsd.org: domain of "bounces+22773047-b8c4-freebsd-virtualization=freebsd.org@em7125.potemkin.co" designates 167.89.12.138 as permitted sender) smtp.mailfrom="bounces+22773047-b8c4-freebsd-virtualization=freebsd.org@em7125.potemkin.co"; dmarc=pass (policy=reject) header.from=potemkin.co DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=potemkin.co; h=from:subject:mime-version:to:content-type:cc:content-type:from: subject:to; s=s1; bh=VrYZmqaAI2MMuLEH3U4ZrLR28I3iJzX51rr6V3toHXQ=; b=lKkTIrPY7ni/ovOJpO3EuJ2/dLgZMoFWEfxre+KQ1jx48PQXr0MGtkflzyrrvjHHbKsc Vmv7KyWd5TLXH62LGWkW2wuINg6S5ycHqkKCi+y/dQIzSqTT4qOdFVrkTGx5pZQHyTP+q/ akkEs6w356EQ4/oSDiFjfLBGh+RhvKXqfaHrUVMMZZ8eE7epjdoyC8KQE1FwbDbRJE5gwf QU6TL27K/LTzhu7CqlzboyHCmrvKF+ikQWrfj6JRPYGrHkl5sviMqzyx7g2cCyF8edQoXg hMKZtWi8zWsXBjGDT21YYeWP3obJtqsBkgR6Kbdjc2b1bAXMaTCGHikm+hpSapXQ== Received: by filterdrecv-7dfc98557c-d4gqh with SMTP id filterdrecv-7dfc98557c-d4gqh-1-63F32BA2-1A 2023-02-20 08:13:22.955327987 +0000 UTC m=+825151.348176351 Received: from my.potemkin.co (unknown) by geopod-ismtpd-3-1 (SG) with ESMTP id S4NjJQarT-6uxaNzc5Au1A for ; Mon, 20 Feb 2023 08:13:22.572 +0000 (UTC) Received: (Haraka outbound); Mon, 20 Feb 2023 08:13:22 +0000 Received: from Homack.local ([104.28.229.190]) by my.potemkin.co (Haraka/2.8.28) with ESMTPSA id CD29B6A4-AD83-4A81-9D4E-B23D364AB77A.1 envelope-from tls TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (authenticated bits=0); Mon, 20 Feb 2023 08:13:22 +0000 Date: Mon, 20 Feb 2023 08:13:22 +0000 (UTC) From: "alex@potemkin.co" Message-ID: Subject: Actual status of Docker (ready for production?) 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 X-SG-EID: =?us-ascii?Q?qI+I72nsxr9uFgKupIWE7ea2Iz6Lg4g5c6vrw4IYmWV0BtfPlRKVoWYnL4Uj1R?= =?us-ascii?Q?QXi5dAKiFxlw=2F0eJyI2F0xfy4O=2Fd0cLj+pGsezn?= =?us-ascii?Q?EFLjEXBHpoK9wW0GpN=2FUQv+hoRAk+GbEgXBEnYc?= =?us-ascii?Q?8uWGsCeC5Fsut9aG12scSlKYtvMyWRcLyk31Ayu?= =?us-ascii?Q?8GKkxfL3xxWWMw=2FkgLO5TJoBIPA=2F7fL=2FSxoxsh0?= =?us-ascii?Q?5szD9KrjjnwQEHNKVuqCqxAu6sMffEx=2FZSeUT32?= =?us-ascii?Q?LIZCS25oE1GV8scnr9fdg=3D=3D?= To: "freebsd-virtualization@FreeBSD.org" X-Entity-ID: tFn0ONcU0Zp0/w+lH/ofsA== Content-Type: multipart/alternative; boundary="63f32ba0_515f007c_3a3" X-Spamd-Result: default: False [-2.68 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_DN_EQ_ADDR(1.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.991]; NEURAL_HAM_LONG(-0.99)[-0.990]; DMARC_POLICY_ALLOW(-0.50)[potemkin.co,reject]; FORGED_SENDER(0.30)[alex@potemkin.co,bounces@em7125.potemkin.co]; R_SPF_ALLOW(-0.20)[+ip4:167.89.0.0/17]; R_DKIM_ALLOW(-0.20)[potemkin.co:s=s1]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org]; TO_DN_EQ_ADDR_ALL(0.00)[]; ASN(0.00)[asn:11377, ipnet:167.89.0.0/18, country:US]; RWL_MAILSPIKE_POSSIBLE(0.00)[167.89.12.138:from]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_NEQ_ENVFROM(0.00)[alex@potemkin.co,bounces@em7125.potemkin.co]; TAGGED_FROM(0.00)[22773047-b8c4-freebsd-virtualization=freebsd.org]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DKIM_TRACE(0.00)[potemkin.co:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; RCVD_COUNT_THREE(0.00)[4]; SUBJECT_HAS_QUESTION(0.00)[] X-Rspamd-Queue-Id: 4PKwCm3fgqz45Qs X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --63f32ba0_515f007c_3a3 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline =20 Hello! =20 =E2=80=8B =20 =E2=80=8BI'm trying to understand an actual status of Docker / podman to ch= eck if I can pick FreeBSD as a platform for the application servers running= pre-packaged apps inside Docker. =20 =E2=80=8B =20 =E2=80=8BI've tried to google things, but I'm getting controversial informa= tion here: =20 =E2=80=8B- wiki (https://wiki.freebsd.org/Docker) says things doesn't actua= lly works since around 2019-2022 =20 =E2=80=8B- ports seems to contain Docker (https://www.freshports.org/sysuti= ls/docker/) and it seems to be regularly updated =20 =E2=80=8B- there doesn't seem to be any discussion in this maillist lately,= which makes me thing it's either dead or very much alive =3D) =20 =E2=80=8B =20 =E2=80=8BAny real-life Docker usage feedback would be much appreciated! =20 =E2=80=8BI'm considering production servers, would love to make it on FreeB= SD as opposed to Linux, but if it will be crashing / throwing errors and/or= won't just work out of the box, like it does on (Debian/Ubuntu) Linux, I w= ill be in trouble. =20 =E2=80=8B =20 =E2=80=8BThanks in advance! =20 =E2=80=8B =20 =20 =20 =20 =20 With best regards, =20 =E2=80=8BAlex Potemkin. =20 =20 =20 =20 =20= --63f32ba0_515f007c_3a3 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hello!
=E2=80=8B
=E2=80=8BI'm trying to understand an actual status of Do= cker / podman to check if I can pick FreeBSD as a platform for the applicat= ion servers running pre-packaged apps inside Docker.
=E2=80=8B
=E2=80=8BI've tried to google things, but I'm gett= ing controversial information here:
=E2=80=8B- wiki (https://wiki.freebsd.org/Docker) says thi= ngs doesn't actually works since around 2019-2022
=E2=80=8B- ports seems to contain Docker (ht= tps://www.freshports.org/sysutils/docker/) and it seems to be regularly upd= ated
=E2=80=8B- the= re doesn't seem to be any discussion in this maillist lately, which makes m= e thing it's either dead or very much alive =3D)
=E2=80=8B
=E2=80=8BAny real-life Docker usage feedback would be = much appreciated!
= =E2=80=8BI'm considering production servers, would love to make it on FreeB= SD as opposed to Linux, but if it will be crashing / throwing errors and/or= won't just work out of the box, like it does on (Debian/Ubuntu) Linux, I w= ill be in trouble.
= =E2=80=8B
=E2=80=8B= Thanks in advance!
= =E2=80=8B
=
With best regards,<= /div>
=E2=80=8BAlex Potemkin.
 --63f32ba0_515f007c_3a3-- From nobody Mon Feb 20 11:00:17 2023 X-Original-To: freebsd-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 4PKzwX0lz4z3scmj for ; Mon, 20 Feb 2023 11:00:28 +0000 (UTC) (envelope-from torsten.kaestel@cgnf.net) Received: from smtp.cgnf.net (smtp.cgnf.net [IPv6:2003:a:173:af30::a:101]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PKzwW13g3z3FFL for ; Mon, 20 Feb 2023 11:00:26 +0000 (UTC) (envelope-from torsten.kaestel@cgnf.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cgnf.net header.s=mail header.b=uSkYC1eS; spf=pass (mx1.freebsd.org: domain of torsten.kaestel@cgnf.net designates 2003:a:173:af30::a:101 as permitted sender) smtp.mailfrom=torsten.kaestel@cgnf.net; dmarc=pass (policy=reject) header.from=cgnf.net Received: from smtp.cgnf.net (localhost [127.0.0.1]) by smtp.cgnf.net (Postfix) with ESMTP id 224E3202F6 for ; Mon, 20 Feb 2023 12:00:18 +0100 (CET) Content-Type: multipart/alternative; boundary="------------hwSeaHoyH1p4L0EVjRSHpkEv" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cgnf.net; s=mail; t=1676890818; bh=slXZ7Yvp9eQknqol0U7bcY7qzb5k7bl8QcqA6ZAOf1c=; h=Date:Subject:From:To:References:In-Reply-To:From; b=uSkYC1eSzu6KvpQD4tKEchHF7Z56uwURB+tTDMTbQ7Op9mXPqpO1rWsldsJmiFvBI Wr4a/KL51TfV+CTlF3R1YcSmTBBZ1X/wkowpHBnsjlcawdli0oOUAgZQqt5rRvWgW+ Py5Ou/nCdwlH1sHOW4wXay0f0BW6Yg+HOdVDcD94= Message-ID: <874516bd-58cb-d9c6-a36c-ac18a6cdbc45@cgnf.net> Date: Mon, 20 Feb 2023 12:00:17 +0100 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 Subject: Re: xn_txeof Warning repsonse is -1! Content-Language: de-DE From: =?UTF-8?Q?Torsten_K=c3=a4stel?= To: freebsd-virtualization@freebsd.org References: In-Reply-To: X-Antivirus: Avast (VPS 230220-0, 20.2.2023), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: ClamAV using ClamSMTP X-Spamd-Result: default: False [-0.46 / 15.00]; URI_COUNT_ODD(1.00)[5]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_MIXED_CHARSET(0.63)[subject]; DMARC_POLICY_ALLOW(-0.50)[cgnf.net,reject]; NEURAL_HAM_SHORT(-0.39)[-0.387]; NEURAL_SPAM_LONG(0.30)[0.305]; R_SPF_ALLOW(-0.20)[+ip6:2003:a:173:af30::a:101]; R_DKIM_ALLOW(-0.20)[cgnf.net:s=mail]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org]; ASN(0.00)[asn:3320, ipnet:2003::/19, country:DE]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_EXCLAIM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[cgnf.net:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4PKzwW13g3z3FFL X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --------------hwSeaHoyH1p4L0EVjRSHpkEv Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sorry, forgot to mention that I'm using XEN 4.11 Am 19.02.2023 um 14:21 schrieb Torsten Kästel: > > Hello all, > > I am running a firewall OPNsense 23.1.1 with FreeBSD 13.1-RELEASE-p6 > virtualized on a server with Ubuntu 20.04. After a kernel update in > the Ubuntu dom0 to 5.4.0-139 , I repeatedly get the following error > message when starting my OPNSense VM in its console > > xn_txeof: WARNING: response is -1! > > This means that the firewall is not working.  Also with the hwe kernel > 5.15.0-60 of Ubuntu this error occurs. > > With the Ubuntu kernel 5.4.0-136 the error does not occur. > > I have tried google but can't find anything to help with this message. > Does anyone have any idea where this is coming from or what setting I > need to change in freebsd. What setting could I adjust? > > Many greetings > Torsten > > > > > Virenfrei.www.avast.com > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -- Diese E-Mail wurde von Avast-Antivirussoftware auf Viren geprüft. www.avast.com --------------hwSeaHoyH1p4L0EVjRSHpkEv Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Sorry, forgot to mention that I'm using XEN 4.11


Am 19.02.2023 um 14:21 schrieb Torsten Kästel:

Hello all,

I am running a firewall OPNsense 23.1.1 with FreeBSD 13.1-RELEASE-p6 virtualized on a server with Ubuntu 20.04. After a kernel update in the Ubuntu dom0 to 5.4.0-139 , I repeatedly get the following error message when starting my OPNSense VM in its console

xn_txeof: WARNING: response is -1!

This means that the firewall is not working.  Also with the hwe kernel 5.15.0-60 of Ubuntu this error occurs.

With the Ubuntu kernel 5.4.0-136 the error does not occur.  

I have tried google but can't find anything to help with this message. Does anyone have any idea where this is coming from or what setting I need to change in freebsd. What setting could I adjust?

Many greetings
Torsten



Virenfrei.www.avast.com
--------------hwSeaHoyH1p4L0EVjRSHpkEv-- From nobody Mon Feb 20 16:08:25 2023 X-Original-To: freebsd-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 4PL6m84M7Bz3t1Qt for ; Mon, 20 Feb 2023 16:08:40 +0000 (UTC) (envelope-from pprocacci@gmail.com) Received: from mail-oa1-x2d.google.com (mail-oa1-x2d.google.com [IPv6:2001:4860:4864:20::2d]) (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 4PL6m81hjCz48KZ for ; Mon, 20 Feb 2023 16:08:40 +0000 (UTC) (envelope-from pprocacci@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oa1-x2d.google.com with SMTP id 586e51a60fabf-17213c961dfso1332710fac.0 for ; Mon, 20 Feb 2023 08:08:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Fp/oHu0I8ha1CeHWiBuWZOe6Vdailo8HxggBHioyw24=; b=oXeBHSLJh6dMrxYDR7hajBBwJMr9PrMIjGM7w1PvmdWu003AspeY7QCpDBlaMXeaRN sK2NM5KL8SPazxsVS/t/3dIzwNlj8dzdV7PfRSmfTbReVn1+AOPWlW+Nd+AMBmq4A92o myqzJ4crjuGg+rZoHnMK+959KoaDvDkjLDQa8mmuiv3yn6MvcMF07lLGgQjfbY9hkBcn +28ZLrLoOvPQgXjSi4fZwpWP+TARLE54HjF0I2Sg3j4Oe3FkVAb0llRtqaR44V/lhSJ6 TYDIB5M5pW0PH4BXn3HgdTB7/T/fx8wLo0GY/28QlmJ5gZUNW9Rtg274F5zYz/MpZYA8 6MKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=Fp/oHu0I8ha1CeHWiBuWZOe6Vdailo8HxggBHioyw24=; b=rzxAkeGl7CM2fkwVkK72EJrzBZ6GvQ4dEkl4y1ckI5PlWwicfBQSGjKwO4xgsANleW bN11jzQn65nCnPi37xPtC3u45ZtUEtuURA2JlPnleHADXK75OWUe7nSS/ps3DWdtay2l UXgl883YayrHH0fNDdOL8kZEAMTIGbKpR18zoZuScNe2Om1Cs9miuxRHvmLru0Z7xuyj iyUOTLpqOVkZzGgPazO/QseQL6X3qsFMUKfezesUK5eLv5fU3p2Cn9F4RIh0zzLTX5un rrQG09BY6CrqlUkf4dLSJQSxfHDcnhEFPGiihxnE1ssUzFvLbgkZlUEh7y9/R/QyJDr8 Vf7g== X-Gm-Message-State: AO0yUKXHIdPVKzaEWNGilb+curBtQQ0cP6O9Rez4EKZ2RQgIhkl8p6we qbkH6566RZ2wtB0Eh9/343hAXzfHwOPizgQcelT/QsjNZpLV X-Google-Smtp-Source: AK7set9bHWDZd2QMpKCeUwHhLBa1iOMQKCEKg2GVzH0LtbfIYhYQO+4Zd6skLwagfCDnwBkzbHZJ/foeLoPuOO7CmFM= X-Received: by 2002:a05:6870:241f:b0:163:2745:c494 with SMTP id n31-20020a056870241f00b001632745c494mr372672oap.174.1676909318930; Mon, 20 Feb 2023 08:08:38 -0800 (PST) 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: In-Reply-To: From: Paul Procacci Date: Mon, 20 Feb 2023 11:08:25 -0500 Message-ID: Subject: Re: Actual status of Docker (ready for production?) To: "alex@potemkin.co" Cc: "freebsd-virtualization@FreeBSD.org" Content-Type: multipart/alternative; boundary="0000000000004687af05f523e0d0" X-Rspamd-Queue-Id: 4PL6m81hjCz48KZ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000004687af05f523e0d0 Content-Type: text/plain; charset="UTF-8" On Mon, Feb 20, 2023 at 3:13 AM alex@potemkin.co wrote: > Hello! > I'm trying to understand an actual status of Docker / podman to check if I > can pick FreeBSD as a platform for the application servers running > pre-packaged apps inside Docker. > I've tried to google things, but I'm getting controversial information > here: > - wiki (https://wiki.freebsd.org/Docker) says things doesn't actually > works since around 2019-2022 > - ports seems to contain Docker ( > https://www.freshports.org/sysutils/docker/) and it seems to be regularly > updated > - there doesn't seem to be any discussion in this maillist lately, which > makes me thing it's either dead or very much alive =) > Any real-life Docker usage feedback would be much appreciated! > I'm considering production servers, would love to make it on FreeBSD as > opposed to Linux, but if it will be crashing / throwing errors and/or won't > just work out of the box, like it does on (Debian/Ubuntu) Linux, I will be > in trouble. > Thanks in advance! > With best regards, > Alex Potemkin. > There's not really a controversy. sysutils/docker is client only and works. The docker Daemon doesn't work. ~Paul -- __________________ :(){ :|:& };: --0000000000004687af05f523e0d0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Feb 20, 2023 at 3:13 AM alex@potemkin.co <alex@= potemkin.co> wrote:
Hello!
I'm trying to understand an actual status of Docker / podman = to check if I can pick FreeBSD as a platform for the application servers ru= nning pre-packaged apps inside Docker.
I've tried to google things, but I'm getting controversial inform= ation here:
- wiki = (https://wiki= .freebsd.org/Docker) says things doesn't actually works since aroun= d 2019-2022
- ports= seems to contain Docker (https://www.freshports.org/sysutils/docker/) a= nd it seems to be regularly updated
- there doesn't seem to be any discussion in this mail= list lately, which makes me thing it's either dead or very much alive = =3D)
<= div>Any real-life Docker usage feedb= ack would be much appreciated!
I'm considering production servers, would love to make it o= n FreeBSD as opposed to Linux, but if it will be crashing / throwing errors= and/or won't just work out of the box, like it does on (Debian/Ubuntu)= Linux, I will be in trouble.
Thanks = in advance!
=
With best regards,<= /font>
Alex Potemkin.

There's no= t really a controversy.=C2=A0 sysutils/docker is client only and works.
= The docker Daemon doesn't work.

~Paul
<= br>
--
__________________

:(){ :|:& };:
--0000000000004687af05f523e0d0-- From nobody Mon Feb 20 18:32:58 2023 X-Original-To: freebsd-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 4PL9yr04fzz3rTPl for ; Mon, 20 Feb 2023 18:33:08 +0000 (UTC) (envelope-from joneum@FreeBSD.org) Received: from toco-domains.de (mail.toco-domains.de [IPv6:2a01:4f8:151:4202::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PL9yq2TSFz4bPX for ; Mon, 20 Feb 2023 18:33:07 +0000 (UTC) (envelope-from joneum@FreeBSD.org) Authentication-Results: mx1.freebsd.org; none Received: from [IPV6:2003:e2:b706:4800:5853:2f62:446b:9be0] (p200300e2b706480058532f62446b9be0.dip0.t-ipconnect.de [IPv6:2003:e2:b706:4800:5853:2f62:446b:9be0]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by toco-domains.de (Postfix) with ESMTPSA id C68911FCC9C; Mon, 20 Feb 2023 19:32:58 +0100 (CET) Content-Type: multipart/alternative; boundary="------------BsbJnvLJxUGC03zGt00NEqLr" Message-ID: Date: Mon, 20 Feb 2023 19:32:58 +0100 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 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: Actual status of Docker (ready for production?) To: "alex@potemkin.co" , "freebsd-virtualization@FreeBSD.org" References: Content-Language: de-DE From: Jochen Neumeister In-Reply-To: X-Rspamd-Queue-Id: 4PL9yq2TSFz4bPX X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --------------BsbJnvLJxUGC03zGt00NEqLr Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hello Alex, most people use either Jails or Bhyve on FreeBSD. I took over maintaining the Docker port a few days ago. I had another Docker port almost ready to use on FreeBSD about 2 years ago. Here, however, little time and too little manpower was the reason that it could not be implemented. I would like to make a new attempt to make the Docker port usable. Currently I would not recommend to use it in a productive environment, because it is also relatively expensive. However, I don't want to make any promises that this time I will succeed in getting Docker running on FreeBSD so that it can be used productively. Cheers Jochen Am 20.02.23 um 09:13 schrieb alex@potemkin.co: > Hello! > ​ > ​I'm trying to understand an actual status of Docker / podman to check > if I can pick FreeBSD as a platform for the application servers > running pre-packaged apps inside Docker. > ​ > ​I've tried to google things, but I'm getting controversial > information here: > ​- wiki (https://wiki.freebsd.org/Docker) says things doesn't actually > works since around 2019-2022 > ​- ports seems to contain Docker > (https://www.freshports.org/sysutils/docker/) and it seems to be > regularly updated > ​- there doesn't seem to be any discussion in this maillist lately, > which makes me thing it's either dead or very much alive =) > ​ > ​Any real-life Docker usage feedback would be much appreciated! > ​I'm considering production servers, would love to make it on FreeBSD > as opposed to Linux, but if it will be crashing / throwing errors > and/or won't just work out of the box, like it does on (Debian/Ubuntu) > Linux, I will be in trouble. > ​ > ​Thanks in advance! > ​ > With best regards, > ​Alex Potemkin. --------------BsbJnvLJxUGC03zGt00NEqLr Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Hello Alex,

most people use either Jails or Bhyve on FreeBSD.
I took over maintaining the Docker port a few days ago. I had another Docker port almost ready to use on FreeBSD about 2 years ago. Here, however, little time and too little manpower was the reason that it could not be implemented.
I would like to make a new attempt to make the Docker port usable.
Currently I would not recommend to use it in a productive environment, because it is also relatively expensive.

However, I don't want to make any promises that this time I will succeed in getting Docker running on FreeBSD so that it can be used productively.

Cheers
Jochen

Am 20.02.23 um 09:13 schrieb alex@potemkin.co:
Hello!
​
​I'm trying to understand an actual status of Docker / podman to check if I can pick FreeBSD as a platform for the application servers running pre-packaged apps inside Docker.
​
​I've tried to google things, but I'm getting controversial information here:
​- wiki (https://wiki.freebsd.org/Docker) says things doesn't actually works since around 2019-2022
​- ports seems to contain Docker (https://www.freshports.org/sysutils/docker/) and it seems to be regularly updated
​- there doesn't seem to be any discussion in this maillist lately, which makes me thing it's either dead or very much alive =)
​
​Any real-life Docker usage feedback would be much appreciated!
​I'm considering production servers, would love to make it on FreeBSD as opposed to Linux, but if it will be crashing / throwing errors and/or won't just work out of the box, like it does on (Debian/Ubuntu) Linux, I will be in trouble.
​
​Thanks in advance!
​
With best regards,
​Alex Potemkin.
--------------BsbJnvLJxUGC03zGt00NEqLr-- From nobody Mon Feb 20 20:24:42 2023 X-Original-To: freebsd-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 4PLDRl0z9wz3s7JY for ; Mon, 20 Feb 2023 20:24:51 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gold.funkthat.com [IPv6:2001:470:800b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PLDRk3DnRz3Nw9 for ; Mon, 20 Feb 2023 20:24:50 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Authentication-Results: mx1.freebsd.org; none Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id 31KKOgjY026196 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 20 Feb 2023 12:24:42 -0800 (PST) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id 31KKOgO1026195; Mon, 20 Feb 2023 12:24:42 -0800 (PST) (envelope-from jmg) Date: Mon, 20 Feb 2023 12:24:42 -0800 From: John-Mark Gurney To: "alex@potemkin.co" Cc: "freebsd-virtualization@FreeBSD.org" Subject: Re: Actual status of Docker (ready for production?) Message-ID: <20230220202442.GN95670@funkthat.com> References: 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.3-STABLE amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Mon, 20 Feb 2023 12:24:43 -0800 (PST) X-Rspamd-Queue-Id: 4PLDRk3DnRz3Nw9 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N alex@potemkin.co wrote this message on Mon, Feb 20, 2023 at 08:13 +0000: > ???I'm trying to understand an actual status of Docker / podman to check if I can pick FreeBSD as a platform for the application servers running pre-packaged apps inside Docker. > > ??? > > ???I've tried to google things, but I'm getting controversial information here: > > ???- wiki (https://wiki.freebsd.org/Docker) says things doesn't actually works since around 2019-2022 > > ???- ports seems to contain Docker (https://www.freshports.org/sysutils/docker/) and it seems to be regularly updated > > ???- there doesn't seem to be any discussion in this maillist lately, which makes me thing it's either dead or very much alive =) > > ??? > > ???Any real-life Docker usage feedback would be much appreciated! > > ???I'm considering production servers, would love to make it on FreeBSD as opposed to Linux, but if it will be crashing / throwing errors and/or won't just work out of the box, like it does on (Debian/Ubuntu) Linux, I will be in trouble. Significant progress has been made in the last year or two. I don't have any specific guides, but, runj network is working: https://samuel.karp.dev/blog/2022/12/docker-style-networking-for-freebsd-jails-with-runj/ Also, podman is apparently working: https://medium.com/@dfr/oci-containers-for-freebsd-512a6df2bc85 which should get you what you need, ask podman is OCI compliant and mostly compatible w/ docker, see: https://soc.crashed.org/objects/2d51da12-7262-4576-bf53-0ea6a61d0da0 The last message is on the dev version of FreeBSD, I'm not sure if it will run on 13 if you need it to run on a RELEASE, but it likely should work. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From nobody Thu Feb 23 14:21:56 2023 X-Original-To: freebsd-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 4PMwFm6X4sz3tmxG for ; Thu, 23 Feb 2023 14:22:04 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PMwFm0C65z4LfR for ; Thu, 23 Feb 2023 14:22:04 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=LYKSKlVS; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="N Z9kDkX"; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.20 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 92D733200902 for ; Thu, 23 Feb 2023 09:21:59 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 23 Feb 2023 09:21:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:date:date:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to; s=fm1; t= 1677162119; x=1677248519; bh=xd0GBS8pJXiHddhOx3Ilc7p+D5dflpsxMvM xoVdhfCM=; b=LYKSKlVSDzY2W9THXQtGuf/XJhvT5XSVcbqFss8/XR5wzPZoZes CkOQu/w130p418wCcvI0K/fLgBI7kwTF39lOd4+5kppYomNB03hYcUIxr+ruStKV Mg1jv4Tz2iZu4WPx7/+JOSY4binU+y7ssATCnX8rGFan0bDRTppJeL2/ay7v7kjw 1oeZONntyaeVtbLfFYHI5CPZCvCvfBunUakzJpOcu3YizLm3BuXKAWC2W4iSIlu0 2d7EE+qMA74eZPQZvG7lgpj6R4yhIkR3k2iOXqOP0m8Tw6D/+j1++fkMuedj1yqP 0WT56bhuJyNAGpirbfkIupFK5uq5v/PppQg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1677162119; x= 1677248519; bh=xd0GBS8pJXiHddhOx3Ilc7p+D5dflpsxMvMxoVdhfCM=; b=N Z9kDkXLEN4reHuhi6+sO7DJwfVaQ78bZ0jbBeQh1Qhqr9+F1thTxRDsddSEGzXzM YgWlwQ27rCz/6K2gG3xOdluYEwrBJq6ce/PjQ/gAOz/UwdIotzN8JsVxa6ihJ/Xz mBsfl7BqarXSUTwZihvla37NlD74BF5w0xiy6UKibXoHzBqZbKKLSmCKj1ukjJGx dOC+TusM5bQ0VaibRm0D0+q5togNGUSOMK8tY3NWN3b7GIkKAVhnaqciDK3BIWrS ViF16fTL6lvfvensTUpONEkvEillTMyaP8zDEaCVT0jMr3jn2WeQpyJI74VZzV2K fAXsw9NXWnkiQSdWjK4yA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudekuddgiedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugesthdtredttd dtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgrthht vghrnhepveduffeivdfffffghfegfeejfefftdeiteehteekfefhvdefgfettdeuheegff eunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvhho ihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Thu, 23 Feb 2023 09:21:58 -0500 (EST) Date: Thu, 23 Feb 2023 14:21:56 +0000 From: void To: freebsd-virtualization@freebsd.org Subject: how to import a freebsd azure instance into an offsite bhyve? Message-ID: Mail-Followup-To: freebsd-virtualization@freebsd.org 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 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Spamd-Result: default: False [-3.51 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-0.98)[-0.980]; NEURAL_HAM_SHORT(-0.93)[-0.925]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.20]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.20:from]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; FREEMAIL_FROM(0.00)[f-m.fm]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4PMwFm0C65z4LfR X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Hello @virtualization As subject: what's the best method of importing an azure instance into bhyve? The only way I can think of, so far, is to log into the instance then do a dd over ssh of the main partition to the bhyve server. fstab on the azure instance looks like so: # # Device Mountpoint FStype Options Dump Pass# /dev/label/rootfs / ufs rw 1 1 /dev/label/swap none swap sw 0 0 Is there a better way? tia, -- From nobody Thu Feb 23 14:28:45 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 4PMwPl4fH0z3tnJJ for ; Thu, 23 Feb 2023 14:28:59 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from mail.flex-it.com.ua (mail.flex-it.com.ua [193.239.74.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PMwPk5Vs0z4Nh0 for ; Thu, 23 Feb 2023 14:28:58 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of shuriku@shurik.kiev.ua designates 193.239.74.7 as permitted sender) smtp.mailfrom=shuriku@shurik.kiev.ua; dmarc=none Received: from [188.231.181.61] (helo=[10.2.1.122]) by mail.flex-it.com.ua with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.95 (FreeBSD)) (envelope-from ) id 1pVCaY-0008pT-9h for virtualization@freebsd.org; Thu, 23 Feb 2023 16:28:50 +0200 Content-Type: multipart/alternative; boundary="------------mE3gZblb9sAXXEUVHhlZq7ps" Message-ID: <74aa1600-0056-85e3-871d-c15c5c5981d8@shurik.kiev.ua> Date: Thu, 23 Feb 2023 16:28:45 +0200 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: how to import a freebsd azure instance into an offsite bhyve? Content-Language: uk-UA To: virtualization@freebsd.org References: From: Oleksandr Kryvulia In-Reply-To: X-Spamd-Result: default: False [-2.24 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.995]; NEURAL_HAM_MEDIUM(-0.95)[-0.947]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[virtualization@freebsd.org]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:35297, ipnet:193.239.72.0/22, country:UA]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[shurik.kiev.ua]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4PMwPk5Vs0z4Nh0 X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --------------mE3gZblb9sAXXEUVHhlZq7ps Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 23.02.23 16:21, void пише: > Hello @virtualization > > As subject: what's the best method of importing an azure instance > into bhyve? > > The only way I can think of, so far, is to log into the instance > then do a dd over ssh of the main partition to the bhyve server. > > fstab on the azure instance looks like so: > > # > # Device        Mountpoint      FStype  Options Dump    Pass# > /dev/label/rootfs       /               ufs     rw      1       1 > /dev/label/swap         none            swap    sw      0       0 > > Is there a better way? > If you have an access to azure portal you can download vhd disk and convert it using emulators/qemu --------------mE3gZblb9sAXXEUVHhlZq7ps Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 23.02.23 16:21, void пише:
Hello @virtualization

As subject: what's the best method of importing an azure instance
into bhyve?

The only way I can think of, so far, is to log into the instance
then do a dd over ssh of the main partition to the bhyve server.

fstab on the azure instance looks like so:

#
# Device        Mountpoint      FStype  Options Dump    Pass#
/dev/label/rootfs       /               ufs     rw      1       1
/dev/label/swap         none            swap    sw      0       0

Is there a better way?


If you have an access to azure portal you can download vhd disk and convert it using emulators/qemu
 --------------mE3gZblb9sAXXEUVHhlZq7ps-- From nobody Thu Feb 23 15:36:30 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 4PMxvl48CHz3s7q7 for ; Thu, 23 Feb 2023 15:36:35 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PMxvk6WKwz3Hjh for ; Thu, 23 Feb 2023 15:36:34 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=uKf2QEx4; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=r7LOUbTz; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.20 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id EB4DC3200959 for ; Thu, 23 Feb 2023 10:36:32 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 23 Feb 2023 10:36:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1677166592; x=1677252992; bh=hms3a7pCDJ qNvmcR6vSp4Gwtlbyhx11Y73T3tfJlq0o=; b=uKf2QEx4sueBmlftjokAerN9g3 EjM79pxi9RUytoXWqEsCvKahnu0ihxy69gU9TUqUJOvXV6eY67ZX8Q/tQ61QZQnZ uom5PxWR1ule108RlR+Fldj/7jtgAvkwiM1vf+I0vhlfERvWf7QTsEwIuoFZhhKZ QzP79dKD46oLegRiHJDT2o4Wv4LC81pAUogJr6oGXmsFGHx6Mr06nwO1vC884ZFX D6TTNMlZ5nfK7P9yHYnvs7UmnYZeDRhtpmhEwOlMDmaSA+JA5pkwme8/mIb5Cf4o NyYX2djaaGskCbRckADT4ltREieRZz+cVqJPXACmoRkv0tQOLxCErn2oT7ZQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1677166592; x=1677252992; bh=hms3a7pCDJqNvmcR6vSp4Gwtlbyh x11Y73T3tfJlq0o=; b=r7LOUbTzhgFy6PPmoSMo0fnaKkYCHClQJY6oCe3aDC/Q 4wVoz71elYg04f8Q0t2wxroCPTqtwMWP0f0HuTdMYa9OSm5W6vuhB4g34O1fm4+u M+Mu5dXhK9uirIwxlv838SYXVOqq8ukJbNfBjnwe2mMg9W+3wpDkSkdUXAu5tl5Q GcYZMBGwkYr0qjWIErndLGeFVM7J5/vmAszZu/D+nV8xz3/1iwOZ27pAftvVvTyZ BDkATleeQCc38lXPQREHvVTwbWi81cIkik0jlNaNUJdHShfGUNodrygYm+n2kTqC xeAl2LGN/iYvmI6S2A9CUItMz7C8OCHRlpo4O2KH9A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudekuddgjeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepkeeluddvlefhieelfefggffhffektdehleelgfdugfdvgeekjeejuddthe ehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Thu, 23 Feb 2023 10:36:31 -0500 (EST) Date: Thu, 23 Feb 2023 15:36:30 +0000 From: void To: virtualization@freebsd.org Subject: Re: how to import a freebsd azure instance into an offsite bhyve? Message-ID: References: <74aa1600-0056-85e3-871d-c15c5c5981d8@shurik.kiev.ua> 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 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <74aa1600-0056-85e3-871d-c15c5c5981d8@shurik.kiev.ua> X-Spamd-Result: default: False [-3.47 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_LONG(-0.95)[-0.946]; NEURAL_HAM_SHORT(-0.93)[-0.925]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.20]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.20:from]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[virtualization@freebsd.org]; FREEMAIL_FROM(0.00)[f-m.fm]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MLMMJ_DEST(0.00)[virtualization@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4PMxvk6WKwz3Hjh X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On Thu, Feb 23, 2023 at 04:28:45PM +0200, Oleksandr Kryvulia wrote: >If you have an access to azure portal you can download vhd disk and >convert it using emulators/qemu Really! I wasn't aware. Is this a recent thing and does the azure vm need to be turned off beforehand? -- From nobody Thu Feb 23 15:46:02 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 4PMy6k2swGz3s8gV for ; Thu, 23 Feb 2023 15:46:06 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PMy6j5pRNz3Jd1 for ; Thu, 23 Feb 2023 15:46:05 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=rVkDxCQ+; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=EZKp3xBb; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.20 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id C39BF3200909 for ; Thu, 23 Feb 2023 10:46:04 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Thu, 23 Feb 2023 10:46:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1677167164; x=1677253564; bh=ET1RAWqSmT Ws3V5VFg2xDcvC45tGioAIHsg3ZTMZPNU=; b=rVkDxCQ+ZBM9aGJLAeHCOzbd/C IeiSkQSHSEqen6RkWajkSqJ9GWL3sGMlQpXXSxf8ipLO/vr3GZt50WP4zb/FZKQy Lx+2IYZ6s9oqrwQ9SKaAoRCjGymKKL6hNs/KQHfv3CVF7Um8x9tdlzTmBh2+89If S9JtUSbshs7GAEjnRad2P4/2Ty+5l3SW6awb4tDIneNiqjwlNygDwzPYmxD30DRr KW2LySSX0NXmxQvajDtf1Jx5yLytekotgSnZ0sQCkLrJHDZZXg/LkMaWjUiNfIiX DL1e0RQ10cuDdWlGtCTHwntoR0pmHswuhz8hW7VcqBlERu5hnhdH+d+Q+rzA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1677167164; x=1677253564; bh=ET1RAWqSmTWs3V5VFg2xDcvC45tG ioAIHsg3ZTMZPNU=; b=EZKp3xBbUEFb16zJREo+l4V54coecR8bRz6booeBY9Zl 8Nd9cdam4KEsP4l73uc0SCJgTkAx3VIiOhsaSL0ehIzqx8Vr9S6EP9nBlvG7Jqe3 l2W5SPoa0V/OTYJcYhYkRuiOqVBEtuwAxl4kk4nUd0j2ewX0lvjghXQeO6TwbULf CBS53pp3klq3WtzClDjzkC3DIi+iD5z0fzYwYZjDzxEhG527uJOYdaXz84zMk04P BHEr+OjhZLUKlVXbVY9VRLjriNXSZVPUgHo+H5LU/SHXuiaozxhQaFYBYGYG1m3/ B6kwvGXeq6DN0Yph6u7RXBLLiiZG49fBDoYte9en4w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudekuddgjeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepffetvefffeffkeeljeduhfeuhffgiedtvdfgleekleekgfeggeekjeffje elteeunecuffhomhgrihhnpehmihgtrhhoshhofhhtrdgtohhmnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Thu, 23 Feb 2023 10:46:03 -0500 (EST) Date: Thu, 23 Feb 2023 15:46:02 +0000 From: void To: virtualization@freebsd.org Subject: Re: how to import a freebsd azure instance into an offsite bhyve? Message-ID: References: <74aa1600-0056-85e3-871d-c15c5c5981d8@shurik.kiev.ua> 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 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <74aa1600-0056-85e3-871d-c15c5c5981d8@shurik.kiev.ua> X-Spamd-Result: default: False [-3.56 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-0.99)[-0.995]; NEURAL_HAM_SHORT(-0.96)[-0.963]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.20:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.20:from]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[virtualization@freebsd.org]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; FREEMAIL_FROM(0.00)[f-m.fm]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[virtualization@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4PMy6j5pRNz3Jd1 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On Thu, Feb 23, 2023 at 04:28:45PM +0200, Oleksandr Kryvulia wrote: >If you have an access to azure portal you can download vhd disk and >convert it using emulators/qemu I found https://learn.microsoft.com/en-us/azure/virtual-machines/linux/download-vhd?tabs=azure-cli#alternative-snapshot-the-vm-disk and am presuming what applies to linux would apply to freebsd too? -- From nobody Fri Feb 24 09:28:27 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 4PNPhd0qxDz3tljL for ; Fri, 24 Feb 2023 09:28:33 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from mail.flex-it.com.ua (mail.flex-it.com.ua [193.239.74.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PNPhb4hrWz3QQw for ; Fri, 24 Feb 2023 09:28:31 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of shuriku@shurik.kiev.ua designates 193.239.74.7 as permitted sender) smtp.mailfrom=shuriku@shurik.kiev.ua; dmarc=none Received: from 93.183.208.50.ipv4.datagroup.ua ([93.183.208.50] helo=[192.168.200.124]) by mail.flex-it.com.ua with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.95 (FreeBSD)) (envelope-from ) id 1pVUNQ-000COx-DO for virtualization@freebsd.org; Fri, 24 Feb 2023 11:28:28 +0200 Message-ID: Date: Fri, 24 Feb 2023 11:28:27 +0200 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: how to import a freebsd azure instance into an offsite bhyve? Content-Language: uk-UA To: virtualization@freebsd.org References: <74aa1600-0056-85e3-871d-c15c5c5981d8@shurik.kiev.ua> From: Oleksandr Kryvulia In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-2.30 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[virtualization@freebsd.org]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:35297, ipnet:193.239.72.0/22, country:UA]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[shurik.kiev.ua]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4PNPhb4hrWz3QQw X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N 23.02.23 17:46, void пише: > On Thu, Feb 23, 2023 at 04:28:45PM +0200, Oleksandr Kryvulia wrote: > >> If you have an access to azure portal you can download vhd disk and >> convert it using emulators/qemu > > I found > https://learn.microsoft.com/en-us/azure/virtual-machines/linux/download-vhd?tabs=azure-cli#alternative-snapshot-the-vm-disk > and am presuming what applies to linux > would apply to freebsd too? > This may be applied to freebsd too. I suggest you to shutdown or prepare your guest workload before snapshotting vm. For example call pg_start_backup() for postgres database before snapshotting and pg_stop_backup() after. From nobody Sat Feb 25 11:06:06 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 4PP3pk29Jjz3t1p9 for ; Sat, 25 Feb 2023 11:06:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PP3pk0DpQz4LD3 for ; Sat, 25 Feb 2023 11:06:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677323166; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Uq5dv89oB74/1SVdH2QpzjPHaYJ5X3GXQKxXd6XPs+w=; b=I8ixOjang5XCU0Ld4YmebJBIesm9vzShQDaeODXNsYL5bpGT3EWzKL40G21EMReybzcQ+V GXF4r7S6M/JsJtQQjOBhdMmq7j/4axSlxe39NxqOndz0wmMV8YAvDnLge03I6gFjrdnb8d aPdffBSh6/KG6N8CZFpeCHjApfvuX+98dqcQxx4SJujx8CCJWpMi0GRyaQiYKUhlo3v1Eh yHIbiZDmqzDW9hgHU/6n08LbFKqr6o1m9vObCWwpMAvXdymXaT3c6eYhWCRnPbqHjfbGSd rrTPTh0UEGZWQkU71j2KiaK0SYlK7bhTPotutqz40nE5O/V4WaJ7vckg1INYKg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677323166; a=rsa-sha256; cv=none; b=vpm2/JaGMyoMdBhSeNEuBBK0eUn5U0dgiJCHbSuq28jFKmEbScTWDyVd1JryqrzVXeIXbU 3byc6cKjjVb6sBvPXB/p9g3F7bacCVid96puocWP1ybuwFavQRC00ZspSfnXfsq5cLhCL0 zV0mAU8mN0l7ELQR5ArgRafLYPm9pgbmRuDQ/V615YXTEGJE/2a686leBJgYBLQITBIcsH XoX2VTWZmSIardASTpfHfHJu89djiksR797GQeaMA3WhvUb4VYdxY3kzAB6rnRtkD8G9SQ TlaOJVq0V8hY1aEZdxMioK5FT8D7UT7OpcLNLk0fLWWQYIAdspeGTNkkip9GhQ== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4PP3pj6PCQz124J for ; Sat, 25 Feb 2023 11:06:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 31PB65Ue050973 for ; Sat, 25 Feb 2023 11:06:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31PB65XJ050972 for virtualization@FreeBSD.org; Sat, 25 Feb 2023 11:06:05 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 269821] if_vtnet: Lock order reversal on LXD's Qemu profile (Q35) Date: Sat, 25 Feb 2023 11:06:06 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd@igalic.co X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D269821 Mina Gali=C4=87 changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |virtualization@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Sat Feb 25 11:37:00 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 4PP4VP0GD2z3t4M9 for ; Sat, 25 Feb 2023 11:37:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PP4VN5MMrz4Nk1 for ; Sat, 25 Feb 2023 11:37:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677325020; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=zL/Glk2Trmau94/3uHJcFC508B4L7XrsRiWjqKFm8Yc=; b=t/yG/LJZyvkkiz+au/wqpjBNBh53sjPKLIZK9ERb4puaK3qMhHI2LDvdm7wSX5rxrJJVgk Hk2ZnCPqPiz3h4e64NBmVJGykthIB4NK84AMG/ogR8PeQjy6pJedHh9F0aqau9ppI/V/Lv 53JtmdNwIOIAAHjMUNVjaPfUhQtmacnfaxZba/rAmYpef98P/BQRjKq87GlMnsMVI6RV8C syq9t+sT9ZPUN7KlJCRFM1Zn7LWkjTtx9pgPHGo9cHppm/r2chalK4sYg9kKuKUb/GvZjd JJ7xE11N+CzDmBbPJ2NGzFxzBkIHF2O1qjpMOzcGWgYvYPj+NSAaM8Dudt1KoQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677325020; a=rsa-sha256; cv=none; b=hD3gVZTeS6clmdOHPrOW+E1MbWUUjwnjMIhcXFE2Z79GkDw/xQurnZ20tTtLqJJdn/pvXL sTQQ5T1ughjTWUW6sAXUfnme9yXaWKxtXK0lzADZmf5gpYwSELH7Xs8WslZVhVXEnJmrna +gsDIcxmS9Ah2yIOCFV6qec0mR/Xr1luxKrQy3XTDa+jTXqRNrlI4yV9nCV2lv8HS/I02Q mxUiu0hALwTQnus+BZzqOcHoPO87yu4xQjjmEQJSFbWk0muiEZ1c4tXtflVCCCL8yk/v9D 4zPoYRcla63MyoaeHIh6npY/0oxEEPXthBgM+sXcLoTCDbx4X2KInfWzGs/vYw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4PP4VN4QMfz12np for ; Sat, 25 Feb 2023 11:37:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 31PBb0nA097924 for ; Sat, 25 Feb 2023 11:37:00 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31PBb0iq097922 for virtualization@FreeBSD.org; Sat, 25 Feb 2023 11:37:00 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 269823] rand_harvest produces 100%CPU on 1 CPU with virtio_random.ko loaded Date: Sat, 25 Feb 2023 11:37:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd@igalic.co X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D269823 Mina Gali=C4=87 changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |virtualization@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Sat Feb 25 19:53:04 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 4PPHVm4ySMz3tpTs for ; Sat, 25 Feb 2023 19:53:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PPHVm0wkFz4BLl for ; Sat, 25 Feb 2023 19:53:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677354784; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=MrzRbAPHInX/mqQAGrpUxDhkKWLxBf8Bg89F6I+BE0U=; b=gwhhjqPbKF9VhJrTqLWDG11Zcea1Az2Aos8k+ZTVt8E9a81LnZnkgDvqhX3I5SpjRmevDd 3QHebzyPQwmaPhUvQ2d8g6GFTBUrtyGT3G7B7Hwf/+2LSSwDDBvDdROutguVdAM6jIeKjI FTrZoDqfFk8E472YQSxRqfn+AGjdra6ho8hBqiYlChqmTCI1mN1MEswoB3/IC2USw/6784 OS1Y6VzAPt2Pzsm8u38oncRMzDNo2DJ0m9Sl7RLkLCkoJ8v6ZkBS/XsDMD4QIHfqPRXbrM Zegb03OviMYloOTGYZcm0pfSa6nOkLqj58l8XF2GMoQXtkzet6dGkreUfTPXUQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677354784; a=rsa-sha256; cv=none; b=Bt3hOdpog9Auso4fOX0InM3BqLq2bxCxcPU9Dmg7+Sdfc3IxVYdN2S1ECLpCPEybWBRrUS vEw5XcFZEKdB0S7k4dyy05kzPT+NZiiJjNQNf1TMao2bmuLySJpIaDeftx1gFC5Ko0GbPT UlmGGFtAHNHiKd+p8lp9/dZpDMf9fJSOGK+A1F/zzq1mjoThDKKTKe9wFhMA9xVupgC8tK ps0jCQH2vdML9AvwrQDWp/YOT4agVqEdC9FTX8a4ytSUtRo8AB35QbYI3LdyFumEBXtskR 1lGjmohGMzzShBDypDpVRZC+QsYnwJdPD7AEBauiw8wTt5ieZc746TvNx7G63Q== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4PPHVl6JCfzGsP for ; Sat, 25 Feb 2023 19:53:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 31PJr3dA010152 for ; Sat, 25 Feb 2023 19:53:03 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31PJr39u010151 for virtualization@FreeBSD.org; Sat, 25 Feb 2023 19:53:03 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 269823] rand_harvest produces 100%CPU on 1 CPU with virtio_random.ko loaded Date: Sat, 25 Feb 2023 19:53:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd@igalic.co X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D269823 --- Comment #2 from Mina Gali=C4=87 --- not much different or unexpected from procstat kstack either: root@freebsd:~ # procstat -w 1 kstack -v 6 PID TID COMM TDNAME KSTACK 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe 6 100074 rand_harvestq - vtrnd_read+0xa4 random_kthread+0x174 fork_exit+0x80 fork_trampoline+0xe --=20 You are receiving this mail because: You are on the CC list for the bug.=