Search results

hi, tonight we have the problem, thats the fingerprint of backup server was automatical changed. ssl was changed too. all proxmox nodes / servers dont have access after it, why all servers have other fingerprint key. why it do change automatical? what is problem and how can i solve it without...

No thats wront, well with old kernel it boots. i have disable VT-d in BIOS of Server, than it works fine. For other, i hope it help to solve your problems. regards

Hi, anyone a idea? regards

same issue after set entry and update and reboot. thats not solution :( with 6.5.* it works wihtout errors.

nice information, that i have overread. thanks i would test it. also only add in /etc/default/grub the entry: intel_iommu=off than update-grub and reboot right? regards

Hi all, in last kernels we have many Problems, We cant use only kernel 6.5.13-5-pve as last working kernel. All newer kernels >= 6.8.* have following error: ...iock error debug interrupt for reason 61 on cpu 0... system hang up and was not reachable.... only hard reboot with power off works...

hi, a small question, how can i create a prune-job for special vm-ids only. i would save for special vm-ids weekly abnd monthly backups 1x, but i dont find a option to set vm-ids on a job. on normal job all backups are in the job. any ideas here? regards

was a problem with pve kernel, older kernal and newer kernal works fine. dm error comes too in the used version... regards

Im Log fand ich noch: nmi iock error (debug interrupt ) for reason 71 on cpu 0 CPU ist aber OK.

hi all, same issu again on backup, network was unreachable after a while o running backup with newest proxmox version. any ideas to solve?

solution: delete all ssl in pve dir and under folders than renew ssl´s reboot node and cluster than add again works fine regards

# rm /etc/pve/pve-root-ca.pem and than # pvecm updatecerts --force on new node than restart than add again dont work, same issue.

hi all i get following error message if i add a new node on web gui. waiting for quorum...OK (re)generate node files generate new node certificate Certificate request self-signature ok subject=OU = PVE Cluster Node, O = Proxmox Virtual Environment, CN = phoenix.mydomain.de CA certificate and CA...

hi all in proxmox i have receive today a network firmware bug. all network ports a disabled/unreachable after start automatival backup, any ideas. log in attachment version here... i have make a upgrade after hard reboot ot node... after i have newer pve version as before... log are old vetsion...

Edit: have add PVEDataStoreuser to Storage as @usergroup and in my own usergroup i add permission mapping.use

hi all, i have a group since older versions for users. since v8 group rights are different/new. i have mount a nfs storage with iso´s, how can i add rights to my user group, thats users can only use iso´s, but don´t can remove and edit it and don´t show others on this storage? my user-group is...

hi all, after a debian upgrade on a kvm i have following errors. any ideas to solve it? system starts in new version only in initramf, in old errors come... regards error: update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.10.0-27-amd64 W: initramfs-tools configuration sets...

Hi all, ich habe heute ein normale update und dist-upgrade gemacht. Alles lief bis fast zum Ende durch, Danach wurde die Verbindung zum Server getrennt und ich kam nicht mehr drauf. Alle Nodes die ich upgedatet habe sind nun von außen nicht mehr erreichbar. Wenn ich lokal per Console drauf gehe...

der Befehl hat geklappt: bekomme die Ausgabe mit dem Snapshot, wie kann ich den nun löschen bzw. wiederherstellen? Wenn Ausgabe folgende ist: ID TAG VM SIZE DATE VM CLOCK ICOUNT 1 vormount 0 B 2023-11-03 20:30:201781:40:52.805...

hi, sorry für die späte antwort hier noch die ausgabe: bootdisk: virtio0 cores: 12 ide2: none,media=cdrom memory: 131072 name: myhostname net0: e1000=A1:62:93:21:E8:3F,bridge=vmbr1 net1: virtio=42:6F:55:6D:95:98,bridge=vmbr2 numa: 0 onboot: 1 ostype: other scsihw: virtio-scsi-pci smbios1...