Recent content by werter

  1. W

    CPU type `host` is significantly SLOWER than `x86-64-v2-AES`

    Hello, Try x86-64-v3-AES if you has modern CPU from 2015 to now.
  2. W

    NAT for VM not working with dhcp

    Hi, Solved the problem, but only using static ip. I cannot solve the problem with dhcp.
  3. W

    NAT for VM not working with dhcp

    Hello, 1. vmbr1 - bridge with enp3s0 ('bridge-ports enp3s0' in my config above). 2. I'm don't have vmbr0 - I have vmbr1 and the name of the bridge doesn't matter. 3. And why 'pre-up' instead of 'post-up'? I did what it says here...
  4. W

    NAT for VM not working with dhcp

    Hi! PVE version 8.4.1 cat /etc/network/interfaces ... auto enp3s0 iface enp3s0 inet manual auto vmbr1 iface vmbr1 inet dhcp...
  5. W

    CPU type `host` is significantly SLOWER than `x86-64-v2-AES`

    Hi and thx for this topic. But with x86-64-v3 cpu type we can't use avx512 cpu instructions https://brentk.io/thoughts/qemu-and-kvm/making-sense-of-qemu-cpu-types.html
  6. W

    Automatic backup from one PVE to another, on another hosting

    Добрый. Вы хотите бэкапить вм с одного прокса на другой? Если да, то обновите оба до самой свежий версии, соберите из них кластер и настройте репликацию вм по крону. Но это возможно, если на обоих проксах используется zfs.
  7. W

    Automatic backup from one PVE to another, on another hosting

    Добрый. Мой вам совет НИКОГДА не открывать самбу в мир. За такое в приличных местах выгоняют с работы. Настройте кластер на zfs-репликации и по крону реплицируйте нужные вам виртуалки, но для этого ОБА хоста должны быть на zfs. P.s. Как вариант, отдельно развернуть truenas scale и бэкапить туда...
  8. W

    Feature: When creating virtual machine snapshots, you are allowed to exclude individual disks.

    Hi there. Add the option: When creating virtual machine snapshots, you are allowed to exclude individual disks, which allows you, for example, to avoid adding disks with temporary and renewable data, such as caches, swap partitions, and backups, to the snapshot to save space. That would be very...
  9. W

    Improve virtio-blk device performance using iothread-vq-mapping

    Hi there! Will this feature be added to Proxmox VE ? https://blogs.oracle.com/linux/post/virtioblk-using-iothread-vq-mapping
  10. W

    the problem with updating to 8.2

    Hi! I have the same problem after update to latest 8.2 kernel. After update network interface names have changed! Fix: 1. Show new names: ip a s 2. nano /etc/network/interfaces and change to new name(s) 3. ifreload -a OR Here https://wiki.debian.org/NetworkInterfaceNames#custom from "CUSTOM...
  11. W

    Linux 6.9 Features: DM VDO, AMD Preferred Core, Intel FRED & Larger Console Fonts

    Hi there :) https://www.phoronix.com/review/linux-69-features Among the key highlights for Linux 6.9 are the Device Mapper Virtual Data Optimizer (DM VDO) finally making it upstream Question to Proxmox team: Will dm-vdo support appear on PVE? P.s. Yes, I know about zfs and zfs features like...
  12. W

    Virtio disk type is much faster then iscsi disk type in VM?

    Thx :)
  13. W

    Virtio disk type is much faster then iscsi disk type in VM?

    But as u see above Virtio disk MUCH faster. Why ?
  14. W

    Virtio disk type is much faster then iscsi disk type in VM?

    Only for Win VMs?
  15. W

    Virtio disk type is much faster then iscsi disk type in VM?

    Hi there ) Virtio disk type is much faster then scsi disk type ? Controller type for both: Virtio scsi single. fio: fio --name=fiotest --filename=/mnt/diskX/test1 --size=4Gb --rw=randrw --bs=8K --direct=1 --rwmixread=50 --numjobs=8 --ioengine=libaio --iodepth=32 --group_reporting --runtime=60...
See more
Top Bottom