From owner-freebsd-virtualization@freebsd.org Fri Feb 2 17:21:51 2018 Return-Path: Delivered-To: freebsd-virtualization@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 65A92EE5077 for ; Fri, 2 Feb 2018 17:21:51 +0000 (UTC) (envelope-from dave@daverball.com) Received: from mx.daverball.com (mx.daverball.com [212.83.175.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "daverball.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E0F8575A85 for ; Fri, 2 Feb 2018 17:21:49 +0000 (UTC) (envelope-from dave@daverball.com) Received: from mx.daverball.com (localhost [127.0.0.1]) by mx.daverball.com (OpenSMTPD) with ESMTP id 531b9193 for ; Fri, 2 Feb 2018 18:15:07 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=daverball.com; h= mime-version:from:date:message-id:subject:to:content-type; s= default; bh=SYV/IzU6hY5m+hOhxYB0CDjRdVA=; b=DWNz36SO+bo4K094ey0c Kj8O0Brm9ePdZ0hmW5OwwFhKFq32Ru7FbV1KkZZ3bLnEZgOAiqMHQovHX86RtFGv H2v3sNjq81WSf/naI1q/5dqpABZK00E3rmwZOsL2AHXFU7FpalrFsRBmCCBEsXSU 4uVliE2zqdMzz3WXJeJmK5zhrdDEwf97U9B0a7s6NjfS9Xwr3Awg9776RqwXv3Yl j3HZ2wu7bOTEe9qWdgXuOW4No2z7kDhjhgH8rNHHdeuGwy+o14Mo3QZz/+hCuTPU e+jEP2qrrKtNaZvGOnJ3d87EB9pJI2mj0MazIDmfr/42aQvXmqCsFFV5RLNDYOko dQ== DomainKey-Signature: a=rsa-sha1; c=nofws; d=daverball.com; h= mime-version:from:date:message-id:subject:to:content-type; q= dns; s=default; b=m1sGTtUP+prZgHcOVvywtDh15Zo89Kahbk8PqSFe3MzQDw TPBM9YeDqrRIB2lvkPk0bj3IwZPOfW0lMW7OaGHPvvBuvxfDRkBdi3EjcnAjU8ST DUXf3AZpfRCAKq/6mcuqhKq7EaKxOZqVWZNGBBzbg2aiVoLPgFOnx/mBkLz4qs3l nxmEZpXq85x8IijKoCuVH9z3uvPEJOdQZFMF+Nbq7OgwBK9W+an7FzqZLWLXS5P/ 5jW6deNSFCcJ4gWehX+0b595plGz8nTLd6YcGKVTFlZjuhfpETlPaIUDzIeENCqs 4zUG+uLFvWSQaVxCvzEUkXAxtn9++gqQROYIlTpg== Received: from mail-vk0-f46.google.com (mail-vk0-f46.google.com [209.85.213.46]) by mx.daverball.com (OpenSMTPD) with ESMTPSA id 4f400ba8 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO) for ; Fri, 2 Feb 2018 18:15:07 +0100 (CET) Received: by mail-vk0-f46.google.com with SMTP id x203so13887265vkx.10 for ; Fri, 02 Feb 2018 09:15:07 -0800 (PST) X-Gm-Message-State: AKwxytcBP3zXo2tDcdJ+kPxRuL3PLs5lAsvZ7JEoJU0JVJAFqjsrfPeg FFx0OJ4NqK3107QjdySTCwiUqLIlnJ1Ax9EfQw== X-Google-Smtp-Source: AH8x226ssqBphD+piqle4bQG4cO0v9IIq4kgYVu+xr5IOZVuZJrKvfA2va+HlN7SmUG7XOKEVnOEFwCSFJ9DFM4EHIk= X-Received: by 10.31.110.205 with SMTP id j196mr34031654vkc.101.1517591706528; Fri, 02 Feb 2018 09:15:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.3.38 with HTTP; Fri, 2 Feb 2018 09:14:45 -0800 (PST) From: David Salvisberg Date: Fri, 2 Feb 2018 18:14:45 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Xen on FreeBSD 11.1 - Auto creating VMs on boot To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 17:21:51 -0000 Hello, I recently switched from Debian as my Dom0 to FreeBSD to make use of ZFS without having to rely on zfs-on-linux. The experience has been pretty good so far, albeit a bit more limited compared to Debian obviously. One of the things I haven't been able to figure out is /etc/xen/auto or rather /usr/local/etc/xen/auto in FreeBSDs case. It doesn't look like Xen on FreeBSD ships with any of the configuration options for this feature, possibly due to lack of support for save and restore. I don't really need save and restore but auto spawning VMs on boot would be a nice thing to be able to do without having to write my own rc.d script or something along those lines. Is there a way to make use of the auto creation feature on FreeBSD Xen or is that feature just missing entirely due to the lack of save/restore functionality? If there is no builtin way, I'd appreciate any recommendations for writing my own scripts to make sure that they're only being run after Xen has been fully initialized and is ready for xl create commands. Best Regards David Salvisberg