Recent content by ducs4rs

I am adding my issue to this thread. I ran through all these but should have checked journalctl first. The port showed good using ss. I then checked journalctl and found system could not read /var/log/pveproxy/access.log. Checking permissions it was set to -rw root root . Looking at my other...

I did the vcpu and it works like a charm.

Thanks for the pointer. I am going to try it out.. I was able to pass the GPU and a VF nic through to Ubuntu. Windows 11 wasn't happy with either.

Thanks for the pointers. The kernel parameters were from my notes when I first did pci passthrough on VE 5 or 6. I made all the changes you recommended and now the audio is correct, 02:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1) ... Kernel driver in...

I picked up a Supermicro X9SRL-F installed Proxmox VE (pve-manager/8.3.1/fb48e850ef9dde27 (running kernel: 6.8.12-4-pve) and I am trying to get PCI passthrough to work on a NVIDIA Corporation GP106GL [Quadro P2200]. While the Video is getting set properly "Kernel driver in use: vfio-pci" the...

I am running: root@pveprod:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm Linux pveprod 6.8.4-2-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.4-2 (2024-04-10T17:36Z) x86_64 GNU/Linux grub...

I had an Intel i350 setup with SR-IOV and it was working fine. I could use ViFs with Linux, and Windows 11. I swapped out the i350 with an i710. This was smooth as the OS saw the new NIC and it seemed to work. I changed the # of Vifs from 7 for the i350 to 32 for the i710. I have assigned ViFs...

That was it, thanks dir: vm_images path /tank/vm_images/ content images prune-backups keep-all=1 shared 1 changed to dir: vm_images path /tank/vm_images/ content rootdir,images prune-backups keep-all=1 shared 1

On my test system I ran PVE7to8 and got this warning on my only LXC vm WARN: CT 102 - volume 'vm_images:102/vm-102-disk-1.raw' (in config) - storage does not have content type 'rootdir' configured. WARN: Proxmox VE enforces stricter content type checks since 7.0. The guests above might not...

while the doc is not 100% clear, your pointers got me over the hump. Mirror is back together and system boots just fine. Thanks ! root@pveprod:~# zpool status rpool pool: rpool state: ONLINE scan: resilvered 7.34G in 01:23:32 with 0 errors on Wed Nov 1 20:09:15 2023 config: NAME...

Got it. Thanks..

It looks to me the guide you posted was to replace a rpool device and not to recreate a rpool mirror. Am I mis-reading this?

I had a bad disk in my rpool. I replaced the disk but the new disk turned out to be really slow. I decided to remove it with zpool detatch . I am trying to attach a new drive to the rpool but I get an error. See below root@pveprod:~# zpool status rpool pool: rpool state: ONLINE scan...

I am getting flooded with: IPv4: martian destination 0.0.0.0 from 192.168.1.1, dev ens2f1v0 I am using SR-IOV on a an intel quad port i350 nic. ens2f1v0 is a passthrough to an LXC container. This nic is 5:10.1 root@pveprod:/etc/pve/lxc# ip -br a lo UNKNOWN 127.0.0.1/8...

Thomas, I followed the directions and like you had an issue getting the container to be seen. I have a zpool setup for container templates since I use a 64G USB key for Proxmox OS. I made sure all file types were selected under Datacenter->Storage->templates. Templates points to zpool...