Latest activity
-
Bboisbleu replied to the thread [SOLVED] HyperV-Fehler nach Migration / VM bootet nicht.Passt soweit, auch wenn ich die Kombi seabios und win11 schräg finde. Wie hast du die Maschine migriert? https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE Hast du die VirtIO Treiber installiert und aktiviert...
-
Wwindowsdesxtop reacted to fabian's post in the thread [SOLVED] Force delete of "Pending removals" with
Like.
you can put the datastore into read-only maintenance mode, wait until that is active (no more writes by PBS or clients possible), then reset the atime of all chunks to > 24h ago (e.g. with a find .. -exec .. command), disable the maintenance mode... -
Wwindowsdesxtop reacted to fabian's post in the thread [SOLVED] Force delete of "Pending removals" with Like.
the problem with offering it in a very straight-forward fashion is that it has the potential for dataloss that will only show up later: - start backup -- backup writes new chunk - touch all chunks with date in the past - start GC - GC cleans up...
-
Rrothkraut replied to the thread [SOLVED] HyperV-Fehler nach Migration / VM bootet nicht.bios: seabios boot: order=scsi0;scsi1;ide2 cores: 4 cpu: x86-64-v2-AES hotplug: disk,network,usb machine: pc-i440fx-11.0 memory: 24576 meta: creation-qemu=11.0.0,ctime=1780549481 name: server net0: virtio=xx:xx:xx:xx:xx:xx,bridge=VLAN1 numa: 0...
-
Mmvarst posted the thread [SOLVED] Hung startup sequence in Proxmox VE: Installation and configuration.Startup suddenly stopped working. It gets hung here every time and for an hour+. I did edit the fstab but when i have made fstab mistakes in the past it would just go into emergency mode where i could just fix the mistake, it's different this...
-
-
Bboisbleu replied to the thread [SOLVED] HyperV-Fehler nach Migration / VM bootet nicht.Kannst du bitte mal die gesamte Config des Hyper-V Servers posten (in Codeblöcken)? Oder endet die Config tatsächlich mit ostype: win11?
-
TTari reacted to sthielo's post in the thread [SOLVED] PMG in a LXC container: 'timedatectl show' fails (used by UI) with Like.
YES - it was as simple as that. apt install dbus && systemctl start dbus So, I do NOT understand how this package can be missing. ok, my container is quite old (2021) made some upgrades ... even some major ones from 8 to 9. Thanks a lot.
-
RRiHe posted the thread Unable to acquire lock "/var/log/proxmox-backup/tasks/.active.lock" in Proxmox Backup: Installation and configuration.We noticed backups failing due to the reason: Unable to acquire lock "/var/log/proxmox-backup/tasks/.active.lock" We got a similar error (only at random times) as this thread...
-
Rrothkraut replied to the thread [SOLVED] Fehler beim Löschen von VMs (rbd: listing images failed).Danke für die Rückmeldung. Es war eine fehlerhaft Konfiguration von unserer Seite aus. Berechtigungen für den User, welcher für das Verbinden des RBD genutzt wurde, haben seitens CEPH nicht gepasst.
-
SSchellimen replied to the thread Fujitsu Esprimo P7010n dosen't recognize PVE Boot Stick.I couldn't get the Boot-Stick working with the Fujitsu. So I installed Deb 12.14 on the hard drive via another PC and switched them back. But EFI Partition wasn't meant to be read ready for the Esprimo. So I had to format the EFI Partition and...
-
Rrothkraut replied to the thread [SOLVED] HyperV-Fehler nach Migration / VM bootet nicht.@boisbleu Welche Konfig macht Sinn? Bin in ESXi nicht so fit und habe die Umgebung auch nur "geerbt" habe die VM selbst nicht aufgesetzt.
-
-
Mmason64 replied to the thread Changed IPs on my cluster before reading anythings.thanks tried that but i got a few errors, when i ran pvecm status on node 2 i get the old IP still of 10.0.0.42 when it should be 192.168.1.42 i can get on to the GUI with 192.168.1.42 also when i run pvecm status on the first node i get this...
-
-
AArnOCP replied to the thread All VM can't accessible after kernel UPdate of the nodes?.Hello, I confirm with the old kernel 6.8.12-28-pve all VM's Worked (during day and 18 hours the VM's are ok) So there is a problem with the new 6.8.12-29-pve kernel on proxmox 8.4.19 VE?
-
Ssynexa replied to the thread S3 chunk lock files accumulate indefinitely in tmpfs causing memory exhaustion.Hi, Thank you for your help and quick response. We have submitted the bug to the tracker as requested. In the meantime, we have implemented the suggested workaround by mounting a dedicated filesystem on top of...
-
Bboisbleu replied to the thread [SOLVED] HyperV-Fehler nach Migration / VM bootet nicht.An der Stelle wäre mal die ESXi-Config interessant. Bist du sicher, dass die Maschine im MBR-Mode lief? Kein UEFI? Und pc-i440fx ist ein asbach-alter Standard - q35 wäre sicher sinnvoller.
-
Rrothkraut posted the thread [SOLVED] HyperV-Fehler nach Migration / VM bootet nicht in Proxmox VE (Deutsch/German).Hallo zusammen, ich beiße mir jetzt schon seit Stunden die Zähne an folgendem Problem aus: Ich habe eine VM von VMWare (Esx 8) zu Proxmox (9.2) migriert. Auf dieser VM ist Hyper V installiert und es laufen zwei VMs darauf. Leider bekomme ich...
-
-
SSteen_A replied to the thread IO Pressure Stall issue after upgrade to 9.1.Maybe it is obvious, but I did a mistake in the config that caused a very high IO pressure stall on my system As can be seen from the graph the IO pressure stall was around 80-90% all the time on the graph, and has been like this for months. But...
-
-
Ddaanw replied to the thread Changed IPs on my cluster before reading anythings.If you still want to make the change you can update everything to the desired new ips of course. In that thread the user already created a correct corosync config file. But you can Just edit /etc/pve/corosync.conf and copy the changed file to...
-
Mmason64 replied to the thread Changed IPs on my cluster before reading anythings.thanks found that the /etc/hosts was still on the old ips. i did take a look at that link before posting. i got stuck where it says # put correct corosync config into local pmxcfs and corosync config dir (make sure to bump the 'config_version'...
-
RRobFantini replied to the thread [SOLVED] backup fails: Unable toacquire lock "/var/log/proxmox-backup/tasks/.active.lock.changing backup start time away from midnight solved the issue.
