Search results

  1. DynFi User

    I can't start LXC

    Hello, and thanks for the feedback. This pool has been setup with Proxmox 4, when we have started to use Proxmox. We have been leaving with it long time ago. The problem seems to be tied to the existence of the /dev/ directory as described by someone on this thread. I have "recreated the...
  2. DynFi User

    I can't start LXC

    Going into each mounted directory, removing the "dev" directory in it and remounting with "zfs mount" did temporarily solve my issue. But this is really a deviated solution, not something one would like to do at every reboot… Looks like we all have in common to have more than one zpool...
  3. DynFi User

    I can't start LXC

    Can the proxmox team provide an answer to this problem which seems to impact many persons. Running : pve-manager/5.4-13/aee6f0ec (running kernel: 4.15.18-21-pve) In my case I have 15 containers running on a server. I have deployed a new container yesterday (Ubuntu 18) I have stopped a...
  4. DynFi User

    [SOLVED] Failure to load disk at boot (FreeBSD)

    I'd love to mark It as solved, but I don't know where to do that !
  5. DynFi User

    [SOLVED] Failure to load disk at boot (FreeBSD)

    Sometimes you get a bit stupid… I specified 32 in the RAM for the VM… Instead of 32768 (32Go). Of course even booting was difficult. Message is a bit cryptic though !
  6. DynFi User

    [SOLVED] Failure to load disk at boot (FreeBSD)

    I am trying to boot a compilation environment that we have and which was behaving quite well until we reached this problem… It simply refuses to boot ! The disk is located on an NFS v.4 mount (as all our disks). We have had no particular problem until this failure…...
  7. DynFi User

    Routing inside LXC container (Ubuntu 18)

    Nice suggestion too ! Do you have any pointer for template creation ?
  8. DynFi User

    Routing inside LXC container (Ubuntu 18)

    Ok so here is how to proceed : You need to create a file in the container called ".pve-ignore.hosts" file should be located in "/etc/" so "/etc/.pve-ignore.hosts" This will let the system know NOT to rewrite on boot any modification operated in the "/etc/systemd/network/" Then you need to...
  9. DynFi User

    Routing inside LXC container (Ubuntu 18)

    Nobody has answer to this ?
  10. DynFi User

    Routing inside LXC container (Ubuntu 18)

    While this seems to be interesting : https://wiki.archlinux.org/index.php/Systemd-networkd#Configuration_examples I still would like to know what is the advised way to handle custom networking configuration in Proxmox Containers ? This can be done at many different level including...
  11. DynFi User

    Routing inside LXC container (Ubuntu 18)

    We are migrating container from Ubuntu 14 to Ubuntu 18. We have a configuration with routing inside the container (in /etc/network/interfaces) : auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 23.51.52.24 netmask 255.255.255.240 gateway 23.51.52.1 auto...
  12. DynFi User

    Proxmox on SuperMicro / AMD EPYC 7501

    Hello, I am about to spend a quite important amount of money on a new Proxmox server which will be mainly used for big time compilation and other KVM / LXC hosting. Hardware is SuperMicro AS-1113S-WN10RT + AMD 7501 w32 cores https://www.supermicro.com/Aplus/system/1U/1113/AS-1113S-WN10RT.cfm...
  13. DynFi User

    Slow perf: removing zfs intent log and l2arc

    We have a Proxmox install where everything is up and running and up to date (5.2.5)… but with ridiculously slow performances (write) on the disks. For a dual socket with 256GB of RAM and SAS 10K disks this is really bad… System has been formated with two SSD (Mirror) for the system on...
  14. DynFi User

    Moving ZFS based LXC containers

    Hello, We are trying to move LXC containers from one host to another. We have more than one zfs mount point on the target system : root@proxmonster:/home/xxxx# zfs list NAME USED AVAIL REFER MOUNTPOINT monster 640G 2.54T 192K /monster monster/data 639G 2.54T 208K /monster/data...
  15. DynFi User

    IGMP multicast issues after upgrade 4.3 > 4.4

    That being said, I would be interested to know why this seems to happen after the reboot and upgrade of the system from 4.3 to 4.4 ? What is the root cause of this IGMP problem ? Because we didn't notice such problem before the update.
  16. DynFi User

    IGMP multicast issues after upgrade 4.3 > 4.4

    Ok this is where we were heading toward. Thanks for your confirmation. Will post the detailed conf of our HP switch once It is done.
  17. DynFi User

    IGMP multicast issues after upgrade 4.3 > 4.4

    Hi all, We are having some strange issues with IGMP. We have a three cluster node running v.4.4 (latest stable) The Cluster is working and we have managed to have everything running. Server indicates that : Cluster: pmox-osnet, Quorate: Yes. Problem is that we have experienced a very...
  18. DynFi User

    Backup naming policy

    Well, It would be simpler to just migrate all backup to this improved version. The suggestion of adding a ticker to include the name of the VM is nice and shouldn't break anything but older backups. From my point of view (and obviously others) - It is better to move on with something better...
  19. DynFi User

    Backup naming policy

    Hello, It is really very very annoying (to say the least) to have Containers and VM backed up without having the name of the container in the prefix of the backup. There is nothing more similar than : vzdump-lxc-125-2016_12_13-15_43_49.tar.lzo Than the same backup that you will do couple...