Search results

Looks like the answer is not (output of cat /proc/cmdline): initrd=\EFI\proxmox\5.13.19-2-pve\initrd.img-5.13.19-2-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs I am running ZFS on the boot media. I have a ZFS Mirror configured on a pair of SSD's which PROXMOX boots from. Also if I try to run...

Hello, I'm running PROXMOX 7.1-7 on a Intel Xeon platform and I'm attempting to get hardware pass-through working. I've enabled VT-d in the BIOS. I've added intel_iommu=on to GRUB_CMDLINE_LINUX_DEFAULT I've ran proxmox-boot-tool refresh The system persists in telling me that IOMMU isn't...

I've spent the latter part of the last 24 hours trying to setup some VM's from backup onto PROXMOX 7.1-4. I was upgrading from an older version. Relevant hardware: Motherboard: Supermicro X10DRi-T (BIOS: 3.4a) CPU(s): Intel Xeon E5-2698v3 Hardware pass-through worked great until I performed a...

It did. I later learned that the vfio-pci driver is designed to be used with basically any hardware device that the host can do without. It's not strictly for GPUs.

I'm looking to pass-though an LSI HBA (the 9207-8i) to a VM. I already have everything configured as far as IOMMU groups, VT-d, enabling IOMMU within Proxmox, etc. It's all ready to go except the fact that Proxmox grabs the HBA when the OS starts and I need it to remain free. The Proxmox...

That's difficult to answer. Weather the VM is running or not, weather I start it or stop it no new errors are printed to the terminal. No new ones are appearing so I'm not sure what has caused them. For both to appear at the same time make me think they're related though.

So what I have here is an error I've not dealt with before and find myself rather confused by. The following screen shots are from the PROXMOX Terminal: The strangest thing about these errors is that according to lsblk I don't have a sda device: I have found that one of my VMs has had a...

Just a really old Radeon HD 7970 because it's what I have on hand/available. I plan to buy a half-height RX 560. This VM doesn't need high GPU compute performance just enough to run some basic 3D/OpenCL applications. While exploring GPU pass-though you never learned about the infamous NVIDIA...

...the documentation lied to me. It said running "pve-eftboot-tool refresh" was the same as running update-grub. Well the two different update commands I used apparently didn't do this because I decided to run update-grub and all of a sudden everything is working. Passing-though the GPU took a...

It does not. It does appear I'm using a UEFI BIOS (looks like the classic BIOS though) but it's not showing me a UEFI boot option for the SATA controller I'm using. Going into the Boot tab I see "CSM parameters" which I've set to UEFI only but I don't know if that will install the OS under...

@n1nj4888 It's the C602 chipset which i believe boarders when UEFI first started coming out so I don't know if it's booting using UEFI or not but it's worth trying. What you've linked is what I've already read in the documentation. Checking the /etc/kernel/ directory cmdline does not exist as...

Software: PROXMOX 6.0-4 Hardware: 2xIntel Xeon E5-2670v1, ASRock Rack EP2C602-4L/D16 In the BIOS I have enabled VT-d. This brings up ATS Support & Coherency Support. I've looked into these and I don't think they're necessary. but please correct me there. I opened up the Proxmox documentation...

What I did to "fix" the problem was import the backups from my backup server. I'm seriously glad I did that just prior to updating the OS/boot drive. The reason I've updated is because the final goal is GPU pass-though for a Windows VM which would be the next thing not working... Motherboard...

Well, the unexpected occurred. So I went to that directory and those "files" were links to nodes/pve/lxc & nodes/pve/qemu-server. These folders did contain the *.config files. I shutdown the server because I ran out of time to work on it. Coming back to it today for no explainable reason I can...

I've upgraded the boot drive on my PROXMOX server and imported my old ZFS pools with: zpool import [pool] Then added them to the GUI via: Datacenter -> Storage -> Add -> ZFS Both pools show the Disks that existed on them previously but I cannot figure out how to import the Containers & VMs from...

I had a feeling it had something to do with that. Didn't know setting UEFI directly impacted the screen resolution. Set it to 1600x900. Windows didn't like it at all but after a couple restarts and retries it's working correctly now. Thank you.

I recently created a new Windows VM (version 1804) and no matter what I do it won't let me resize the display window to anything higher than 800x600. I tried changing the Display to Standard VGA (no change), VMWare compatible (does not work at all), SPICE (only works partially - not enough). I...