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
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-bhy
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
u
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
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 bo
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 ha
$ 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 directo
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 u
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 devic
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 assig
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 si
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.
>
> Subseq
12 matches
Mail list logo
