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 4459271703 for ; Wed, 18 May 2022 18:50:21 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 33B5F2F437 for ; Wed, 18 May 2022 18:49:51 +0200 (CEST) Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (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 13AC72F42B for ; Wed, 18 May 2022 18:49:50 +0200 (CEST) Received: by mail-ej1-x62c.google.com with SMTP id ch13so4907101ejb.12 for ; Wed, 18 May 2022 09:49:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=r5r3GuBFqvM4a5wcZwk9iTk9jo3NUc02rdNcjry62ww=; b=EVy1KIaazyOUaMZHiydSapjRUITQGlQCSjW7WckZCyOn9u9ZQD3KKJ+U7DklAcD9m3 S8XqDwzAmn2GKFu999eivyR/BgJS6e2gOs86M9sExs4SwvHOfHBtvRHQUMo+EF4n5o/P 4dkEsqZRNiGihNpvXw936vyTWhnxkjJE2D2Cig9q6LlWS+Gca+51OS1wIaqGpwuNAlEK AghcjEaLWnGWsm2gI0ukG0YzFzSkQVSIx3vZlcI+Z49UeN+XIzTCLTFz5jno0SoTBKBy a/slVcFUADxDhn1z8M0RbFVWtusAb4Ot9pSPLv6zCveVdBP7iC4VzcXQ3CkEzuOuP9zP SvSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=r5r3GuBFqvM4a5wcZwk9iTk9jo3NUc02rdNcjry62ww=; b=4/ZqzyefPVS/cTy/IaD1rjAQP/D70Akwzmw291vAv8U6rl+GvQmJsoFTMlHNO6Qh9X gC8SdTgkAY09Yce+XnCONhd/dU4b6Umr5hrbtEer1snbOnu6plZ2f6bkk0LhnvPFmUPu WXZTiFUie4fiy+9X5jsFz8wWhe9FPSOBzL5wDcDbPqzzRZJxN9FqZfBEC3HI/2v0hDOm o+R6F73BvAp9IOeLqxPZrM79AzCqzt/Cu16PsPBR7oQSpRe/r+x2m2IpEEQPUwrPAgcB Vdwps8D+B3xfhzq2gQiEA20R8AxYPFRF2mC9VkFWWNJxUSyDWhBJ983c1TIuhVe+SS/D yMFA== X-Gm-Message-State: AOAM532GWUgrsc6BCuc1YCRKa0SxwEjtC5JB3fwFwunaKjGxwz8hFVPI IjWbbNctWAKYpe6/p5VHmv42zD66SJK1YDcRUcQ8Ki+3 X-Google-Smtp-Source: ABdhPJwHz6WzRsE32W//3EcKISjRkdIUY9Tp2eR07Pjzl/SyrFHCsK8tJWf+FnSjvCTwefHy8tzG9q2K7ygi9YjD3Iw= X-Received: by 2002:a17:907:1b14:b0:6ef:a5c8:afbd with SMTP id mp20-20020a1709071b1400b006efa5c8afbdmr459819ejc.151.1652892583320; Wed, 18 May 2022 09:49:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: JR Richardson Date: Wed, 18 May 2022 11:49:32 -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: Re: [PVE-User] VMware SD-WAN Virtual Edge Not Working [SOLVED] 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 16:50:21 -0000 Quick update, changed CPU to single socket and multi-core, appliance started acting as expected. Not sure why but when using multi-sockets, even with NUMA enabled, the VM would not fully work. I guess something in the appliance code checks for socket/core configs and requires a single socket only. Hope this helps. Regards. JR On Wed, May 18, 2022 at 10:24 AM JR Richardson wrote: > > 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