Re: Struggle with bhyve and Kali.
That doesn't seem to help for kali. I found the binary, and I think it boots... but it goes from the 1080p that I select for it down to some 4x3 resolution that is tiny. Then I think X is up, but I don't get a login or any other response to input other than a mouse cursor. Really, this should be documented (the uefi boot variables thing). I suppose I'll keep messing with it --- maybe booting with the full resolution and the correct file will work --- which will likely require me to mount the efi partition on the host and mess around. On Sat, Dec 7, 2024 at 7:23 PM Bakul Shah wrote: > This may help: > > https://record99.blogspot.com/2021/12/bdsdex-failed-to-load-boot0001-uefi-bhyve-sata-disk.html > > > > On Dec 7, 2024, at 3:27 PM, Zaphod Beeblebrox wrote: > > > > So... I've installed kali a few times on bhyve. Lately on 14.1 that is > now 14.2 (no change there). The graphical install proceeds fine (using the > vm install command), and the first reboot (cd still attached) works fine. > > > > Subsequent reboots fail with this message: > > > > > > > > ... which since Kali linux does install on hardware, seems to be Bhyve's > problem. > > > > Help? > >
Re: Struggle with bhyve and Kali.
Is a bug filed to mark this yet? On Sat, Dec 7, 2024 at 8:27 PM Kyle Taylor wrote: > This happens to me when working with Debian on Bhyve (which Kali is based > on). Here's a description from the maintainer of the vm-bhyve port > explaining what's going on : > https://github.com/churchers/vm-bhyve/issues/336#issuecomment-573731049 . > > The fix is to rename the /boot entries so the Linux bootloader knows where > to look for them back to their standard naming convention for UEFI. Here's > an example : > https://blog.tkrn.io/freenas-11-boot-failed-efi-misc-device-fix-debian/ . > You can do this on the first boot. > > > On Sat, Dec 7, 2024, 4:27 PM Zaphod Beeblebrox wrote: > >> So... I've installed kali a few times on bhyve. Lately on 14.1 that is >> now 14.2 (no change there). The graphical install proceeds fine (using the >> vm install command), and the first reboot (cd still attached) works fine. >> >> Subsequent reboots fail with this message: >> >> [image: image.png] >> >> ... which since Kali linux does install on hardware, seems to be Bhyve's >> problem. >> >> Help? >> >
Re: Struggle with bhyve and Kali.
To check I did a graphical install of kali. After install, when bhyve exited, as root I did this (to let efiboot work in bhyve): mdconfig -a -t vnode -f kali.img # the filename I used for kali's disk mount -t msdosfs /dev/md0p1 /mnt cd /mnt/EFI mkdir BOOT cp kali/grubx64.efi BOOT/bootx64.efi cd umount /mnt I just use bhyve, not vm, so I manually started the VM after removing the .iso line. Choosing the default blanks the screen and shows just vnc's tiny cursor. So I killed it with bhyvectl --vm=kali --destroy and started it again. This time I chose the second option, that allows booting in "recovery mode" -- no X, just the console. Now I could login as the user I created & get a shell prompt. I don't use kali (or much linux) so I stopped. You're on your own at this point! May be you can ask on some kali related site > On Dec 7, 2024, at 8:37 PM, Zaphod Beeblebrox wrote: > > That doesn't seem to help for kali. I found the binary, and I think it > boots... but it goes from the 1080p that I select for it down to some 4x3 > resolution that is tiny. Then I think X is up, but I don't get a login or > any other response to input other than a mouse cursor. > > Really, this should be documented (the uefi boot variables thing). I suppose > I'll keep messing with it --- maybe booting with the full resolution and the > correct file will work --- which will likely require me to mount the efi > partition on the host and mess around. > > On Sat, Dec 7, 2024 at 7:23 PM Bakul Shah wrote: > This may help: > https://record99.blogspot.com/2021/12/bdsdex-failed-to-load-boot0001-uefi-bhyve-sata-disk.html > > > > On Dec 7, 2024, at 3:27 PM, Zaphod Beeblebrox wrote: > > > > So... I've installed kali a few times on bhyve. Lately on 14.1 that is now > > 14.2 (no change there). The graphical install proceeds fine (using the vm > > install command), and the first reboot (cd still attached) works fine. > > > > Subsequent reboots fail with this message: > > > > > > > > ... which since Kali linux does install on hardware, seems to be Bhyve's > > problem. > > > > Help? >
Re: Struggle with bhyve and Kali.
This may help: https://record99.blogspot.com/2021/12/bdsdex-failed-to-load-boot0001-uefi-bhyve-sata-disk.html > On Dec 7, 2024, at 3:27 PM, Zaphod Beeblebrox wrote: > > So... I've installed kali a few times on bhyve. Lately on 14.1 that is now > 14.2 (no change there). The graphical install proceeds fine (using the vm > install command), and the first reboot (cd still attached) works fine. > > Subsequent reboots fail with this message: > > > > ... which since Kali linux does install on hardware, seems to be Bhyve's > problem. > > Help?
Re: Struggle with bhyve and Kali.
This happens to me when working with Debian on Bhyve (which Kali is based on). Here's a description from the maintainer of the vm-bhyve port explaining what's going on : https://github.com/churchers/vm-bhyve/issues/336#issuecomment-573731049 . The fix is to rename the /boot entries so the Linux bootloader knows where to look for them back to their standard naming convention for UEFI. Here's an example : https://blog.tkrn.io/freenas-11-boot-failed-efi-misc-device-fix-debian/ . You can do this on the first boot. On Sat, Dec 7, 2024, 4:27 PM Zaphod Beeblebrox wrote: > So... I've installed kali a few times on bhyve. Lately on 14.1 that is > now 14.2 (no change there). The graphical install proceeds fine (using the > vm install command), and the first reboot (cd still attached) works fine. > > Subsequent reboots fail with this message: > > [image: image.png] > > ... which since Kali linux does install on hardware, seems to be Bhyve's > problem. > > Help? >
Re: Tap device problem on FreeBSD 14.2-RELEASE
On 12/7/2024 4:37 PM, Thomas Laus wrote: I used FreeBSD-update to go from 14.1-RELEASE to 14.2-RELEASE and there is an issue with creating and using the tap device. The device doesn't get created during the boot process and can't be created or used after the system is up. The UPDATING file has just one entry concerning the tap device and that is change the 'tap' name in all configuration files with 'tuntap'. I did that and get an invalid device reply. I installed the latest package for vm-bhyve which did not make any difference. I also deleted /usr/obj/* and checked out a fresh /usr/src and rebuilt FreeBSD-14.2-RELEASE from source without anything working differently. If anyone has a working tap device using FreeBSD 14.2-RELEASE, I would appreciate you sharing your bhyve portions of /etc/rc.conf, /etc/sysctl.conf and /boot/loader.conf files. I dont have anything unusual in my config. I am running just a few days ahead of 14.2, but I dont think that makes a difference kldstat Id Refs Address Size Name 1 47 0x8020 1f3d9c0 kernel 2 1 0x8213f000 5da658 zfs.ko 3 1 0x8271a000 36c8 coretemp.ko 4 2 0x8271e000 8dae8 pf.ko 5 1 0x827ac000 77d8 cryptodev.ko 6 1 0x827b4000 3c58 pflog.ko 7 1 0x83c2 3390 acpi_wmi.ko 8 1 0x83c24000 4250 ichsmb.ko 9 1 0x83c29000 2178 smbus.ko 10 1 0x83c2c000 7798 if_bridge.ko 11 1 0x83c34000 60e0 bridgestp.ko 12 1 0x83c3b000 33c0 uchcom.ko 13 1 0x83c3f000 4e10 ucom.ko 14 1 0x83e0 33e438 vmm.ko 15 1 0x83c44000 4850 nullfs.ko Starting up a vm works as before for me vmrun.sh -t tap0 -d /baseimage/14-1VM-p6.raw -E vm0 Launching virtual machine "vm0" ... fbuf frame buffer base: 0x2be256a0 [sz 16777216] 3h 3h 3h BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x3,0x0) BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x3,0x0) Consoles: EFI console Reading loader env vars from /efi/freebsd/loader.env Setting currdev to disk0p2: FreeBSD/amd64 EFI loader, Revision 1.1 Command line arguments: loader.efi Image base: 0x1e27a000 EFI version: 2.70 EFI Firmware: BHYVE (rev 1.00) Console: efi (0x20001000) Load Path: \EFI\BOOT\BOOTX64.EFI Load Device: PciRoot(0x0)/Pci(0x3,0x0)/HD(2,GPT,E140336F-1F4D-11EF-AE18-002590EC5BF2,0x17B,0x10418) BootCurrent: 0001 BootOrder: 0001[*] 0002 0003 0004 BootInfo Path: PciRoot(0x0)/Pci(0x3,0x0) Ignoring Boot0001: Only one DP found Trying ESP: PciRoot(0x0)/Pci(0x3,0x0)/HD(2,GPT,E140336F-1F4D-11EF-AE18-002590EC5BF2,0x17B,0x10418) Setting currdev to disk0p2: Trying: PciRoot(0x0)/Pci(0x3,0x0)/HD(1,GPT,E1403365-1F4D-11EF-AE18-002590EC5BF2,0x22,0x159) Setting currdev to disk0p1: Trying: PciRoot(0x0)/Pci(0x3,0x0)/HD(3,GPT,E1403374-1F4D-11EF-AE18-002590EC5BF2,0x10593,0x20) Setting currdev to disk0p3: Trying: PciRoot(0x0)/Pci(0x3,0x0)/HD(4,GPT,E1403378-1F4D-11EF-AE18-002590EC5BF2,0x210593,0x11FFF6D) Setting currdev to zfs:zroot/ROOT/default: - Loading /boot/defaults/loader.conf Loading /boot/defaults/loader.conf Loading /boot/device.hints Loading /boot/loader.conf Loading /boot/loader.conf.local ?c\ | __ _ _ | | | _ \ / | __ \ | |___ _ __ ___ ___ | |_) | (___ | | | | | ___| '__/ _ \/ _ \| _ < \___ \| | | | | | | | | __/ __/| |_) |) | |__| | | | | | | | || | | | . . . root@freebsd:~ # ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: icmp_seq=0 ttl=114 time=28.173 ms ^C --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 28.173/28.173/28.173/0.000 ms root@freebsd:~ # shutdown -p now Shutdown NOW! ... The bridge to tap0 works as expected. It gets auto created for me I can create new ones too # ifconfig tap1 create # ifconfig tap1 tap1: flags=8802 metric 0 mtu 1500 options=408 ether 58:9c:fc:10:63:02 groups: tap media: Ethernet 1000baseT status: no carrier nd6 options=29 On an actually 14.2R box, if I add to rc.conf cloned_interfaces="bridge0 tap0" it gets created at boot % ifconfig tap0 tap0: flags=8802 metric 0 mtu 1500 options=8 ether 58:9c:fc:10:ff:ed groups: tap media: Ethernet 1000baseT status: no carrier nd6 options=29
Re: Tap device problem on FreeBSD 14.2-RELEASE
$ uname -v FreeBSD 14.2-RELEASE releng/14.2-n269506-c8918d6c7412 GENERIC $ kldstat |grep 'if_.*tap' $ kldstat -v |grep 'if_.*tap' 388 if_tap 386 if_tuntap $ ifconfig tap5 ifconfig: interface tap5 does not exist $ ls -l /dev/tap5 ls: /dev/tap5: No such file or directory $ sudo ls -l /dev/tap5 crw--- 1 uucp dialer 0x89 Dec 7 14:40 /dev/tap5 $ ifconfig tap5 tap5: flags=8802 metric 0 mtu 1500 options=8 ether 58:9c:fc:10:ff:80 groups: tap media: Ethernet 1000baseT status: no carrier nd6 options=29 /dev/tap is created on access (if you have the permission to do so) and then ifconfig works. You may be able to trigger this by adding tap related lines to /etc/devfs.conf such as own tap0$user:$group# replace with user and group you want ... > On Dec 7, 2024, at 1:37 PM, Thomas Laus wrote: > > I used FreeBSD-update to go from 14.1-RELEASE to 14.2-RELEASE and there is an > issue with creating and using the tap device. The device doesn't get created > during the boot process and can't be created or used after the system is up. > The UPDATING file has just one entry concerning the tap device and that is > change the 'tap' name in all configuration files with 'tuntap'. I did that > and get an invalid device reply. I installed the latest package for vm-bhyve > which did not make any difference. I also deleted /usr/obj/* and checked out > a fresh /usr/src and rebuilt FreeBSD-14.2-RELEASE from source without > anything working differently. > > If anyone has a working tap device using FreeBSD 14.2-RELEASE, I would > appreciate you sharing your bhyve portions of /etc/rc.conf, /etc/sysctl.conf > and /boot/loader.conf files. > > Thanks > > Tom > > > -- > Public Keys: > PGP KeyID = 0x5F22FDC1 > GnuPG KeyID = 0x620836CF > >
Re: Tap device problem on FreeBSD 14.2-RELEASE
On Sat, Dec 07, 2024 at 04:37:31PM -0500, Thomas Laus wrote: > I used FreeBSD-update to go from 14.1-RELEASE to 14.2-RELEASE and there is > an issue with creating and using the tap device. The device doesn't get > created during the boot process and can't be created or used after the > system is up. The UPDATING file has just one entry concerning the tap > device and that is change the 'tap' name in all configuration files with > 'tuntap'. I did that and get an invalid device reply. I installed the > latest package for vm-bhyve which did not make any difference. I also > deleted /usr/obj/* and checked out a fresh /usr/src and rebuilt > FreeBSD-14.2-RELEASE from source without anything working differently. I guess you are misreading UPDATING (20190507?). "device tuntap" is included in GENERIC since 251a32b5b2bab (2019!). So this entry is not relevant for the 14.1-RELEASE to 14.2-RELEASE update. What files have you modified? > If anyone has a working tap device using FreeBSD 14.2-RELEASE, I would > appreciate you sharing your bhyve portions of /etc/rc.conf, /etc/sysctl.conf > and /boot/loader.conf files. You should be able to create tun/tap interfaces with "ifconfig tun0 create" or "ifconfig tap0 create". What error do you get?
Tap device problem on FreeBSD 14.2-RELEASE
I used FreeBSD-update to go from 14.1-RELEASE to 14.2-RELEASE and there is an issue with creating and using the tap device. The device doesn't get created during the boot process and can't be created or used after the system is up. The UPDATING file has just one entry concerning the tap device and that is change the 'tap' name in all configuration files with 'tuntap'. I did that and get an invalid device reply. I installed the latest package for vm-bhyve which did not make any difference. I also deleted /usr/obj/* and checked out a fresh /usr/src and rebuilt FreeBSD-14.2-RELEASE from source without anything working differently. If anyone has a working tap device using FreeBSD 14.2-RELEASE, I would appreciate you sharing your bhyve portions of /etc/rc.conf, /etc/sysctl.conf and /boot/loader.conf files. Thanks Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF
[Bug 279901] glibc-2.39-2 and above on the host segfault
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279901 --- Comment #20 from Getz Mikalsen --- Created attachment 255691 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255691&action=edit ld.so --list-diagnostics from glibc240 -- You are receiving this mail because: You are the assignee for the bug.
Struggle with bhyve and Kali.
So... I've installed kali a few times on bhyve. Lately on 14.1 that is now 14.2 (no change there). The graphical install proceeds fine (using the vm install command), and the first reboot (cd still attached) works fine. Subsequent reboots fail with this message: [image: image.png] ... which since Kali linux does install on hardware, seems to be Bhyve's problem. Help?
Re: Struggle with bhyve and Kali.
On Sat, Dec 7, 2024, at 3:27 PM, Zaphod Beeblebrox wrote: > So... I've installed kali a few times on bhyve. Lately on 14.1 that is now > 14.2 (no change there). The graphical install proceeds fine (using the vm > install command), and the first reboot (cd still attached) works fine. > > Subsequent reboots fail with this message: > > image.png > > ... which since Kali linux does install on hardware, seems to be Bhyve's > problem. > > Help? How are you invoking bhyve?
