From nobody Fri Feb 03 17:09:40 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 4P7hx74T8Hz3kX8B; Fri, 3 Feb 2023 17:10:19 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 4P7hx66RCrz41q8; Fri, 3 Feb 2023 17:10:18 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=SmIP3s8e; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2a00:1450:4864:20::529 as permitted sender) smtp.mailfrom=marietto2008@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x529.google.com with SMTP id u21so5842486edv.3; Fri, 03 Feb 2023 09:10:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=m0VVQL1QfIEeYWx3l6GSicSwdKzAImU44xxtq2ED4ww=; b=SmIP3s8ehsiOj/ZIYJQ6g/eYFv9UmmJlaQvUQvBcrZN4kRxCHTptWj6eS/qq7JGF5/ BneI4IEHS+foEIuCfysphz2FFVOqFHyE5P6nwVOFFqysysNZSWn51bJcKf6uGSLUiNCM 6mMq/AdNYSrRB2enpblen86OjbGe35PLwUgKZdEw+9trCF5rDlzj3Q2T4uP1X0makQ7a 0a11XAcvqxKUMMgR89ytF82+CDhArWA+YSxExSrHykcAxin8wdyUpKVQ2lX50ElkhW/N uOu3fUiccXevXYHzM1f2PMMzGzPDLd6DK2jB5JU2pyQuJvM2l23ne9hZf/lACB4OMcd9 uRFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=m0VVQL1QfIEeYWx3l6GSicSwdKzAImU44xxtq2ED4ww=; b=xuyb9i4Ua/B823AY4hE/8I1cQIYkIU9XHADB7ba0jLeeAg/R0GvfUYvEH6PQSYLsX/ 5yARCfj+FHT+YAQFwZV7K3YjAMTudPAFPGy5YiJ8RYFk6yUISZDDH43zdXq6Eod1eu7u dmAwUzFfOlqK+QyEWOkh9ln4Zy90tmxC/bAdnjjoYPrtkG+H8nmlgfCWStkUPaIzmLvL akOpMWmWICUkbvGFuTQVN3kWoXYL+udDjSbNXbZGF1uUIlsnjvFON4FKAvhDQLzd6ZN+ CCzVVHV/qzxInYgRmduoycWqHoNdjaG1AlbLs457ag4fhb/zH6BVO6bAtZ7SwjbC6lUk /82w== X-Gm-Message-State: AO0yUKXem2V/ldv5+oZFKSMJk+qRKqroNWV2D6R1oH4+bWS3sDILaiKh Hs2ZmIIOX9n7v6C2fxlGvC6YmcFhxA5PO39oX1o= X-Google-Smtp-Source: AK7set/+nP2otbuRwcjHokJ+q4aJnbBrEPu2StIyX7N6Gbkf8fq9ldM/W+Q+HM8VcSVycMcRwPh306/D3HK9ln9xgqo= X-Received: by 2002:a50:cd56:0:b0:49c:a68c:8b6b with SMTP id d22-20020a50cd56000000b0049ca68c8b6bmr3406777edj.84.1675444217111; Fri, 03 Feb 2023 09:10:17 -0800 (PST) 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 References: <15af67efdab54e81bee59aedd2598839@beckhoff.com> <57a5ccfd7c3148f99da730b076a85e01@beckhoff.com> In-Reply-To: From: Mario Marietto Date: Fri, 3 Feb 2023 18:09:40 +0100 Message-ID: Subject: Re: devctl: Failed to detach pci0:2:0:0: Device busy To: =?UTF-8?Q?Corvin_K=C3=B6hne?= , FreeBSD virtualization , freebsd-hackers , Peter Grehan , - - Content-Type: multipart/alternative; boundary="00000000000066e96a05f3cec1de" X-Spamd-Result: default: False [-3.87 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.87)[-0.869]; 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]; ARC_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org,freebsd-hackers@freebsd.org]; FREEMAIL_TO(0.00)[beckhoff.com,freebsd.org,yahoo.com]; 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::529: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)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_FIVE(0.00)[5]; TO_DN_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4P7hx66RCrz41q8 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --00000000000066e96a05f3cec1de Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, bhyve and / or FreeBSD developers and lovers. I=E2=80=99m trying to pass my GTX 1060 from my host os (FreeBSD 13.1-RELEAS= E) to a Linux/Ubuntu VM virtualized with bhyve,but unsuccessfully. Last year I tried to do the same with another GPU that I have on my PC,the RTX 2080 ti and with the help of @generix ,after a tricky trouble shooting we have been able to do that. Point is that the same patches which worked (and that works right now) for the 2080 ti aren=E2=80=99t working fo= r the GTX 1060. The error that I see is the same that I saw when I have cooperated with Generix for passing through the 2080 ti. I really would like to know which differences there are between the two gpus because for the 1060 I'm using the same new driver that I=E2=80=99m using for the 2080 = ti and the latter one can be passed without problems. Anyway,I would know what I should do to fix that error. For this matter I've created a new post on the nvidia forum. If someone would like to give it a look,it is here : https://forums.developer.nvidia.com/t/rminitadapter-failed-error-produced-w= hen-i-try-to-passthru-my-gtx-1060-to-a-linux-ubuntu-bhyve-vm-instead-my-rtx= -2080ti-is-passed-correctly/241594 Il giorno ven 3 feb 2023 alle ore 15:21 Mario Marietto < marietto2008@gmail.com> ha scritto: > Very interesting behavior. I've added this new line in /etc/rc.conf : > (until some minutes ago I didn't use it because I was using the intel > driver,installed by the package : xf86-video-intel-2.99.917.916_2,1) > > kld_list=3D"i915kms acpi_video" > > and this line in /boot/loader.conf : > > pptdevs=3D"1/0/0 1/0/1 2/0/0 2/0/1 2/0/2 2/0/3 5/0/0" > > and boom. pptdevs worked again: > > # pciconf -l > > ppt0@pci0:1:0:0: class=3D0x030000 rev=3D0xa1 hdr=3D0x00 vendor=3D0= x10de > device=3D0x1c02 subvendor=3D0x19da subdevice=3D0x2438 > ppt1@pci0:1:0:1: class=3D0x040300 rev=3D0xa1 hdr=3D0x00 vendor=3D0= x10de > device=3D0x10f1 subvendor=3D0x19da subdevice=3D0x2438 > ppt2@pci0:2:0:0: class=3D0x030000 rev=3D0xa1 hdr=3D0x00 vendor=3D0= x10de > device=3D0x1e04 subvendor=3D0x19da subdevice=3D0x2503 > ppt3@pci0:2:0:1: class=3D0x040300 rev=3D0xa1 hdr=3D0x00 vendor=3D0= x10de > device=3D0x10f7 subvendor=3D0x19da subdevice=3D0x2503 > ppt4@pci0:2:0:2: class=3D0x0c0330 rev=3D0xa1 hdr=3D0x00 vendor=3D0= x10de > device=3D0x1ad6 subvendor=3D0x19da subdevice=3D0x2503 > ppt5@pci0:2:0:3: class=3D0x0c8000 rev=3D0xa1 hdr=3D0x00 vendor=3D0= x10de > device=3D0x1ad7 subvendor=3D0x19da subdevice=3D0x2503 > ppt6@pci0:5:0:0: class=3D0x0c0330 rev=3D0x10 hdr=3D0x00 vendor=3D0= x1b73 > device=3D0x1100 subvendor=3D0x1b73 subdevice=3D0x1100 > > So,maybe there is some incompatibility between the intel and the pptdevs > driver ? take also in consideration that on xorg.cong I'm still using the > intel driver : > > Section "Device" > Identifier "Card0" > Driver "intel" > BusID "PCI:0:2:0" > EndSection. > > It's a confusing situation. > > Il giorno ven 3 feb 2023 alle ore 14:13 Mario Marietto < > marietto2008@gmail.com> ha scritto: > >> I've sent an email to the hackers ML with this content : >> >> > On 30 Jan 2023, at 05:37, Mario Marietto >> wrote: >> > In some FreeBSD 13.1 machines I have the problem below,in some others = I >> don't have it. I would like to know what the causes could be and how to = fix >> it. >> > >> > root@marietto:/usr/home/marietto # devctl detach pci0:1:0:0 >> > >> > devctl: Failed to detach pci0:1:0:0: Device busy >> > >> > root@marietto:/usr/home/marietto # devctl detach pci0:2:0:0 >> > >> > devctl: Failed to detach pci0:2:0:0: Device busy >> > >> > Not even it works if instead of detach them, I try to attach them >> directly to the ppt driver : >> > >> > root@marietto:/usr/home/marietto/bhyve/Files # devctl set driver >> pci0:2:0:0 ppt >> > devctl: Failed to set pci0:2:0:0 driver to ppt: Device busy >> > >> > root@marietto:/usr/home/marietto/bhyve/Files # devctl detach >> pci0:2:0:0 >> > devctl: Failed to detach pci0:2:0:0: Device busy >> > >> > Pci addresses 1:0:0 and 2:0:0 belong to the two GPUs that I have on my >> PC : >> > >> > vgapci0@pci0:1:0:0: class=3D0x030000 rev=3D0xa1 hdr=3D0x00 vendor= =3D0x10de >> device=3D0x1c02 subvendor=3D0x19da subdevice=3D0x2438 >> > vgapci1@pci0:2:0:0: class=3D0x030000 rev=3D0xa1 hdr=3D0x00 vendor= =3D0x10de >> device=3D0x1e04 subvendor=3D0x19da subdevice=3D0x2503 >> > >> > Actually I have commented this line on /boot/loader.conf,because it >> makes no difference if I keep it uncommented or not. It is totally ignor= ed. >> > >> > #pptdevs=3D"1/0/0 1/0/1 2/0/0 2/0/1 2/0/2 2/0/3" >> >> and George replied to me like this : >> >> Do you have 'vmm_load=3D"YES"' in loader.conf? >> >> If not I am not sure it will have an effect - vmm must be loaded early >> otherwise the card will be grabbed by the vgapci driver rather than be p= ut >> under ppt control. >> >> I think this is an interesting answer. Yes,I keep vmm_load=3D"YES" in >> loader.conf,BUT putting the 4 slots under ppt control using the loader.c= onf >> did not work for me for months. We haven't taken this into consideration= . >> And you didn't reply when I've asked you if you have modified the bhyve >> source code,because putting the pci addresses under ppt using the >> loader.conf always worked for me. I would like to understand why it does >> not work anymore. This is important to understand why I'm not able to >> attach / detach the nVidia driver from the host to the guest os. And may= be >> George's consideration is relevant. >> >> Il giorno ven 3 feb 2023 alle ore 12:11 Corvin K=C3=B6hne < >> C.Koehne@beckhoff.com> ha scritto: >> >>> >>> - ---> Figure out if you can blacklist your gpu in the nvidia >>> driver. So, the nVidia driver never gets attached to your device. >>> >>> >>> - nope. I need to attach the nVidia driver to my gpu if I want to >>> run stable diffusion + pytorch + cuda on the Linuxulator on FreeBSD.= I'm >>> thinking of installing Stable Diffusion within the Linux VM,instead = of >>> doing it on FreeBSD. >>> >>> >>> - ---> Wait for drm drivers and use the nouveau driver. Nouveau >>> isn=E2=80=99t maintained by nVidia, so it=E2=80=99s more likely to g= et fixed. >>> >>> >>> - The nouveau driver is always bugged and it never worked well. I >>> wonder if it is still supported. It has even limited features. >>> >>> >>> >>> Afaik, you don=E2=80=99t have other options, sry. I=E2=80=99m no gpu dr= iver developer, >>> so I can=E2=80=99t help you. >>> >>> Btw: Do you refer to linux nouveau or freebsd nouveau? Freebsd made muc= h >>> progress in porting linux drm to freebsd with 14.0. So, if latest linux >>> nouveau fits your requirements, it=E2=80=99s likely that freebsd 14.0 m= ay fit them >>> too. >>> >>> >>> >>> - Are the following commands enough to update the bhyve source code >>> on my machine ? take in consideration that I need to grab only your = new >>> last patch. >>> >>> >>> - cd /usr/src >>> >>> >>> - git checkout -f origin/phab/corvink/13.1/nvidia-wip >>> >>> >>> - # cd /wherever/you/put/my/Makefile >>> >>> # make -j 8 >>> >>> >>> >>> My latest patch is a mouse driver patch for the host. So, no, you have >>> to use: >>> >>> cd /usr/src >>> >>> git fetch >>> >>> git checkout -f origin/phab/corvink/13.1/nvidia-wip >>> >>> make kernel >>> >>> reboot >>> >>> >>> >>> >>> >>> Best regards >>> >>> Corvin >>> >>> >>> >>> >>> >>> This email contains confidential information. If you have received it i= n >>> error, you must not read, use, copy or pass on this e-mail or its >>> attachments. >>> If you have received the e-mail in error, please inform me immediately >>> by reply e-mail and then delete this e-mail from your system. Thank you >>> >>> Diese E-Mail enthaelt vertrauliche Informationen. Sollten Sie sie >>> irrtuemlich erhalten haben, duerfen Sie diese E-Mail oder ihre Anhaenge >>> nicht lesen, verwenden, kopieren oder weitergeben. >>> Sollten Sie die Mail versehentlich erhalten haben, teilen Sie mir dies >>> bitte umgehend per Antwort-E-Mail mit und loeschen Sie diese E-Mail dan= n >>> aus Ihrem System. Vielen Dank >>> >>> Beckhoff Automation GmbH & Co. KG | Managing Director: Dipl. Phys. Hans >>> Beckhoff >>> Registered office: Verl, Germany | Register court: Guetersloh HRA 7075 >>> >>> >> >> -- >> Mario. >> > > > -- > Mario. > --=20 Mario. --00000000000066e96a05f3cec1de Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hello, bhyve and / or FreeBSD developer= s and lovers.

I=E2=80=99m trying to pass my GTX 1060 from my host= os (FreeBSD=20 13.1-RELEASE) to a Linux/Ubuntu VM virtualized with bhyve,but=20 unsuccessfully. Last year I tried to do the same with another GPU that I have on my PC,the RTX 2080 ti and with the help of @generix,aft= er a tricky trouble shooting we have been able to do that. Point is that=20 the same patches which worked (and that works right now) for the 2080 ti=20 aren=E2=80=99t working for the GTX 1060. The error that I see is the same t= hat I saw when I have cooperated with Generix for passing through the 2080 ti. I= really would like to know which differences there are between the two gpus= because for the 1060=20 I'm using the same new driver that I=E2=80=99m using for the 2080 ti an= d the=20 latter one can be passed without problems. Anyway,I would know what=20 I should do to fix that error. For this matter I've created a new post = on the nvidia forum. If someone would like to give it a look,it is here :


Il giorno ven 3 feb 2023= alle ore 15:21 Mario Marietto <marietto2008@gmail.com> ha scritto:
Very interesting behavior. I've added this new line in /etc/rc.conf : (unti= l some minutes ago I didn't use it because I was using the intel=20 driver,installed by the package : xf86-video-intel-2.99.917.916_2,1)=

<= span style=3D"font-family:arial,sans-serif">kld_list=3D"i915kms acpi_video"
=
and this line in = /boot/loader.conf :

ppt= devs=3D"1/0/0 1/0/1 2/0/0 2/0/1 2/0/2 2/0/3 5/0/0"<= br>
and boom. pp= tdevs worked again:

# p= ciconf -l
=
<= span style=3D"color:rgb(0,0,0);background-color:rgb(255,255,255)">ppt0@pci0= :1:0:0: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0class=3D0x030000 rev=3D0x= a1 hdr=3D0x00 vendor=3D0x10de device=3D0x1c02 subvendor=3D0x19da subdevice= =3D0x2438
ppt1@pci0:1:0:1: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0class=3D0x040300 rev=3D0xa1 hdr=3D0x00 vendor=3D0x10de device= =3D0x10f1 subvendor=3D0x19da subdevice=3D0x2438
ppt2@pci0:2:0:0: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0class=3D0x03= 0000 rev=3D0xa1 hdr=3D0x00 vendor=3D0x10de device=3D0x1e04 subvendor=3D0x19= da subdevice=3D0x2503
ppt3@pci0:2:0:1: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0class=3D0x04= 0300 rev=3D0xa1 hdr=3D0x00 vendor=3D0x10de device=3D0x10f7 subvendor=3D0x19= da subdevice=3D0x2503
ppt4@pci0:2:0:2: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0class=3D0x0c= 0330 rev=3D0xa1 hdr=3D0x00 vendor=3D0x10de device=3D0x1ad6 subvendor=3D0x19= da subdevice=3D0x2503
ppt5@pci0:2:0:3: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0class=3D0x0c= 8000 rev=3D0xa1 hdr=3D0x00 vendor=3D0x10de device=3D0x1ad7 subvendor=3D0x19= da subdevice=3D0x2503
ppt6@pci0:5:0:0: =C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0class=3D0x0c0330 rev=3D0x10 hdr=3D0x00 vendor= =3D0x1b73 device=3D0x1100 subvendor=3D0x1b73 subdevice=3D0x1100

So,maybe there is some incompatibility between the intel and the pptdevs driver ? take also in consideration that on xorg.cong I'm still using the intel= =20 driver :

Section "Device"
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Identifier =C2=A0&quo= t;Card0"
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Driver =C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0"intel"
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0BusID =C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0"PCI:0:2:0"
EndSection.

It's a confusing situation.
Il giorn= o ven 3 feb 2023 alle ore 14:13 Mario Marietto <marietto2008@gmail.com> ha scrit= to:
I've sent an email to the hackers ML with this content = :

> On 30 Jan 2023, a= t 05:37, Mario Marietto <marietto2008@gmail.com> wrote:
<= /span>
> In some FreeBSD 13.1 machines I have the problem below,in some=20 others I don't have it. I would like to know what the causes could be= =20 and how to fix it.
>
> root@marietto:/usr/home/marietto # devctl detach pci0:1:0:0
>
> devctl: Failed to detach pci0:1:0:0: Device busy
>
> root@marietto:/usr/home/marietto # devctl detach pci0:2:0:0
>
> devctl: Failed to detach pci0:2:0:0: Device busy
>
> Not even it works if instead of detach them, I try to attach them dire= ctly to the ppt driver :
>
> root@marietto:/usr/home/marietto/bhyve/Files # devctl set driver pci0:= 2:0:0 ppt
> devctl: Failed to set pci0:2:0:0 driver to ppt: Device busy
>=C2=A0
> root@marietto:/usr/home/marietto/bhyve/Files # devctl detach pci0:2:0:= 0
> devctl: Failed to detach pci0:2:0:0: Device busy
>
> Pci addresses 1:0:0 and 2:0:0 belong to the two GPUs that I have on my= PC :
>
> vgapci0@pci0:1:0:0:=C2=A0 =C2=A0 =C2=A0class=3D0x030000 rev=3D0xa1 hdr= =3D0x00 vendor=3D0x10de device=3D0x1c02 subvendor=3D0x19da subdevice=3D0x24= 38
> vgapci1@pci0:2:0:0:=C2=A0 =C2=A0 =C2=A0class=3D0x030000 rev=3D0xa1 hdr= =3D0x00 vendor=3D0x10de device=3D0x1e04 subvendor=3D0x19da subdevice=3D0x25= 03
>
> Actually I have commented this line on /boot/loader.conf,because it makes no difference if I keep it uncommented or not. It is totally=20 ignored.
>
> #pptdevs=3D"1/0/0 1/0/1 2/0/0 2/0/1 2/0/2 2/0/3"
=

and George replied to me like this :

Do you have 'vmm_load=3D"YES"' in loader.conf?

If not I am not sure it will have an effect - vmm must be loaded early=20 otherwise the card will be grabbed by the vgapci driver rather than be=20 put under ppt control.

I think this is an interesting answer. Yes,I keep vmm_load=3D"= ;YES" in loader.conf,BUT putting the 4 slots under ppt control using t= he loader.conf did not work for me for months. We haven't taken this in= to consideration. And you didn't reply when I've asked you if you h= ave modified the bhyve source code,because putting the pci addresses under = ppt using the loader.conf always worked for me. I would like to understand = why it does not work anymore. This is important to understand why I'm n= ot able to attach / detach the nVidia driver from the host to the guest os.= And maybe George's consideration is relevant.

Il giorno ven 3 feb 2023 alle ore 12:11 Corvin K=C3=B6hne = <C.Koehne@bec= khoff.com> ha scritto:
  • ---> Figure out if you can blacklist your = gpu in the nvidia driver. So, the nVidia driver never gets attached to your= device.
  • nope. I need to attach the nVidia driver to m= y gpu if I want to run stable diffusion + pytorch + cuda on the Linuxulator= on FreeBSD. I'm thinking of installing Stable Diffusion within the Linux VM,instead of doing it on FreeBSD.
  • ---> Wait for drm drivers and use the nouv= eau driver. Nouveau isn=E2=80=99t maintained by nVidia, so it=E2=80=99s mor= e likely to get fixed.
  • The nouveau driver is always bugged and it ne= ver worked well. I wonder if it is still supported. It has even limited fea= tures.

=C2=A0

Afaik, you don=E2=80=99t have other options, sry. I= =E2=80=99m no gpu driver developer, so I can=E2=80=99t help you.<= /u>

Btw: Do you refer to linux nouveau or freebsd nouvea= u? Freebsd made much progress in porting linux drm to freebsd with 14.0. So= , if latest linux nouveau fits your requirements, it=E2=80=99s likely that = freebsd 14.0 may fit them too.

=C2=A0

  • Are the following commands enough to update t= he bhyve source code on my machine ? take in consideration that I need to g= rab only your new last patch.
  • cd /usr/src
  • git checkout -f origin/phab/corvink/13.1/nvid= ia-wip
  • # cd /wherever/you/put/my/Makefile<= /u>

# make -j 8

=C2=A0

My latest patch is a mouse driver patch for the host= . So, no, you have to use:

cd /usr/src

git fetch

git checkout -f origin/phab/corvink/13.1/nvidia-wip<= u>

make kernel

reboot

=C2=A0

=C2=A0

Best regards

Corvin

=C2=A0

=C2=A0


This e= mail contains confidential information. If you have received it in error, y= ou must not read, use, copy or pass on this e-mail or its attachments.
If you have received the e-mail in error, please inform me immediately by r= eply e-mail and then delete this e-mail from your system. Thank you

Diese E-Mail enthaelt vertrauliche Informationen. Sollten Sie sie irrtuemli= ch erhalten haben, duerfen Sie diese E-Mail oder ihre Anhaenge nicht lesen,= verwenden, kopieren oder weitergeben.
Sollten Sie die Mail versehentlich erhalten haben, teilen Sie mir dies bitt= e umgehend per Antwort-E-Mail mit und loeschen Sie diese E-Mail dann aus Ih= rem System. Vielen Dank

Beckhoff Automation GmbH & Co. KG | Managing Director: Dipl. Phys. Hans= Beckhoff
Registered office: Verl, Germany | Register court: Guetersloh HRA 7075



--
Mari= o.


--
Mario.
=


--
Mario.
=
--00000000000066e96a05f3cec1de--