Search results

  1. F

    Proxmox 1.1-1 fail to boot after fresh install

    Thank you. I really forgot about legacy grub limit.
  2. F

    Proxmox 1.1-1 fail to boot after fresh install

    I am trying to install Proxmox Backup inside of VM with 8 vCPU, 8GB RAM and 10TB volume disk (that can grow more). I tried to do normal process with EXT4 and XFS and when it finish (without error), it reboot and I attached an image with the error (from grub). This is a LVM disk without...
  3. F

    Proxmox fresh install and weird long times to execute commands

    Today I saw one thing different: We have ony one Ubuntu VM and there it is working perfect: root@ubuntu:/home# time screen -ls No Sockets found in /run/screen/S-root. real 0m0.003s user 0m0.003s sys 0m0.000s But is not with centos: [root@centos home]# time screen -ls No Sockets found in...
  4. F

    Proxmox fresh install and weird long times to execute commands

    I have other server with same CPU, motherboard, memory etc (same datacenter server plan) configured with Proxmox in the same way: [root@ip76 ~]# time screen -ls No Sockets found in /var/run/screen/S-root. real 0m0.008s user 0m0.001s sys 0m0.007s edit: actually they have one...
  5. F

    Proxmox fresh install and weird long times to execute commands

    pveperf results: root@pve:~# pveperf CPU BOGOMIPS: 141011.20 REGEX/SECOND: 1585748 HD SIZE: 54.63 GB (/dev/mapper/pve-root) BUFFERED READS: 502.19 MB/sec AVERAGE SEEK TIME: 0.13 ms FSYNCS/SECOND: 3387.38 DNS EXT: 44.49 ms DNS INT: 1.97 ms (xxx)...
  6. F

    Proxmox fresh install and weird long times to execute commands

    Giving a feedback: - disabling the powersaver gorvernor and set the performance one: no changes - changing kvm64 to host: the time was divided by two for screen -ls command (0.5s to 0.25s). however the ideal number is 0.01s or less in normal situations The IO use is very low. But commandas like...
  7. F

    Proxmox fresh install and weird long times to execute commands

    cpu type: kvm 64 When you talk about BIOS, are you asking about the Host or VM BIOS?
  8. F

    Proxmox fresh install and weird long times to execute commands

    Environment: - fresh proxmox install - proxmox installed under first ssd - second ssd used as a cache of pve - 4 x 2TB disks grouped in one volume There is 6 centos 7 VMs almost doing nothing with I/O. The WA of Host is 0.0 and the WA of the VMs is n, with n 0.0>=n>1.0 screen command executed...
  9. F

    HTTP Error 404 Not Found: Path '/fixed_index' not found.

    Is there any other ISO version to try or a md5sum to check the ISO? https://www.proxmox.com/en/downloads/category/iso-images-pbs
  10. F

    HTTP Error 404 Not Found: Path '/fixed_index' not found.

    Actually I updated all servers (proxmox and pbs) and restarted all the servers (which will restart virtual servers and libvirt. I executed from different node, but all of them are using same packages version. I attached the commands results. Is there any log that I can read to try understand...
  11. F

    HTTP Error 404 Not Found: Path '/fixed_index' not found.

    We did more one update on all packages and then restarted the entire host. Then I tried the backup again: INFO: starting new backup job: vzdump 101 --node pve2 --storage backup --mode snapshot --remove 0 INFO: Starting Backup of VM 101 (qemu) INFO: Backup started at 2020-11-06 18:08:33 INFO...
  12. F

    HTTP Error 404 Not Found: Path '/fixed_index' not found.

    root@pve1:~# proxmox-backup-client version --repository x.y.z.w:backup Password for "root@pam": ******************** client version: 0.9.4 server version: 0.9.4 root@pve1:~#
  13. F

    HTTP Error 404 Not Found: Path '/fixed_index' not found.

    proxmox-ve: 6.2-2 (running kernel: 5.4.34-1-pve) pve-manager: 6.2-14 (running version: 6.2-14/2001b502) pve-kernel-5.4: 6.2-7 pve-kernel-helper: 6.2-7 pve-kernel-5.4.65-1-pve: 5.4.65-1 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph: 14.2.11-pve1 ceph-fuse: 14.2.11-pve1 corosync: 3.0.4-pve1 criu: 3.11-3...
  14. F

    HTTP Error 404 Not Found: Path '/fixed_index' not found.

    I am using Proxmox CE 6.2-14 and last PBS beta version. When I try to manually backup one VM, I get this: () INFO: starting new backup job: vzdump 110 --remove 0 --storage backup --node pve3 --mode snapshot INFO: Starting Backup of VM 110 (qemu) INFO: Backup started at 2020-11-01 21:01:33...