Search results

  1. D

    proxmox-kernel-6.5.11-8-pve-signed

    I've found solution - disable AV on host
  2. D

    proxmox-kernel-6.5.11-8-pve-signed

    # dpkg -C The following packages have been unpacked but not yet configured. They must be configured using dpkg --configure or the configure menu option in dselect for them to work: proxmox-kernel-6.5 Latest Proxmox Kernel Image The following packages are only half configured, probably due to...
  3. D

    proxmox-kernel-6.5.11-8-pve-signed

    # proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. System currently booted with legacy bios 8791-00C0 is configured with: grub (versions: 6.2.16-20-pve, 6.5.11-7-pve, 6.5.11-8-pve) 8792-D696 is configured with: grub (versions: 6.2.16-20-pve...
  4. D

    proxmox-kernel-6.5.11-8-pve-signed

    The following package was automatically installed and is no longer required: proxmox-kernel-6.5.11-7-pve-signed Use 'apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space...
  5. D

    BSOD on many Windows 2016

    # pveversion -v proxmox-ve: 5.4-2 (running kernel: 4.15.18-20-pve) pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec) pve-kernel-4.15: 5.4-8 pve-kernel-4.15.18-20-pve: 4.15.18-46 pve-kernel-4.15.18-19-pve: 4.15.18-45 pve-kernel-4.15.18-10-pve: 4.15.18-32 pve-kernel-4.15.18-9-pve: 4.15.18-30...
  6. D

    Windows 2016 Server 0x80070057

    I installed latest version of pve. It has't fixed the promlem. # pveversion pve-manager/5.2-6/bcd5f008 (running kernel: 4.15.18-1-pve)
  7. D

    Windows 2016 Server 0x80070057

    Windows 2012R2 and Windows 7 have same issue
  8. D

    Windows 2016 Server 0x80070057

    # pveversion pve-manager/5.2-2/b1d1c7f4 (running kernel: 4.15.17-3-pve) Error 0x80070057 when I format a hard disk drive to install Windows 2016 Server disk type: IDE
  9. D

    nfs problem

    With this problem, virtual machines become inaccessible due to strong lags
  10. D

    nfs problem

    Hello. We have Proxmox 4.4 with 4-node cluster. Total number of virtual machines is 40 There was a problem with backups on nfs. Nov 12 15:37:04 vbox1 kernel: [1665093.318616] INFO: task lzop:55243 blocked for more than 120 seconds. Nov 12 15:37:04 vbox1 kernel: [1665093.318631] Tainted: P...
  11. D

    WARNING: No balloon device has been activated

    I have the same problem. How to fix? I already have "balloon: 0" in all of my VMs VMID.conf and this error is still being thrown in the VE syslog constantly. # pveversion -v proxmox-ve: 4.3-71 (running kernel: 4.4.21-1-pve) pve-manager: 4.3-10 (running version: 4.3-10/7230e60f)...
  12. D

    vm synchronization

    Hello!!! I have two HP DL360 servers with proxmox 1.9 cluster connected to HP MSA P2000 via SAS interface. Now I want to buy a second MSA P2000 and server to another building how to synchronize data between MSA? MSA P2000 SAS do not support Remote Snap HP Data Protector support proxmox? or...