From owner-freebsd-testing@freebsd.org Mon Mar 12 21:33:23 2018 Return-Path: Delivered-To: freebsd-testing@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B00B4F4CC8D for ; Mon, 12 Mar 2018 21:33:23 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C26774925; Mon, 12 Mar 2018 21:33:23 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-it0-x236.google.com with SMTP id w63so13098834ita.3; Mon, 12 Mar 2018 14:33:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=gKCUeGWsfZBYrdmMXB3ZBtPZu+VtzOGVjAguDCdtODg=; b=jQY/MDNhxnCTNfjw+ZHT3+fBdzaNjDhU3gUP3hXvwTKVvfWCvsjZcoS4l3V9bEb2/T qXQCTGTmFKFyDaefpVMPaO6fEHAAdp6LxRGkKuq/Li4VVdQMFCZmP3cGLfa93K2WDhdO fNrorI0qCETym7Uv6NEXgdzNbrgKOU26np9VlIFOeg3slbDTfSMsh0THOM/67ShQVCc1 3eZdHcihiLVNjOQAdOpctnlgu+2hZU15I60nGtjiVeUNbm70ZNAqWnBMTtxz3swZk8+K 03TQ1tgGyDuuv2wSO+ithMe4LMXkiw4UX4R+K1N5t4maFesdaNmkxMCaZWVbqB9j1yR3 SbaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=gKCUeGWsfZBYrdmMXB3ZBtPZu+VtzOGVjAguDCdtODg=; b=J7I/oaExhZjpXIhfXgWUD2h/v6H558X+N45gkWyStpFec8vb2H0F2hOpEWGR19rKsw 8epxW3KxFspMOcXqCNhpXHmd8V2xAkK3X0nRHiJ1TxUiVqSITk/XhjB9Iggoypo0WML1 homOi3sfWyjrtakWIq/Mwy0ni0c+T+dot4hEjWwcPdfEzwxxaTune6A5lUUrOc3k/Wxm T05PA249kKreTpbNoaJahvQsnkwvlW692KvPFBOPry+R1o32SM2csBWjToV6JNWuEW4c 4liLT50kMmTH7BAb4iBrne0mMX3CSDT+oSZQoO08trYnY4hhwvExD0pqbD32SRuIXMCt AD5Q== X-Gm-Message-State: AElRT7FXAhH6SfOr1gFco08NaYjiSFYo6S9YPLYXwWUplkhPDrZnzgy7 sLJc6vY8VYaghmNfhotcNV9BJw== X-Google-Smtp-Source: AG47ELuiDP3yWgcGAFphpeSDL7+Nb0kEdWQy/AzaDHlkmmzcEd7nE+pPJygudiWMpvU2M3gRo4xQBg== X-Received: by 10.36.79.12 with SMTP id c12mr10312159itb.37.1520890402156; Mon, 12 Mar 2018 14:33:22 -0700 (PDT) Received: from raichu (toroon0560w-lp130-01-174-88-76-226.dsl.bell.ca. [174.88.76.226]) by smtp.gmail.com with ESMTPSA id 195sm4169215itm.13.2018.03.12.14.33.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Mar 2018 14:33:21 -0700 (PDT) Sender: Mark Johnston Date: Mon, 12 Mar 2018 17:33:19 -0400 From: Mark Johnston To: Alan Somers Cc: "freebsd-testing@freebsd.org" Subject: Re: automatically provisioning a bhyve test VM Message-ID: <20180312213319.GB97195@raichu> References: <20180312154346.GA97195@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2018 21:33:23 -0000 On Mon, Mar 12, 2018 at 02:57:32PM -0600, Alan Somers wrote: > On Mon, Mar 12, 2018 at 9:43 AM, Mark Johnston wrote: > > > Hi, > > > > I have some tests for FreeBSD's kernel dump code that I'd like to make > > more robust. They use bhyve to test a variety of combinations of kernel > > dump configurations: e.g., full dump vs. minidump, encryption, > > compression, dump device block size, etc.. Each test triggers a kernel > > panic and dump, and upon reboot opens the dump in kgdb, in the VM, to > > get some confidence that the dump is valid. > > > > I use sysutils/vm-bhyve to simplify some aspects of VM management, and > > that works pretty well. I use some hacks to configure networking for the > > VM, and this is the part that I don't like. The tests run on the host > > and use ssh to run commands in the VM. For this to work, I need to > > hardcode an IP for the guest and for the bridge to which the guest's tap > > interface is connected, which of course only works if those IPs aren't > > already somehow in use by the host. I'd prefer something that makes zero > > assumptions about the host and just provides the bare minimum needed to > > establish a private communication channel to run commands on the guest > > (which includes getting the output and exit status of said commands). > > Ideally this would still involve assigning private IPv4 addresses to > > each side since I'd like to expand my test suite to cover netdump, which > > makes it possible for a panicking kernel to transmit a dump to a remote > > host. Does anyone have any suggestions for a more elegant way to go > > about this? Does anyone else automatically provision and tear down bhyve > > VMs as part of a test suite? > > _______________________________________________ > > freebsd-testing@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-testing > > To unsubscribe, send any mail to "freebsd-testing-unsubscribe@freebsd.org" > > > > Could you use the virtual serial port instead of a virtual network? That > would eliminate the assumption about a suitable IP address for the guest. Is there an easy way to programmatically run commands over that serial port from the host? > You could also try using an IPv6-only guest with a link-local address. > Thanks to IPv6's scoping rules, this would be guaranteed not to interfere > with any other interface on the host, so long as you don't bridge it. I'd thought a bit about this, but there's also a discoverability problem in that I'd need a way for the host to figure out the guest's link-local address without talking to the guest. The serial port might let me work around this though.