[BitVisor-devel-en:130] Re: Sqlite3 testing in Bitvisor 3.0
Hideki EIRAKU
hdk at igel.co.jp
Wed Aug 20 18:55:28 JST 2025
Hi Lonnie,
> Looks like after some Windows 11 updates were applied then it was able
> to boot up under Bitvisor 3.0. Still would be nice to have any
> patches come out in the next version as well just in case it is run on
> other machines.
I am preparing a patch for Windows 11 guest. I found a bug in the
patch I previously sent to the bitvisor-users-en mailing list, but
Windows 11 should still boot with that. I tested on a machine with
Intel Core i5-12400F CPU.
> On the SQLite side, have you been able to use BV 3.0 to get SQLite
> working as I want to slowly test all of the features that are
> currently implemented in Bitvisor which are, from what I can see,
> mainly SQLite (from dgbsh.efi and from within Ubuntu but did not see
> any Windows build for it), as well as the encrypted filesystem. There
About the SQLite, the latest code with CONFIG_SQLITE=y worked and I
attached a screenshot running SQLite program on QEMU. Using storage
needs more setup but at least sqliteexample should work on dbgsh.
Best regards,
--
Hideki EIRAKU <hdk at igel.co.jp>
From: Lonnie Cumberland <lonnie at outstep.com>
Subject: Re: Sqlite3 testing in Bitvisor 3.0
Date: Tue, 19 Aug 2025 18:44:47 -0400
> Hi Dmitriy,
>
> Looks like after some Windows 11 updates were applied then it was able
> to boot up under Bitvisor 3.0. Still would be nice to have any
> patches come out in the next version as well just in case it is run on
> other machines.
>
> On the SQLite side, have you been able to use BV 3.0 to get SQLite
> working as I want to slowly test all of the features that are
> currently implemented in Bitvisor which are, from what I can see,
> mainly SQLite (from dgbsh.efi and from within Ubuntu but did not see
> any Windows build for it), as well as the encrypted filesystem. There
> are also a few other things like IDMan, that I do not know much about,
> but will look into it more as well as like the Wireguard
> implementation although still having a few problems connecting to
> other Wireguard nodes (i.e. Servers).
>
> Have you been able to work with SQLite and the examples with Bitvisor
> 3.0?
>
> Regarding the transparent disk encryption, I want to test what
> Bitvisor can already do, but have also come across a project called
> "TreVisor" (https://github.com/lakeman/trevisor) which uses the TRESOR
> Encryption
> (https://www.cs1.tf.fau.de/research/system-security-group/tresor-trevisor-armored/)
> to keep the keys out of RAM and seems to be based upon Bitvisor 1.3.
>
> Once I have been able to get a good feel for all of the basic Bitvisor
> 3.0 functionality, I was thinking to perhaps give it a try to port up
> the BitVisor-1.3 patch for TreVisor to hopefully work with the latest
> Bitvisor 3.0 since it looks like a bit of an enhancement in security
> based upon the TreVisor Security paper but I also want to keep the
> latest main Bitvisor features as well.
>
> Mostly exploring at the moment but I am really hoping to dive in
> heavily over the next few months to use it at the core for an
> interesting project that will explore running ultra-thin OS which will
> basically be under Bitvisor, but more on that later.
>
> Best and have a great evening,
> Lonnie
>
> On 8/19/2025 4:20 PM, A.S. wrote:
>> Hi Lonnie,
>>
>> It seems, the Windows 11 patch hasn't been applied into the latest
>> upstream repository yet.
>>
>> If you experience the same problem you should try applying it
>> yourself, hopefully there should be no difficulties with that.
>>
>> ==============
>> Best regards,
>> Dmitriy
>>
>> вт, 19 авг. 2025 г., 22:56 Lonnie Cumberland <lonnie at outstep.com>:
>>
>> Greetings All,
>>
>> Hope that everyone is doing well.
>>
>> I have been compiling the Bitvisor 3.0 from the Github Matsu
>> repository:
>>
>> https://github.com/matsu/bitvisor
>>
>> But still cannot get the SQLiteExample to work through the "dbgsh"
>> as it does not seem to find it no matter what I try. In my last
>> efforts, I even copied the sqliteexample.bin into the "EFI/Boot"
>> directory where the bitvisor.efi and loader are located but it
>> seems that the bin files are not something that is loaded at boot
>> time and I suspect that they would be compiled into bitvisor as a
>> single efi file.
>>
>> Also, I have been testing on my Nuc13 Ubuntu 22.04 (x64) machine
>> since I think that there is a problem booting up Windows 11 (x64)
>> from a recent mailing list message in which a fix was going to be
>> put into place, but I have not see any additional emails on this
>> and if this has bee added to the latest Bitvisor.
>>
>> Any updates on these would be greatly appreciated, my friends.
>>
>> Best,
>> Lonnie
>>
>>
>> On 8/16/2025 2:09 PM, Lonnie Cumberland wrote:
>>> Hello all
>>>
>>> I am testing Sqlite3 in Bitvisor 3.0 on a Ubuntu 22.04 (x64) system.
>>>
>>> In the "make config" setup, I do see the an option for "SQLite in
>>> Protection Domain" and do see some sqlite bin modules including
>>> sqliteexample.bin but am not clear as to if I need to put the bin
>>> files in the EFI directory with bitvisor.efi so that it can load
>>> the modules.
>>>
>>> After I boot bitvisor, I am able to start up "./dbgsh" to talk to
>>> bitvisor, but it does not seem to locate the sqliteexample when I
>>> try to start it.
>>>
>>> My reading has been in an English translation of the
>>>
>>> Trying out BitVisor's SQLite feature
>>> https://qiita.com/mmi/items/613bef0fdc6f41d3cb6b
>>>
>>> and
>>>
>>> Trying out BitVisor's SQLite feature (storage_io)
>>> https://qiita.com/hdk_2/items/ea981dc1da10499fe941
>>>
>>> in which the first one asks to have the configs in place for:
>>>
>>> STORAGESTORAGE_IOCRYPTOSTORAGE_PDSQLITE
>>>
>>> Also, based upon (below) the plugins are static and not able to
>>> be dynamically loaded but I would guess that the plugin modules
>>> still need to be placed in the EFI directory.
>>>
>>> Implementing plugin functionality in BitVisor
>>> https://qiita.com/RKX1209/items/f368ff237bee9efbb0be
>>>
>>> Can you please advise me on this as I am really trying to dig
>>> into bitvisor for this new version of the project that I wanted
>>> to complete.
>>>
>>> Thanks an have a great day, my friends.
>>> Lonnie
>>>
>>>
>>>
>>>
>>>
>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qemu.png
Type: image/png
Size: 30348 bytes
Desc: not available
URL: <http://www.bitvisor.org/archives/bitvisor-devel-en/attachments/20250820/acd2f4ce/attachment-0001.png>
More information about the BitVisor-devel-en
mailing list