The error I get is below. I run PVE 9 with kernel 6.14.11-3.
: amdgpu 0000:c2:00.0: amdgpu: RAS: optional ras ta ucode is not available
: amdgpu 0000:c2:00.0: amdgpu: RAP: optional rap ta ucode is not available
: amdgpu 0000:c2:00.0: amdgpu...
I think pve-firmware package has the amdgpu firmware. Apparently you already have that? Maybe someone will know more if you tell us what GPU you have.
I get an error about not having secure display microcode, but everything seems to work (and it...
I got my FW desktop. PVE 9.0 runs fine on it. No issues so far. The GPU works with virtio-gl, which gives decent desktop performance for my usage. It replaces a Xeon D-1541 that was getting old. Relative to that it is very fast and has twice the...
Also, the reason I asked how @powersupport how he was checking the time in the VM is because on Linux each user can have their own locale settings. The timedatectl settings only apply to root and as a default for other users. So it is entirely...
How are you reading "VM local time"? Do you log in to a shell, do you send a command to the agent, something else? About 99% of the time when there is a time discrepancy of an exact number of hours or half-hours and NTP is synchronized, it is a...
By having them on the same subnet you are telling the kernel routing that it doesn't matter which one it uses because they are all the same. If they aren't actually the same, then you will see what you are seeing. Kernel picks one arbitrarily...
The official method for upgrading is here: https://pve.proxmox.com/wiki/Upgrade_from_8_to_9
Perhaps reviewing it will reveal a step that was overlooked. Did you see any error messages during the upgrade process?
DHCPOFFER of 192.168.48.100 from 192.168.48.1
DHCPREQUEST for 192.168.48.100 on eth1 to 255.255.255.255 port 67
DHCPOFFER of 192.168.48.200 from 192.168.48.1
DHCPREQUEST for 192.168.48.200 on eth0 to 255.255.255.255 port 67
DHCPACK of...
Again, from your log it appears that there are multiple interfaces on the same subnet. If they are not actually all connected somehow, this can't work as you want it to (and is a bad idea to begin with). You can still do what you want by only...
To be clear, did you upgrade the Proxmox packages to PVE 9 or did you only upgrade the Debian packages? If the latter, you need to do the former as well.
Having a bunch of different interfaces on the same subnet with incomplete reachability between them is...sub-optimal. As you've noticed, since they are all on the same subnet the Linux kernel assumes they are equivalent and will just pick one to...
You are running Debian "buster", which is six years old and out of support for a year. Debian generally moves old releases to an archive repository. You will need to update your sources.list files to point to "archive.debian.org". See here...
Apt will ask if you want to keep the current configuration or replace it with the package maintainer version. It will offer a couple of other options including showing the differences.
To operate a cluster you need to have "Quorum" = more than 50% of the votes. That has been mentioned here a zillion times. (And this is not restricted to HA.)
Build a separate thingy to give that third vote! -->...
If a machine can't reach other cluster members it restricts changes so that when it gets back into the cluster there aren't conflicts. That's just how it works, as discussed a million times in this forum. Set up a q-device as recommended in the...
Personally, I just minimize how much I customize PVE and back up /etc. I recently replaced my Intel server with a much newer AMD one and this approach had me back up pretty quickly. No worries about requiring different firmware packages or...
Mainly it is another thing to troubleshoot when things don't work. Stuff like "I changed the DNS but the new IP isn't being used" type of things two years later when you've forgot about the cache.
Honestly, this whole discussion is kind of dumb.