* [PVE-User] Proces BOOTFB
@ 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>
0 siblings, 2 replies; 3+ messages in thread
From: Jack Raats @ 2022-05-05 13:56 UTC (permalink / raw)
To: pve-user
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [PVE-User] Network Mismatch after upgrade to 7.2
2022-05-05 13:56 [PVE-User] Proces BOOTFB Jack Raats
@ 2022-05-06 11:10 ` storm
[not found] ` <UyYrAzFtnjlhdvS8wW11OcjHWAXtk1jVkwCutnvdp-yHIcVnLdDcZRihkaHiLqL-IH2UlRSapLmquQAjeahyzIDls0B1AxXEtmsokHavSK8=@pm.me>
1 sibling, 0 replies; 3+ messages in thread
From: storm @ 2022-05-06 11:10 UTC (permalink / raw)
To: pve-user
Hello,
on one of my nodes I have total chaos in the network configuration after
upgrading from 7.1 to 7.2 (liscensed pve-enterprise repo)
I have some interfaces in the GUI, which are not in the system, the cli
shows something totally different
one actively used for a client network disappeared totally
the mac address reported by the connected switch for this network cannot
be found on the node :(
Any clue whats the issue and how to resolve this?
best regards
Ralf
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PVE-User] Proces BOOTFB
[not found] ` <UyYrAzFtnjlhdvS8wW11OcjHWAXtk1jVkwCutnvdp-yHIcVnLdDcZRihkaHiLqL-IH2UlRSapLmquQAjeahyzIDls0B1AxXEtmsokHavSK8=@pm.me>
@ 2022-05-06 11:23 ` Jack Raats
0 siblings, 0 replies; 3+ messages in thread
From: Jack Raats @ 2022-05-06 11:23 UTC (permalink / raw)
To: Arjen, Proxmox VE user list
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-05-06 11:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-05 13:56 [PVE-User] Proces BOOTFB 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 ` [PVE-User] Proces BOOTFB Jack Raats
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