[BitVisor-devel-en:117] Re: Bitvisor Wireguard problems?

[Lonnie Cumberland]

Hello All,

I was able to replicate the "crashing" out of Bitvisor that was 
exhibited in the VMware Workstation 17 Pro by actually loading Bitvisor 
on the Intel NUC 7 without a hypervisor like VMware or QEMU.

I created a USB boot stick to boot up bitvisor.efi via the loadvmm.efi 
when I went into a UEFI shell. Once bitvisor was loaded then I started 
the Ubuntu 22.04 via the "efi\ubuntu\grub.efi" and the OS cam up as 
expected and started sending Keep-Alive packets to my Wireguard server 
node.  All was good up to this point. Then, I checked that I could ping 
a few places like Yahoo and some others with no problem.

The problem came as soon as I started up a web browser which seemed to 
open and go to an initial website but then everything just "froze up" 
and effectively crashed. I had to hard-boot the system at this stage, 
and was not able to get any logs or helpful information.

My guess is that it may have something to do with the way that bitvisor 
handles multiple CPU's but I am not sure.

I will try to get things working in QEMU and see if I can get some type 
of information to send over to the mailing list since this is a real 
problem that seems to crash out bitvisor in  the way that it handles the 
guest OS and maybe it can be fixed by more knowledgeable people.

Just wanted to report these findings and hope to hear from someone soon.

Thanks and have a great day,
Lonnie

On 6/12/2024 7:20 PM, Lonnie Cumberland wrote:
> Hello All,
>
> Hope that your day has gone well.  I wanted to report on the success 
> that I have now had with getting Wireguard working in Bitvisor running 
> on VMware Workstation 17 (on Windows 10 x64).
>
> I have had success and ultimately the catch was that I had to have the 
> ".wg.gateway" to the wireguard server WG IP as well as I had to ensure 
> that that the ".wg_gos.ipaddr" had to have an IP that was within the 
> 192.168.3.xxx subnet and that the WG server had Allowable ports of 
> 192.168.3.1/24" so that there was space for the guest OS IP to tunnel 
> through the bitvisor wireguard ".wg.ipaddr" space.
>
> I also found that although the VMware Workstation 17 Pro does work 
> "mostly" that it does crash out if it seems to be set for more than 1 
> vCPU although I will do more testing to verify the actual cause.
>
> With that in mind, I think that I am going to migrate the development 
> back over to QEMU on a Ubuntu 24.04 (x64) system and will probably 
> just have to figure out how to set up a network bridge to make it work.
>
> -------------------------------
>     .ip = {
>         .use_dhcp = 0,
>         .ipaddr = { 192, 168, 1, 5 },
>         .netmask = { 255, 255, 255, 0 },
>         .gateway = { 192, 168, 1, 254 },
>     },
>     .wg = {
>         .ipaddr = { 192, 168, 3, 2 },
>         .netmask = { 255, 255, 255, 0 },
>         .gateway = { 192, 168, 3, 1 },
>         .ipaddr_end_point = { 154, 53, 48, 214 },
>         .peer_allowed_ip = { 0, 0, 0, 0 },
>         .peer_allowed_mask = { 0, 0, 0, 0 },
>         .peer_endpoint_port = 51820,
>         .wg_listen_port = 0,
>         .wg_private_key = "<REDACTED>",
>         .peer_public_key = 
> "WhaBE3ruQgEgBvwK6+MWqmUjfeEwXHcS/2fQrEAlZRg=",
>     },
>     .wg_gos = {
>         .ipaddr = { 192, 168, 3, 3 },
>         .dns = { 8, 8, 8, 8 },
>         .mac_gateway = { 0x00, 0x0c, 0x29, 0x0E, 0x67, 0x56 },
>     },
> -------------------------------
>
> Thanks for all of the help and I am now starting to make more and more 
> progress forward but still have a lot of learning to do as well as 
> still have many questions along the way to making this project a reality.
>
> Have a great day,
> Lonnie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.bitvisor.org/archives/bitvisor-devel-en/attachments/20240613/aed0faca/attachment.htm>