Search results

  1. V

    [SOLVED] Can't install proxmox with "AMD Ryzen 5 2400G with Radeon Vega"

    Did not work for me. I've seen that proper APU support is from 4.16. So we have to wait till stuff have been backported. Is there any chance that we could get this soon?
  2. V

    Blue screen with 5.1

    Thx for the info, but this will disable all CPU cores and leave only one for the system, which is not really s solution. I can also confirm that the new kernel 4.13.4-1 still has problems with BSOD...
  3. V

    PVE 5.1: KVM broken on old CPUs

    Hi, is there a possibility to also backport it to 4.10.17-5 as the newer kernel have problems with KVM see https://forum.proxmox.com/threads/blue-screen-with-5-1.37664/. Or is that also fixed. Thx
  4. V

    Blue screen with 5.1

    @cybermcm Thank you for the hint. A newer version of the kernel make my VM crash...we get BSOD! So I'm stucked which is not good...
  5. V

    Blue screen with 5.1

    Hi, after running some time with this kernel: Linux pve-1 4.10.17-5-pve #1 SMP PVE 4.10.17-25 (Mon, 6 Nov 2017 12:37:43 +0100) x86_64 GNU/Linux we had some better experience, but we have still some problems. The BSOD are gone but now the whole system crashs, the only way to recover is hard...
  6. V

    Blue screen with 5.1

    Have you tried this? cat /proc/cpuinfo
  7. V

    Blue screen with 5.1

    @wolfgang I'll try to find a system, if we have enough spare parts around. I'll check that out on monday and give you feedback. Regards
  8. V

    Blue screen with 5.1

    @wolfgang Ok, works so far, no BSOD anymore! VM's are running one day without any problems. Thank you for bringing up a workaround!
  9. V

    Blue screen with 5.1

    Ah great didn't see that. I've successfully downgraded to 4.10.17-5-pve, and my machines do boot! Thank you so far.... I'll report back if we still have BSOD.
  10. V

    Blue screen with 5.1

    Hi, thank you for your feedback, but I was not able to downgrade to older kernel as all the ZVOL are missing and not mapped into /dev/zvol. That makes my vm not start. Even 4.13.3-1-pve wont map the ZVOL. Thx
  11. V

    Blue screen with 5.1

    Or is there a proper way to downgrade to proxmox 5.0 ? Edit: There is no easy way to downgrade to 5.0, as there are changes in the way ZFS works. So downgrading is not a option. We have to wait for a fix, which is really bad!
  12. V

    Blue screen with 5.1

    Hi I've downgraded the kernel version, but I've had problems with booting the qm VMs. It look like the old kernel maps the zvol different, as /dev/zvol is now missing. So I'm not bale to boot the Windows VM. I'm running prxmox 5.1 and kernel was: 4.13.4-1-pve. I've tried to down grade to...
Top Bottom