Search results

  1. GPU passthrough tutorial/reference

    the real name of the file doesn't matter if you keep the .conf at the end this is only for you to remember what it does as pve-blacklist.conf might be provided by "proxmox package", I would use a gpu-passthrough-blacklist.conf to keep proxmox able to update his own file and keep mine separate...
  2. GPU passthrough tutorial/reference

    I don't know if it is expected or related to my hardware no having a 'rom bar' to get mapped but this is NOT what I have on my system. on MY system : rombar=0 hide my proxmox boot logo and system only show at "login screen" rombar=1 show me proxmox boot/bios logo and progress bar, then GRUB...
  3. GPU passthrough tutorial/reference

    Thanks for this info, as per rombar=0/1 : 0 mean you wont see bootscreen until OS is ready, thus hidding proxmox boot logo 1 mean you want to see proxmox bootlog to know your VM is firing up yep, i may give a trial this way first
  4. GPU passthrough tutorial/reference

    Worked fine here with linux Guest (my windows ISO won't boot in EFI mode) exactly as you have done, but this line GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on" without the efifboot=off vm config file added STEP1 bios: ovmf #(from GUI, select BIOS = OVMF) machine: q35 #(from CLI) then...
  5. [SOLVED] Problem with installing Proxmox-VE on Debian

    add same issue here, juste have to fix this way -------------------------- localhost proxmox pvelocalhost -------------------------- with proxmox being the real machine name


The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!