Date: Fri, 23 Feb 2024 19:41:27 +0100 From: Mario Marietto <marietto2008@gmail.com> To: Jo Durchholz <jo@durchholz.org> Cc: "freebsd-virtualization@FreeBSD.org" <freebsd-virtualization@freebsd.org> Subject: Re: Best way to have a FreeBSD VM for automated testing? Message-ID: <CA%2B1FSijjCLn8sxrjMxT_1j2qW3mk4pjvqMBSytCBBpi0tixNkQ@mail.gmail.com> In-Reply-To: <163e57a9-0b61-414c-a8f7-109f5ac90f69@durchholz.org> References: <163e57a9-0b61-414c-a8f7-109f5ac90f69@durchholz.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
To speed up the booting of a bhyve VM I'm using this method :
nohup /usr/sbin/bhyve -S -c sockets=2,cores=2,threads=2 -m 8G -w -H -A \
-s 0,hostbridge \
-s
1,virtio-blk,/mnt/zroot2/zroot2/bhyve/img/Linux/Ubuntu2310.img,bootindex=1
\
-s 11,hda,play=/dev/dsp,rec=/dev/dsp \
-s 13,virtio-net,tap19 \
-s 14,virtio-9p,sharename=/ \
-s 30,xhci,tablet \
-s 31,lpc \
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI_CODE.fd \
vm0:19</dev/null >/dev/null 2>&1 &
if test -f nohup.out; then rm -r nohup.out
fi
I've installed a ssh server within the vm and I connect to it from FreeBSD
using ssh -Y user@IP ; it's faster. But the project is not completed. I
want to install VirGL to have the graphic acceleration without using the
real GPU of the host inside the VM.
On Fri, Feb 23, 2024 at 8:17 PM Jo Durchholz <jo@durchholz.org> wrote:
> Hi all,
>
> I'm in repeatable build land, working in Linux and developing a FreeBSD
> appliance.
>
> For tests, I need to run a FreeBSD VM, put some Python code and test
> data into it, run the script, and get the test results back.
>
> Repeatability means: Everything done with the VM needs to be scriptable
> (using a GUI for exploring is okay but things have to translate).
> Which in turn means that every setup step for a FreeBSD image comes with
> a pretty high coding and maintenance cost.
>
> So my question is:
> What's the FreeBSD image that has the least number of steps to get the
> base system up and running? I suppose it's the VM-IMAGES section, but is
> this correct?
>
> Follow-up question:
> The startup time needs to be as fast as possible. Sub-second would be
> great ("don't disrupt the developer's thought stream").
> I see the boot process from a vanilla VM-IMAGES image takes multiple
> seconds; can this be sped up to just a few seconds, or do I need to run
> the setup and create a VM snapshot at which the VM starts for each test
> run?
>
> Regards,
> Jo
>
>
--
Mario.
[-- Attachment #2 --]
<div dir="ltr"><div><span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">To speed up the booting of a bhyve VM I'm using this method :</span></span></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"><br></span></span></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">nohup /usr/sbin/bhyve -S -c sockets=2,cores=2,threads=2 -m 8G -w -H -A \
</span></span></div><div><span style="font-family:monospace"></span></div><span style="font-family:monospace"><span class="gmail-im">-s 0,hostbridge \
<br>-s 1,virtio-blk,/mnt/zroot2/zroot2/bhyve/img/Linux/Ubuntu2310.img,bootindex=1 \
<br>-s 11,hda,play=/dev/dsp,rec=/dev/dsp \
<br>-s 13,virtio-net,tap19 \
<br>-s 14,virtio-9p,sharename=/ \
<br>-s 30,xhci,tablet \
<br>-s 31,lpc \
<br>-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI_CODE.fd \
<br></span>vm0:19</dev/null >/dev/null 2>&1 &
<br>if test -f nohup.out; then rm -r nohup.out
<br></span><div><span style="font-family:monospace">fi</span></div><div><span style="font-family:monospace"><br></span></div><div><span style="font-family:monospace">I've installed a ssh server within the vm and I connect to it from FreeBSD using ssh -Y user@IP ; it's faster. But the project is not completed. I want to install VirGL to have the graphic acceleration without using the real GPU of the host inside the VM.<br></span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 23, 2024 at 8:17 PM Jo Durchholz <<a href="mailto:jo@durchholz.org">jo@durchholz.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
I'm in repeatable build land, working in Linux and developing a FreeBSD <br>
appliance.<br>
<br>
For tests, I need to run a FreeBSD VM, put some Python code and test <br>
data into it, run the script, and get the test results back.<br>
<br>
Repeatability means: Everything done with the VM needs to be scriptable <br>
(using a GUI for exploring is okay but things have to translate).<br>
Which in turn means that every setup step for a FreeBSD image comes with <br>
a pretty high coding and maintenance cost.<br>
<br>
So my question is:<br>
What's the FreeBSD image that has the least number of steps to get the <br>
base system up and running? I suppose it's the VM-IMAGES section, but is <br>
this correct?<br>
<br>
Follow-up question:<br>
The startup time needs to be as fast as possible. Sub-second would be <br>
great ("don't disrupt the developer's thought stream").<br>
I see the boot process from a vanilla VM-IMAGES image takes multiple <br>
seconds; can this be sped up to just a few seconds, or do I need to run <br>
the setup and create a VM snapshot at which the VM starts for each test run?<br>
<br>
Regards,<br>
Jo<br>
<br>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Mario.<br></div>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B1FSijjCLn8sxrjMxT_1j2qW3mk4pjvqMBSytCBBpi0tixNkQ>