Search results

  1. M

    Proxmox VE 9.1. kernel stack

    Hello. With the new Proxmox VE 9.1. with the next kernel: 6.17.2-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.17.2-1 (2025-10-21T11:55Z) We have a constant process stack (stack traces like): INFO: task iou-wrk-730901:813300 <reader> blocked on an rw-semaphore likely owned by task khugepaged:225...
  2. M

    New feature proposal: Network interfaces advanced option(s)

    Hello. After years of Network tuning many hypervisors like: OpenStack, Proxmox VE, and now also Red Hat/Oracle Virtualization, but in general Linux based ones, i can conclude that there are a constant tuning needs in the network section of hypervisors. Here i am talking about the situations...
  3. M

    Menu: Datacenter --> Storage --> Add

    Hello. I have a one small proposal for changing the Storage drop down menu on: Datacenter ==> Storage --> Add. In the current state we have all the storage types in one place, no matter if they are: local, NAS, SAN or other types. For the older and advanced users this is not an issue, but for...
  4. M

    Purpose of the internal interfaces

    Hello. I just want to understand the standard OpenvSwitch/Linux native interfaces used in Proxmox VE, when using SDN/VNets: VNetINT is name of my VNet Looking at the OpenvSwitch level: ovs-vsctl list interface | egrep "^name|^status|^type" name : vmbr0 --> This is a Bridge...
  5. M

    VirtIO-IOMMU

    Hello. Since new kernel (5.14) supports VirtIO-IOMMU, maybe it would be a nice one to have it as an advanced option to use (as option: enable/disable). Linux kernel 5.14. and VirtIO-IOMMU More details can be found here: QEMU - VT-d (IOMMU) VirtIO-IOMMU explained Br, Hrvoje.
  6. M

    Reserving HW resources for Hypervisor (physical machine) itself

    Hello. I have a question related to the Proxmox VE nodes (hardware/bare metal). Are there any possibility to reserve some hardware resources for Hypervisor itself, like: Reserved amount of RAM Reserved CPU cores Reserved disk spaces (if needed) Similar as it is possible on OpenStack...
  7. M

    MACVTAP as future replacement of classic NIC+BRIDGE+TAP interfaces

    Hello. Are you considering the future replacement of classic Bridge+TAP interface (to VM network) with MACVTAP ?. MACVTAP is a relatively new replacement for TAP interface, but also use /dev/tapXY as the old one (classic TAP) so can be easly used with QEMU. Since MACVTAP can be connected...
  8. M

    eBPF (+XDP) firewall

    Hello. Starting with Linux kernel 4.18. we have a production ready XDP + eBPF capabilities, which is now included in production, starting with RedHat Enterprise Linux v.8.1. and of course included in CentOS Linux 8.1. Other will follow soon. For those not familiar, in simple words: XDP is...
  9. M

    VLAN in GUI

    Dear. It will be a good choice to add a native support for VLANs in GUI for : Linux native interfaces (LAN card, Bond, Bridge) For now it is possible to use it, by manually modifying: /etc/network/interfaces, but it will be much better in GUI (with syntax check) In OpenvSwitch it is...
  10. M

    netmap (+VALE) + QEMU

    According to this article: https://www.linux-kvm.org/images/c/c5/Kvm-forum-2013-High-Performance-IO-for-VMs.pdf Using netmap with VALE switch ( http://info.iet.unipi.it/~luigi/vale/ ) will get a much higher throughput even 5x than virtio (from presentation, for 64 byte packets up to 2.5Mpps in...
  11. M

    OpenvSwitch 2.5 (with connection tracking) as replacement for iptables firewall model in the future

    Hello. Since OpenvSwitch v.2.5 is out now, and it has support for connection tracking with linux kernel module (nf_conntrack) can we expect in the future that Proxmox VE will replace "old" network model and introduce a new one. Situation is similar with OpenStack network model --> Video...
  12. M

    CoreOS supported as LXC template

    Hello. Are there a plan to support CoreOS as LXC template on ProxMox VE 4.x. BR, Hrvoje.