From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 2684571658 for ; Wed, 18 May 2022 17:25:42 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 135E22E7E4 for ; Wed, 18 May 2022 17:25:12 +0200 (CEST) Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 164C32E7DA for ; Wed, 18 May 2022 17:25:11 +0200 (CEST) Received: by mail-ed1-x535.google.com with SMTP id s3so3461309edr.9 for ; Wed, 18 May 2022 08:25:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=8kIgr/zVNCq+BsRsmVTGLAGFsO+fsYuNeJUfEuFVzU8=; b=QPyoerdTXdkleTSlRuUvFAUrpyRIiqk6rFjSM0efn4riGNU37HD88Nmi2IMq7DAjes WOsO1Una/NQjsOpS1Y+4gIxgMKDuVxKzBPquVZaoH2sy5YoIYtqTSNjl9PoeBZPf2D0M wtSXGeO2MUibmjHdkI8YfwaQqEjclgk4CjH0TkE8JUqInHkzWBK4GoDGpprwMMrmk0yU LSJgpJBInuM4k38ZtXuaL/S9+/GLdTPD5wyb6A4Jm4djzBFkqYzXBFQcMijPg89Ye1Al aYB19YZ/345raWDGlp4orkJ5PB7HKsZ2UnKNl9nCU/hRSE65h4JF+0Tjx1KuKeVAE/cJ yqnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=8kIgr/zVNCq+BsRsmVTGLAGFsO+fsYuNeJUfEuFVzU8=; b=t2e6TIKf8gVzgJdQLFxhZ2gkUnkGGZz4f2GJ7AhHlkK51zODrJSzZXdRLk3BYyv8HS OlzkglrG4m1gkT2aRHRiUF+CkhvMzmlJtvt5weS7/gRffIYCSoH/FNjspM1H0uwlVl5a dALXMg6mCRNN8ue0vCx9XYYm8o5sBLTYm3XuwoJ9F7ZqItjTA9xpalgDfm42SGRccECz 9o9dE+tzmPCSoQacEFbKPJRyRrw9RyymEyEjkJxWFGXuyoytWhj/qew6Wfy8IzmfeNNo tjai74nKJ3zKqCsiCOLVETAkzBgXNp4X88lvR0y1ULdxv0Z0sldLx9eCgBY4h60nGxGF cM2g== X-Gm-Message-State: AOAM530GO4zW4GSJIlD3D/fC1c23O1lgG02UnlnOeXBMNSJVtLHZUq1d Fhsat39ZfufOtsroNxZc4EMe/rtU20qxqyklQ+KQvADgTfg= X-Google-Smtp-Source: ABdhPJyo5EhM4fodjdmMwcpgiZt2VTQZ/C72kdQLn19toPXMoheTYtze/Y3DeZxiqTmaVjOlV9Bl2DGNto51EOSUYY0= X-Received: by 2002:a05:6402:cae:b0:42a:ba8f:9d05 with SMTP id cn14-20020a0564020cae00b0042aba8f9d05mr253224edb.277.1652887504579; Wed, 18 May 2022 08:25:04 -0700 (PDT) MIME-Version: 1.0 From: JR Richardson Date: Wed, 18 May 2022 10:24:53 -0500 Message-ID: To: Proxmox VE user list Content-Type: text/plain; charset="UTF-8" X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [PVE-User] VMware SD-WAN Virtual Edge Not Working X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2022 15:25:42 -0000 Hey Folks, We are testing deployment for using VMware/Velo virtual edge appliance on Prox, hypervisor Dell R630 specs: 40 x Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz (2 Sockets) Linux 5.4.174-2-pve #1 SMP PVE 5.4.174-2 (Thu, 10 Mar 2022 15:58:44 +0100) pve-manager/6.4-14/15e2bf61 VMware SD-WAN edge appliance version 4.3.1 latest GA release. We can get the VM started OK and connected to orchestrator except the VPN tunnels are not coming up. We are using 'host' processor type and see all the required CPU Flags available to the VM. We are running a bunch of these virtual edge vms on VMware ESXi hypervisors with no issues, but looking to change over to using Proxmox. The only error we get in orchestration when diagnosing the problem is "Edge dataplane service failed" and there is no vpn traffic coming from the VM so it's like something with the VM is not able to access some resource needed to start VPN services. AES-NI, SSSE3, SSE4, RDTSC, RDSEED, RDRAND instruction sets are all available to the VM. Is anyone else successful deploying VMware SD-WAN appliances with Proxmox/KVM or seeing the same issue I'm having? We're opening a support case with VMware, but no word back from them yet. Thanks. JR