Search results

  1. I

    2-3% IO delay floor with Alder Lake-N CPU family

    I can confirm it works. It's exactly the same on my AliExpress device. Thanks! I've been looking for this solution for months.
  2. I

    2-3% IO delay floor with Alder Lake-N CPU family

    I'm experiencing the same with a Jasper Lake Intel Celeron. Already tried updating the bios / microcode / ... still the same issue. Did you successfully get this fixed?
  3. I

    Hetzner Routed Network (3 Subnets + Additional IPs) Config Check

    Got it working... stupid issue in resolv.conf :/ Thanks again for your time and help.
  4. I

    Hetzner Routed Network (3 Subnets + Additional IPs) Config Check

    On the host OS you mean? That's working because my other hosts are working too. I got it working for a sec .. rebooted and it's gone again. I'm missing something obvious.
  5. I

    Hetzner Routed Network (3 Subnets + Additional IPs) Config Check

    Thanks for replying so swift! Much appreciated. It's added now without error. My debian test server on that IF still doesn't want to connect -- but I think that might be was an issue on my side. This is so much simpler! Thanks so much.
  6. I

    Hetzner Routed Network (3 Subnets + Additional IPs) Config Check

    Sorry to hijack the thread & excuse my ignorance .. I've tried adding an additional subnet (vmbr4) with a /29 the way described above by @jlebherz but my server doesn't want me to add 'scope link' to the route. What am I missing?
  7. I

    Safari on Big Sur : Issues with web-interface

    Nope. Nothing. Clean box. I've tested it on both my iMac & a new M1 MBP. Same issue.
  8. I

    ACME over DNSChallenge failing

    It seems we've all ran into that same tick-box. ¯\_(ツ)_/¯ That definitely wasn't clear to me.
  9. I

    Safari on Big Sur : Issues with web-interface

    Since the latest releases of Safari on Big Sur, I seem to run into a lot of issues dealing with the pop-up screens for creating VM's, adding storage, .. They first of all hang and later reports Safari the pages needed to be reloaded due to an issue. I can't seem to find anything in the console...
  10. I

    [SOLVED] Upgrade issues in 6.2-2

    Morning Moayad, Successfully upgraded to 6.3-2. Went very smooth.
  11. I

    [SOLVED] Upgrade issues in 6.2-2

    That did the trick! Didn't even have to reboot. Thanks so much, @Moayad
  12. I

    [SOLVED] Upgrade issues in 6.2-2

    root@pve:/var/lib/apt/lists# dpkg --list | grep linux-image ii linux-image-4.19.0-10-amd64 4.19.132-1 amd64 Linux 4.19 for 64-bit PCs (signed) ii linux-image-4.19.0-11-amd64 4.19.146-1 amd64 Linux 4.19 for 64-bit PCs...
  13. I

    [SOLVED] Upgrade issues in 6.2-2

    root@pve:/var/lib/apt/lists# dpkg --list | grep pve-kernel ii pve-firmware 3.1-3 all Binary firmware code for the pve-kernel ii pve-kernel-4.15 5.4-17 all Latest Proxmox VE Kernel...
  14. I

    [SOLVED] Upgrade issues in 6.2-2

    root@pve:/var/lib/apt/lists# apt install -f Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dh-python guile-2.0-libs libapparmor-perl libbabeltrace-ctf1 libbind9-140...
  15. I

    [SOLVED] Upgrade issues in 6.2-2

    Yes. Didn't help. Also found a thread about manually updating the kernel, did that too.
  16. I

    [SOLVED] Upgrade issues in 6.2-2

    Made that change, ran 'apt update' but it still wants to remove proxmox-ve :/ Should I do something to restart that apt process/list of things it needs to do?
  17. I

    [SOLVED] Upgrade issues in 6.2-2

    Sure. Thanks for taking the time. root@pve:~# apt update Hit:1 http://ftp.belnet.be/debian buster InRelease Hit:2 http://ftp.belnet.be/debian buster-updates InRelease Hit:3 http://security.debian.org/debian-security buster/updates InRelease Hit:4 http://download.proxmox.com/debian/pve buster...
  18. I

    [SOLVED] Upgrade issues in 6.2-2

    I'm running into an upgrade issue that I can't seem to fix. * Checked all apt sources and they all look OK. * Rebooted the node and retried * Last update happened by : apt update && apt upgrade instead of full-upgrade root@pve:/etc/apt# apt-get full-upgrade Reading package lists... Done...