Search results

Thanks, I'll give this a try. I saw when Proxmox was booting it identified the other disks so once I recreate the vm, I should be able to also add the other volumes still there too?

Hi, I'm trying to rebuilt my Ryzen 2700 box with two GPU's that I had working perfectly before my SSD died. The problem I am having is that I cannot get VFIO to bind with the two GPU's I have installed. My settings are as follows: /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet...

Hi everyone, My SSD died on me a few days ago. Unfortunately, this had my Proxmox root partition and also several VM's. I also have two other disks which did not die and still seem to be fine. I'm replacing my SSD now so if I re-install on the new SSD, will I be able to recover the volumes and...

Yeah, I gradually removed everything and figured out that it was the NVME which is dead. Looks like as it was sharing PCI lanes with the X4 slot, it's failure meant that I got the above errors.

Hi, I'm using the latest Proxmox 6.2 and noticed this morning that some VM's had stalled and I couldn't SSH into Proxmox or access the web admin. I forced a reboot and now I am stuck at "Loading initial ramdisk ...". I have several older 5.4.x and even 4.15 kernel versions which all gave the...

Thanks for the reply. I managed to get the VM booting again by adding svm to the cpu flags but WSL 2 is not working. I'll look up the other threads also.

Hi, i'm not sure what happened with my prior post as it possibly got deleted. I am using a Windows 10 VM in latest Proxmox and after applying the May 2020 update recently am suddenly unable to boot. I get a "STOP CODE: Hypervisor Error". I can't roll back to any previous feature or quality...

Hi everyone, i've had a Windows 10 VM run with GPU passthrough via Proxmox for over a year now without issue. In the last days, I upgraded it to the May 2020 update and then tried to enable WSL 2. At the time, Windows said it could not enable virtualization so I left it at that. I just got...

Sure! Ryzen 2700 on MSI B450M Mortar. You need to use 7B89v14 because later releases includes support for Ryzen 3000 series which introduces the issue. More details on it are at https://www.reddit.com/r/VFIO/comments/bqeixd/apparently_the_latest_bios_on_asrockmsi_boards/eo4neta/

I ended up fixing this. It turns out newer BIOS's to support the latest Ryzen processors introduce issues with pass through. Downgrading the BIOS fixed this instantly.

Hi, I'm trying to set up a Linux VM to use the virgl 3d accelerated graphics driver. My VM config is: agent: 1 bootdisk: scsi0 cores: 8 cpu: host,flags=+pcid efidisk0: shared:vm-103-disk-1,size=128K ide2: local:iso/linuxmint-19.1-cinnamon-64bit.iso,media=cdrom,size=1927648K machine: q35...

Ah yeah, then I tried that (see earlier). It gives the same error.

My device address is 1c:00, not 01:00. Can you explain how or why changing it would work?

Yep, I extracted it from my GPU. I tried one or two others also that I found online but none of them worked at all.

Thanks for replying. I tried exactly that and get the same ""!!! Unknown header type 7f" error.

Hi, I'm trying to get my NVidia 1050ti to pass through to a Windows VM on a Ryzen 2700 running Proxmox 5.4-6. The main problem I am having is getting the NVidia audio controller to pass through and work. The graphics card and kernel drivers are: root@pve:~# lspci -v -s 1c:00 1c:00.0 VGA...

Thank you, that worked!

Thanks for replying. This has worked for node B. Now I am trying to rejoin the cluster in node A. In the web UI on node A, cluster information says it's a standalone node with no cluster defined. Yet, the two cluster nodes (including the one I have removed) is still there. "Join Information" is...

Hi, I'm running Proxmox 5.3.12 on two nodes (A & B). I had them in a cluster. I was toying around with some cluster commands and I accidentally removed node B from the cluster. I now can't start any VM's on node B because it is complaining about the quoram. On node A, I've been able to restart...

I think I've got this solved now. Passing the bios file (unpatched) seems to work. Note that getting the ones from techpowerup.com did not work. only grabbing my own worked.