Search results

You need to use multipath to avoid this. See https://pve.proxmox.com/wiki/ISCSI_Multipath

Looks like an hardware issue without any relation to Proxmox (and probably any other OS too). Try to install a simple Ubuntu server and check whether you have the same phenomenon.

Sollte problemlos möglich sein, der erste und zweite Container müssen am gelichen (virtuellen) Netz hängen. Nicht zu vergessen, dass im Routing auch die Rückwärtsrichtung (also vom zweiten Container auf den fernen Computer) passen muss. Beispiel: 1. Container (der mit VPN, angenommen der hat...

Sollte das so machen wie gewüscht: Bei Ausfall des bevorzugten Nodes die VMs auf die verbliebenen aufteilen. Kriterium ist dabei die Anzahl der zu verteilenden VMs (also NICHT die Auslastung der Nodes, was außerhalb HA läuft wird nicht berücksichtigt). Wenn trotzdem alles auf eine Node geschoben...

Um das im Detail beurteilen zu können müsste man sich /etc/pve/ha/groups.cfg und /etc/pve/ha/resources.cfg genauer anschauen und aud diser Basis bewerten was eim Ausfall welcher Node mit den einzelnen VMs passieren soll.

Depends on your needs - if you have suffient RAM and you do not plan to hibernate or sleep your server (usually not the case) best is to not specify swap at all ( size = 0).

For test: exchange the cables between th e2 NICs and check if the problem remains at the NIC. If - yes: NIC defect - no: cable defect

You're talking about connection via WAN (internet) I suppose. First of all check whether the packets arrive as expected at the WAN NIC by running tcpdump -eni enp3s0 - If the packets arrive properly (but are not answered) check the guest's IP configuration respectively track the packets in...

Einfach mal beobachten , welcher Verkehr über Netzwerk läuft, d.h. sowohl im Gast als auch im Proxmox Host das Interface tracen (im Host mit tcpdump auf dem Brigdeport, z.b. tap111i0 für VM111) , wenn im Gast Widows läuft Wireshark nehmen. Auf grund der Pakete kann man dann rauskriegen we was...

See e.g. https://www.tecmint.com/extend-and-reduce-lvms-in-linux/

Put simply the requested swapsize into the respective field in the "Target Harddisk"'s "options" menu.

vmbr1 (as well as all other bridges) does not exist at boot time, only after ifup has been processed. Should work if you put the service as post-up in /etc/network/interfaces

Assuming your thinpool is pve/data (default in Proxmox VE) and you want to create a 10GB volume for backups named "backupvolume" run lvcreate -V10G -T pve/data -n backupvolume and create afterwards a filesystem in it and mount it. Note that 10G is just the virtual size. Be careful to avoid...

It can happen since firewalls as well as intelligent switches may react on packets changing rules for blocking/allowing packets. Therefore the hint: remove all firewalls and use simple unmanaged switches (at least temporarily for a test).

If GRUB/BIOS is able to read the USB hard-drive it will be possible by configuring grub manually, i.e. install grub at you thumbdrive but using data from diskdrive,e.g. grub-install --boot-directory=<path-do-grub-data-at-disk> /dev/<thumbdrive> Then you have to configure...

First of all check your LAN cabling and firewall settings In any case use different switches for different subnets a deactivate (for a test) all firewalls. If the problem persists track the IP packets via tcpdump (i.e. in container, Proxmox host, "another remote physical server") in order to...

Tipps in https://tldp.org/HOWTO/NFS-HOWTO/troubleshooting.html sollten weiterhelfen.

How are the response times when using the simple ping (from node to node) on the command line? Maybe stopping deep scrubbing improves the situation (see https://ceph.io/geen-categorie/temporarily-disable-ceph-scrubbing-to-resolve-high-io-load/)

This is rather an "eve-ng" topic than a Proxmox one. However: as soon as a guest OS is not starting up properly any more try several variants of configuring the VM, as e.g. CPU type, virtual disk controller etc.

https://docs.ceph.com/en/latest/rados/configuration/ceph-conf/ gives an overview about the relevant services. Restart them with systemctl restart ceph-mon.target etc.