all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Jack Raats <mlist@jarasoft.net>
To: Arjen <leesteken+proxmox@pm.me>,
	Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Proces BOOTFB
Date: Fri, 6 May 2022 13:23:48 +0200	[thread overview]
Message-ID: <a2d24f02-d819-260f-a436-87124d7f66cd@jarasoft.net> (raw)
In-Reply-To: <UyYrAzFtnjlhdvS8wW11OcjHWAXtk1jVkwCutnvdp-yHIcVnLdDcZRihkaHiLqL-IH2UlRSapLmquQAjeahyzIDls0B1AxXEtmsokHavSK8=@pm.me>


Op 05-05-2022 om 16:08 schreef Arjen:
> On Thursday, May 5th, 2022 at 15:56, Jack Raats <mlist@jarasoft.net> wrote:
>
>> Hi,
>>
>> At this moment I use proxmox 7.2-3. Before this version I could run a VM
>> passthrough.
>> On proxmox 7.2-3 I get an error that BAR1 doesn't have memory anymore.
>> The memory ism occupied by a proces called BOOTFB.
>>
>> What is this proces doing?
>> How to get the passthroug thing working again?
>>
>> Thanks
>> Jack Raats
> Before (with kernel 5.13) using video=efifb:off video=vesafb:off would fix this (at the expense of boot messages).
> With 7.2 (or kernel 5.15), I would expect video=simplefb:off to fix this, but I my experience this does not work for every GPU.
>
> I found that, for AMD GPUs, unblacklisting amdgpu AND not early binding to vfio_pci AND removing those video= parameters works best.
> amdgpu just takes over from the bootfb, and does release the GPU nicely to vfio_pci when starting the VM.
> (Of course, for AMD vendor-reset and reset_method=device_specific might be required.)
> I don't know if this also works for nouveau or i915.
>
> I hope this helps,
> Arjen

I've tried all the possible, but nothing works...
Until I started the old kernel and everything worked perfectly!

I think that amdgpu, which is included in the kernel, doesn't takes over 
from bootfb

Greetings,
Jack Raats








      parent reply	other threads:[~2022-05-06 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 13:56 Jack Raats
2022-05-06 11:10 ` [PVE-User] Network Mismatch after upgrade to 7.2 storm
     [not found] ` <UyYrAzFtnjlhdvS8wW11OcjHWAXtk1jVkwCutnvdp-yHIcVnLdDcZRihkaHiLqL-IH2UlRSapLmquQAjeahyzIDls0B1AxXEtmsokHavSK8=@pm.me>
2022-05-06 11:23   ` Jack Raats [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a2d24f02-d819-260f-a436-87124d7f66cd@jarasoft.net \
    --to=mlist@jarasoft.net \
    --cc=leesteken+proxmox@pm.me \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal