Proxmox ISO Installation Fails on New (amd64) Server Hardware


Nov 4, 2019
Hi Proxmox Community

When trying to install Proxmox 6.0 (from "proxmox-ve_6.0-1.iso", ) on relatively new server hardware, the installation process fails before the full screen Proxmox GUI shows up. I would appreciate your help in understanding what is going wrong with my ISO from USB installation so that I can install Proxmox from the installation media.

Steps to Replicate:
1. Download the "proxmox-ve_6.0-1.iso" file from the Proxmox website and verify the downloaded file's SHA256 signature
2. Follow the instructions on "Install from USB Stick" ( under "Instructions for Windows"
a. I used Etcher Portable 1.5.45 to create the install disk on the first attempt
b. On second attempt I used Rufus 3.3p with the following settings: MBR Partition Scheme, BIOS (or UEFI-CSM) Target, FAT32 (default), 8192 Cluster (default), download compatible syslinux, write in DD mode. I realize that the Wiki says that Rufus won't work, but I'm betting that this advice is from before Rufus supported "DD" writing mode because I have several other PVE installations that have been successful using this method.
3. Power on system, allow it to POST, select USB stick as boot device
4. The Proxmox splash screen, with 4 choices and a white background, appears. Select "Install Proxmox".
5. The system flashes a message about initializing a ramdisk, then the display changes to a linux boot sequence.
6. Booting to the Proxmox ISO\USB fails a few seconds into the process. See screenshot (from video card) for reference and error messages. Installation proceeds quickly to this point, but hangs on this display. No display is observed on the BMC's video output.


Since this problem may be due to the new hardware, I'll provide some basic information about it:
Gigabyte MZ32-AR0 board (Released 10/1/2019)
AMD EPYC 7002 Series processor (Released 8/7/2019)
AMD Vega 64 Graphics card (temporary, for manipulating BIOS)
All other installed hardware (RAM, network, etc) is on board's QVL (RAM released September 2019)
USB Keyboard Microsoft Natural Ergonomic 4000 (May explain messages about 'EVIOCSKEYCODE')

My current work-around for this situation is as follows:

1. Download the Debian 10.1 (from net-install or ISO with non-free firmware), media from
a. The standard net-install works, but upgrading certain packages results in errors talking about missing firmware. This may have to do with the AMD Vega based graphics card I am using to view the BIOS, or it may have to do with the newer AMD EPYC Rome chip in the system. Using the non-free firmware distro results in fewer error messages and (annecdotal) "faster" OS install time.
2. Burn ISO to USB disk. I used Rufus 3.3p with the following settings: MBR Partition Scheme, BIOS (or UEFI-CSM) Target, FAT32 (default), 8192 Cluster (default), download compatible syslinux, write in ISO mode.
3. Proceed through Debian install, selecting desired options
4. Re-boot to Debian Buster
5. From a terminal, execute the steps to install Proxmox 6 on Debian Buster from
6. Re-boot after install, log in to Proxmox 6 install

I've only been testing the work-around setup for a few days, and so haven't verified that every single function of Proxmox 6 is actually working on the resulting system. I have verified that VMs can be created and that KVM will execute them. In any case, my objective is to run the Proxmox 6 distro straight from the installation media, and that is why I am asking for assistance.

Thanks in advance for any help!

We have no experience at the moment with EPYC2 aka ROME.
But why you need a Vega for accessing the Bios?
This MB has an integrated AST2500 as the most Server Boards does.
This works fine for this kind of usage.
Please remove the Vega and try again.
Also, the error code from the installer would interesting.
Hi Wolfgang,

Thanks for your suggestions.

You are right, the management controller on the board allows me to access the BIOS. At first glance, I did not think this was the case, but it turned out that the BIOS setting for quick boot being enabled and the short amount of time the BIOS was set to hold on on the screen caused me to miss it.

After removing the Vega card, and using the Rufus 3.3 in DD write mode, I was able to create a USB boot disk for PVE. I booted from this disk, observed no startup errors, and was able to run through the PVE installation wizard. After the install ProxmoxVE came up and I am able to run VMs without issue.


Is the issue I ran into related to attempting to install on a secondary display or do you think that it was related to use of AMD Vega hardware?
It is hard to say if the AMD Vega HW(Firmware) or the Bios was set incorrectly.
But I know from our VGPU setup there are many thinks where you can mess up the boot.


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, 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 yours easily in our online shop.

Buy now!