Hi,
I've been having issues with an ubuntu 20.04 VM on both proxmox 6.1 and proxmox 6.2.
At first, after completing the ubuntu installation (with gpu passthru) and enabling auto login and rebooting all was fine.
Next I ran ubuntu update and rebooted.
After the reboot I was auto logged-in...
Hi,
I'm glad you got it working.
As for me, with my setup Ryzen 1700, Nvidia 1050Ti, I could not get GPU passthru working with my installation of proxmox 6.2 (in release upgrade from proxmox 6.1). I tried a lot of command combinations with no success. I might start with a fresh install of...
dmesg reports:
[93022.808178] vfio-pci 0000:08:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
[93022.810196] vfio-pci 0000:08:00.0: No more image in the PCI ROM
From reading around I have my grub setup as this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 video=efifb:off"
but still I have no GPU passthrough functioning.
my VM conf file is this:
#ubuntu
#
#ip%3A 196.168.2.176
balloon: 0
bios: ovmf...
I haven't tried a fresh install but upgraded from 6.1 to 6.2 by installing updates. Something in proxmox 6.2 has changed that stops a previously working VM config setup for GPU passthru now only comes up with a blank screen.
Hi,
I've just updated from proxmox 6.1 to 6.2 and now the GPU passthru fails to function on my existing ubuntu guest VM. At first I though maybe the pci host device numbering may have changed after the update but after checking lspci it is the same as in my VM conf file.
Any ideas?
Thanks for your replies. I managed to recreate the conf file for my container disks and managed to spin up the container images. It took a little trial and error to create a dummy config and then substituting the disk entry in the conf file. In the end I got it working.
Hi,
My proxmox 6.0 installation crashed (usb stick) and is non-booting. I have now started up a fresh proxmox 6.1 install. Although, my lxc machine .conf files are gone I still have access to the subvol-disk-0 files/directories which were stored on a seperate zfs drive.
How can I spin up...
Hi,
I've had a power outage recently which caused some corruption on by USB bootable stick and is playing up (shows grub rescue, complains boot.mod not found and other things). After several reboots the PVE server did bootup and my VM's and containers which I have set to start on boot are...
Finally managed to put back the bios version 4023 and ran up proxmox and my ubuntu VM with GPU passthorugh..... and it is working again!
This is the method I had to use to put back the bios...
Googling this message suggests it's a issue with the Motherboard bios . The new version I installed now was Version 5220 which has AGESA 1.0.0.3ABBA (I updated from Version 4022 which was on the board previously). I tried to roll back the bios to other previous releases which I was able to...
Hi,
In my attempt to make my home server more stable I decided to update both PVE (running community release 6.0) and my Motherboard bios Asus B350 Prime Plus to the latest release. Now, I've noticed my GPU passthru. doesn't function anymore and shows the message in dmeg in relation to my...
Thanks!
I managed to make a new install Proxmox 6.0 and imported my zpools which holds my data and my VM/LXC disks. However, the VM and LXC configs are all gone. I tried to re-create a config of a LXC and link it the sub-vol disk but that didn't work (I don't remember the failure message...
I've been running proxmox 5.4 from a usb stick for some time. Lately, my machine has been crashing and now on reboot I get the grub rescue prompt and on the top line the message error unknown lvm metadata header
Error: disk lvmid/B6iwj-..... not found.
How do I get my proxmox installation to...
I think that container disk is corrupt as the content in very minimal compared to the new disk associated with the new mediaserver container.
root@pve:/osdisks/image/subvol-104-disk-1# ls
bignas dev nasdrive
(bignas, nasdrive) are mountpoints. And dev is empty.
Comparing with the new disk...
I checked my notes from the past and it seems that previously my mediaserver container was created with the unpriviledged container unticked. But the wizard now has that as ticked by default. So, now I can create a new mediaserver container but will I be able to start-up the old server?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.