Deshalb halte ich es ja für wichtig, dass solche Fehler öffentlich diskutiert werden.
Ich bin guter Hoffnung, dass es irgendwann auch mit dem 7 -er Kernel funktioniert.
Event data for report 22 was too short (4 vs 2) weißt ja auf einen Fehler im...
Please add some system description like which OS you are using - and add a screenshot.
If you have a Display Scaling mechanism activated please try to disable that one by setting it to "100 percent" - first only in the OS and then only in the...
Nur direkt am Gerät, nicht remote. (Es sei denn per iDRAC/IPMI/KVMxyz, sofern vorhanden.)
Direkt nach dem Einschalten einfach den Cursor auf/ab tippen, das ist unschädlich. Am Ende sollte das Grub-Menu sichtbar sein - mit "Proxmox VE GNU/Linux"...
Hi all I’ve go a strange issue on my pve, I set my s5 option in the bios as last state or power on after an ac power loss and it works( auto start ok).
My system boot up. But it show that it can be reached via it ip etc but nothing.
It is...
Wenn es nur um einzelne Dateien geht, kann man sonst auch auf dem Host oder innerhalb der VM (sofern Linux) mit dem backup-client einen restore machen. Mit der mount-Option sogar so, als ob das ein Laufwerk wäre.
Hi all,
Still very new at this so please bear with me.
I have 2 node cluster that I set up and had working earlier this week. I upgraded my router and that caused a whole bunch of IP issues of both nodes. I updated them and in all the correct...
Can you please explain what configuration you started with? What is the goal?
Provide the requested information, as well as "qm config [vmid]".
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
Thank you for the reply.
Yes they are both installed in the host.
I understand it's not a recommended setup, which is one reason I'm asking about it.
From your answer, I think I'll just wait for PVE Enterprise repository to offer the 7.0...
Running 9.1.9, and I'm seeing the status of all VMs and LXCs are frequently reporting 'unknown status', I would say it happens 5 to 6 times a day
Temp Fix
systemctl restart pvestatd pveproxy pvedaemon
Has anyone experienced this issue and found...
Running 9.1.9, and I'm getting the same issue, the status of all VMs and LXCs is frequently 'unknown status'
systemctl restart pvestatd pveproxy pvedaemon
This is only temporarily fixes the issue, it frequently happens again
Reviewing what you suggested looked normal (there were no specific references to vm-999-disk-0).
local-pbs is an LVM.
Should vm-999-disk-0 exist as a file somewhere? I couldn't find it.
Yessss thank you for your advice.
All went OK. Update is finished and PVE 9.1.9 is running.
All my containers and vms are running again without problems.
Thank you all very much!
The patch here published: https://www.reddit.com/r/Proxmox/s/cYmX4PKxgX (The patch code is duplicated, take only the first half)
makes version R535 v16.12 compatible with kernel 6.17 (I personally tested it and it works).
Then versions 16.13 and...
A quick note on when you want multiple encrypted ZFS pools in addition to having a ZFS system pool:
Turns out when you have more than one and try to create a second systemd unit for them you will cause a systemd dependency cycle, and things will...
2 years later I found the solution to this. Got iGPU passthrough from Mac Mini 2018 running on Windows 11 VM.
First I tried installing the newest 7th-10th gen iGPU drivers with no avail, still got code 43 - Windows has stopped this device...
The newer R580 drivers (let's say from 19.2 or 19.3 onwards, I think; we're at 19.5 now) compile correctly under the 6.17 kernel, while the R535 drivers (at least up to version 6.12; no one seems to have reported news on the more recent versions...