Search results

  1. D

    proxmox 7.0 sdn beta test

    Yes I would normally only announce local prefixes from the host which would more likely receive default from the Arista's. We would definitely also filter on the arista's.
  2. D

    proxmox 7.0 sdn beta test

    This would be great. Cool - we are using Arista as well. I don't at this stage, but it would just be a prefix list with the local interfaces I want to announce listed in it.
  3. D

    proxmox 7.0 sdn beta test

    Hey! This is what our initial setup is going to look like. Every device in our network has a unique ASN. Once we've tested fully, every host will be multihomed to at least 2 switches. In an ideal world we would be able to do a type 5 EVPN interface for the management interface. Being able...
  4. D

    proxmox 7.0 sdn beta test

    +1 this is absolutely a requirement for our EVPN implementation as well.
  5. D

    Proxmox 5.0 and nvme

    Sadly mine is not so happy :( root@bruce:~# dmesg |grep -i nvme root@bruce:~#
  6. D

    Proxmox 5.0 and nvme

    Hi Guys, Do I need to install/configure anything special for Proxmox 5.0 to see a PCI NVME disk? I can't see any kernel modules activated for nvme or the actual disk itself. Any hints? root@bruce:~# modinfo nvme modinfo: ERROR: Module nvme not found. root@bruce:~# root@bruce:~# lsmod | grep...
  7. D

    pvestatd.pm - Use of uninitialized value $cost

    I'm running 5.0-9/c7bdd872 on an HP P4500, my logs are currently filling up with the following errors: May 17 10:36:19 bruce pvestatd[4823]: Use of uninitialized value $cost in numeric lt (<) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344. May 17 10:36:19 bruce pvestatd[4823]: Use of...
  8. D

    unregister_netdevice: waiting for lo to become free

    I am seeing this error as well on my host running 5.0-9/c7bdd872
  9. D

    v5.0 beta 1 LXC Problem - "cpu id '16' is out of range"

    Hi, The install is directly installed on an HP P4500 G2, there is no containerisation. The 4.4 version was completely up to date and worked fine prior to the upgrade. I have no idea about the CPU ID's prior to the upgrade but I suspect it may be related to the new version of Debian.
  10. D

    v5.0 beta 1 LXC Problem - "cpu id '16' is out of range"

    Hi Guys, I've just run an upgrade from 4.4 to 5.0-6/669657df using the apt dist-upgrade method. Everything seems to have run properly however LXC containers won't come up, I am getting a "cpu id '16' is out of range" error in the front end and am seeing the following in...
  11. D

    Proxmox VE 5.0 beta1 released!

    Hi Guys, I've just run an upgrade from 4.4 to 5.0-6/669657df using the apt dist-upgrade method. Everything seems to have run properly however LXC containers won't come up, I am getting a "cpu id '16' is out of range" error in the front end and am seeing the following in...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!