Search results

  1. Y

    Container or VM

    Networking stack is complex - adding additional layer for this would block the oportuninty of tuning in many ways. So I think I probbably use IOMMU instead of SRV-IO and not to use virtio as a bridge to network nic. OS: Proxmox 7.1 --> Debian 11
  2. Y

    Container or VM

    I will do tests between LXC and KVM with passthrough. I could do also (virtio vs passthrough) but You show me the way to simply simulate 100.000 connections with different src/dst ips....
  3. Y

    Container or VM

    @tom I plan not to use virtio nics because of performance (I need multiqueue and offload from my hw nic). So there is not a good idea to do that - i will use VirtIO nic for management nics.
  4. Y

    Container or VM

    I would like to make a router for a 10G+ bandwidth (BGP+QoS+Firewall). Of course I will passthrough the network cards inside to the VM/Container. What is better for that purpose: Container or Virtual machine?
  5. Y

    Apparmor DENIED audid failed flags warnings after LXCupgrades to Debian Bullseye

    I mean: Why the Nesting feature is not enabled for newly created containers? (and not why the "unprivileged container" option is set by default) :)
  6. Y

    Apparmor DENIED audid failed flags warnings after LXCupgrades to Debian Bullseye

    Why this isn't enabled by defaults? When creating container the "unprivileged container" option is set by default.
  7. Y

    [SOLVED] Proxmox Debian 10 Buster Template and mariadb

    Please see the attached image from earlier post.
  8. Y

    [SOLVED] Update problem

    Well some angel gave me (after sending a post) an answer - You need only to fsck unmounted EFI partition listed in /etc/kernel/pve-efiboot-uuids and run: pve-efiboot-tool refresh. Thats all.
  9. Y

    [SOLVED] Update problem

    What can I do with that: # dpkg --configure -a Setting up initramfs-tools (0.133+deb10u1) ... update-initramfs: deferring update (trigger activated) Setting up pve-kernel-5.4.78-2-pve (5.4.78-2) ... Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal...
  10. Y

    [SOLVED] Proxmox Debian 10 Buster Template and mariadb

    Look inside the features in LXC Options - see attached screenshot
  11. Y

    Migration issue - storage 'zfs1-vps1' is not available on node

    I opened FR at bug tracker allready after few commants here.
  12. Y

    Migration issue - storage 'zfs1-vps1' is not available on node

    its still workaround.... Users need to do one click and forget about that thing.
  13. Y

    Migration issue - storage 'zfs1-vps1' is not available on node

    Now I do migration by zfs send+ssh and copying config file... but that's smells like temporary solution ;-)
  14. Y

    Migration issue - storage 'zfs1-vps1' is not available on node

    > based on my experience having hostnames in the storage names is a bad idea Why? It's not quite bad... In moniotoring software - If You got many storages there are distinguishable without aliases... > kind of gives it away: names of source and target storage must be identical. There should...
  15. Y

    Migration issue - storage 'zfs1-vps1' is not available on node

    I use the newest Proxmox. I cannot migrate between nodes when the nodes has local-storages.
  16. Y

    Restoring failed

    I tried to restore privileged to unprivileged container. Is it supported? If not how to convert one to another and vice versa.
  17. Y

    Migration issue - storage 'zfs1-vps1' is not available on node

    This is not suitable for containers and pct command. How to do migration with one click instead of clicking backup&waiting&restore... ?