Recent content by amey

  1. A

    exit code 133 error while restoring windows vm from pve 7.1 to 6.3.x

    root@proxmox-svr3:~# qm config 197 [I deleted the restored vm and generated new 1. Hence using the new vm ID. thanks] memory: 128 root@proxmox-svr3:~# cat /etc/pve/storage.cfg dir: local path /var/lib/vz content iso,vztmpl,backup prune-backups keep-all=1 shared 0...
  2. A

    exit code 133 error while restoring windows vm from pve 7.1 to 6.3.x

    Hello, I do know that PV 6.3 has reached EOL. But just want to know if there is any work around to repair this issue. I am trying to restore a Windows server 2016 vm which was created in pve 7.x and trying to restore it in pve 6.3 But I am getting following error = estore vma archive: zstd -q...
  3. A

    Need Proxmox VE 6.3-2 iso

    When you can finish your task in 20 minutes, why would you spend time & money just because the installer is not available? :) I think it is OK to ask if we can get the ISO. If no, that's ok. Luckily I found the iso on 1 of my server drive's after performing extensive search. What a life saver...
  4. A

    Need Proxmox VE 6.3-2 iso

    Those are not production vm's my friend so the underlaying base storage also don't have any hardware RAID's ;-) But if you calculate the man power & storage cost for this upgrade alone, it is not justifiable. Look at this case study from a view of a start-up company. Pls don't look at this...
  5. A

    Need Proxmox VE 6.3-2 iso

    I don't have that much storage to take backup of all vm's before upgrading 6.3 to 6.4 And the hardware/storage costing & man hours that will be involved for this process is a over head for us. I did the calculation. Anyways ...
  6. A

    Need Proxmox VE 6.3-2 iso

    I tried to install VE 7.x and tried to add the host to existing cluster which has all servers having 6.3 version. I ran in to many issues for the newly added host. Hence I want to install the same version that I have on other servers. I am not sure if I will run in to any issues after adding...
  7. A

    [SOLVED] Remove node from cluster

    I am facing a strange issue. After removing 1 node [1] from the cluster= 1) pvcmnodes = Result is OK 2) pvecm status = Result is OK But, If I login to web UI, it still shows server3 in the list. How to remove it? I don't see the entry of the removed server in = 1) /etc/pve/corosync.conf 2)...
  8. A

    Need Proxmox VE 6.3-2 iso

    Hello, I am searching for Proxmox 6.3-2 iso Unable to find it at https://www.proxmox.com/en/downloads/category/iso-images-pve Pls suggest how to download the iso thanks. Regards, Amey.
  9. A

    vm info keeps loading in VE 7.0.11

    I found something interesting after referring to similar threads = I have following entry of same IP in proxmox servers = 10.200.104.46 ssh-rsa AAAAB3NzaCeIp9OuDOin+6yrTJ+ECo9KE0n0/pxUXIYpmkak= prod-proxmox-svr3 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQC9G/Iye0CeEbH0RakjQuPKb0= 10.200.104.46...
  10. A

    vm info keeps loading in VE 7.0.11

    Quick update: After logout & login back in cluster via web UI, I am getting following error when I click on any vm on newly added server = tls_process_server_certificate: certificate verify failed (596)
  11. A

    vm info keeps loading in VE 7.0.11

    I just tried to execute the command on the newly added server. Same issue continues. root@prod-proxmox-svr3:~# pvecm updatecerts --force (re)generate node files generate new node certificate merge authorized SSH keys and known hosts
  12. A

    vm info keeps loading in VE 7.0.11

    I should execute this command on the newly added proxmox server? Thanks.
  13. A

    vm info keeps loading in VE 7.0.11

    Hello, I have an existing proxmox VE cluster on 6.3.2 version I have added a new physical server in the existing proxmox cluster The new server has Proxmox VE 7.0.11 version. Problem is, when I click on any vm which is on VE 7.0.11, the info keeps loading with the circle. I tried rebooting...
  14. A

    How to add qcow2 disk in proxmox

    Thanks. Following commands helped = 1) tmp# qemu-img convert gitlab-server.qcow2 -O raw gitlab-server.raw 2) tmp# dd if=gitlab-server.raw dd of=/dev/pve/vm-101-disk-0 I was not sure about how to import the disk in 'local-lvm' volume. I tried to use following flags in step number 2 = pv -s...