<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://nofu.jp/wiki/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://nofu.jp/wiki/feed.php">
        <title>のふ処|NOFUDOKORO en:blog:2021</title>
        <description></description>
        <link>https://nofu.jp/wiki/</link>
        <image rdf:resource="https://nofu.jp/wiki/lib/tpl/bootstrap3/images/favicon.ico" />
       <dc:date>2026-05-04T22:21:16+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://nofu.jp/wiki/en/blog/2021/2021-01-07?rev=1610238957"/>
                <rdf:li rdf:resource="https://nofu.jp/wiki/en/blog/2021/2021-01-09?rev=1641441888"/>
                <rdf:li rdf:resource="https://nofu.jp/wiki/en/blog/2021/2021-01-16?rev=1638756357"/>
                <rdf:li rdf:resource="https://nofu.jp/wiki/en/blog/2021/2021-02-02?rev=1612243639"/>
                <rdf:li rdf:resource="https://nofu.jp/wiki/en/blog/2021/2021-02-10?rev=1638840430"/>
                <rdf:li rdf:resource="https://nofu.jp/wiki/en/blog/2021/2021-02-19?rev=1638755689"/>
                <rdf:li rdf:resource="https://nofu.jp/wiki/en/blog/2021/2021-05-02?rev=1622505279"/>
                <rdf:li rdf:resource="https://nofu.jp/wiki/en/blog/2021/2021-12-26?rev=1640579793"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://nofu.jp/wiki/lib/tpl/bootstrap3/images/favicon.ico">
        <title>のふ処|NOFUDOKORO</title>
        <link>https://nofu.jp/wiki/</link>
        <url>https://nofu.jp/wiki/lib/tpl/bootstrap3/images/favicon.ico</url>
    </image>
    <item rdf:about="https://nofu.jp/wiki/en/blog/2021/2021-01-07?rev=1610238957">
        <dc:format>text/html</dc:format>
        <dc:date>2021-01-10T09:35:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>boot1.efi has no longer been used in FreeBSD 12 as UEFI bootloader</title>
        <link>https://nofu.jp/wiki/en/blog/2021/2021-01-07?rev=1610238957</link>
        <description>boot1.efi has no longer been used in FreeBSD 12 as UEFI bootloader

It is perceived that boot sequence steps of FreeBSD (x64) in UEFI environment are as below. It is pedigreed process written on manpages.
manmancurrdevloaddev
The UEFI firmware gets BOOTX64.EFI up in EFI system partition. Next it runs the boot1.efi, then the loader.efi is lunched, and finally the kernel boots up.
Actually the process is supposed to move ahead as BOOTX64.EFI</description>
    </item>
    <item rdf:about="https://nofu.jp/wiki/en/blog/2021/2021-01-09?rev=1641441888">
        <dc:format>text/html</dc:format>
        <dc:date>2022-01-06T13:04:48+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>How to boot a FreeBSD system in any partitions with loader.efi</title>
        <link>https://nofu.jp/wiki/en/blog/2021/2021-01-09?rev=1641441888</link>
        <description>How to boot a FreeBSD system in any partitions with loader.efi

In about FreeBSD 12.0-RELEASE, loader.efi has been used as UEFI bootloader instead of prior boot.efi.

Both loaders can boot a FreeBSD system from ZFS or UFS file system.
The loader.efi only looks for the boot file system from the disk which the loader is loaded from, though the boot1.efi does it from its disk and also another disks.
Briefly speaking, current loader.efi can't boot the system from other disks.
Well, it can do it if w…</description>
    </item>
    <item rdf:about="https://nofu.jp/wiki/en/blog/2021/2021-01-16?rev=1638756357">
        <dc:format>text/html</dc:format>
        <dc:date>2021-12-06T11:05:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ConnectX-3 VF finally works in Windows guest on PVE!</title>
        <link>https://nofu.jp/wiki/en/blog/2021/2021-01-16?rev=1638756357</link>
        <description>ConnectX-3 VF finally works in Windows guest on PVE!


The SR-IOV is mine at last!

I finally succeed in working a virtual function of ConnectX-3 SR-IOV on a Windows 10 Pro. guest on Proxmox VE 6.3!

Getting the device manager to recognise the VF was a piece of cake, but I struggled with an</description>
    </item>
    <item rdf:about="https://nofu.jp/wiki/en/blog/2021/2021-02-02?rev=1612243639">
        <dc:format>text/html</dc:format>
        <dc:date>2021-02-02T14:27:19+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ConnectX-3 VFs are not working on pfSense 2.4.5 on PVE 6.3</title>
        <link>https://nofu.jp/wiki/en/blog/2021/2021-02-02?rev=1612243639</link>
        <description>ConnectX-3 VFs are not working on pfSense 2.4.5 on PVE 6.3

The project builds up stout router with SR-IOV is now starting up!

That being so I tried to create a pfSense 2.4.5-p1 VM on Proxmox VE 6.3-2 with ConnectX-3 VFs by PCI pass-through, but it didn't recognise them properly</description>
    </item>
    <item rdf:about="https://nofu.jp/wiki/en/blog/2021/2021-02-10?rev=1638840430">
        <dc:format>text/html</dc:format>
        <dc:date>2021-12-07T10:27:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ConnectX-3 VF not working on Windows comes from old in-box MLNX_OFED driver of PVE</title>
        <link>https://nofu.jp/wiki/en/blog/2021/2021-02-10?rev=1638840430</link>
        <description>ConnectX-3 VF not working on Windows comes from old in-box MLNX_OFED driver of PVE

It seems the matter ConnectX-3's SR-IOV doesn't work on Windows 10 VM on Proxmox VE 6.3 is a pretty old inbox mlx4 driver of PVE, to be exact, the driver is boxed in Linux.</description>
    </item>
    <item rdf:about="https://nofu.jp/wiki/en/blog/2021/2021-02-19?rev=1638755689">
        <dc:format>text/html</dc:format>
        <dc:date>2021-12-06T10:54:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Scrubing degraded ZFS pools can't be imported by another systems?</title>
        <link>https://nofu.jp/wiki/en/blog/2021/2021-02-19?rev=1638755689</link>
        <description>Scrubing degraded ZFS pools can't be imported by another systems?

It's a long story, I imported a RAIDZ pool which consisted of 4 HDDs and was created by FreeBSD to a ZoL environment as a degraded pool consisted of 3 HDDs.

Although scrub was automatically running, I cancelled it and exported it, then tried to import the entire 4 HDDs on the BSD system, but it couldn't.</description>
    </item>
    <item rdf:about="https://nofu.jp/wiki/en/blog/2021/2021-05-02?rev=1622505279">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-01T08:54:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>VirtIO RNG may cause high CPU utilization by rand_harvestq in FreeBSD 13 VM</title>
        <link>https://nofu.jp/wiki/en/blog/2021/2021-05-02?rev=1622505279</link>
        <description>VirtIO RNG may cause high CPU utilization by rand_harvestq in FreeBSD 13 VM

I found my home server suddenly got increased power consumption. Its difference was up to 30W, so it's not obviously error.

It was caused by powering up FreeBSD VM on ProxmoxVE, but I had no reasonable reasons. When I casually saw the PVE's CPU utilization graph, I found it increased considerably after upgrading to 13.0-RELEASE.</description>
    </item>
    <item rdf:about="https://nofu.jp/wiki/en/blog/2021/2021-12-26?rev=1640579793">
        <dc:format>text/html</dc:format>
        <dc:date>2021-12-27T13:36:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>1.5 Peta-Byte written PM9A3 doesn't work with PS5</title>
        <link>https://nofu.jp/wiki/en/blog/2021/2021-12-26?rev=1640579793</link>
        <description>1.5 Peta-Byte written PM9A3 doesn't work with PS5

I found that a Samsung's PCIe 4.0-gen SSD PM9A3 1.92TB (MZ1L21T9HCLS-00A07) was sold for just a little over 20000 JPY in a certain place. The SSD is read and written 1520465GB = 1.5PB, so it's a slightly fishy stuff, but the price is quite low as PCIe Gen4 2TB NVMe SSD. Its endurance is promoted as 1 DWPD which is equivalent to 3540 TBW for enterprise. This means its lifetime still remains more than half according to the</description>
    </item>
</rdf:RDF>
