Search results

Thx in advance - here it is: ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host...

Hi, we have a three node Proxmox Cluster on Proxmox 6. We have added new hardware network cards and disks to one system. After installing the hardware during the first boot the network was unreachable. The name of the network card changed from "enp3s0=>enp4s0". We have one bridging device for...

Hi, I can confirm this - we are using: proxmox-ve: 5.4-2 pve-manager: 5.4-13 My Containers are all located on LVM-THIN storages. All backups are done with snapshots. I have changed some backup targets a few days before from local to a NFS storage. The local backups with snapshots had worked...

I had the same problem with a newly added node, after the restart of corsync the old existing nodes know the new node, and the migration works...

Oh my god - you are right :eek: I really did not see it... 4 eyes see more than 2 :) thx, the systems are drbd clean now...

Hi, we used DRDB in the past on our systems... they where upgraded from Proxmox 4=>5... We do not use it anymore (for a long time). Now we are on ProMox 5.3.8. During every backup we get the message: Plugin "PVE::Storage::Custom::DRBDPlugin" is implementing an older storage API, an upgrade is...

Hi, I have tested and verified it with additional phyiscal disks for the transient storage. The solution with a local directory storage marked as shared works for me. The only thing to keep in mind, you have to create the disk for the transient storage once manually for all migration targets...

OK, I will test it with dedicated additional physical disks ...

Version 5.3.8. I tried it on the local directory storage, I can select "shared" but OK is not active. Because I have no free space at the moment and I have learned it is not possible to reduce my lvm-thin storage :-(( So the only way for me is to add some physical disks.

Hm, ... it is not possible to set shared on a directory in the gui - I tried it on local for testing https://pve.proxmox.com/pve-docs/chapter-pvesm.html#_storage_types

Thanks for your answer. Just to understand it: On the shared directory storage I have to put the disk image (on all target nodes). During migration all Disks on shared storages are skipped. Right?

Hi, we want to setup a qemu vm with 2 disks on Proxmox 5. Disk 1 CEPH Disk 2 local-lvm (big disk with temporary data) We want to speed up the migration, the temporary data can be lost after the migration. Is there a possibilty in Proxmox to skip the local disk 2 during migration? I thought in...

Hm, due to another dependency there was a hold on a package which caused the problem: apt-mark showhold pve-edk2-firmware After removing the package hold, the dist-upgrade worked ...

@tom Any ideas?

That is correct, I did not read this before. Like always, I have just made the upgrade via the webgui... By the way, the repository is missing in all my other proxmox systems (with a different minor version) , but the upgrade was successful. If I add this, the result is the same: apt-get...

Yes, I'm guilty, I'm not denying it ;-) But the problem was already there before, the "apt upgrade" was a bad try... apt-get update Hit:1 http://security.debian.org stretch/updates InRelease Ign:2 http://ftp.de.debian.org/debian stretch InRelease Hit:3 http://ftp.de.debian.org/debian stretch...

apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libnvpair1linux libpve-common-perl libpve-guest-common-perl libpve-storage-perl libuutil1linux libzfs2linux...

Hi, yesterday I wanted to upgrade my Proxmox 5.2.6 to current (5.3.8). We are using the non-subscription repo. The dist-upgrade reports: The following packages have unmet dependencies: libpve-common-perl : Breaks: qemu-server (< 5.0-42) but 5.0-30 is to be installed libpve-guest-common-perl...

Hi, I found the problem: ring1_addr: pxhost1pm ring1_addr: pxhost2pm ... The ring1_addrs must be a reslovable hostname or an IP ... prior to 2.4.3 this is not an issue and was working. If found it, because the newer Proxmox installations use the IP there and not the hostname. After adding the...

There was change in corosync 2.4.3... https://github.com/corosync/corosync/wiki/Corosync-2.4.3-Release-Notes totemconfig: Prefer nodelist over bindnetaddr I think this will break ALL ProxMox default corosync configurations prior to 2.4.3 ...