Search results

Why do you think so? Did you change some settings? If you have backups, you should also have the previous VM configuration and can probably compare the old ones to the current.

Have you seen this? https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#Unable_to_boot_due_to_grub_failure

Hi :), die einfachste Variante ist, die VLANs an den Interfaces der virtuellen Maschinen zu konfigurieren und auf der Firewall die VLANs auf entsprechende (virtuelle) Interfaces zu legen. Dann hast du in der Firewall die Kontrolle welche Übergänge erlaubt sind. Deine Switche müssen dann nur...

Um VLANs zu nutzen brauchst du das SDN erst mal nicht. Mögliche Problemlösung wäre, auf jedem Server nacheinander: pvecm status sagt dir vermutlich, dass dein Cluster Inquorate ist und "Activity Blocked". Dann: Auf jedem Server nacheinander folgende Schritte ausführen: 1. Quorum Votes...

Sind das mehrere Server in einem Cluster? Nutzt ihr das experimentelle SDN? Ihr könntet aus der /etc/network/interfaces Datei die VLANs temporär wieder entfernen und mit einem systemctl restart networking.service das Netzwerk neu starten. Sollte das nicht funktionieren, poste bitte mal die...

Am besten nimmst du das ISO von ISO von fedorapeople.org. Das hast du vermutlich aber schon. Sieht in deinem Screenshot so aus als fehlte einfach der richtige VirtIO Treiber. Schritte: 1. Es gibt einen Bug in Windows 10 21H2, der das verursachen kann. Dann läuft auch die Installation der...

Same problem here on a pve 6.3-6 test cluster connected to a 1.1.2 pbs. two nodes can connect and backup without a problem, the third node just tells me it can't connect. from the third node, a telnet pbs.xxx.com 8007 is successful, so it isn't likely a firewall or connection problem. pvestatd...

Trägt nichts zur Lösung bei, aber könnte die pve integrierte Firewall dein Problem nicht lösen? Welche Latenz hast du zwischen beiden Servern und weshalb möchtest du das so machen? VG, Marco

The problem disappeared suddenly when I upgraded Ceph from Nautilus to Octopus as well. Not sure if this is the reason why it disappeared and I wouldn't recommend doing this on a production cluster while ceph is in HEALTH_ERR. It would be fine if anyone could test also and confirm that an...

Same problem here after upgrading a test cluster from 6.2.15 to 6.3. Access to Ceph is possible, but HEALTH_ERR status. cluster: id: 27438f91-f51c-431a-9343-c1d5613ce181 health: HEALTH_ERR Module 'dashboard' has failed: ('invalid syntax'...

So my outlined case above works, at least if only one job targets a pbs. Thanks!

Hi, after the first backup, the dirty-bitmap is created and used for subsequential backups. the dirty-bitmap gets reset when a new backup is started. I wonder what happens if a VM is backed up in two different jobs to different backup targets, first to pbs and second to a local rdx drive. If...

The configured rbd_cache_size is located on the machine where the client runs (e.g. the hypervisor that runs the VM that uses the image).

Same problem here. Certain VMs freeze after backup was finished. It's always the same VMs, but not always all of them. Will do a downgrade for now and watch this thread. I filed a bug on bugzilla - see https://bugzilla.proxmox.com/show_bug.cgi?id=3043 and added some screenshots: - output of...

Congratulations for this big step forward. Since I discovered the first references in the installer, I've been waiting for it. Will try very soon and deploy as soon as stable to customers :-).

We solved it yesterday, as it seems. Tests are ongoing. We had two HP 5700 switches in place and wanted to use the virtual trunking wit IRF to be able to do LACP over both switches due to redundancy. IRF didn't work for us, so we disabled it but we still had the link between the two switches...

I'd also be interested in a solution or an explanation. We discovered exactly the same behaviour in a very common, yet fresh setup of a proxmox VE cluster with 3 Nodes. Totally different hardware, but due to a switch outage of less than a second, the cluster falls apart and does not come back...

Yes - both nodes were rebooted. Here are the /etc/network/interfaces of both nodes: Node Obelix: root@obelix:~# cat /etc/network/interfaces # network interface settings auto lo iface lo inet loopback iface eth0 inet manual iface eth1 inet manual iface eth2 inet manual iface eth3 inet...

Unfortunately, this does not work. We have a dedicated cluster link between two nodes, the nodes are resolved in the /etc/hosts to the IPs of this dedicated link. If I ping these IPs or the names, I can see iptraf counting packets on those interfaces. If I stop pinging, there is no activity on...

Thanks. That makes sense... :)