Recent content by tukiyo3

  1. T

    Firewall stops vm/ct communication - also have to reboot to fix

    me too.
  2. T

    Unmet dependencies issue when updating 5.x

    apt dist-upgrade I have solved the problem. pveversion pve-manager/5.0-32/2560e073 (running kernel: 4.10.17-4-pve)
  3. T

    Unmet dependencies issue when updating 5.x

    I've got the same trouble. /etc/apt/sources.list.d/pve-enterprise.list deb http://download.proxmox.com/debian stretch pve-no-subscription /etc/apt/sources.list deb http://ftp.at.debian.org/debian stretch main contrib deb http://security.debian.org stretch/updates main contrib The following...
  4. T

    Multiple NIC issue.

    Sorry for the late reply. kernel 4.4.44 - 1 - pve (proxmox 4) did not occur. Occurred in kernel 4.10.17-3-pve (proxmox 5: latest). I did fresh install debian9.1, apt install pve packages. # This file describes the network interfaces available on your system # and how to activate them. For...
  5. T

    Multiple NIC issue.

    I can not go to the Internet if there are multiple nic. proxmox 4.4 is works fine. proxmox 5.0 beta2 has that issue. * vmbr0 : 192.168.2.2/24 gateway : 192.168.2.1 * vmbr1 : 192.168.1.2/24 ping 192.168.1.3 is responsed. ping 192.168.1.1 is no response. ping 192.168.2.1 is no response. Even if...
  6. T

    Is qed file format support ?

    much faster than QCOW2 Qcow2 vs Qed performance
  7. T

    Is qed file format support ?

    TASK ERROR: unable to parse volume filename 'vm-325-disk-1.qed' pve-manager/5.0-9/c7bdd872 (running kernel: 4.10.8-1-pve) cd /var/lib/vz/images/325 qemu-img convert -O qed vm-325-disk-1.qcow2 vm-325-disk-1.qed modify /etc/pve/qemu-server/325.conf - virtio0...
  8. T

    /usr/bin/pveupdate: Wide character in print at /usr/share/perl5/PVE/APLInfo.pm line 22

    version: 5.0-9/c7bdd872 fresh install debian9 with LANG=ja_JP.UTF-8 and apt fresh install. echo "deb http://download.proxmox.com/debian/pve stretch pvetest" > /etc/apt/sources.list.d/pve-enterprise.list wget http://download.proxmox.com/debian/proxmox-ve-release-5.x.gpg -O...
  9. T

    wrong vma extent header chechsum

    see also: https://forum.proxmox.com/threads/cannot-restore-vm-backup-image-at-5-0beta1-5-0-5-error-restore-failed-wrong-vma-extent.33820/#post-166109
  10. T

    Cannot restore VM backup image at 5.0beta1(5.0-5) : ERROR **: restore failed - wrong vma extent

    VM backup image restored fail with error meesage "ERROR **: restore failed - wrong vma extent". CT backup image restored success. ## 1. backup VM image at 5.0-5/c155b5bc ``` INFO: starting new backup job: vzdump 1053 --node pve50b1 --compress lzo --storage g1000 --mode snapshot --remove 0...
  11. T

    Proxmox VE 5.0 Beta1 VM, CT Autostart issue.

    I have following issue 1. Clean install Proxmox 5.0. 2. I restored container and kvm image from backup it created on Proxmox 4.4. 3. It was setted "autostart : Yes" and Proxmox 5.0 reboot. 4. Coutainer and kvm doesn't autostart, but "TASK OK". 5. I scheduled root's cron, that start...
Top Bottom
Back