[Bug 288488] sysutils/bhyve-firmware: Chimera Linux bhyve VM crashes only with uefi loader
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 27 Jul 2025 10:55:20 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288488
Bug ID: 288488
Summary: sysutils/bhyve-firmware: Chimera Linux bhyve VM
crashes only with uefi loader
Product: Ports & Packages
Version: Latest
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs@FreeBSD.org
Reporter: polyduekes@proton.me
CC: fabian.freyer@physik.tu-berlin.de
CC: fabian.freyer@physik.tu-berlin.de
Flags: maintainer-feedback?(fabian.freyer@physik.tu-berlin.de
)
a Chimera Linux VM created using the image
https://repo.chimera-linux.org/live/latest/chimera-linux-x86_64-LIVE-20250420-base.iso
crashes only with uefi loader but works fine on bare metal, with bhyve with
grub loader, with vbox
System info:-
CPU: Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz (3191.27-MHz K8-class CPU)
Origin="GenuineIntel" Id=0x20652 Family=0x6 Model=0x25 Stepping=2
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0x298e3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AESNI>
AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
AMD Features2=0x1<LAHF>
VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
FreeBSD version:-14.3-RELEASE
bhyve example config:-
[bhyve options: -c 2 -m 4096M -AHPw -l
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/Pool/vm-bhyve/chimera/uefi-vars.fd
-U 47ba7a95-6ace-11f0-9515-00e04f0a8040 -u]
[bhyve devices: -s 0,hostbridge -s 31,lpc -s
4:0,nvme,/Pool/vm-bhyve/chimera/disk0.img -s
5:0,virtio-net,tap0,mac=58:9c:fc:00:22:ec -s 6:0,fbuf,tcp=0.0.0.0:5900,wait -s
7:0,xhci,tablet]
[bhyve console: -l com1,/dev/nmdm-chimera.1A]
[bhyve iso device: -s
3:0,ahci-cd,/media/SanDisk_Ultra_4C531001580322108071_s1/chimera-linux-x86_64-LIVE-20250420-base.iso,ro]
bhyve crash log: vm exit[0]
reason VMX
rip 0x00000000be79369e
inst_length 3
status 0
exit_reason 33 (VM-entry failure due to invalid guest state)
qualification 0x0000000000000000
inst_type 0
inst_error 0
--
You are receiving this mail because:
You are the assignee for the bug.