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?
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.
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.
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?
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...
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...
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...
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...
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?
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...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.