Search results

Following this thread PVE Logging, I have changed PBS_LOG by adding [Service] Environment="PBS_LOG=error" proxmox-backup.service and proxmox-backup-proxy.service because my system ssd writes were so high just logging and murdering my ssd. This works great except that when I run...

I have a USB hard drive encrypted with LUKS currently connected to my Proxmox Backup Server through a mount point defined in fstab. I would like to be able to use the 'Removable Datastore' feature with this drive but unfortunately it does not work. Looking inside datastore.cfg, I can see normal...

Hi, thanks for all your help tsprox. It's working now but I am not sure why. I have a 'standard' install with no zfs: /dev/nvme0n1p1 34 2047 2014 1007K BIOS boot /dev/nvme0n1p2 2048 2099199 2097152 1G EFI System /dev/nvme0n1p3 2099200 1953525134 1951425935 930.5G...

proxmox-boot-tool status just gives: Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. System currently booted with uefi My /etc/kernel/proxmox-boot-uuids file is present but empty. I think this is ok as I have another machine where proxmox-boot-tool does work as...

I am trying set boot image with: proxmox-boot-tool kernel pin 6.5.13-5-pve This reports back: Set kernel '6.5.13-5-pve' in /etc/kernel/proxmox-boot-pin. Refresh the actual boot ESPs now? [yN] y Running hook script 'proxmox-auto-removal'.. Running hook script 'zz-proxmox-boot'.. Re-executing...

I think I have the saem problem. Running 8.1.3 pve versions: proxmox-ve: 8.1.0 (running kernel: 6.5.11-7-pve) pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15) proxmox-kernel-helper: 8.1.0 pve-kernel-6.2: 8.0.5 proxmox-kernel-6.5: 6.5.11-7 proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7...

/dev/hwrng for AMD Ryzen seems to be broken again. If try to spin up one of my VMs with rng0: source=/dev/hwrng, I get: TASK ERROR: Cannot start VM with passed-through RNG device: '/dev/hwrng' exists, but '/sys/devices/virtual/misc/hw_random/rng_current' is set to 'none'. Ensure that a...

Hi Ramalama, Thanks very much for the pointer to the maint_mode script - very useful! I often want to be able to do this. As you have an x570 motherboard does /dev/hwrng work for you? It would be useful to know what board you have and what AGESA version? Kind regards, Jonathan

Hi Fiona, No, I am not running the very latest BIOS for my motherboard. My current BIOS is from August 2022 and has the 'Update to AGESA ComboAm4v2PI 1.2.0.7.' patches. I thought this patch was meant to fix these problems. Your link does not mention what AGESA patch is necessary to fix this but...

So if I boot with the old kernel (5.15.108-1-pve), the output of the above commands is: root@pve1:~# cat /sys/devices/virtual/misc/hw_random/rng_current tpm-rng-0 root@pve1:~# cat /sys/devices/virtual/misc/hw_random/rng_available tpm-rng-0 and I can start the VM without problem using rng0...

Hi Fiona, This is the output I get from those 2 commands (on 5950x):root@pve1:~# cat /sys/devices/virtual/misc/hw_random/rng_current none root@pve1:~# cat /sys/devices/virtual/misc/hw_random/rng_available root@pve1:~# Note that the last command seems to output a blank line. I also have a...

Slight problem running my VM after upgrading to 8.0.3. Upgrade seemed to go well but my VM won't start with it's original settings. I get the error: Cannot start VM with passed-through RNG device: '/dev/hwrng' exists, but '/sys/devices/virtual/misc/hw_random/rng_current' is set to 'none'...

Are there any updates on this problem?

Does anyone know if this problem has been fixed yet?

On my Ryzen 3900x: All my LXCs (5 of them) work fine 2 x VM (Windows 10 Pro 12Gb and 8Gb RAM respectively) with PCIe passthrough: still work fine VM (Nethserver based on CentOS 3Gb RAM) with PCIe passthrough: can't find any drives VM Ubuntu with PCIe passthrough (8Gb RAM): works fine VM Ubuntu...

Hopefully someone will be able to diagnose what the problem is with Ryzen and this firmware. Until then I will stick with the old firmware. Thanks for all the help! Kind regards, Jonathan

Hi Fiona, I tried it with pve-edk2-firmware: 3.20221111-1 and pve-qemu-kvm: 7.2.0-5 on the Ryzen node but the VM fails as before. If I go back to pve-edk2-firmware: 3.20220526-1 and pve-qemu-kvm: 7.2.0-7, it works again. So I think the problem lies with pve-edk2-firmware: 3.20221111-1...

This seems to be the same problem that I was experiencing. See here: https://forum.proxmox.com/threads/select-vms-fail-to-start-after-latest-update.124240/#post-540903 Leesteken's solution solved my problem as well. Thanks to him for tracking it down

Hi leesteken, You fixed it! Thank you so much for your help. I will also +1 in the other thread.