Search results

  1. S

    Which ports must be open and forwarded to pve on a router to use Spice from Proxmox Webinterface?

    Forwarded ports 8006 and 3128 from the router to the proxmox node, I see a spice proxy from Internet via nc, but can't connect to a vm. Seems that something is missing. Got "connection refused". # ss -tulpn | grep spice tcp LISTEN 0 4096 *:3128 *:*...
  2. S

    [SOLVED] problem with mounting cephfs from Ubuntu 22.04 vm via a kernel driver

    When I'm trying to mount cephfs from the proxmox cluster 6.4 with ceph 15.2.15 to the vm client Ubuntu 22.04 I'm getting an error: $ sudo cat /etc/ceph/ceph.conf [global] auth_client_required = cephx auth_cluster_required = cephx auth_service_required = cephx...
  3. S

    ZFS over iSCSI messages when create or remove LUN

    I'm using ZFS over iSCSI storage. ISCSI provider - LIO. ISCSI server - Proxmox backup server with a kernel 5.11. PVE version - 6.4.6 with a kernel 5.11. When create or remove VM disk, create or remove a snaphot there from the PVE GUI, I'm getting error messages from another LUNs: qemu-img: iSCSI...
  4. S

    bare metal host backup and restore

    How to do a bare metal live host backup using Proxmox backup client and then restore it from this backup like a Clonezilla?
  5. S

    Raspberry Pi port of Proxmox

    Somebody did it :) Also can be useful as a quorum host in an adult 2 nodes cluster. Here
  6. S

    different CPU models in a cluster

    I have servers with different CPU models in a cluster. So, want to create the config file /etc/pve/virtual-guest/cpu-models.conf with common flags for all my CPU. Is there any tool in Proxmox to automate this task? Manually compare flags and create config is a very long and error prone task...
  7. S

    [SOLVED] slow live migration after upgrade proxmox to the 6.4

    I see that live migration goes much slower after updating all cluster to the 6.4. Here is a dedicated migration network 10Gb. root@asr5:~# cat /etc/pve/datacenter.cfg keyboard: en-us migration: network=192.168.122.1/24,type=insecure Now it is: 2021-04-30 00:33:14 use dedicated network address...
  8. S

    [SOLVED] Rename vm frm GUI: "-" and "." not accepted

    When I'm trying to rename a vm from a web gui, it doesn't accept at least "-" and ".", even if an original vm name contains minus and dot. root@asr5:~# pveversion --verbose proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve) pve-manager: 6.3-7 (running version: 6.3-7/85c4930a) pve-kernel-5.4...
  9. S

    [SOLVED] problem with the last update and a live migration

    After tonight's update there are many live migrations were failed, what has never happened before. I did reboot all nodes after installing updates, but it didn't help. The installation log: Preparing to unpack .../0-libgstreamer-plugins-base1.0-0_1.14.4-2+deb10u1_amd64.deb ... Unpacking...
  10. S

    Question about adding an addtional network to Ceph

    I have a spare 10G interfaces at all cluster nodes. Planning to add this interface to Ceph. What is the best way to do it? I see following choises: 1) Add an additional network to Ceph. It will mean stop a service, delete all monitors and create it again, right? 2) Just create LACP (802.3ad)...
  11. S

    can't destroy or create ceph monitor

    I have removed the monitor via web GUI, later created it again, but it doesn't start. Can't remove it or create again. root@asr3:~# pveceph mon destroy asr3 no such monitor id 'asr3' root@asr3:~# pveceph mon create --monid asr3 monitor address '192.168.121.3' already in use root@asr3:~# pveceph...
  12. S

    "ceph : command not allowed" in syslog

    What is a reason of following error messages in the syslog every night? Proxmox 6.3, Ceph 15.2. Apr 14 03:00:49 asr2 sudo[181953]: ceph : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -a --json=o /dev/sdb Apr 14 03:00:49 asr2 sudo[181953]: pam_unix(sudo:session): session...
  13. S

    Proxmox 6 - network won't start

    I have a problem with a network during a boot. pve-asrock-02 log # grep systemd syslog ... Jul 25 19:38:16 pve-asrock-02 systemd[1]: ifupdown-pre.service: Main process exited, code=exited, status=1/FAILURE Jul 25 19:38:16 pve-asrock-02 systemd[1]: ifupdown-pre.service: Failed with result...