Solved Using bhyve to run Kali

Maxnix said:
I've seen this a lot of times when booting Linux systems, and was always harmless.
That said, if you didn't already enable debug output in the VM config file adding debug=yes.

Then post the output of vm-bhyve.log and of bhyve.log (they are both in the VM directory).
Click to expand...
I will collect those logs, but I disagree about this being harmless. It does not boot! That is the only message I get when I attempt to boot. Next post I will include my configuration file.....
 
Ok, wiped the slate clean; destroyed the previous VM and created a new one. The problem remains, it will do the install, try to reboot and then hang with that one line in the VNC window -- No irq handler for 1.55

Here is the configuration file:
Code: 
loader="uefi"
uefi_var="yes"
debug="yes"

cpu="2"
memory="4G"
network0_type="virtio-net"
network0_switch="public"
disk0_type="virtio-blk"
disk0_name="kali.img"

graphics="yes"
# graphics_listen="0.0.0.0"
graphics_port="5901"
graphics_res="1280x1024"
xhci_mouse="yes"

# network0_mac=""
uuid="4eb0c805-92a8-11f1-bbd8-04d4c43907d1"
network0_mac="58:9c:fc:09:37:42"

The bhyve.log file:
Code: 
wrmsr to register 0x140(0) on vcpu 0
wrmsr to register 0x140(0) on vcpu 1
rdmsr to register 0x64e on vcpu 0
rdmsr to register 0x34 on vcpu 0
rdmsr to register 0xc0011029 on vcpu 0
Unhandled ps2 mouse command 0xe1
Unhandled ps2 mouse command 0x88
rdmsr to register 0x64d on vcpu 0
rdmsr to register 0x64d on vcpu 0

And finally the vm-bhyve.log file:
Code: 
2026-08-07T15:38:19-06:00: generated static mac 58:9c:fc:09:37:42
2026-08-07T15:39:57-06:00: initialising
2026-08-07T15:39:57-06:00:  [loader: uefi]
2026-08-07T15:39:57-06:00:  [cpu: 2]
2026-08-07T15:39:57-06:00:  [memory: 4G]
2026-08-07T15:39:57-06:00:  [hostbridge: standard]
2026-08-07T15:39:57-06:00:  [com ports: com1]
2026-08-07T15:39:57-06:00:  [uuid: 4eb0c805-92a8-11f1-bbd8-04d4c43907d1]
2026-08-07T15:39:57-06:00:  [debug mode: yes]
2026-08-07T15:39:57-06:00:  [primary disk: kali.img]
2026-08-07T15:39:57-06:00:  [primary disk dev: file]
2026-08-07T15:39:57-06:00: initialising network device tap1
2026-08-07T15:39:57-06:00: adding tap1 -> vm-public (public addm)
2026-08-07T15:39:57-06:00: bring up tap1 -> vm-public (public addm)
2026-08-07T15:39:57-06:00: booting
2026-08-07T15:39:57-06:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U 4eb0c805-92a8-11f1-bbd8-04d4c43907d1 -u]
2026-08-07T15:39:57-06:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/mnt/vm/kalivm/kali.img -s 0:5:0,virtio-net,tap1,mac=58:9c:fc:09:37:42 -s 0:6:0,fbuf,tcp=0.0.0.0:5901,w=1280,h=1024,wait -s 0:7:0,xhci,tablet]
2026-08-07T15:39:57-06:00:  [bhyve console: -l com1,/dev/nmdm-kalivm.1A]
2026-08-07T15:39:57-06:00:  [bhyve iso device: -s 3:0,ahci-cd,/mnt/vm/.iso/kali-linux-2026.2-installer-amd64.iso,ro,bootindex=1]
2026-08-07T15:39:57-06:00: starting bhyve (run 1)
2026-08-07T15:55:12-06:00: bhyve exited with status 0
2026-08-07T15:55:12-06:00: restarting
2026-08-07T15:55:12-06:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U 4eb0c805-92a8-11f1-bbd8-04d4c43907d1 -u]
2026-08-07T15:55:12-06:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/mnt/vm/kalivm/kali.img -s 0:5:0,virtio-net,tap1,mac=58:9c:fc:09:37:42 -s 0:6:0,fbuf,tcp=0.0.0.0:5901,w=1280,h=1024 -s 0:7:0,xhci,tablet]
2026-08-07T15:55:12-06:00:  [bhyve console: -l com1,/dev/nmdm-kalivm.1A]
2026-08-07T15:55:12-06:00:  [bhyve iso device: -s 3:0,ahci-cd,/mnt/vm/.iso/kali-linux-2026.2-installer-amd64.iso,ro,bootindex=1]
2026-08-07T15:55:12-06:00: starting bhyve (run 2)

The log files looked clean to me - nothing obvious anyway.
 
I think this is the issue with Debian based systems in UEFI boot mode. Here is the solution: start rescue system with the disc attached, or mount the EFI partition of your image on your host. Then
mkdir /target/boot/efi/EFI/BOOT/ && cp /target/boot/efi/EFI/kali/grubx64.efi /target/boot/efi/EFI/BOOT/bootx64.efi
hopefully does the trick
 
This is not needed. When installing kali from an iso (as I showed earlier), an EFI partition is created and populated. dr_grid's problem likely has to do with some vm-bhyve setting.
 
I think what I will do next is create the VM and install it without the vm-bhyve tools. I know that works -- did it yesterday. If I can then start the VM with the vm-bhyve tools, rather than type in the bhyve command, that will be a win for me. I am curious as to why the "all vm-bhyve tools" approach is not working -- but that's the fun of computers! Thanks all, I will report how it works out in case it may be helpful to someone else.
 
Ok, I think I probably found the culprit.
Since in your vm-bhyve.log there is no trace that UEFI variables are used I re-read your VM config file and noticed a typo: you used uefi_var instead of uefi_vars.
 
Maxnix said:
Ok, I think I probably found the culprit.
Since in your vm-bhyve.log there is no trace that UEFI variables are used I re-read your VM config file and noticed a typo: you used uefi_var instead of uefi_vars.
Click to expand...
That was a great catch Maxnix, and thanks for proofreading my config file. I gave it all another try today, wiped everything out and started fresh. Using uefi_vars did make a difference, with the uefi-vars.fd file appearing in the VM home directory now. I still have no luck when the installation reboots - everything hangs as before. The vm-bhyve.log confirms that it has restarted bhyve.

I noticed during installation the installer mentions it does install grub. So I thought to restart the VM with the console running vm console -w kalivm and here is what I got:
Code: 
BdsDxe: loading Boot0003 "kali" from HD(1,GPT,E9107797-DF01-4F28-829B-71FA92E2608D,0x800,0x1E8000)/\EFI\kali\grubx64.efi
BdsDxe: starting Boot0003 "kali" from HD(1,GPT,E9107797-DF01-4F28-829B-71FA92E2608D,0x800,0x1E8000)/\EFI\kali\grubx64.efi

I find the reference to grubx64.efi suspicious and wonder if this may be the problem, or at least a clue. With the console still running and the boot still hung, I ran vm list and got this:
Code: 
root@dagobah:/mnt/vm/kalivm # vm list
NAME    DATASTORE  LOADER  CPU  MEMORY  VNC           AUTO  STATE
kalivm  default    uefi    2    4G      0.0.0.0:5901  No    Running (39997)
All of that looks correct, but I do notice the loader is specified as uefi.

It just feels like the wrong loader is being used, but I don't know. I will do a bit more research and see if I can figure this out.

Again thanks for the pointer.
 
dr_grid said:
I still have no luck when the installation reboots - everything hangs as before.
Click to expand...
Strange, I tried installing Kali with kali-linux-2026.2-installer-amd64.iso and it installed and booted fine (I got the No irq handler for 1.55 too, but was irrelevant):
Schermata_20260808_111620.png
Schermata_20260808_111654.png
Schermata_20260808_111805.png

My config file:
Code: 
cpu=2
disk0_name="disk0.img"
disk0_type="virtio-blk"
graphics="YES"
graphics_listen="127.0.0.1"
graphics_port="5900"
graphics_res="1280x800"
graphics_wait="YES"
loader="uefi"
memory=4G
network0_switch="public"
network0_type="virtio-net"
uefi_vars="YES"
xhci_mouse="YES"
uuid="21232251-9302-11f1-8c12-98fa9bd4e8d6"
network0_mac="58:9c:fc:05:6d:91"
My whole vm-bhyve.log (since installation):
Code: 
2026-08-08T10:21:18+02:00: generated static mac 58:9c:fc:05:6d:91
2026-08-08T10:37:34+02:00: initialising
2026-08-08T10:37:34+02:00:  [loader: uefi]
2026-08-08T10:37:34+02:00:  [cpu: 2]
2026-08-08T10:37:34+02:00:  [memory: 4G]
2026-08-08T10:37:34+02:00:  [hostbridge: standard]
2026-08-08T10:37:34+02:00:  [com ports: com1]
2026-08-08T10:37:34+02:00:  [uuid: 21232251-9302-11f1-8c12-98fa9bd4e8d6]
2026-08-08T10:37:34+02:00:  [debug mode: no]
2026-08-08T10:37:34+02:00:  [primary disk: disk0.img]
2026-08-08T10:37:34+02:00:  [primary disk dev: file]
2026-08-08T10:37:34+02:00: initialising network device tap0
2026-08-08T10:37:34+02:00: adding tap0 -> vm-public (public addm)
2026-08-08T10:37:34+02:00: bring up tap0 -> vm-public (public addm)
2026-08-08T10:37:34+02:00: booting
2026-08-08T10:37:34+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-08T10:37:34+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-08T10:37:34+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-08T10:37:34+02:00:  [bhyve iso device: -s 3:0,ahci-cd,/home/max/Scaricati/kali-linux-2026.2-installer-amd64.iso,ro,bootindex=1]
2026-08-08T10:37:34+02:00: starting bhyve (run 1)
2026-08-08T10:54:22+02:00: bhyve exited with status 0
2026-08-08T10:54:22+02:00: restarting
2026-08-08T10:54:22+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-08T10:54:22+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-08T10:54:22+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-08T10:54:22+02:00:  [bhyve iso device: -s 3:0,ahci-cd,/home/max/Scaricati/kali-linux-2026.2-installer-amd64.iso,ro,bootindex=1]
2026-08-08T10:54:22+02:00: starting bhyve (run 2)
2026-08-08T11:08:11+02:00: bhyve exited with status 1
2026-08-08T11:08:11+02:00: destroying network device tap0
2026-08-08T11:08:11+02:00: stopped
2026-08-08T11:15:46+02:00: initialising
2026-08-08T11:15:46+02:00:  [loader: uefi]
2026-08-08T11:15:46+02:00:  [cpu: 2]
2026-08-08T11:15:46+02:00:  [memory: 4G]
2026-08-08T11:15:46+02:00:  [hostbridge: standard]
2026-08-08T11:15:46+02:00:  [com ports: com1]
2026-08-08T11:15:46+02:00:  [uuid: 21232251-9302-11f1-8c12-98fa9bd4e8d6]
2026-08-08T11:15:46+02:00:  [debug mode: no]
2026-08-08T11:15:46+02:00:  [primary disk: disk0.img]
2026-08-08T11:15:46+02:00:  [primary disk dev: file]
2026-08-08T11:15:46+02:00: initialising network device tap0
2026-08-08T11:15:46+02:00: adding tap0 -> vm-public (public addm)
2026-08-08T11:15:46+02:00: bring up tap0 -> vm-public (public addm)
2026-08-08T11:15:46+02:00: booting
2026-08-08T11:15:46+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-08T11:15:46+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-08T11:15:46+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-08T11:15:46+02:00: starting bhyve (run 1)
2026-08-08T11:18:41+02:00: bhyve exited with status 1
2026-08-08T11:18:41+02:00: destroying network device tap0
2026-08-08T11:18:41+02:00: stopped
2026-08-10T02:43:25+02:00: initialising
2026-08-10T02:43:25+02:00:  [loader: uefi]
2026-08-10T02:43:25+02:00:  [cpu: 2]
2026-08-10T02:43:25+02:00:  [memory: 4G]
2026-08-10T02:43:25+02:00:  [hostbridge: standard]
2026-08-10T02:43:25+02:00:  [com ports: com1]
2026-08-10T02:43:25+02:00:  [uuid: 21232251-9302-11f1-8c12-98fa9bd4e8d6]
2026-08-10T02:43:25+02:00:  [debug mode: no]
2026-08-10T02:43:25+02:00:  [primary disk: disk0.img]
2026-08-10T02:43:25+02:00:  [primary disk dev: file]
2026-08-10T02:43:25+02:00: initialising network device tap0
2026-08-10T02:43:25+02:00: adding tap0 -> vm-public (public addm)
2026-08-10T02:43:25+02:00: bring up tap0 -> vm-public (public addm)
2026-08-10T02:43:25+02:00: booting
2026-08-10T02:43:25+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-10T02:43:25+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=1024,wait -s 0:7:0,xhci,tablet]
2026-08-10T02:43:25+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-10T02:43:25+02:00: starting bhyve (run 1)
2026-08-10T02:43:53+02:00: bhyve exited with status 1
2026-08-10T02:43:53+02:00: destroying network device tap0
2026-08-10T02:43:53+02:00: stopped
2026-08-10T09:14:58+02:00: initialising
2026-08-10T09:14:58+02:00:  [loader: uefi]
2026-08-10T09:14:58+02:00:  [cpu: 2]
2026-08-10T09:14:58+02:00:  [memory: 4G]
2026-08-10T09:14:58+02:00:  [hostbridge: standard]
2026-08-10T09:14:58+02:00:  [com ports: com1]
2026-08-10T09:14:58+02:00:  [uuid: 21232251-9302-11f1-8c12-98fa9bd4e8d6]
2026-08-10T09:14:58+02:00:  [debug mode: no]
2026-08-10T09:14:58+02:00:  [primary disk: disk0.img]
2026-08-10T09:14:58+02:00:  [primary disk dev: file]
2026-08-10T09:14:58+02:00: initialising network device tap0
2026-08-10T09:14:58+02:00: adding tap0 -> vm-public (public addm)
2026-08-10T09:14:58+02:00: bring up tap0 -> vm-public (public addm)
2026-08-10T09:14:58+02:00: booting
2026-08-10T09:14:58+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-10T09:14:58+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-10T09:14:58+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-10T09:14:58+02:00: starting bhyve (run 1)
2026-08-10T09:15:09+02:00: bhyve exited with status 0
2026-08-10T09:15:09+02:00: restarting
2026-08-10T09:15:09+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-10T09:15:09+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-10T09:15:09+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-10T09:15:09+02:00: starting bhyve (run 2)
2026-08-10T09:15:19+02:00: bhyve exited with status 0
2026-08-10T09:15:19+02:00: restarting
2026-08-10T09:15:19+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-10T09:15:19+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-10T09:15:19+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-10T09:15:19+02:00: starting bhyve (run 3)
2026-08-10T09:15:36+02:00: bhyve exited with status 0
2026-08-10T09:15:36+02:00: restarting
2026-08-10T09:15:36+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-10T09:15:36+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-10T09:15:36+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-10T09:15:36+02:00: starting bhyve (run 4)
2026-08-10T09:17:01+02:00: bhyve exited with status 1
2026-08-10T09:17:01+02:00: destroying network device tap0
2026-08-10T09:17:01+02:00: stopped
dr_grid said:
I find the reference to grubx64.efi suspicious and wonder if this may be the problem, or at least a clue.
Click to expand...
Nope, it's just the EFI loader; it's the same for my installation.
dr_grid said:
All of that looks correct, but I do notice the loader is specified as uefi.
Click to expand...
The UEFI loader is the only option to have graphics under bhyve, so it's ok.

At this point my guess is that the VM boots, but there is a job taking too much time to complete; edit the default boot entry (press e at the GRUB menu), and remove both quiet and splash from the kernel arguments, so you can see where it gets stuck.
 
Maxnix said:
Strange, I tried installing Kali with kali-linux-2026.2-installer-amd64.iso and it installed and booted fine (I got the No irq handler for 1.55 too, but was irrelevant):
View attachment 26947View attachment 26948View attachment 26949
My config file:
Code: 
cpu=2
disk0_name="disk0.img"
disk0_type="virtio-blk"
graphics="YES"
graphics_listen="127.0.0.1"
graphics_port="5900"
graphics_res="1280x800"
graphics_wait="YES"
loader="uefi"
memory=4G
network0_switch="public"
network0_type="virtio-net"
uefi_vars="YES"
xhci_mouse="YES"
uuid="21232251-9302-11f1-8c12-98fa9bd4e8d6"
network0_mac="58:9c:fc:05:6d:91"
My whole vm-bhyve.log (since installation):
Code: 
2026-08-08T10:21:18+02:00: generated static mac 58:9c:fc:05:6d:91
2026-08-08T10:37:34+02:00: initialising
2026-08-08T10:37:34+02:00:  [loader: uefi]
2026-08-08T10:37:34+02:00:  [cpu: 2]
2026-08-08T10:37:34+02:00:  [memory: 4G]
2026-08-08T10:37:34+02:00:  [hostbridge: standard]
2026-08-08T10:37:34+02:00:  [com ports: com1]
2026-08-08T10:37:34+02:00:  [uuid: 21232251-9302-11f1-8c12-98fa9bd4e8d6]
2026-08-08T10:37:34+02:00:  [debug mode: no]
2026-08-08T10:37:34+02:00:  [primary disk: disk0.img]
2026-08-08T10:37:34+02:00:  [primary disk dev: file]
2026-08-08T10:37:34+02:00: initialising network device tap0
2026-08-08T10:37:34+02:00: adding tap0 -> vm-public (public addm)
2026-08-08T10:37:34+02:00: bring up tap0 -> vm-public (public addm)
2026-08-08T10:37:34+02:00: booting
2026-08-08T10:37:34+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-08T10:37:34+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-08T10:37:34+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-08T10:37:34+02:00:  [bhyve iso device: -s 3:0,ahci-cd,/home/max/Scaricati/kali-linux-2026.2-installer-amd64.iso,ro,bootindex=1]
2026-08-08T10:37:34+02:00: starting bhyve (run 1)
2026-08-08T10:54:22+02:00: bhyve exited with status 0
2026-08-08T10:54:22+02:00: restarting
2026-08-08T10:54:22+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-08T10:54:22+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-08T10:54:22+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-08T10:54:22+02:00:  [bhyve iso device: -s 3:0,ahci-cd,/home/max/Scaricati/kali-linux-2026.2-installer-amd64.iso,ro,bootindex=1]
2026-08-08T10:54:22+02:00: starting bhyve (run 2)
2026-08-08T11:08:11+02:00: bhyve exited with status 1
2026-08-08T11:08:11+02:00: destroying network device tap0
2026-08-08T11:08:11+02:00: stopped
2026-08-08T11:15:46+02:00: initialising
2026-08-08T11:15:46+02:00:  [loader: uefi]
2026-08-08T11:15:46+02:00:  [cpu: 2]
2026-08-08T11:15:46+02:00:  [memory: 4G]
2026-08-08T11:15:46+02:00:  [hostbridge: standard]
2026-08-08T11:15:46+02:00:  [com ports: com1]
2026-08-08T11:15:46+02:00:  [uuid: 21232251-9302-11f1-8c12-98fa9bd4e8d6]
2026-08-08T11:15:46+02:00:  [debug mode: no]
2026-08-08T11:15:46+02:00:  [primary disk: disk0.img]
2026-08-08T11:15:46+02:00:  [primary disk dev: file]
2026-08-08T11:15:46+02:00: initialising network device tap0
2026-08-08T11:15:46+02:00: adding tap0 -> vm-public (public addm)
2026-08-08T11:15:46+02:00: bring up tap0 -> vm-public (public addm)
2026-08-08T11:15:46+02:00: booting
2026-08-08T11:15:46+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-08T11:15:46+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-08T11:15:46+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-08T11:15:46+02:00: starting bhyve (run 1)
2026-08-08T11:18:41+02:00: bhyve exited with status 1
2026-08-08T11:18:41+02:00: destroying network device tap0
2026-08-08T11:18:41+02:00: stopped
2026-08-10T02:43:25+02:00: initialising
2026-08-10T02:43:25+02:00:  [loader: uefi]
2026-08-10T02:43:25+02:00:  [cpu: 2]
2026-08-10T02:43:25+02:00:  [memory: 4G]
2026-08-10T02:43:25+02:00:  [hostbridge: standard]
2026-08-10T02:43:25+02:00:  [com ports: com1]
2026-08-10T02:43:25+02:00:  [uuid: 21232251-9302-11f1-8c12-98fa9bd4e8d6]
2026-08-10T02:43:25+02:00:  [debug mode: no]
2026-08-10T02:43:25+02:00:  [primary disk: disk0.img]
2026-08-10T02:43:25+02:00:  [primary disk dev: file]
2026-08-10T02:43:25+02:00: initialising network device tap0
2026-08-10T02:43:25+02:00: adding tap0 -> vm-public (public addm)
2026-08-10T02:43:25+02:00: bring up tap0 -> vm-public (public addm)
2026-08-10T02:43:25+02:00: booting
2026-08-10T02:43:25+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-10T02:43:25+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=1024,wait -s 0:7:0,xhci,tablet]
2026-08-10T02:43:25+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-10T02:43:25+02:00: starting bhyve (run 1)
2026-08-10T02:43:53+02:00: bhyve exited with status 1
2026-08-10T02:43:53+02:00: destroying network device tap0
2026-08-10T02:43:53+02:00: stopped
2026-08-10T09:14:58+02:00: initialising
2026-08-10T09:14:58+02:00:  [loader: uefi]
2026-08-10T09:14:58+02:00:  [cpu: 2]
2026-08-10T09:14:58+02:00:  [memory: 4G]
2026-08-10T09:14:58+02:00:  [hostbridge: standard]
2026-08-10T09:14:58+02:00:  [com ports: com1]
2026-08-10T09:14:58+02:00:  [uuid: 21232251-9302-11f1-8c12-98fa9bd4e8d6]
2026-08-10T09:14:58+02:00:  [debug mode: no]
2026-08-10T09:14:58+02:00:  [primary disk: disk0.img]
2026-08-10T09:14:58+02:00:  [primary disk dev: file]
2026-08-10T09:14:58+02:00: initialising network device tap0
2026-08-10T09:14:58+02:00: adding tap0 -> vm-public (public addm)
2026-08-10T09:14:58+02:00: bring up tap0 -> vm-public (public addm)
2026-08-10T09:14:58+02:00: booting
2026-08-10T09:14:58+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-10T09:14:58+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-10T09:14:58+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-10T09:14:58+02:00: starting bhyve (run 1)
2026-08-10T09:15:09+02:00: bhyve exited with status 0
2026-08-10T09:15:09+02:00: restarting
2026-08-10T09:15:09+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-10T09:15:09+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-10T09:15:09+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-10T09:15:09+02:00: starting bhyve (run 2)
2026-08-10T09:15:19+02:00: bhyve exited with status 0
2026-08-10T09:15:19+02:00: restarting
2026-08-10T09:15:19+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-10T09:15:19+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-10T09:15:19+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-10T09:15:19+02:00: starting bhyve (run 3)
2026-08-10T09:15:36+02:00: bhyve exited with status 0
2026-08-10T09:15:36+02:00: restarting
2026-08-10T09:15:36+02:00:  [bhyve options: -c 2 -m 4G -AHPw -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/srv/bhyve/default/Kali/uefi-vars.fd -U 21232251-9302-11f1-8c12-98fa9bd4e8d6 -u]
2026-08-10T09:15:36+02:00:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 0:4:0,virtio-blk,/srv/bhyve/default/Kali/disk0.img -s 0:5:0,virtio-net,tap0,mac=58:9c:fc:05:6d:91 -s 0:6:0,fbuf,tcp=127.0.0.1:5900,w=1280,h=800,wait -s 0:7:0,xhci,tablet]
2026-08-10T09:15:36+02:00:  [bhyve console: -l com1,/dev/nmdm-Kali.1A]
2026-08-10T09:15:36+02:00: starting bhyve (run 4)
2026-08-10T09:17:01+02:00: bhyve exited with status 1
2026-08-10T09:17:01+02:00: destroying network device tap0
2026-08-10T09:17:01+02:00: stopped

Nope, it's just the EFI loader; it's the same for my installation.

The UEFI loader is the only option to have graphics under bhyve, so it's ok.

At this point my guess is that the VM boots, but there is a job taking too much time to complete; edit the default boot entry (press e at the GRUB menu), and remove both quiet and splash from the kernel arguments, so you can see where it gets stuck.
Click to expand...

Thanks for the post Maxnix, I will give this a study today. It is helpful.

I did finally get it up and running yesterday, after six hours with Google Gemini. I left it running overnight, and this morning the VNC connection to the MacOS was dropped. The vm start -f kalivm still has a connection to the VM, so I still have things to sort out. I plan to post a follow up today in a different thread talking about the six hour session yesterday and some of the problems that came up during the installation. It should not have been that difficult, but I am a lucky fellow.
 
You must log in or register to reply here.
Back
Top