Search results

dir: local path /var/lib/vz content vztmpl,iso,backup,images prune-backups keep-last=3 shared 0 lvmthin: local-lvm thinpool data vgname pve content rootdir,images dir: btrfs path /mnt/nfs/btrfs/pve content rootdir,images...

❯ tree -aL 1 /mnt/nfs/nvme_btrfs /mnt/nfs/nvme_btrfs ├── .beeshome ├── Games ├── pve └── .Trash-1000 /mnt/nfs/nvme_btrfs/pve ├── dump ├── images │ └── 104 │ └── vm-104-disk-0.raw └── private Note: I've reverted to Directory type storage for now, since btrfs isn't working

❯ lsblk -o +FSTYPE NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT FSTYPE sda 8:0 0 1.8T 0 disk └─sda1 8:1 0 1.8T 0 part /mnt/nfs/btrfs btrfs sdb 8:16 0 111.8G 0 disk...

Hello, i can't seem to be able to create/move a container volume on the Btrfs storage type. I get the following error: btrfs error: open3: exec of btrfs -q subvolume create -- /mnt/nfs/nvme_btrfs/pve/images/104/vm-104-disk-0 failed: No such file or directory at /usr/share/perl5/PVE/Tools.pm line...

Thanks for the insight but the issue still persists, I already had c states completely disabled and have also just tried manually setting the power supply control setting to "Typical current idle" - issue still persists. I don't think this is the same problem as those posts, the issue only...

I seem to be having issues with the latest 5.19.17-1 kernel, throws out watchdog cpu soft lockup bug after a couple minutes after boot. I'm on a ryzen-based system with 3700x. Downgrading to 5.15 and 5.19.7-2 seems to work fine. The issue seemed to pop up randomly though as the latest kernel was...

For Nvidia GPUs i think all that is needed is a basic cron script to detach it on startup to get boot gpu passthrough to work, no kernel parameter required - atleast for me with a 1070ti: #!/bin/sh echo 1 > /sys/bus/pci/devices/0000\:0x\:00.0/remove echo 1 > /sys/bus/pci/rescan for their case...

I'm having a similar experience with an nvidia gpu also (1070ti) on latest kernel. (5.15) I've tried the workarounds described above to no avail. The only thing I've found that works so far is not having it be used for boot i.e. Using another gpu (in my case amdgpu) for boot/host. Passthrough of...

I've also had the same experience with bar reservation errors on the 5.15.19-2 kernel when using the boot-gpu (nvidia), passthrough of the non-boot gpu seems to work fine (using the same card). For now I've just rolled back to the 5.13.19-3 kernel and boot-gpu passthrough seems to work fine there.

Ah yes! xD that seems to have fixed things. root@pve:/var/lib/pve-manager# pveupdate root@pve:/var/lib/pve-manager# pveupgrade Starting system upgrade: apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0...

root@pve:~# pveversion -v proxmox-ve: 6.4-1 (running kernel: 5.11.21-1-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-5.11: 7.0-2~bpo10 pve-kernel-5.4: 6.4-4 pve-kernel-helper: 6.4-4 pve-kernel-5.11.21-1-pve: 5.11.21-1~bpo10 pve-kernel-5.11.17-1-pve: 5.11.17-1~bpo10...

Hi, yes apt update & apt dist-upgrade work fine. Same problem occurs from pveupdate command: root@pve:~# pveupdate Not an ARRAY reference at /usr/share/perl5/PVE/API2/APT.pm line 169.

Hello, I'm plagued by an error that I have had but have ignored until now since I want to upgrade to Pve7. The output from pve6to7: Checking for package updates.. WARN: Not an ARRAY reference at /usr/share/perl5/PVE/API2/APT.pm line 169. FAIL: unable to retrieve list of package updates! I've...