<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>netbsd — LowEndSpirit</title>
        <link>https://lowendspirit.com/index.php?p=/</link>
        <pubDate>Tue, 21 Jul 2026 16:30:10 +0000</pubDate>
        <language>en</language>
            <description>netbsd — LowEndSpirit</description>
    <atom:link href="https://lowendspirit.com/index.php?p=/discussions/tagged/netbsd/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Quick Recipe For Self-Compiled NetBSD-current On A Linveo VPS</title>
        <link>https://lowendspirit.com/index.php?p=/discussion/8525/quick-recipe-for-self-compiled-netbsd-current-on-a-linveo-vps</link>
        <pubDate>Wed, 06 Nov 2024 00:56:33 +0000</pubDate>
        <category>LES Talk</category>
        <dc:creator>Not_Oles</dc:creator>
        <guid isPermaLink="false">8525@/index.php?p=/discussions</guid>
        <description><![CDATA[<h2>Quick Recipe For Self-Compiled NetBSD-current On A Linveo VPS</h2>

<p><img src="https://lowendspirit.com/uploads/editor/hy/50xjrfom6n2s.png" alt="" title="" /></p>

<p><a rel="nofollow" href="https://linveo.com">Linveo</a> kindly provided several free VPSes to guys actively posting in the <a rel="nofollow" href="https://lowendspirit.com/discussion/8278/les-bsd-thread/p1">LES BSD Thread.</a> Linveo also kindly added <a href="https://lowendspirit.com/index.php?p=/profile/cmeerw" rel="nofollow">@cmeerw</a>'s NetBSD 10 Minimum image. As shown above, NetBSD 10 Minimum now easily can be installed at Linveo directly from "Other BSD" category on the Rebuild page of vmcontrol.linveo.com.</p>

<p>After installing <a href="https://lowendspirit.com/index.php?p=/profile/cmeerw" rel="nofollow">@cmeerw</a>'s NetBSD 10 Minimum image, with help from the NetBSD Guide references linked below, I followed the steps listed below to upgrade from NetBSD 10 to self-compiled NetBSD-current.</p>

<p>Getting to self-compiled NetBSD-current requires us to add to the NetBSD 10 Minimum VPS a NetBSD 10 compiler, other build tools, and the source code for both the NetBSD-current kernel and the NetBSD-current userland. Then a NetBSD-current compiler and other build tools are compiled by the NetBSD 10 compiler. Next, the newly compiled NetBSD-current build tools are used to build the NetBSD-current kernel and the NetBSD-current userland. The end result is a NetBSD-current VPS running its own code as compiled on itself by its own compiler.</p>

<p>My Linveo VPS seems to reboot and to run normally following the upgrade to NetBSD-current. There seems to be plenty of space remaining available, though the X sources and pkgsrc haven't yet been added:</p>

<pre><code>linveo# df -h .
Filesystem     Size   Used  Avail %Cap Mounted on
/dev/dk2        48G    10G    35G  22% /
linveo# 
</code></pre>

<div>  <p>Installing <code>pkgsrc</code> added 1 G to the usage:</p>

<pre><code>linveo$ CVS_RSH=ssh cvs -danoncvs@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc
  [ . . . ]
linveo$ df -h .
Filesystem     Size   Used  Avail %Cap Mounted on
/dev/dk2        48G    11G    35G  24% /
linveo$ 
</code></pre></div>

<ul>
<li>Issue</li>
</ul>

<p>The biggest issue that I know about with respect to the NetBSD-current upgrade proposed here relates to the <code>etcupdate</code> command, which is the last command in the sequence below.</p>

<p><code>etcupdate</code> is an <code>sh</code> shell script. There also is a man page, which mentions that the idea for <code>etcupdate</code> came from FreeBSD's <code>mergemster</code>.</p>

<p>I need to figure out how to set options making <code>etcupdate</code> faster and easier to run within the limited scope of this single CPU architecture NetBSD-current upgrade. The VPS is not attempting to build the full multi-architecture NetBSD panopoly. Perhaps limiting the <code>etcupdate</code> source directory to my VM's amd64 architecture might help. Perhaps -- as recommended in the man page -- running <code>etcupdate</code> on a <code>tar</code> file instead of directly on the sources also might help.</p>

<ul>
<li>NetBSD 10 Image</li>
</ul>

<p>Here are links to <a href="https://lowendspirit.com/index.php?p=/profile/cmeerw" rel="nofollow">@cmeerw</a>'s NetBSD 10 image and to a discussion of how the image was made:</p>

<p><a href="https://lowendspirit.com/discussion/comment/187386/#Comment_187386" rel="nofollow">https://lowendspirit.com/discussion/comment/187386/#Comment_187386</a><br />
<a href="https://lowendspirit.com/discussion/comment/187452/#Comment_187452" rel="nofollow">https://lowendspirit.com/discussion/comment/187452/#Comment_187452</a></p>

<ul>
<li>NetBSD Guide Reference Links</li>
</ul>

<p>Here are reference links to the very helpful NetBSD Guide:</p>

<p><a href="https://www.netbsd.org/docs/guide/en/chap-fetch.html#chap-fetch-cvs-netbsd-release" rel="nofollow">https://www.netbsd.org/docs/guide/en/chap-fetch.html#chap-fetch-cvs-netbsd-release</a><br />
<a href="https://www.netbsd.org/docs/guide/en/chap-updating.html" rel="nofollow">https://www.netbsd.org/docs/guide/en/chap-updating.html</a></p>

<ul>
<li>Adding Compilers To The NetBSD 10 Image</li>
</ul>

<p>Here is the LES comment where <a href="https://lowendspirit.com/index.php?p=/profile/cmeerw" rel="nofollow">@cmeerw</a> showed us the one line command used below to add NetBSD 10 compilers to the NetBSD 10 base image:</p>

<p><a href="https://lowendspirit.com/discussion/comment/186774/#Comment_186774" rel="nofollow">https://lowendspirit.com/discussion/comment/186774/#Comment_186774</a></p>

<ul>
<li>Recipe</li>
</ul>

<p>Here are the steps I followed to convert a clean, new Linveo VPS install of <a href="https://lowendspirit.com/index.php?p=/profile/cmeerw" rel="nofollow">@cmeerw</a>'s NetBSD 10 image to what seems to be self-compiled NetBSD-current:</p>

<ul>
<li>Run as root to install a compiler, create needed directories, and an unprivileged user</li>
</ul>

<pre><code>ftp -o - https://cdn.netbsd.org/pub/NetBSD/NetBSD-10.0/amd64/binary/sets/comp.tar.xz | progress -z tar xpf - -C /
cd /usr
mkdir obj src tools
mkdir /home
useradd -m -G wheel tom
passwd tom
chown tom obj src tools
su tom 
</code></pre>

<ul>
<li>Run as the unprivileged user which owns the <code>obj</code>, <code>src</code>, and <code>tools</code> subdirectories</li>
</ul>

<pre><code>export CVSROOT="anoncvs@anoncvs.NetBSD.org:/cvsroot"
export CVS_RSH="ssh"
cvs checkout -A -P src
cd src
less UPDATING
./build.sh -j 2 -O ../obj -T ../tools -U distribution
./build.sh -j 2 -O ../obj -T ../tools -U kernel=GENERIC
</code></pre>

<ul>
<li>Back to root to install and reboot to use our newly compiled NetBSD-current kernel</li>
</ul>

<pre><code>mv /netbsd /netbsd.old
mv /usr/obj/sys/arch/amd64/compile/GENERIC/netbsd /
shutdown -r now
</code></pre>

<ul>
<li>As root, install and reboot to run the newly compiled NetBSD-current userland</li>
</ul>

<pre><code>cd /usr/src
./build.sh -j 2 -O ../obj -T ../tools -U install=/
shutdown -r now
</code></pre>

<ul>
<li>As root, <code>postinstall</code></li>
</ul>

<pre><code>/usr/sbin/postinstall -s /usr/src check
/usr/sbin/postinstall -s /usr/src fix
</code></pre>

<ul>
<li>As root, <code>etcupdate</code></li>
</ul>

<pre><code>/usr/sbin/etcupdate -s /usr/src
</code></pre>

<p>Please point out any mistakes.</p>

<p>Any questions, please ask.</p>

<p>Thanks <a href="https://lowendspirit.com/index.php?p=/profile/linveo" rel="nofollow">@linveo</a> for the nice VPS! Thanks <a href="https://lowendspirit.com/index.php?p=/profile/cmeerw" rel="nofollow">@cmeerw</a> for the NetBSD 10 Minimum image! Thanks to the <a rel="nofollow" href="https://NetBSD.org">NetBSD project!</a> And thanks to LES!</p>
]]>
        </description>
    </item>
    <item>
        <title>&quot;Invalid file offset&quot; Error Installing NetBSD With IPMI On A Crunchbits Dedicated Server</title>
        <link>https://lowendspirit.com/index.php?p=/discussion/7023/invalid-file-offset-error-installing-netbsd-with-ipmi-on-a-crunchbits-dedicated-server</link>
        <pubDate>Mon, 18 Dec 2023 06:00:27 +0000</pubDate>
        <category>Help</category>
        <dc:creator>Not_Oles</dc:creator>
        <guid isPermaLink="false">7023@/index.php?p=/discussions</guid>
        <description><![CDATA[<h2>Introduction</h2>

<p>I failed to install <a rel="nofollow" href="https://netbsd.org">NetBSD</a> on crunchy, my dedicated <a rel="nofollow" href="https://crunchbits.com/">crunchbits</a> server. The IPMI install setup seems successfully to get started installing from a known-working Ubuntu 22.04 ISO, but the NetBSD ISO errors out. The NetBSD errors are "invalid file offset" and "No such file or directory." The NetBSD errors can be seen in the last of the screenshots below.</p>

<p>The "Invalid file offset" error and the CDROM format are discussed at <a href="https://mail-index.netbsd.org/netbsd-bugs/2018/08/16/msg058532.html" rel="nofollow">https://mail-index.netbsd.org/netbsd-bugs/2018/08/16/msg058532.html</a>. Maybe "invalid file offset" means that no files could be read. In other words, maybe the "invalid file offset" error explains all the "No such file or directory" errors.</p>

<p>The problem might be with the NetBSD ISO. I'm sure crunchbits checked the SHA512 sum. And, happily, as also shown in the screenshots below, the NetBSD boot seems to begin okay prior to erroring repeatedly. But, maybe I chose the wrong ISO? Is there something about my IPMI boot setup, detailed below, that interferes with NetBSD but works with Ubuntu? What else could be wrong?</p>

<p>Here are the steps I followed.</p>

<h2>Step 1 -- Ticket #DVO-787826 - Please add NetBSD ISO to crunchbits lineup</h2>

<p>Thanks to crunchbits <img src="https://lowendspirit.com/plugins/emojiextender/emoji/twitter/heart.png" title="&lt;3" alt="&lt;3" height="18" /> for uploading the NetBSD ISO!</p>

<p><img src="https://lowendspirit.com/uploads/editor/qw/n829fg5phf55.png" alt="" title="" /></p>

<p><img src="https://lowendspirit.com/uploads/editor/i2/5rh3upp6t1le.png" alt="" title="" /></p>

<h2>Step 2 -- Launch The Console</h2>

<p>Log in to the <a rel="nofollow" href="https://metal.crunchbits.com/servers">Crunchbits Server Management Panel.</a> Click on Servers &gt; Servername &gt; Our Servername.</p>

<p><img src="https://lowendspirit.com/uploads/editor/ae/e145pzrhlvln.jpeg" alt="" title="" /></p>

<p>In the server's Management Panel, click CONSOLE.</p>

<p><img src="https://lowendspirit.com/uploads/editor/y7/t0od97mwzhaq.jpeg" alt="" title="" /></p>

<p>We see a pop-up telling us that the Console will be available in a moment. A new tab opens showing the Console loading. Next, the newly loaded Console shows our server's login prompt.</p>

<p><img src="https://lowendspirit.com/uploads/editor/hc/0636dxvxvqpg.png" alt="" title="" /></p>

<p><img src="https://lowendspirit.com/uploads/editor/0k/jxr8a6evszjr.png" alt="" title="" /></p>

<h2>Step 3 -- Set Console Window Auto-resize Preference</h2>

<p>Here, our console window is displaced toward the right and toward the bottom of the screen. This happens because of the IPMI auto-resize feature. To disable auto-resize, in the console top menu bar, click Options &gt; Preference. In the Preference window pop-up, select Window. Uncheck "Auto-resize window" and then click OK.</p>

<p><img src="https://lowendspirit.com/uploads/editor/73/c7hd1dmkge46.png" alt="" title="" /></p>

<p>After disabling auto-resize, we see the Console window appearing approximately as expected.</p>

<p><img src="https://lowendspirit.com/uploads/editor/qv/04c23s9w1vrj.png" alt="" title="" /></p>

<h2>Step 4 -- Load netbsd.iso Image</h2>

<p>On the Console top bar menu, the first item on the left is Virtual Media. Click Virtual Media.</p>

<p><img src="https://lowendspirit.com/uploads/editor/34/9gprt93lh1hb.png" alt="" title="" /></p>

<p>Then select Virtual Storage.</p>

<p><img src="https://lowendspirit.com/uploads/editor/bf/nggyqu8jfmpj.png" alt="" title="" /></p>

<p>In the Virtual Storage dialog window, select ISO as the Logical Drive Type. Then, still in the Virtual Storage Dialogue window, we click on Open ISO (this choice shows as "Open I . . .").</p>

<p>A new "Open" dialog window appears. This window shows just one choice, ISOs. So, double click ISOs. Then we can see inside the ISOs folder. Find and select the netbsd.iso. Click the Open button.</p>

<p><img src="https://lowendspirit.com/uploads/editor/f7/tpsfwdx7farf.png" alt="" title="" /></p>

<p>Now we are back in the Virtual Storage dialog. The NetBSD ISO appears greyed out as /var/www/ISOs/netbsd.iso in the "Image Full Name and Full Path" box. It might be hard to see this in the screenshot.</p>

<p>Finally we click the "Plug in" button to connect the ISO file to the virtual CDROM. After we click "Plug in," we see "Device1 :VM Plug-in OK!!"</p>

<p><img src="https://lowendspirit.com/uploads/editor/7u/207o9jxl5nhl.png" alt="" title="" /></p>

<p>Click the OK button to close the Virtual Storage dialogue.</p>

<h2>Step 5 -- Open the Virtual Keyboard</h2>

<p>Here, from Chrome Browser on my daily driver Duet 5 Chromebook, it seemed that the next few upcoming steps did not work with my Chromebook's emulated function keys. Thus. I opened the IPMI's Virtual Keyboard.</p>

<p>In the Console top bar menu, click Virtual Media. Then click Virtual Keyboard. The keyboard shows in the Console Window.</p>

<p><img src="https://lowendspirit.com/uploads/editor/8t/l3qv182e1p6a.png" alt="" title="" /><br />
<img src="https://lowendspirit.com/uploads/editor/g9/i3zbaed4gte0.png" alt="" title="" /></p>

<h2>Step 6 -- Set BIOS Options To Permit Booting From CDROM</h2>

<p>Our crunchbits server was delivered with her BIOS set to LEGACY. We need to reset the BIOS in order to work with an ISO image. If we later resume using the crunchbits auto-installed images, we need to revert our changes to the BIOS. So, let's launch the BIOS Setup and make a record of the initial settings where we started.</p>

<p>Of the various methods for getting into the BIOS, what worked here was to launch the virtual keyboard and spam the F11 virtual key during the reboot process.</p>

<p>To reboot the server, choose Macro in the top menu bar of the Console window. Then, choose Macro again and Ctrl+Alt+Del in the submenu. The big CTRL + ALT + DEL button in the upper right of the Console didn't seem to work for me, regardless of whether the Virtual Keyboard was open or closed.</p>

<p><img src="https://lowendspirit.com/uploads/editor/qt/zrufeu4uh9az.png" alt="" title="" /></p>

<p>During the reboot, spamming the Virtual F11 key while the display keeps changing, brings us to the "Please select boot device:" menu. Here, we select Setup to enter the BIOS.</p>

<p><img src="https://lowendspirit.com/uploads/editor/ya/kxg8m5scrf05.png" alt="" title="" /></p>

<p>In the BIOS, use the Virtual right arrow key to move five steps from left to right across the top level Setup Utility menu from Main to Boot. Here we can see the boot sequence settings as our server was delivered by crunchbits. Again, we need to remember these settings if we decide to revert to using the crunchbits auto-installer. Again, note that the boot method originally selected is LEGACY.</p>

<p><img src="https://lowendspirit.com/uploads/editor/zl/ri30fjtx0pma.png" alt="" title="" /></p>

<p>It would seem that Legacy BIOS boot mode should work for most ISOs. However, here, it seems necessary to change the boot mode to UEFI and also to position CDROM ahead of the Micron hard drives in our server.  So, we use the virtual "+" key to change Boot Mode Select to UEFI.</p>

<p>Here, the single change in the boot mode automatically also changed the boot sequence to UEFI USB CD/DVD:U . . . + UEFI CD/DVD + UEFI Hard Disk.</p>

<p><img src="https://lowendspirit.com/uploads/editor/zu/j5g2m7b869x6.png" alt="" title="" /></p>

<p>Save and exit with the Virtual F4 key followed by the Virtual Enter key to select Yes.</p>

<p><img src="https://lowendspirit.com/uploads/editor/r7/qmqrpzu7t5xs.png" alt="" title="" /></p>

<p>The boot sequence continues, and we see NetBSD beginning to boot.</p>

<p><img src="https://lowendspirit.com/uploads/editor/h3/uqrzdxukf0cf.png" alt="" title="" /></p>

<p>But . . . there seems to be an issue! I closed the Virtual Keyboard so it wouldn't block reading the error messages.</p>

<p><img src="https://lowendspirit.com/uploads/editor/v4/xrzvwj3bp7me.png" alt="" title="" /></p>

<h2>Step 7 -- Test With Known-Working Ubuntu ISO</h2>

<p>I switched to the Ubuntu 22.04 ISO and tried that. Like NetBSD, the Ubuntu ISO began booting. It took awhile, but the Ubuntu ISO successfully got all the way through booting and beginning the install process.</p>

<p><img src="https://lowendspirit.com/uploads/editor/o5/gvxo1kv3ch7r.png" alt="" title="" /></p>

<p><img src="https://lowendspirit.com/uploads/editor/k6/esd6u4xhte5j.png" alt="" title="" /></p>

<p><img src="https://lowendspirit.com/uploads/editor/03/20wi900vnbf4.png" alt="" title="" /></p>

<p><img src="https://lowendspirit.com/uploads/editor/lb/oyn7hpandfru.png" alt="" title="" /></p>

<h2>Step 8 -- Re-try NetBSD</h2>

<p>I re-tried NetBSD, but saw the same issue as before. <img src="https://lowendspirit.com/plugins/emojiextender/emoji/twitter/smile.png" title=":)" alt=":)" height="18" /></p>

<p><img src="https://lowendspirit.com/uploads/editor/gz/vwingfr3jraz.png" alt="" title="" /></p>

<h2>Step 9 -- Try Booting From NetBSD ISO With Legacy Mode</h2>

<p>I tried the NetBSD ISO after changing the BIOS back to LEGACY and the boot sequence to Network + CD/DVD + Hard Disk.</p>

<p><img src="https://lowendspirit.com/uploads/editor/71/7fta49a3zn42.png" alt="" title="" /></p>

<p>The result was that crunchy booted back into her current Fedora Rawhide installation on the hard disks. In other words, apparently neither the network boot nor the hoped for CDROM boot worked with LEGACY.</p>

<p><img src="https://lowendspirit.com/uploads/editor/iu/nwl69wtyp3au.png" alt="" title="" /></p>

<p>I double checked to make sure the netbsd.iso was selected and plugged in.</p>

<p><img src="https://lowendspirit.com/uploads/editor/47/mm562ddgmzzj.png" alt="" title="" /></p>

<h2>Conclusion -- Help Request</h2>

<p>Happily, all the IPMI shennanigans didn't hurt the existing install. Nevertheless, the hoped for NetBSD install failed.</p>

<p>Can some kind person please help me figure out what was going wrong with the NetBSD install?</p>

<p>Thanks so much! <img src="https://lowendspirit.com/plugins/emojiextender/emoji/twitter/smile.png" title=":)" alt=":)" height="18" /></p>
]]>
        </description>
    </item>
    <item>
        <title>Has anybody here run *BSD as a virtualization host?</title>
        <link>https://lowendspirit.com/index.php?p=/discussion/5261/has-anybody-here-run-bsd-as-a-virtualization-host</link>
        <pubDate>Sun, 15 Jan 2023 04:21:45 +0000</pubDate>
        <category>Help</category>
        <dc:creator>Not_Oles</dc:creator>
        <guid isPermaLink="false">5261@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>FreeBSD has bhyve as a virtualization host. I was just reading "23.6.3. Creating a Linux® Guest" at <a href="https://docs.freebsd.org/en/books/handbook/virtualization/" rel="nofollow">https://docs.freebsd.org/en/books/handbook/virtualization/</a> and I wonder, has anybody here tried a *BSD virtualization host? Thanks! <img src="https://lowendspirit.com/plugins/emojiextender/emoji/twitter/smile.png" title=":)" alt=":)" height="18" /></p>
]]>
        </description>
    </item>
    <item>
        <title>NetBSD Not Quite Installed On Hetzner EX101</title>
        <link>https://lowendspirit.com/index.php?p=/discussion/5928/netbsd-not-quite-installed-on-hetzner-ex101</link>
        <pubDate>Wed, 17 May 2023 01:46:49 +0000</pubDate>
        <category>Technical</category>
        <dc:creator>Not_Oles</dc:creator>
        <guid isPermaLink="false">5928@/index.php?p=/discussions</guid>
        <description><![CDATA[<p><a rel="nofollow" href="https://netbsd.org/">NetBSD</a> has a <a rel="nofollow" href="http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/202305131120Z/amd64/installation/cdrom/">serial, non-video installer</a> which seems to work with qemu inside tmux inside Hetzner's rescue system:</p>

<pre><code>root@rescue ~ # cat start-install 
qemu-system-x86_64 \
    -enable-kvm \
    -nographic \
    -cpu host \
    -boot once=d \
    -cdrom ./boot-com.iso \
    -m 4096 \
    -drive file=/dev/nvme0n1,format=raw,media=disk,if=virtio \
    -drive file=/dev/nvme1n1,format=raw,media=disk,if=virtio 
root@rescue ~ # 
</code></pre>

<p>One downloads from the above linked page the SHA512 file and the boot-com.iso file, checks the SHA512, and runs something like the above qemu-command. A prerequisite might be having used Hetzner installimage to put a non-RAID install on the server so that the rescue system's qemu will see /dev/nvme* devices instead of /dev/md*.</p>

<p>After running through the install sequence and rebooting inside qemu inside tmux, the system seemed to come up from the NVMe drive.</p>

<p>After <code>shutdown -h now</code> inside NetBSD and then Ctrl-b, x, y to get out of tmux and then rebooting to get out of the Hetzner Rescue System, the server seemed to come up! It responded to IPv4 ping, but <code>ssh root@fsn.metalvps.com</code> gave me <code>ssh: connect to host fsn.metalvps.com port 22: Network is unreachable</code>.</p>

<p>Re-enabling the Hetzner rescue system and restarting qemu, NetBSD booted again from the NVMe disk (same qemu command as above, but with the following two lines removed).</p>

<pre><code>     -boot once=d \
    -cdrom ./boot-com.iso \
</code></pre>

<p>Eventually I may figure out why the live, booted-from-metal server could respond to ping but ssh wouldn't work. It's been more than 20 years since I last used NetBSD, so I've forgotten everything. <img src="https://lowendspirit.com/plugins/emojiextender/emoji/twitter/smile.png" title=":)" alt=":)" height="18" /></p>

<p>Why didn't I use Hetzner's <a rel="nofollow" href="https://docs.hetzner.com/robot/dedicated-server/maintainance/kvm-console/">free KVM console</a> option? Well, if qemu works, I don't have to bother Hetzner's support guys to have them attach and then remove the KVM.</p>

<p>Thanks to the <a rel="nofollow" href="https://depenguin.me/">depenguin.me guys</a> for helpful hints.</p>

<p>Here's <code>ps aux</code> output from the rebooted server running inside qemu. Notice that there are fewer processes than contemporary Linux.</p>

<pre><code>fsn# date -u; ps aux
Tue May 16 23:57:19 UTC 2023
USER     PID %CPU %MEM   VSZ   RSS TTY   STAT STARTED    TIME COMMAND
root       0  0.0  0.8     0 33688 ?     DKl  11:30PM 0:00.32 [system]
root       1  0.0  0.0 11944  1660 ?     Is   11:30PM 0:00.00 init 
postfix  328  0.0  0.1 21456  4900 ?     I    11:30PM 0:00.01 pickup -l -t unix
postfix  329  0.0  0.1 21504  4968 ?     I    11:30PM 0:00.00 qmgr -l -t unix -
root     331  0.0  0.0 13360  1488 ?     Is   11:30PM 0:00.00 /usr/sbin/inetd -
root     339  0.0  0.0 12212  1740 ?     Is   11:30PM 0:00.00 /usr/sbin/cron 
root     351  0.0  0.1 18408  2676 ?     S    11:30PM 0:00.03 ntpd: asynchronou
root     829  0.0  0.1 18036  2476 ?     Ss   11:30PM 0:00.03 /usr/sbin/syslogd
root    1313  0.0  0.0 11768  1416 ?     Is   11:30PM 0:00.00 /usr/sbin/powerd 
root    1442  0.0  0.4 18272 17824 ?     Ss   11:30PM 0:00.14 /usr/sbin/ntpd -p
root    1532  0.0  0.1 23044  3200 ?     Is   11:30PM 0:00.00 sshd: /usr/sbin/s
root    1821  0.0  0.1 21528  2876 ?     Is   11:30PM 0:00.01 /usr/libexec/post
root     306  0.0  0.0 12076  1720 tty00 O+   11:57PM 0:00.00 ps -aux 
root     335  0.0  0.1 12584  2228 tty00 S    11:31PM 0:00.07 -sh 
root     347  0.0  0.3 24872 10492 tty00 Is   11:30PM 0:00.09 login 
root     348  0.0  0.0 11860  1684 ttyE1 Is+  11:30PM 0:00.00 /usr/libexec/gett
root    2013  0.0  0.0 11856  1684 ttyE2 Is+  11:30PM 0:00.00 /usr/libexec/gett
root    1118  0.0  0.0 11856  1680 ttyE3 Is+  11:30PM 0:00.00 /usr/libexec/gett
fsn# 
</code></pre>

<p>Here's <code>dmesg</code> output from the rebooted server running inside qemu.</p>

<pre><code>fsn# dmesg | cat -n                                                                                                                                        
     1  [     1.000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003,                                                                      
     2  [     1.000000]     2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013,                                                                    
     3  [     1.000000]     2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023                                                                     
     4  [     1.000000]     The NetBSD Foundation, Inc.  All rights reserved.                                                                              
     5  [     1.000000] Copyright (c) 1982, 1986, 1989, 1991, 1993                                                                                         
     6  [     1.000000]     The Regents of the University of California.  All rights reserved.                                                             
     7                                                                                                                                                     
     8  [     1.000000] NetBSD 10.99.4 (GENERIC) #0: Sat May 13 11:19:19 UTC 2023                                                                          
     9  [     1.000000]         mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/amd64/compile/GENERIC                                                         
    10  [     1.000000] total memory = 4095 MB                                                                                                             
    11  [     1.000000] avail memory = 3935 MB                                                                                                             
    12  [     1.000000] timecounter: Timecounters tick every 10.000 msec                                                                                   
    13  [     1.000000] Kernelized RAIDframe activated                                                                                                     
    14  [     1.000000] timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100                                                                  
    15  [     1.000004] mainbus0 (root)                                                                                                                    
    16  [     1.000004] ACPI: RSDP 0x00000000000F5AF0 000014 (v00 BOCHS )                                                                                  
    17  [     1.000004] ACPI: RSDT 0x00000000BFFE1550 000034 (v01 BOCHS  BXPCRSDT 00000001 BXPC 00000001)                                                  
    18  [     1.000004] ACPI: FACP 0x00000000BFFE1404 000074 (v01 BOCHS  BXPCFACP 00000001 BXPC 00000001)                                                  
    19  [     1.000004] ACPI: DSDT 0x00000000BFFE0040 0013C4 (v01 BOCHS  BXPCDSDT 00000001 BXPC 00000001)                                                  
    20  [     1.000004] ACPI: FACS 0x00000000BFFE0000 000040                                                                                               
    21  [     1.000004] ACPI: APIC 0x00000000BFFE1478 000078 (v01 BOCHS  BXPCAPIC 00000001 BXPC 00000001)                                                  
    22  [     1.000004] ACPI: HPET 0x00000000BFFE14F0 000038 (v01 BOCHS  BXPCHPET 00000001 BXPC 00000001)                                                  
    23  [     1.000004] ACPI: WAET 0x00000000BFFE1528 000028 (v01 BOCHS  BXPCWAET 00000001 BXPC 00000001)                                                  
    24  [     1.000004] ACPI: 1 ACPI AML tables successfully acquired and loaded                                                                           
    25  [     1.000004] ioapic0 at mainbus0 apid 0: pa 0xfec00000, version 0x11, 24 pins                                                                   
    26  [     1.000004] cpu0 at mainbus0 apid 0                                                                                                            
    27  [     1.000004] cpu0: Use lfence to serialize rdtsc                                                                                                
    28  [     1.000004] cpu0: 13th Gen Intel(R) Core(TM) i9-13900, id 0xb0671
    29  [     1.000004] cpu0: node 0, package 0, core 0, smt 0
    30  [     1.000004] acpi0 at mainbus0: Intel ACPICA 20221020
    31  [     1.000004] acpi0: X/RSDT: OemId &lt;BOCHS ,BXPCRSDT,00000001&gt;, AslId &lt;BXPC,00000001&gt;
    31  [     1.000004] acpi0: X/RSDT: OemId &lt;BOCHS ,BXPCRSDT,00000001&gt;, AslId &lt;BXPC,00000001&gt;                                                     [76/526]
    32  [     1.000004] LNKS: ACPI: Found matching pin for 0.1.INTA at func 3: 9                                                                           
    33  [     1.000004] LNKC: ACPI: Found matching pin for 0.3.INTA at func 0: 11                                                                          
    34  [     1.000004] LNKD: ACPI: Found matching pin for 0.4.INTA at func 0: 11                                                                          
    35  [     1.000004] LNKA: ACPI: Found matching pin for 0.5.INTA at func 0: 10                                                                          
    36  [     1.000004] acpi0: SCI interrupting at int 9                                                                                                   
    37  [     1.000004] acpi0: fixed power button present                                                                                                  
    38  [     1.000004] timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000                                                             
    39  [     1.046041] hpet0 at acpi0: high precision event timer (mem 0xfed00000-0xfed00400)                                                             
    40  [     1.046041] timecounter: Timecounter "hpet0" frequency 100000000 Hz quality 2000                                                               
    41  [     1.046619] pckbc1 at acpi0 (KBD, PNP0303) (kbd port): io 0x60,0x64 irq 1                                                                      
    42  [     1.046619] pckbc2 at acpi0 (MOU, PNP0F13) (aux port): irq 12                                                                                  
    43  [     1.046619] fdc0 at acpi0 (FDC0, PNP0700): io 0x3f2-0x3f5,0x3f7 irq 6 drq 2                                                                    
    44  [     1.046619] lpt0 at acpi0 (LPT1, PNP0400-1): io 0x378-0x37f irq 7                                                                              
    45  [     1.046619] com0 at acpi0 (COM1, PNP0501-1): io 0x3f8-0x3ff irq 4                                                                              
    46  [     1.046619] com0: ns16550a, 16-byte FIFO                                                                                                       
    47  [     1.046619] com0: console                                                                                                                      
    48  [     1.046619] qemufwcfg0 at acpi0 (FWCF, QEMU0002): io 0x510-0x51b                                                                               
    49  [     1.046619] qemufwcfg0: &lt;QEMU&gt;                                                                                                                 
    50  [     1.046619] ACPI: Enabled 2 GPEs in block 00 to 0F                                                                                             
    51  [     1.046619] pckbd0 at pckbc1 (kbd slot)                                                                                                        
    52  [     1.046619] pckbc1: using irq 1 for kbd slot                                                                                                   
    53  [     1.046619] wskbd0 at pckbd0 mux 1                                                                                                             
    54  [     1.046619] pms0 at pckbc1 (aux slot)                                                                                                          
    55  [     1.046619] pckbc1: using irq 12 for aux slot                                                                                                  
    56  [     1.046619] wsmouse0 at pms0 mux 0                                                                                                             
    57  [     1.046619] pci0 at mainbus0 bus 0: configuration mode 1                                                                                       
    58  [     1.046619] pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok                                                                 
    59  [     1.046619] pchb0 at pci0 dev 0 function 0: Intel 82441FX (PMC) PCI and Memory Controller (rev. 0x02)                                          
    60  [     1.046619] pcib0 at pci0 dev 1 function 0: Intel 82371SB (PIIX3) PCI-ISA Bridge (rev. 0x00)                                                   
    61  [     1.046619] piixide0 at pci0 dev 1 function 1: Intel 82371SB IDE Interface (PIIX3) (rev. 0x00)                                                 
    62  [     1.046619] piixide0: bus-master DMA support present                                                                                           
    63  [     1.046619] piixide0: primary channel wired to compatibility mode                                                                              
    64  [     1.046619] piixide0: primary channel interrupting at ioapic0 pin 14                                                                           
    65  [     1.046619] atabus0 at piixide0 channel 0                                                                                                      
    66  [     1.046619] piixide0: secondary channel wired to compatibility mode                                                                            
    67  [     1.046619] piixide0: secondary channel interrupting at ioapic0 pin 15                                                                         
    68  [     1.046619] atabus1 at piixide0 channel 1 
    69  [     1.046619] piixpm0 at pci0 dev 1 function 3: Intel 82371AB (PIIX4) Power Management Controller (rev. 0x03)                            [38/526]
    70  [     1.046619] timecounter: Timecounter "piixpm0" frequency 3579545 Hz quality 1000                                                               
    71  [     1.046619] piixpm0: 24-bit timer                                                                                                              
    72  [     1.046619] piixpm0: interrupting at ioapic0 pin 9                                                                                             
    73  [     1.046619] iic0 at piixpm0 port 0: I2C bus                                                                                                    
    74  [     1.046619] vga0 at pci0 dev 2 function 0: vendor 1234 product 1111 (rev. 0x02)                                                                
    75  [     1.046619] wsdisplay0 at vga0 kbdmux 1                                                                                                        
    76  [     1.046619] wsmux1: connecting to wsdisplay0                                                                                                   
    77  [     1.046619] wskbd0: connecting to wsdisplay0                                                                                                   
    78  [     1.046619] drm at vga0 not configured                                                                                                         
    79  [     1.046619] wm0 at pci0 dev 3 function 0, 64-bit DMA: Intel i82540EM 1000BASE-T Ethernet (rev. 0x03)                                           
    80  [     1.046619] wm0: interrupting at ioapic0 pin 11                                                                                                
    81  [     1.046619] wm0: 32-bit 33MHz PCI bus                                                                                                          
    82  [     1.046619] wm0: 64 words (6 address bits) MicroWire EEPROM                                                                                    
    83  [     1.046619] wm0: Ethernet address 52:54:00:12:34:56                                                                                            
    84  [     1.046619] wm0: 0x200002&lt;LOCK_EECD,WOL&gt;                                                                                                       
    85  [     1.046619] makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev. 0                                                                          
    86  [     1.046619] makphy0: Failed to access EADR. Are you an emulator?                                                                               
    87  [     1.046619] makphy0: Failed to read EXTSR. Are you an emulator?. Regard as 1000BASE-T.                                                         
    88  [     1.046619] makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto                                            
    89  [     1.046619] virtio0 at pci0 dev 4 function 0                                                                                                   
    90  [     1.046619] virtio0: block device (id 2, rev. 0x00)                                                                                            
    91  [     1.046619] ld0 at virtio0: features: 0x10000a54&lt;INDIRECT_DESC,CONFIG_WCE,FLUSH,BLK_SIZE,GEOMETRY,SEG_MAX&gt;                                     
    92  [     1.046619] virtio0: allocated 1060864 byte for virtqueue 0 for I/O request, size 256                                                          
    93  [     1.046619] virtio0: using 1048576 byte (65536 entries) indirect descriptors                                                                   
    94  [     1.046619] virtio0: config interrupting at msix0 vec 0                                                                                        
    95  [     1.046619] virtio0: queues interrupting at msix0 vec 1                                                                                        
    96  [     1.046619] ld0: 1788 GB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 3750748848 sectors                                                      
    97  [     1.046619] virtio1 at pci0 dev 5 function 0                                                                                                   
    98  [     1.046619] virtio1: block device (id 2, rev. 0x00)                                                                                            
    99  [     1.046619] ld1 at virtio1: features: 0x10000a54&lt;INDIRECT_DESC,CONFIG_WCE,FLUSH,BLK_SIZE,GEOMETRY,SEG_MAX&gt;                                     
   100  [     1.046619] virtio1: allocated 1060864 byte for virtqueue 0 for I/O request, size 256                                                          
   101  [     1.046619] virtio1: using 1048576 byte (65536 entries) indirect descriptors                                                                   
   102  [     1.046619] virtio1: config interrupting at msix1 vec 0                                                                                        
   103  [     1.046619] virtio1: queues interrupting at msix1 vec 1                                                                                        
   104  [     1.046619] ld1: 1788 GB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 3750748848 sectors                                                      
   105  [     1.046619] isa0 at pcib0                                                                                                                      
   106  [     1.046619] attimer0 at isa0 port 0x40-0x43 
   107  [     1.046619] pcppi0 at isa0 port 0x61
   108  [     1.046619] spkr0 at pcppi0: PC Speaker
   109  [     1.046619] wsbell at spkr0 not configured
   110  [     1.046619] midi0 at pcppi0: PC speaker
   111  [     1.046619] sysbeep0 at pcppi0
   112  [     1.046619] attimer0: attached to pcppi0
   113  [     1.046619] acpicpu0 at cpu0: ACPI CPU
   114  [     1.046619] acpicpu0: C1: HLT, lat   0 us, pow     0 mW
   115  [     1.046619] vmt0 at cpu0
   116  [     1.046619] vmt0: UUID: 00000000-0000-0000-0000-000000000000
   117  [     1.046619] vmware: open failed, eax=0xffffffff, ecx=0x1e, edx=0x5658
   118  [     1.046619] vmt0: autoconfiguration error: failed to open backdoor RPC channel (TCLO protocol)
   119  [     1.046619] timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
   120  [     1.046619] fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
   121  [     1.046619] ld1: GPT GUID: 7ac59b06-d775-499c-b672-f71133e62986
   122  [     1.046619] ld0: GPT GUID: 868d363e-b930-4142-944f-e70905997bdb
   123  [     1.046619] IPsec: Initialized Security Association Processing.
   124  [     1.046619] dk0 at ld1: "be45d1a2-c15f-4fa9-a36b-db22ab2e15e0", 524288 blocks at 4096, type: msdos
   125  [     1.046619] dk1 at ld1: "c6fc5a64-7669-464c-8578-77c52a1ebe6c", 1048576 blocks at 528384, type: &lt;unknown&gt;
   126  [     1.046619] dk2 at ld1: "24fde94d-ca86-46bd-8358-93c1ac2f8b9e", 3749171855 blocks at 1576960, type: &lt;unknown&gt;
   127  [     1.046619] dk3 at ld0: "02a153e5-14e1-45f0-8e65-d55f5f7da62c", 3742359552 blocks at 2048, type: ffs
   128  [     1.046619] dk4 at ld0: "981d2b55-1018-4fc9-9f3c-5847d6751eb7", 8387215 blocks at 3742361600, type: swap
   129  [     5.005793] atapibus0 at atabus1: 2 targets
   130  [     5.015571] cd0 at atapibus0 drive 0: &lt;QEMU DVD-ROM, QM00003, 2.5+&gt; cdrom removable
   131  [     5.015571] cd0: 32-bit data port
   132  [     5.015571] cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
   133  [     5.015571] cd0(piixide0:1:0): using PIO mode 4, DMA mode 2 (using DMA)
   134  [     5.015571] swwdog0: software watchdog initialized
   135  [     5.025557] WARNING: 1 error while detecting hardware; check system log.
   136  [     5.025557] boot device: ld0
   137  [     5.025557] root on dk3 dumps on dk4
   138  [     5.025557] root file system type: ffs
   139  [     5.025557] kern.module.path=/stand/amd64/10.99.4/modules
   140  [    10.485560] wsdisplay0: screen 1 added (80x25, vt100 emulation)
   141  [    10.485560] wsdisplay0: screen 2 added (80x25, vt100 emulation)
   142  [    10.485560] wsdisplay0: screen 3 added (80x25, vt100 emulation)
   143  [    10.485560] wsdisplay0: screen 4 added (80x25, vt100 emulation)
fsn# 
</code></pre>
]]>
        </description>
    </item>
   </channel>
</rss>
