Recent content by Splise

  1. S

    apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/usr/bin/lxc-start" name="/proc/sys/kernel/random/boot_id"

    I am not able to create an unprivileged TK File Server. When attempting top create it I receive the following error: extracting archive '/dpool/vmstorage/template/cache/debian-9-turnkey-fileserver_15.0-1_amd64.tar.gz' tar: ./var/spool/postfix/dev/urandom: Cannot mknod: Operation not...
  2. S

    apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/usr/bin/lxc-start" name="/proc/sys/kernel/random/boot_id"

    Thanks for your response. Why can it be ignored? What does it mean? In my experience, ignoring an error in Linux eventually leads to other issues which eventually cause a catastrophic failure. I would like to understand the error, fix it, and possibly help others with the same problem. It...
  3. S

    apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/usr/bin/lxc-start" name="/proc/sys/kernel/random/boot_id"

    Part2: lxc-start 101 20200626024150.684 DEBUG start - start.c:lxc_try_preserve_namespaces:166 - Preserved mnt namespace via fd 56 lxc-start 101 20200626024150.684 DEBUG start - start.c:lxc_try_preserve_namespaces:166 - Preserved pid namespace via fd 57 lxc-start 101 20200626024150.684...
  4. S

    apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/usr/bin/lxc-start" name="/proc/sys/kernel/random/boot_id"

    For sure, please see below. I am testing with the TK File-Server as that is really what I am looking to use if possible. Thanks for your help Part1: lxc-start 101 20200626024149.728 INFO lsm - lsm/lsm.c:lsm_init:29 - LSM security driver AppArmor lxc-start 101 20200626024149.728 INFO...
  5. S

    apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/usr/bin/lxc-start" name="/proc/sys/kernel/random/boot_id"

    Hi, I have been attempting to mount a ZFS dataset in a LXC container, but cannot get past the "error=-13 profile" error. I have been searching the internet and forums to find a concrete solution, but nothing seems to work. Adding "nesting=1", seems to resolve most of the apparmor errors...
  6. S

    VM Storage Location

    Thanks, that makes sense for the most part. I was trying to configure a storage structure that is organized/logical, but does not deviate from what Proxmox is expecting. Is the new storage configuration defined below a better way to go? Using the structure below (and this is probably a dumb...
  7. S

    VM Storage Location

    Hi, When creating a new VM, the VM images are located in a different location than what I have specified. I also see four copies of the disk image when creating a VM. How do I take /dev out of the picture, and use only /rpool/data/vmstorage/vm-images, and only have one copy of the image? Any...
  8. S

    Proxmox PCIE Passthrough Multiple NIC Interfaces

    This is really unfortunate. I was hoping to create a guide for my peers on how to configure Proxmox for use with a PA VM firewall. I have spent weeks trying to get this working and read hundreds of articles and forums, but I just can't afford to spend this kind of time just to get a VM spun...
  9. S

    Proxmox PCIE Passthrough Multiple NIC Interfaces

    Don't see anything for 4-g. But I cam able to see the driver health status for the Chelsio NIC in the BIOS, and both ports show up, and the device is "healthy"
  10. S

    Proxmox PCIE Passthrough Multiple NIC Interfaces

    All of the logs are form the Host at this point. Sorry, just trying to provide as much info as possible. I will check the 4-g, but I don't remember seeing that option.
  11. S

    Proxmox PCIE Passthrough Multiple NIC Interfaces

    can you also post the output of 'lspci -k' ? # lspci -k: 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) Subsystem: Lenovo 4th Gen Core Processor DRAM Controller Kernel driver in use: hsw_uncore 00:01.0 PCI bridge: Intel Corporation Xeon...
  12. S

    Proxmox PCIE Passthrough Multiple NIC Interfaces

    Thanks for your response! It looks like Proxmox is not recognizing the second port of the NIC from what I can tell.