Search results

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.

I have a weird recent problem that some of my VMs fail to start after updating Proxmox. Some start fine but 2 always fail. The weird part is that if I copy them over to another Proxmox machine (which has not been updated) they start without any problem but I do have to make a couple of config...

I have an Intel x710 nic with 24 SR-IOV instances some of which are used in VMs. Before the VMs are launched, I set their mac address and vlan in systemd script like so: ExecStart=/usr/bin/bash -c '/usr/sbin/ip link set enp43s0f0 vf 1 mac 80:06:90:10:00:01 vlan 1 trust on' The VMs spin up fine...

Hi All, I wondered if anyone can shed a little light on a problem I have. I have a Windows 10 VM with Spice drivers and virtual nic passthrough working perfectly. When I try to update it with the 22H2 update, everything seems to be ok until I reboot. Then I get a BSOD error 0xc000021a and...

I am having exactly the same problem. Works fine for containers but not vms. Any ideas?

I think we just have to wait. I think MS are aware of an issue but whether it is to do with our VM Bios or not we wll have to see.